Hi list,
speaking about software raid, not hardware controller based.
I am trying to go for some local OpenSuse machine and adding some
storage to it. Was considering Raid6, and now reading about a bit and
people left and right scaremongering about the larger the disks these
days in the double digit terabyte capacities even, the more likely it
is that during a reconstruction of a raid subsequent errors would
occur.
I would absolutely like to keep my data consistent, and I am not
thinking about double digit terabytes either, would stick to 2TB or
4TB disks, with Raid6 thats at least 4 physical drives.
Now I am wondering if it possible to use a good robust file system
that can add some more parity or check blocks or redundancy on top of
the hardware disks, to absolutely be able to always read my data.
I can't add multiple machines or like those high availability stuff
like clusters and what not I read about DRBD (Distributed Replicated
Block Device), or maybe I am just too scared by those technical terms
or consider myself to be just a simpleton and wanting to keep it
rather simple.
My use case here is also not constant availablity, when a disk needs
to be replaced, so be it, but I don't want to lose my data that I can
not ever read certain parts of it again or such stuff.
The thing that came to my mind was, if there is some file systems that
would add redundancy and robustness onto the mdraid system of the
linux kernel?
Anyone with some useful insights? Roughly speaking, I was considering
some simple pcie esata interfaced controller card and an external case
enclosure with esata port and portmulitplier stuff inside, that can
present at least 4 physical disks as JBOD, just a bunch of disks, so
that the Linux can seem them all separately.
Speed and rebuild times are not my concern, but data persistence and
data integrity. Not even number of physical disks, I could live with
even one of those 8 bay device enclosures and cases that are out there
on the market.
Thanks for any help and hints.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have one disk that is giving me problems with the smartd daemon. I get
this in the log:
<3.6> 2018-10-21T13:45:23.829155+02:00 Isengard smartd 1173 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state
<3.6> 2018-10-21T13:45:24.483719+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], opened
<3.6> 2018-10-21T13:45:24.484570+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB
<3.6> 2018-10-21T13:45:24.503334+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not found in smartd database.
<3.6> 2018-10-21T13:45:24.525071+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Attribute Autosave.
<3.6> 2018-10-21T13:45:24.530486+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Automatic Offline Testing.
<3.6> 2018-10-21T13:45:24.535003+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], is SMART capable. Adding to "monitor" list.
<3.6> 2018-10-21T13:45:24.535627+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state
<3.6> 2018-10-21T13:45:24.880219+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state
<3.6> 2018-10-21T14:15:25.233525+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 147 to 144
<3.6> 2018-10-21T15:45:31.681938+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check
<3.2> 2018-10-21T15:45:33.632399+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data
<3.6> 2018-10-21T16:15:24.678100+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email
<3.6> 2018-10-21T18:15:31.767150+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check
<3.2> 2018-10-21T18:15:33.717688+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data
<3.6> 2018-10-21T18:45:24.587304+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email
It intermitently but periodically fail to read atributes, triggering
hundreds of emails sent to me to warn of the problem:
+++------------
Subject: SMART error (FailedReadSmartData) detected on host: Isengard
This message was generated by the smartd daemon running on:
host name: Isengard
DNS domain: valinor
The following warning/error was logged by the smartd daemon:
Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT],
failed to read SMART Attribute Data
Device info:
WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.
- ------------++-
The disk is indeed smart capable and it works fine, as long as I call
smartctl with "-d sat,16", which I do:
Isengard:~ # smartctl --test=short -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Sun Oct 21 13:50:18 2018
Use smartctl -X to abort test.
Isengard:~ #
Isengard:~ # smartctl --health -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Isengard:~ #
It is crucial to use "-d sat,16" or it fails:
Isengard:~ # smartctl --health
/dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0: Unknown USB bridge [0x1058:0x25ee (0x4004)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
Isengard:~ #
Of course I use that option on the config:
Isengard:~ # cat /etc/smartd.conf | egrep -v "^[[:space:]]*$|^#"
/dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor
/dev/disk/by-id/wwn-0x5000000000000001 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor
/dev/disk/by-id/wwn-0x5000c5009399305f -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor
/dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 -d sat,16 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor
Isengard:~ #
What else am I missing? Is smartd not using "-d sat,16" somewhere else? Is
it some other problem?
Isengard:~ # rpm -q smartmontools
smartmontools-6.6-135.1.x86_64
Isengard:~ #
- --
Cheers
Carlos E. R.
(from 42.3 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlvM5UMACgkQtTMYHG2NR9WCwQCePjOt8PSMKsx6DwSe9bZJRhHf
2lQAn02eBTrtfAqmEg5ydZVagvMfW2r6
=eIzR
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hello List
am using Xfce : - in /var/log/warn : i see warning
" The gnome keyring socket is not owned with the same credentials as
the user login: /run/user/1000/keyring-4i77r7/control
2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login
keyring "
...............
- any ideas how to fix ?
thanks
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 27/06/17 12:22, Paul Groves wrote:
>
> On 27/06/17 08:34, Aaron Digulla wrote:
>> xmodmap -pke | less
>
> These keycodes do not seem to match the system. For example in the
> output of this command it says:
>
> keycode 158 = XF86WWW NoSymbol XF86WWW
>
> I ran setkeycodes e020 158
>
> When I press the e020 (Internet) button xev says I have pressed code
> 166 (Back button).
>
> How on earth has this happened? I specified 158 not 166. What have I
> done wrong?
>
>
Just been emailed this link:
https://unix.stackexchange.com/questions/49650/how-to-get-keycodes-for-xmod…
To quote this article:
Here you can see keycode 97 is unused on my system:
|keycode 94 = less greater less greater bar brokenbar keycode 95 = F11
XF86Switch_VT_11 F11 XF86Switch_VT_11 keycode 96 = F12 XF86Switch_VT_12
F12 XF86Switch_VT_12 keycode 97 = keycode 98 = Katakana NoSymbol
Katakana keycode 99 = Hiragana NoSymbol Hiragana |
The keycode X uses and the keycode the kernel uses are OFF BY 8 for
"historical reasons". So take 97 - 8 = 89 and use 89 with the
setkeycodes command (again as root):
So to make my vol - button work (xmodmap keycode 122 -8 = 114)
setkeycodes e01e 114
This has worked! I have re-mapped apl the buttons apart from my hotkeys.
>> No but there are lots of uncommon keycodes which you can use. For
>> example, F13-F35 or KP_F1...KP_F4.
>
> In the output of the command xmodmap -pke | less there are no codes
> for F13-F35 or KP_F1 etc
>
> I would like to set HK1 - HK4 to F13 - F16 How do I find the keycodes
> for these buttons
Still looking for the keycodes for F13-16
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
All,
I bought a used iSCSI based Drobo in 2016 with 50TB in it. It works
great, but it isn't fast by today's standards. (100 MB/sec absolute
max). And I never got it to work from openSUSE (Windows and Mac did
work).
I now need to buy something similar, but with fast I/O and Linux
support: 10 Gbit Ethernet and fibre-channel may be my only options?
Or are there point-to-point SAS external racks I should consider?
Also, I will likely want to put a SSD based cache in the mix at some
point. It could be integrated into the storage subsystem, or I could
use something like bcache and have the SSD be in the server,. It just
needs to be reliable and fast.
Recommendations? (I'm thinking used and $10K at the high-end for the
subsystem including PCIx cards and switches, if needed.)
== details
I need to buy a server with 50TB usable disk for a production
environment. A high speed disk subsystem is critical. And the project
may scale up over time.
It doesn't need to be a fail-over cluster, just a single server. I'm
looking at used equipment most likely.
I was thinking one with 4 CPU sockets would let me start with 2 CPUs
and then expand to 4 later on. Lots of RAM capacity would also be
great.
My first thought was to get a Dell R920 and throw a bunch of disks in it.
https://goo.gl/images/x3Rfj2
24 disk slots!
But then I looked at what size drives are available for those slots:
2.5 inch. I only see 2TB drives max.
I'm hoping to use a Dell server because it's the preferred brand at my
(new) job. Unless I'm missing something a standalone rack mount Dell
won't work.
So, now I'm looking at a used R820 most likely and some sort of disk
subsystem to support it. I picked it because it is only a 5-year old
design and it has 4 CPU sockets I can expand into as the server demand
increases over time. Also 3TB max ram is way above what this will
require, even long term.
https://media.adn.de/media/DE/DocLib/Poweredge_Easy_Matrix.pdf
A used, barebones R820 can be had for under $2K. Just add CPUs and ram.
Greg
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi,
On multiple of my machines I have the root filesystem on a dm-crypt device
placed on an SSD. Now, I would like to use `fstrim /`. Now, I know about the
security implications. But, as encryption for me primarily is a way to be able
to throw out disks without further effort, I don't consider those a problem
for me.
Sadly, on any system I installed directly with Leap 15.0 I cannot get this to
work. Despite having `rd.luks.options=discard` in my kernel arguments I get
the following output from `lsblk`:
# lsblk --discard /dev/sda
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
sda 0 512B 2G 0
├─sda1 0 512B 2G 0
├─sda2 0 512B 2G 0
└─sda3 0 512B 2G 0
└─cr_sda3 0 0B 0B 0
Curiously the same works on a different systems which has been upgraded
through various versions of Leap and is now also running on 15.0.
# lsblk --discard /dev/sda
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
sda 0 512B 2G 0
├─sda1 0 512B 2G 0
├─sda2 0 512B 2G 0
├─sda3 0 512B 2G 0
├─sda4 0 512B 2G 0
├─sda5 0 512B 2G 0
└─sda6 0 512B 2G 0
└─luks-081…3e1 0 512B 2G 0
The only difference I can see between the systems is, that the older system
uses the UUID instead of the name, and for some reason the newer system does
have the device containing root in `/etc/crypttab` while the old system does
not.
Any hints on what might be causing the different behavior?
Kind Regards,
Matthias
--
Dr. Matthias Bach
www.marix.org
„Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig
über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
Seamonkey does not compile properly with gcc 7. Although it works
superficially, it crashes on a website.
Leap 15 does not have 4.8. We need a backward compatible compiler don't we?
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I am trying to update my wife's Leap 15.0 system and get this error when
using either zypper or Yast2.
I am using the kernel from the ../Kernel:/stable/standard/ repository on
my Leap 15.0 as well as hers but I am not having this hassle.
When using zypper to update I get this error msg (pls see attached
zypper_error-31.png) and when using Yast I get the error msg in the
attached Yast_error-31.png.
Yesterday when I tried to do same, the 'zypper up' got a lot further in
the installation - pls see attached zypper_error.png.
I have run 'zypper clean -a' and 'zypper refresh -fdb' but this hasn't
helped.
Anyone please suggest what is causing this problem and how to how to get
rid of the cause of this problem?
BC
--
'When I use a word', Humpty Dumpty said, in a rather scornful tone,
'it means just what I choose it to mean.'
Lewis Carroll, Through the Looking-Glass
I am running Firefox 60.4 under 42.3. In the past I was able to play
.mp4 files using my browser. A recent trial failed. What am I doing
wrong and how can I view these files?
don
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org