openSUSE Users December 2019

users@lists.opensuse.org

64 participants
64 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, 1 week

[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] How to make sure that each vNIC in guest is always associated with a correct VLAN?

by Martin T

Hi, I have six virtual bridges in xen host machine and following virtual machine configuration file section defining the vifs: vif = [ 'bridge=br10', 'bridge=br20', 'bridge=br30', 'bridge=br40', 'bridge=br50', 'bridge=br60' ] This means that in the guest(openSUSE Leap 42.1) I have six vNICs(eth0 - eth5). Can I be sure that eth0 is always connected to br10, eth1 to br20, etc? Or should I specify a MAC address for each vNIC created like this: vif = [ 'bridge=br10, mac=00:14:5E:11:C6:F1', 'bridge=br20, mac=00:14:5E:11:C6:F2', 'bridge=br30, mac=00:14:5E:11:C6:F3', 'bridge=br40, mac=00:14:5E:11:C6:F4', 'bridge=br50, mac=00:14:5E:11:C6:F5', 'bridge=br60, mac=00:14:5E:11:C6:F6' ] .. and then configure udev rules which make sure that interface associated with MAC 00:14:5E:11:C6:F1 and br10 is always named eth0, interface associated with MAC 00:14:5E:11:C6:F2 and br20 is always named eth1, etc? Or maybe there is a better way using /etc/sysconfig/network/ifcfg-* files? thanks, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year

[opensuse] Any progress on susepaste reporting failed when it actually succeeds?

by David C. Rankin

