openSUSE Users July 2019

users@lists.opensuse.org

65 participants
85 discussions

[opensuse] Raid, Raid6, what file system for good fault tolerance?

by cagsm

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

2 months

[opensuse] Issue with smartd

by Carlos E. R.

-----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

4 months, 1 week

[opensuse] Re: questions about webpin

by Knurpht-openSUSE

Try zypper in opi Then f.e. opi dog -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 months, 2 weeks

[opensuse] Another annoying "feature" - 15.1 & KDE

by James Knott

There seems to be a bug with KDE on 15.1. Frequently, when I click on an open item on the task bar, the list of windows for that app no longer appears. However, if I just hover over it, then the windows are listed in a horizontal row. Is there anyway to fix this? At the moment, I have to log out & in. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 6 months

[opensuse] Epson Inkjet Printer can't connect

by Doug McGarrett

Re: Tumbleweed: I have an Epson WP-4530 all-in-one printer/copier/scanner. The Driver is available in /usr/etcetera, and Yast claims to have installed it, and if I try to print something, the Epson is shown as a choice, but nothing happens. If I try to use XSane, a message tells me it can't find a device. Meanwhile, an HP LaserJet Pro is found and prints perfectly. But it can't scan or print in color. I've gotten used to Tumbleweed and I like it, but why won't it print? All help appreciated! --doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 6 months

[opensuse] oS 13.1 : "gnome keyring socket is not owned with the same credentials as the user"

by ellanios82

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

1 year, 6 months

[opensuse] Compressed filesystems?

by Carlos E. R.

Hi, What filesystems do we have with transparent compression? Read/write, of course. I intend to create a compressed backup external disk (Leap 15.0) I know of btrfs and zfs. zfs is not supported officially on openSUSE, that's a con. I read on some sites not to use zfs on single drives (<https://www.ixsystems.com/community/threads/single-drive-zfs.35515/#post-21…>) «Well, the CTO of iXsystems said something like "single disk ZFS is so pointless it's actually worse than not using ZFS". Technically you can do deduplication and compression. But there is no protection from corruption since there is no redundancy. So any error can be detected, but cannot be corrected. This sounds like an acceptable compromise, but its actually not. The reason its not is that ZFS' metadata cannot be allowed to be corrupted. If it is it is likely the zpool will be impossible to mount (and will probably crash the system once the corruption is found). So a couple of bad sectors in the right place will mean that all data on the zpool will be lost. Not some, all. Also there's no ZFS recovery tools, so you cannot recover any data on the drives. You cannot use the standard recovery tools that are designed for NTFS, FAT32, etc either. They don't work correctly.» Other alternatives? btrfs seems to support it well. <https://btrfs.wiki.kernel.org/index.php/Compression> Then, what compression method to use? Default is zlib, says the wiki. «There's a speed/ratio trade-off: ZLIB -- slower, higher compression ratio (uses zlib level 3 setting, you can see the zlib level difference between 1 and 6 in zlib sources). LZO -- faster compression and decompression than zlib, worse compression ratio, designed to be fast ZSTD -- (since v4.14) compression comparable to zlib with higher compression/decompression speeds and different ratio levels (details) The differences depend on the actual data set and cannot be expressed by a single number or recommendation. Do your own benchmarks. LZO seems to give satisfying results for general use.» That seems to point to ZSTD. The wiki says there are 15 compression levels with ZSTD, but does not say which is the default or describe the expectations for each level. Points to a "details" link. Maybe level 1 would do. I do not want really high compression ratio, I prefer speed because backups are large. And things like email compress very well, anyway. Ideas? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 year, 6 months

[opensuse] libreoffice LibreLogo macro bug

by Dave Howorth

There's apparently a bug in LO that can run arbitrary code. https://www.theregister.co.uk/2019/07/30/libreoffice_macro_virus/ Does anybody know whether this has been or will be patched for Leap 15.0 (LO 6.1.5.2)/ i.e. an openSUSE back patch since LO aren't fixing AIUI. LibreLogo appears to be part of the libreoffice-pyuno package. Is there any way to disable it, or just remove the /usr/lib64/libreoffice/share/Scripts/python/LibreLogo directory? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 6 months

[opensuse] Clone disk

by Roger Oberholtzer

I have a user (openSUSE 12.3 - I know...) that wants to clone the root disk. In fact, long ago, they did this. But apparently both they and I have forgotten exactly what we did... The disk copy went ok. dd the entire thing from one disk to another of the same type. We always mount by_id since there may be multiple disks. So, after the dd, one needs to mount the new disk and edit /etc/fstab with the new disk's ID. This has been done. The boot seems to then be looking for the correct disk. However, the boot does not happen. It just hangs. The kernel command line is the only thing printed. I do not have the disk in my possession (it's on a different continent). So, before I tell them to send it to me, I just want to be sure that I have not missed another step. Could there be a need to remake the initial ram disk? Is the disk id in there as well? If one has to do mkinitrd, how can one do that on a mounted disk (not the system's root disk)? Or maybe it is something else? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 6 months

[opensuse] Trying to create a compressed (and encrypted) btrfs filesystem

by Carlos E. R.

Leap 15.0 /etc/fstab: /dev/mapper/cr_my_book_tlcntr /mnt/BookTelcontar btrfs lazytime,compress=zlib:1 1 3 This is per instructions on the wiki (and man): <https://btrfs.wiki.kernel.org/index.php/Compression> But yields error: Isengard:~ # mount -v /mnt/BookTelcontar/ mount: /mnt/BookTelcontar: wrong fs type, bad option, bad superblock on /dev/mapper/cr_my_book_tlcntr, missing codepage or helper program, or other error. I have to use: /dev/mapper/cr_my_book_tlcntr /mnt/BookTelcontar btrfs lazytime,compress 1 3 which yields: mount: /dev/mapper/cr_my_book_tlcntr on /mnt/BookTelcontar type btrfs (rw,relatime,lazytime,compress=zlib,space_cache,subvolid=5,subvol=/) Is this a bug? Is the syntax different? man: compress, compress=type, compress-force, compress-force=type (default: off) Control BTRFS file data compression. Type may be specified as zlib, lzo, zstd or no (for no compression, used for remounting). If no type is specified, zlib is used. If compress-force is specified, then compression will always be attempted, but the data may end up uncompressed if the compression would make them larger. Otherwise some simple heuristics are applied to detect an incompressible file. If the first blocks written to a file are not compressible, the whole file is permanently marked to skip compression. As this is too simple, the compress-force is a workaround that will compress most of the files at the cost of some wasted CPU cycles on failed attempts. The heuristics of compress will improve in the future so this will not be necessary. Note If compression is enabled, nodatacow and nodatasum are disabled. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 year, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users July 2019