openSUSE Users March 2018

users@lists.opensuse.org

70 participants
73 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

9 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

2 years, 1 month

Re: [opensuse] Mapping and re-mapping Keyboard Keys

by Paul Groves

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

2 years, 6 months

[opensuse] Spec'ing a 50 TB dedicated storage subsystem and room to grow?

by Greg Freemyer

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

2 years, 6 months

[opensuse] continous access on/spinning up of floppy drive

by Paul Neuwirth

This is an OpenPGP/MIME signed message (RFC2440, RFC3156). --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: text/plain; charset="utf-8" Content-Disposition: inline; filename="message.txt" Content-Transfer-Encoding: quoted-printable Hello group, I have on several machines this problem: they are continously trying to=20 access the floppy drives. Two drives already defective, due to the=20 mechanic stress. dmesg shows following continously: [1537682.559487] sd 0:0:3:0: [sdc] Read Capacity(10) failed: Result:=20 hostbyte=3DDID_OK driverbyte=3DDRIVER_SENSE [1537682.559496] sd 0:0:3:0: [sdc] Sense Key : Not Ready [current] [1537682.559498] sd 0:0:3:0: [sdc] Add. Sense: Logical unit not ready,=20 cause not reportable [1537682.656688] sd 0:0:3:0: [sdc] Spinning up disk... [1537683.668046]=20 ............................................................................= ..................not=20 responding... [1537783.093938] sd 0:0:3:0: [sdc] Spinning up disk... [1537784.104049]=20 ............................................................................= ..................not=20 responding... this can't be the wanted behaviour for any removable storage devices? Any Hints? Thank you and have a nice weekend --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_= Content-Type: application/pgp-signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Topal (http://freshmeat.net/projects/topal) iQIcBAEBAgAGBQJaLS66AAoJEIiaa+Y8YDPuZSUP/itt7+QHjNCwX6Wi352+lANf whjep7nBWy6Q0bS2PO/ymWDGiodFkO/AvM+MIitdK4cAm1HCBbMZjKsZYLD3e1LR ZnskqO66VG58TU6lVB1jEXWKlp6OKeb6Ar24SR0YxB4F+ZcbSwZI5w62JEBsozhV X4imcBdO+ztJFSW/hFLeV4WrfrplcTufyL6nw+5TtImrVs62uEg20LYjA//OxlHJ NmXM07A48uVBijRUmMsqeyRMevoKjKop2iICZgKyvTnRtRqx0jbzVeqj+aLqnbaq ncdBnBr7Vr9S86TVGHjIDHPN8Ws8dnufk1GwRTQR+Aj4z58g2r88j/u6o7csTFla vINP3ClCp6MRVbVbEqIYOIvG8NDIVTiwQwXk3CeCf+Be71JbDUMjV9GwVl+X9ksC oNBwwFi+mhHQGJOuX/54HGUEn3lJ1ixQzLimuXTgWmdsb1WoWuG+lNO13NhU+ZVn /IKpcqVjkXikQi9hrmZTUutmrFjJ1QusjnPJQDuBLYB0E/lMWjTpUNmRGw71hrDb uccAYc3sQP6zMuUfEgPWewhMmuTwn1LoQdqYrZ0p1+1z/+w5cB3DOB4JILmbKBUH QUYaDhefxPL1oRBtOxoDAdABJLAfgfKdEE0+g0u6HA67Atioe3HP8MWonrKgs3FC pvU9BHc2k0ASHh7HEsRx =uYfb -----END PGP SIGNATURE----- --=_MIME_CONTENT_BREAK_=_ZVSGRBXMZBOOXUGBRBCHOBMGKKNVGJR_=-- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 years, 11 months

[opensuse] 'mailto' + 'postfix' at local machine, host or domain name not found