This came up a month or so back, susepaste reports that it failed on the command line, but the paste actually succeeds. I believe it was a curl issue at the time and there was a recommendation on changing the script from http to https to make curl happy. Well, it still continues to report failure even though the paste succeeds, e.g. $ pst "ptr2array-3" ptr2array3.c c Dec 25 02:38:00 - "ptr2array-3" ptr2array3.c Paste failed :-( expires: Wed Jan 22 02:38:02 CST 2020 Paste happily made it: https://paste.opensuse.org/70684135 but I still get the "Paste failed :-(" message. http/https makes no difference. Any suggestions? (also... to you and your's this holiday!) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

[opensuse] Hardware Recommendations?

by Lew Wolfgang

Hi Folks, My 13-year old HP desktop is still working fine, but it's obviously time to retire it before it permanently dies. Also, my wife recently found a bit of luck at the casino and this is the perfect time to upgrade. So I have a couple of questions about hardware compatibility with openSUSE. It looks like the AMD Ryzen cpu's have a bit of an edge over Intel, but has anyone seen compatibility issues? And what about high-res monitors? I'm looking at a UHD (3840 x 2160) monitor, any issues with Leap 15.1? And how about those really wide/curved monitors? Thanks in advance for any advice, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

[opensuse] KDE Plasma weight vs XFCE weight

by Felix Miata

Interesting comparison: https://www.forbes.com/sites/jasonevangelho/2019/10/23/bold-prediction-kde-… -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

[opensuse] DNS/Bind9 - success resolving 'XXX' after reducing the advertised EDNS UDP packet size to 512 octets

by David C. Rankin

All, This is more a general question about a rash of DNS resolution issues that seem to be on the increase on my ipv4 network lately. They basically have to do with Bind 9 trying to resolve names with EDNS (and I guess the default UDP package size of 4K) I don't handle ipv6 at all. In my named.conf I have: listen-on-v6 { none; }; But regardless, I end up with a slew of messages, e.g. error (network unreachable) resolving 'gateway.discord.gg/A/IN': 2001:630:0:9::14#53 success resolving 'gateway.discord.gg/A' (in 'discord.gg'?) after reducing the advertised EDNS UDP packet size to 512 octets I don't understand why I'm seeing the attempts to resolve the ipv6 address to begin with? However, the same issue seems to effect normal ipv4 addresses, even opensuse.org, e.g. Dec 30 22:03:48 nirvana named[15060]: success resolving 'www.opensuse.org/A' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets Dec 30 22:03:54 nirvana named[15060]: success resolving 'nshou1.novell.com/A' (in 'novell.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Dec 30 22:03:54 nirvana named[15060]: success resolving 'nshou1.novell.com/AAAA' (in 'novell.com'?) after reducing the advertised EDNS UDP packet size to 512 octets Dec 30 22:03:54 nirvana named[15060]: success resolving 'opensuse.org/A' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets Dec 30 22:03:54 nirvana named[15060]: success resolving 'opensuse.org/AAAA' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets From Bind9ARM, I have set the EDNS UDP packet size to 512, but I'm still having the problems. I have included: edns-udp-size 512; and I still do not eliminate the "success ... after reducing the advertised EDNS UDP packet size to 512 octets" messages that are logged. The EDNS resolution is working, but only for 512 octets (the related posts seem to indicate this is a problem largely to do with misconfigured load-balancing and failover configurations of the target machines. I don't recall seeing much of this before a month or two ago -- so I don't know if it is at all related to the DNS over http growing pains or what... Has anyone else run into this problem -- or have a solution? The time it takes for Bind to try from UDP size of 4096 (default) to 512 on some sites with 50 linked domains can be quite noticeable. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

[opensuse] A 16TB hard disk drive is on sale for far less than you'd think

by Anton Aylward

A 16TB hard disk drive is on sale for far less than you'd think 16TB HDD for just over $400 <https://www.techradar.com/news/a-16tb-hard-disk-drive-is-on-sale-for-far-le…> Storage giant Seagate unveiled two new hard disk drives with a 16TB capacity earlier this year and for once, it was not all about data centers. The Exos X16 and the IronWolf/IronWolf Pro targeted two different audiences (data center for the first and NAS users for the second) and feature SATA or SAS interface only for the first one and SATA only for the second model. Provantage is selling the _Exos_ <https://www.provantage.com/seagate-st16000nm001g~7SEGE1K1.htm> (ST16000NM001G) for just over $400 while the _IronWolf_ <https://www.amazon.com/Seagate-IronWolf-16TB-256Mb-7200Rpm/dp/B07SNW9W48/re…> one (ST16000VN001) retails for just under $500 from Amazon. Both have nine platters, use Helium technology and have a five year warranty (the IronWolf has three); they also share the s same spinning speed (7200RPM), idle power (5W), average latency (4.16ms) and cache (256MB). The Exos range carries a MTBF (mean time before failures) at 2.5M hours and boasts a higher sustained transfer rate at 261MBps; the IronWolf Pro and the IronWolf reach 250 and 210MBps respectively. Note that the IronWolf Pro also comes with bundled Rescue Services, great for data recovery. * These are the best cloud storage <https://www.techradar.com/news/the-best-cloud-storage> of 2020, great to save your files online. * We also compiled the list of best cloud backup services <https://www.techradar.com/best/best-cloud-backup> * It is advisable that you keep a local copy of your files, so check out our best NAS <https://www.techradar.com/news/the-10-best-nas-devices-reviewed> Toshiba announced the 16TB _MG08_ <https://www.techradar.com/news/toshiba-unveils-new-16tb-enterprise-capacity…> series in January 2019 but we have yet to see any stock in the channel. Western Digital also shipped its first 16TB hard disk drives as well but based on MAMR rather than HAMR technology - as used by Seagate. While SSD prices have been falling, they are still far more expensive than their hard disk drive counterparts. At about $2800, Micron’s 9300 Pro <https://www.connection.com/product/micron-15.36tb-9300-pro-pcie-gen3-x4-nvm…> is nearly *SEVEN* times more expensive although this gap has all but disappeared for sub-1TB capacities. * _Cloud storage vs external hard disk drive: which one is better?_ <https://www.techradar.com/news/cloud-storage-vs-external-hard-disk-drive-wh…> *Source: https://www.techradar.com/news/a-16tb-hard-disk-drive-is-on-sale-for-far-le… ================================================================================ <AJA> I see mention that the gap between HDD and SSD prices has "all but disappered for sub-1TB capacities" which is interesting. The basic Linux OS as a healthy instlation can fit on under 500MB never mind 500GB, probably less. Let's not forget that memory is cheap and you probably can manage without swap unless you are doing something intense like photediting. Short of and EMP (and even then it's questionable) from various sources (and then there's the issue of how concerned with your digital memories will you be in the aftermath?) that might leave magnetic memory intact but erase (unsheilded) semiconductor memory ... No, wait! My current generation Dell box is heavily RF shlded. It's far removed from some of the 'white box from Tiawan' PCs chassis I have in my basement in this regard. Not that my neighbours ever complained about my PC (or, in times past, my radio HAM equipment) interfering with their TV (whihc was probably cable anyway). So I wonder how well sheilded our compters are? How easy it is to do? Is the present RF protection adequate? https://www.futurescience.com/emp/emp-protection.html https://www.csmonitor.com/2005/1219/p25s02-stct.html </AJAJ> -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

[opensuse] Skype replacements

by Cons Brouerius van Nidek

With one my daughters who lives half the world away I had a good exchange with Skype. Since she works on an older I pad which is excluded from the last IOS updates her Skype does not work anymore. What are the programs we both can use to start connecting again. Is there a opensuse variant for IOS based systems? -- opensuse:tumbleweed:20191228 Qt: 5.13.1 KDE Frameworks: 5.65.0 - KDE Plasma: 5.17.4 - kwin 5.17.4 kmail2 5.13.0 (19.12.0) - akonadiserver 5.13.0 (19.12.0) - Kernel: 5.3.12-2- default - xf86-video-nouveau: -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 year, 1 month

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