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
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
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
As the Subject states, the Nvidia driver will not compile using the
5.5.0-1 kernel -- stops with an error during the compiling stage.
Anyone aware of any "fixes", please?
BC
--
All things are possible, except skiing through a revolving door.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I've been running IPv6 on my notebook computer for years, using
NetworkManager to configure the networking. The consistent IPv6 address
had long been based on the MAC address, but now it's a random number.
How did this happen and what do I do to go back to the MAC based
address? As always, the temporary privacy addresses are random.
tnx jk
--
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
Telcontar:~ # systemctl status mlocate.service
● mlocate.service - Update locate database
Loaded: loaded (/usr/lib/systemd/system/mlocate.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:updatedb
Telcontar:~ # systemctl enable mlocate.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Telcontar:~ #
Telcontar:~ # systemctl status mlocate.timer
● mlocate.timer - Daily locate database update
Loaded: loaded (/usr/lib/systemd/system/mlocate.timer; enabled; vendor preset: disabled)
Active: inactive (dead)
Trigger: n/a
Docs: man:updatedb
Telcontar:~ # systemctl enable mlocate.timer
Telcontar:~ # systemctl status mlocate.timer
● mlocate.timer - Daily locate database update
Loaded: loaded (/usr/lib/systemd/system/mlocate.timer; enabled; vendor preset: disabled)
Active: inactive (dead)
Trigger: n/a
Docs: man:updatedb
Telcontar:~ #
So, what should I do to enable it?
- --
Cheers
Carlos E. R.
(from 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjDJpRwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVAjMAoIslX0KthL9O8aXHpaDP
+umnwknKAJ9gCEQKn/keiNIl2luD2m+fpPftiw==
=zcdt
-----END PGP SIGNATURE-----
I did create a paste in
https://paste.opensuse.org/22334414
I am not good enough to understand what the system actually complains. I do
not think it is a memory problem, could be related to the OS instead.
The swap fills although the memory remains free. If you sudo swapoff -a the
swap turns into memory, the system turns responsive.
sudo dmesg reveals a flood of entries (disregard the martians, these are due
to a vpn.)
I do not understand if, and if which, hardware is failing. Memory does nor
reveal errors. Sometimes I get a complaint about CPU3 should not be sleeping.
This is all I know.
Thanks in advance if somebody understands (and maybe can a bit explain) the
output. Why does the swap not return to memory once memory is abundantly
available?
_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
--
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
On Tuesday, 2020-01-21 at 21:10 +0300, Andrei Borzenkov wrote:
> 21.01.2020 17:46, stakanov пишет:
>> In data martedì 21 gennaio 2020 14:43:22 CET, Andrei Borzenkov ha scritto:
>>> On Tue, Jan 21, 2020 at 4:32 PM stakanov <stakanov(a)eclipso.eu> wrote:
>>>> I hope now that the problematic became somewhat clearer.
>>>
>>> I still miss desktop environment for each user and openSUSE version,
>>> as well as how exactly you start multiple sessions.
>>
>>
>> My bad, as I am always on the "KDE is default thought".
>> Multiple session are started from KDE with sddm as session manager and "start
>> new session". However I do never start multiple sessions for the same user.
>> /home is on a separate partition see also below the listing of devices.
>>
>
> I tested on Leap 15.1 with XFCE + lightdm. I added custom polkit rule to
> force root authentication for active session. I switched user using
> dm-tool switch-to-user (I did not find XFCE GUI element for it). dm-tool
> talks to lightdm and makes it allocate new session or switch to existing
> one.
Wow! Thanks for telling of "dm-tool switch-to-user". Will it work with
sddm and XFCE?
Switch to another user from XFCE seems to be broken currently. I have not
investigated, but I noticed recently that it does not work, while it did
work months ago. The option is there in my exit menu (action buttons
applet), but does nothing.
> I logged in as user u1, u2, u3, then switched to u2 session and checked
> that u2 session was active. After inserting USB stick I got password
> request for u2. I checked process list that there was just one active
> password request. After cancelling this request it was started for
> another user. In this case it was u3. Switching to u3 and cancelling
> request now started request for u1.
>
> So it seems to basically work as expected. I do not know how exactly
> requests are ordered (it was new to me that request would be cycled
> across all current sessions).
Interesting. New to me as well.
- --
Cheers,
Carlos E. R.
(from openSUSE 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjKw5Bwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV/D4AnjyOG+andu9KGYQKwg1P
R5hJEMcsAJ9lgXnrOWN5A+CJxynxSEPQE1qexQ==
=QaJn
-----END PGP SIGNATURE-----
If I am attributing the system "secure rights" in yast.
If I am activating group wheel for sudo.
If I am taking off sudo rights for everybody else who is not wheel.
If I plug now in an usb device, is the user still asked the password for root
to mount the device? Or is he now unable to root any usb device (given secure
settings)?
Is there a way to avoid hat (if you have three users working, only he last
open one is presented with the password request for opening an usb device
(this is actually very annoying because if you work in one user you do not
want to switch to another, to cancel the request, to to have finally the pop
up coming up in the right place.....
_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