by Simon Becherer

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, ipv4, /etc/hosts 127.0.0.1 localhost 127.0.0.2 becherer1.site becherer1 195.167.0.5 becherer1.site becherer1 /etc/postfix/main.cf myhostname = becherer1.site inet_protocols = ipv4 on my older systems (opensuse 11.4) i can use: programm "mailto" and as address: simon@becherer1 simon@localhost simon(a)becherer1.site simon all will be delivered correct at the local machine. if i use the simon@becherer1 or simon(a)becherer1.site or simon the mail tells me in all cases: send to: simon(a)becherer1.site if i use simon@localhost the mail tells me: send to: simon(a)localhost.site i have the same settings like above in the same files in tumbleweed. (because of newer system, there are much more settings in main.cf) only send to "simon(a)becherer1.site" and "simon" will pass. the simon@becherer1 will generate a "undelivered mail return to sender" host or domain name not found name service error for name = becherer1 type=a: host not found the simon@localhost will generate a "undelivered mail return to sender" "simon@localhost loopbacks to myself." sending a "ping" to becherer1 or becherer1.site will return "from becherer1.site 127.0.0.2" and localhost will return "from localhost 127.0.0.1" on both machnines identical, so normally the names are set correct? i guess some other default for postfix may be changed, but i do not find whats wrong, why did postfix not deliver the mails? regards, simoN - -- www.becherer.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJat+L4AAoJEOuDxDCJWQG+cmYQAKdAWjrF05rtV4B0Sj6AwmWR HtU4gNauN+RB5hIxaBLE2b+/t1+URGkbNdR7jbS/VVmAazFoaJS3uWt3BerGy9kr AvFbnMEJQWjVehHwlnREkjX3Ed3WSPmRYehhqfgKflzZG1tsopfnx8SEJCpIi7yB hcyLRCH7eBF8CStSZ5gf4M76KPwGxkQ602r9pC+IqR0MtOtRmCUMRIJE8UUPK7Fw nVGgOLN8C33xPsNTEbLcM7qzZAEywj4r2qu+a4Fnvpr9fcS2QahpDJ/Drj1YiqJE OaA9GcCKkwab4lvD1BZp0kJEfniPV4W69g5oUq5rHslayXXbYGeQ9OeRryy2O93f c8nV4HBsqjnXrhewWG1wQO8+lcP0UFlztSYy20BX5zZMxyBcWRMEmKgyiQYoOAVX gws2+gs+XnJR0nTN1WT775K/5S8zGHb5C+D+Q7iO2JX/jblWq6zlNnkejSHVWLFV jqv+0GF0bvQ3VpNgtuu5WJrNF36DIxiinOp8VZWg1oT8Z6WKH8p5Eie555PkFxhg t3PWfY+oHNyZhU8SQP3p8myg1Cux3AEQI8bhm/lswMhT88btkEBGb2DSI/VK9mWW 56k2tc90mf8dHrfGZHOd0cWHSE2hiW84AOGRXqY2TS90oAasWdVJgDKxm85VqJVH x/MF6lAOlAXOTHXmQVGQ =egfF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 3 months

[opensuse] zypper addrepo - http:// vs. https://

by Per Jessen

I'm sure someone has a quick explanation: a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…' This fails: Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openS…' Works fine. (notice the extra slash between 'Virtualization:' and 'container'. c) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:containers/openSUS…' d) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:/containers/openSU…' Both work fine. -- Per Jessen, Zürich (9.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 5 months

[opensuse] prime-select: unable to query GPU information

by Daniel Bauer

Hi, I just upgraded my asus laptop with intel/nvidia graphics from 42.1 to 42.3, all went well so far. But when entering prime-select nvidia I get: ERROR unable to query GPU information The script runs anyway, I guess, because when I reboot at some point the screen with the boot messages begins to flicker heavily (I could not read the last message...). I had to restart and boot to runlevel 3, then entered "prime-sectect intel" and now I can boot normally - but of course only using the intel card. I don't know which information you need to help me: please ask and I'll try to provide it. Thanks for your help! Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 5 months

[opensuse] Which distros for ReiserFS?

by Stevens

On the odd chance that I was ignored for possibly hijacking a thread, I shall start a new one but copy and paste my comments in hope of an answer: (re: Killing ReiserFS) I have been following this thread with some interest because of having been running ReiserFS since before he turned homicidal. I have had zero, count that ZERO, problems in all that time so I read with some dismay the effort to actively kill its usage in this whatever-you-call-it distro. I think that the more relevant question to ask is not "can we keep this file system around, pretty please" but "what distros are allowing its use by not actively trying to kill it"? I have used opensuse since before Mandrake went away, which has been a while and, although I don't really want to change distros, I am not married to suse (or leap, or whatever). I feel that what we have here with opensuse/leap is an example of the classic "swing" cartoon which shows the stages of project development from sales, engineering, installation and what the customer actually wanted. My need is not as complex as some and for that ReiserFS works quite well. So, my question remains, "If not suse/leap, then who"? Hopefully someone will know what distros allow the freedom to use whichever FS one wishes without running afoul of the FS nazis. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 5 months

[opensuse] bumblebeed oops

by Markus Koßmann

Anyone seen this before: 2018-03-31T06:11:24.251115+02:00 linux-86i0 kernel: [ 9.778199] ------------[ cut here ]------------ 2018-03-31T06:11:24.251116+02:00 linux-86i0 kernel: [ 9.778206] WARNING: CPU: 1 PID: 2105 at ../drivers/pci/pci.c:1596 pci_disable_device+0x90/0xa0() 2018-03-31T06:11:24.251117+02:00 linux-86i0 kernel: [ 9.778208] pci 0000:02:00.0: disabling already-disabled device 2018-03-31T06:11:24.251118+02:00 linux-86i0 kernel: [ 9.778208] Modules linked in: vmnet(O) ppdev parport_pc parport fuse vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) msr bnep btrfs xor raid6_pq arc4 nls_iso8859_1 nls_cp437 vfat intel_rapl fat x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm irqbypass crct10dif_pclmul snd_hda_intel crc32_pclmul snd_hda_codec snd_hda_core crc32c_intel snd_hwdep ghash_clmulni_intel snd_pcm pn544_mei drbg snd_seq uvcvideo mei_phy iwlmvm videobuf2_vmalloc videobuf2_memops snd_seq_device pn544 mac80211 ansi_cprng videobuf2_v4l2 hci snd_timer videobuf2_core aesni_intel btusb btrtl v4l2_common btbcm iTCO_wdt aes_x86_64 dell_wmi videodev nfc snd iTCO_vendor_support sparse_keymap lrw dell_laptop gf128mul btintel glue_helper rtsx_pci_ms bluetooth iwlwifi dcdbas ablk_helper ipmi_msghandler ie31200_edac cryptd memstick soundcore cfg80211 acpi_als joydev edac_core pcspkr i2c_i801 lpc_ich kfifo_buf mei_me shpchp mei industrialio fjes fan thermal int3403_thermal int3402_thermal int3400_thermal battery dell_rbtn dell_smo8800 ac int340x_thermal_zone acpi_thermal_rel rfkill processor ext4 crc16 jbd2 mbcache sd_mod hid_multitouch usbhid sg dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ahci rtsx_pci_sdmmc libahci mmc_core i915(O) i2c_algo_bit libata rtsx_pci mxm_wmi drm_kms_helper(O) syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci serio_raw scsi_mod mfd_core ehci_pci xhci_hcd ehci_hcd usbcore usb_common drm(O) wmi video button dm_mirror dm_region_hash dm_log dm_mod bbswitch(O) efivarfs autofs4 [last unloaded: nvidia] 2018-03-31T06:11:24.251119+02:00 linux-86i0 kernel: [ 9.778263] CPU: 1 PID: 2105 Comm: bumblebeed Tainted: P O 4.4.120-45-default #1 2018-03-31T06:11:24.251120+02:00 linux-86i0 kernel: [ 9.778264] Hardware name: Dell Inc. XPS 15 9530/XPS 15 9530, BIOS A08 01/08/2015 2018-03-31T06:11:24.251121+02:00 linux-86i0 kernel: [ 9.778266] 0000000000000000 ffffffff813438a7 ffff88041d86fd98 ffffffff81a532f5 2018-03-31T06:11:24.251121+02:00 linux-86i0 kernel: [ 9.778269] ffffffff810844e1 ffff88041f123000 ffff88041d86fde8 00007fc07cd8e000 2018-03-31T06:11:24.251122+02:00 linux-86i0 kernel: [ 9.778271] ffff88041d86ff28 0000000000000028 ffffffff8108455c ffffffff81a6dc88 2018-03-31T06:11:24.251123+02:00 linux-86i0 kernel: [ 9.778274] Call Trace: 2018-03-31T06:11:24.251124+02:00 linux-86i0 kernel: [ 9.778284] [<ffffffff8101b0f9>] dump_trace+0x59/0x350 2018-03-31T06:11:24.251125+02:00 linux-86i0 kernel: [ 9.778288] [<ffffffff8101b4ea>] show_stack_log_lvl+0xfa/0x180 2018-03-31T06:11:24.251125+02:00 linux-86i0 kernel: [ 9.778291] [<ffffffff8101c2b1>] show_stack+0x21/0x40 2018-03-31T06:11:24.251126+02:00 linux-86i0 kernel: [ 9.778295] [<ffffffff813438a7>] dump_stack+0x5c/0x85 2018-03-31T06:11:24.251127+02:00 linux-86i0 kernel: [ 9.778301] [<ffffffff810844e1>] warn_slowpath_common+0x81/0xb0 2018-03-31T06:11:24.251128+02:00 linux-86i0 kernel: [ 9.778305] [<ffffffff8108455c>] warn_slowpath_fmt+0x4c/0x50 2018-03-31T06:11:24.251128+02:00 linux-86i0 kernel: [ 9.778309] [<ffffffff8138d960>] pci_disable_device+0x90/0xa0 2018-03-31T06:11:24.251129+02:00 linux-86i0 kernel: [ 9.778314] [<ffffffffa000c1cd>] bbswitch_off+0x8d/0x240 [bbswitch] 2018-03-31T06:11:24.251143+02:00 linux-86i0 kernel: [ 9.778319] [<ffffffffa000c5ae>] bbswitch_proc_write+0xae/0xbc [bbswitch] 2018-03-31T06:11:24.251146+02:00 linux-86i0 kernel: [ 9.778324] [<ffffffff81281bcc>] proc_reg_write+0x3c/0x70 2018-03-31T06:11:24.251147+02:00 linux-86i0 kernel: [ 9.778329] [<ffffffff81215ff6>] __vfs_write+0x26/0x140 2018-03-31T06:11:24.251148+02:00 linux-86i0 kernel: [ 9.778332] [<ffffffff81216d7f>] vfs_write+0xaf/0x1d0 2018-03-31T06:11:24.251149+02:00 linux-86i0 kernel: [ 9.778336] [<ffffffff81217e22>] SyS_write+0x42/0xa0 2018-03-31T06:11:24.251150+02:00 linux-86i0 kernel: [ 9.778342] [<ffffffff81640809>] entry_SYSCALL_64_fastpath+0x22/0xba 2018-03-31T06:11:24.253122+02:00 linux-86i0 systemd[1]: Started Network Manager Script Dispatcher Service. 2018-03-31T06:11:24.253330+02:00 linux-86i0 dbus[1340]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 2018-03-31T06:11:24.255077+02:00 linux-86i0 kernel: [ 9.781274] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x22/0xba 2018-03-31T06:11:24.255083+02:00 linux-86i0 kernel: [ 9.781275] 2018-03-31T06:11:24.255083+02:00 linux-86i0 kernel: [ 9.781275] Leftover inexact backtrace: 2018-03-31T06:11:24.255085+02:00 linux-86i0 kernel: [ 9.781275] 2018-03-31T06:11:24.255086+02:00 linux-86i0 kernel: [ 9.781303] ---[ end trace 0beb54cbaeaebc1a ]--- Is bumblebeed doing the wrong thing here by not checking the graphics cards state before trying to disable it on startup ? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 5 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 March 2018