February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c7 --- Comment #7 from Gerben Jansen <gerben.jansen(a)aol.com> --- Scenario: manta: mount /MyDisk manta: unmount /MyDisk guppy: journalctl -f guppy: pull the USB cable of sdb Feb 01 10:38:54 guppy kernel: XFS (sdc1): Unmounting Filesystem Feb 01 10:38:54 guppy kernel: XFS (sdc1): metadata I/O error: block 0x575e22df ("xlog_iodone") error 5 numblks 64 Feb 01 10:38:54 guppy kernel: XFS (sdc1): xfs_do_force_shutdown(0x2) called from line 1245 of file ../fs/xfs/xfs_log.c. Return address = 0xffffffffa0569579 Feb 01 10:38:54 guppy kernel: XFS (sdc1): Log I/O Error Detected. Shutting down filesystem Feb 01 10:38:54 guppy kernel: XFS (sdc1): Unable to update superblock counters. Freespace may not be correct on next mount. Feb 01 10:38:54 guppy kernel: XFS (sdc1): Please umount the filesystem and rectify the problem(s) Feb 01 10:38:54 guppy kernel: nfsd: last server has exited, flushing export cache Feb 01 10:38:54 guppy systemd[1]: Unmounted /MyDisk. guppy: put the USB cable back Feb 01 10:39:18 guppy kernel: usb 2-1.1: new high-speed USB device number 5 using ehci-pci Feb 01 10:39:18 guppy kernel: usb 2-1.1: New USB device found, idVendor=04e8, idProduct=5f06 Feb 01 10:39:18 guppy kernel: usb 2-1.1: New USB device strings: Mfr=1, Product=11, SerialNumber=3 Feb 01 10:39:18 guppy kernel: usb 2-1.1: Product: Samsung STORY Station Feb 01 10:39:18 guppy kernel: usb 2-1.1: Manufacturer: JMicron Feb 01 10:39:18 guppy kernel: usb 2-1.1: SerialNumber: 0000002CE09310500C0B Feb 01 10:39:18 guppy kernel: usb-storage 2-1.1:1.0: USB Mass Storage device detected Feb 01 10:39:18 guppy kernel: scsi host5: usb-storage 2-1.1:1.0 Feb 01 10:39:18 guppy mtp-probe[2716]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1" Feb 01 10:39:18 guppy mtp-probe[2716]: bus: 2, device: 5 was not an MTP device Feb 01 10:39:20 guppy kernel: scsi 5:0:0:0: Direct-Access Samsung STORY Station PQ: 0 ANSI: 2 CCS Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] Write Protect is off Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] Mode Sense: 28 00 00 00 Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] No Caching mode page found Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through Feb 01 10:39:20 guppy kernel: sdc: sdc1 Feb 01 10:39:20 guppy kernel: sd 5:0:0:0: [sdc] Attached SCSI disk Feb 01 10:39:21 guppy sddm-greeter[2112]: "/org/freedesktop/UDisks2/drives/SAMSUNG_HD154UI_S20YJ1MSC11476" has new interfaces: ("org.freedesktop.UDisks2.Drive", "org.freedesktop.UDisks2.Drive.Ata") Feb 01 10:39:21 guppy sddm-greeter[2112]: "/org/freedesktop/UDisks2/block_devices/sdc" has new interfaces: ("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.PartitionTable") Feb 01 10:39:21 guppy sddm-greeter[2112]: "/org/freedesktop/UDisks2/block_devices/sdc1" has new interfaces: ("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.Filesystem", "org.freedesktop.UDisks2.Partition") Feb 01 10:39:21 guppy systemd[1]: Mounting /MyDisk... Feb 01 10:39:21 guppy kernel: XFS (sdc1): Mounting V4 Filesystem Feb 01 10:39:23 guppy kernel: XFS (sdc1): Ending clean mount Feb 01 10:39:23 guppy systemd[1]: Mounted /MyDisk. manta: mount /MyDisk manta:~ # mount /MyDisk mount.nfs: requested NFS version or transport protocol is not supported So i reproduced the same error without going through a suspend/resume sequence. Also i created an ext4 file system on a USB stick on guppy, mounted and exported it to manta. On manta i saw the same "mount.nfs: requested NFS version or transport protocol is not supported" error after a suspend/resume sequence. This was on the ext4 file system. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123747] New: AUDIT-0: udisks2: polkit-untracked-privilege
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1123747 Bug ID: 1123747 Summary: AUDIT-0: udisks2: polkit-untracked-privilege Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjorn.lie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Sec team - New priv for a new sub-package for udisks2 [ 543s] libudisks2-0_vdo.x86_64: E: polkit-untracked-privilege (Badness: 10000) org.freedesktop.udisks2.vdo.manage-vdo (auth_admin:auth_admin:auth_admin_keep) Since this is an all auth_admin thing I expect it to be a walk in the park :-) Package lives in https://build.opensuse.org/package/show/home:iznogood:factory/udisks2 Please review. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123525] Errors during boot of updated system on Raspberry Pi 2
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123525 http://bugzilla.suse.com/show_bug.cgi?id=1123525#c11 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(freek(a)opensuse.or | |g) --- Comment #11 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Freek de Kruijf from comment #8) > # rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz > kbd-2.0.4-9.1.x86_64 > > # lsinitrd | grep us.map > > shows nothing. > > I have: > > # lsinitrd | grep '\.map' > -rw-r--r-- 1 root root 11915 Aug 6 12:03 > usr/share/kbd/keymaps/legacy/i386/qwerty/us-acentos.map Please provide: /var/log/YaST2/mkinitrd.log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123525] Errors during boot of updated system on Raspberry Pi 2
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123525 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c6 --- Comment #6 from Gerben Jansen <gerben.jansen(a)aol.com> --- Heeeeey, i did the suspend/resume one more time and this time dmesg shows similar messages but now on the sdb1 device (which does contain /MyDisk) also after the sdb1 device re-appeared it was automatically mounted again. (due to the default "auto" option in the /etc/fstab) However i can imagine that nfsd would like a device to disappear and re-appear without getting into troubles in the dmesg now told me (booted without the "debug printk.devkmsg=on" options: [ 1384.440416] PM: Finishing wakeup. [ 1384.440417] OOM killer enabled. [ 1384.440418] Restarting tasks ... done. [ 1384.467852] video LNXVIDEO:00: Restoring backlight state [ 1384.480297] usb 2-1.1: USB disconnect, device number 3 [ 1384.520617] usb 1-1.5: new full-speed USB device number 10 using ehci-pci [ 1384.544996] XFS (sdb1): Unmounting Filesystem [ 1384.545072] XFS (sdb1): metadata I/O error: block 0x575e22cb ("xlog_iodone") error 5 numblks 64 [ 1384.545079] XFS (sdb1): xfs_do_force_shutdown(0x2) called from line 1245 of file ../fs/xfs/xfs_log.c. Return address = 0xffffffffa057f579 [ 1384.545090] XFS (sdb1): Log I/O Error Detected. Shutting down filesystem [ 1384.545093] XFS (sdb1): Please umount the filesystem and rectify the problem(s) [ 1384.545098] XFS (sdb1): Unable to update superblock counters. Freespace may not be correct on next mount. [ 1384.572759] nfsd: last server has exited, flushing export cache [ 1384.604764] usb 1-1.5: device descriptor read/64, error -32 [ 1384.796612] usb 1-1.5: device descriptor read/64, error -32 [ 1384.984666] usb 1-1.5: new full-speed USB device number 11 using ehci-pci [ 1385.064664] usb 1-1.5: device descriptor read/64, error -32 [ 1385.252662] usb 1-1.5: device descriptor read/64, error -32 [ 1385.360935] usb 1-1-port5: attempt power cycle [ 1385.964662] usb 1-1.5: new full-speed USB device number 12 using ehci-pci [ 1386.380692] usb 1-1.5: device not accepting address 12, error -32 [ 1386.460673] usb 1-1.5: new full-speed USB device number 13 using ehci-pci [ 1386.876648] usb 1-1.5: device not accepting address 13, error -32 [ 1386.876931] usb 1-1-port5: unable to enumerate USB device [ 1387.828690] usb 2-1.1: new high-speed USB device number 5 using ehci-pci [ 1387.938383] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=5f06 [ 1387.938387] usb 2-1.1: New USB device strings: Mfr=1, Product=11, SerialNumber=3 [ 1387.938390] usb 2-1.1: Product: Samsung STORY Station [ 1387.938392] usb 2-1.1: Manufacturer: JMicron [ 1387.938394] usb 2-1.1: SerialNumber: 0000002CE09310500C0B [ 1387.939303] usb-storage 2-1.1:1.0: USB Mass Storage device detected [ 1387.939465] scsi host4: usb-storage 2-1.1:1.0 [ 1388.996079] scsi 4:0:0:0: Direct-Access Samsung STORY Station PQ: 0 ANSI: 2 CCS [ 1388.996346] sd 4:0:0:0: Attached scsi generic sg1 type 0 [ 1388.997051] sd 4:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [ 1388.998191] sd 4:0:0:0: [sdb] Write Protect is off [ 1388.998193] sd 4:0:0:0: [sdb] Mode Sense: 28 00 00 00 [ 1388.999274] sd 4:0:0:0: [sdb] No Caching mode page found [ 1388.999279] sd 4:0:0:0: [sdb] Assuming drive cache: write through [ 1389.194081] sdb: sdb1 [ 1389.197639] sd 4:0:0:0: [sdb] Attached SCSI disk [ 1390.466170] XFS (sdb1): Mounting V4 Filesystem [ 1392.601746] XFS (sdb1): Ending clean mount guppy:~ # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.8G 0 2.8G 0% /dev tmpfs 2.9G 8.0K 2.9G 1% /dev/shm tmpfs 2.9G 1.7M 2.9G 1% /run tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup /dev/sdc2 20G 12G 8.9G 56% / /dev/sda1 4.6T 3.1T 1.6T 67% /MyLib /dev/sdc3 276G 7.8G 269G 3% /home tmpfs 576M 0 576M 0% /run/user/481 tmpfs 576M 0 576M 0% /run/user/0 /dev/sdb1 1.4T 922G 475G 67% /MyDisk Notice that the /MyDisk file system was removed (=unmounted) and added to the end of the list of mounted file systems (=mounted) again. These 2 file systems (/MyLib and /MyDisk) are on 2 external USB disks. Should those disks disappear during/after a suspend=resume and is my file system even safe a suspend/resume ??? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c5 --- Comment #5 from Gerben Jansen <gerben.jansen(a)aol.com> --- Created attachment 795780 --> http://bugzilla.suse.com/attachment.cgi?id=795780&action=edit output of "dmesg > file" run after the suspend/resume of the NFS server -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c4 --- Comment #4 from Gerben Jansen <gerben.jansen(a)aol.com> --- Scenario: boot manta (NFS-client) boot guppy (NFS-server) manta: mount /MyDisk manta: mount | grep MyDisk manta: umount /MyDisk guppy: systemctl suspend guppy: press power button guppy: systemctl status nfsserver nfs-mountd nfs-server nfs-idmapd ● nfsserver.service - Alias for NFS server Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled) Active: inactive (dead) since Fri 2019-02-01 09:14:55 CET; 1min 16s ago Main PID: 1270 (code=exited, status=0/SUCCESS) Feb 01 09:12:30 guppy systemd[1]: Starting Alias for NFS server... Feb 01 09:12:30 guppy systemd[1]: Started Alias for NFS server. Feb 01 09:14:55 guppy systemd[1]: Stopped Alias for NFS server. ● nfs-mountd.service - NFS Mount Daemon Loaded: loaded (/usr/lib/systemd/system/nfs-mountd.service; static; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-mountd.service.d └─options.conf Active: inactive (dead) since Fri 2019-02-01 09:14:55 CET; 1min 16s ago Main PID: 1871 (code=exited, status=0/SUCCESS) Feb 01 09:12:42 guppy systemd[1]: Starting NFS Mount Daemon... Feb 01 09:12:42 guppy rpc.mountd[1871]: Version 2.1.1 starting Feb 01 09:12:42 guppy systemd[1]: Started NFS Mount Daemon. Feb 01 09:13:31 guppy rpc.mountd[1871]: authenticated mount request from 192.168.2.141:953 for /MyDisk (/MyDisk) Feb 01 09:13:53 guppy rpc.mountd[1871]: authenticated unmount request from 192.168.2.141:935 for /MyDisk (/MyDisk) Feb 01 09:14:55 guppy systemd[1]: Stopping NFS Mount Daemon... Feb 01 09:14:55 guppy rpc.mountd[1871]: Caught signal 15, un-registering and exiting. Feb 01 09:14:55 guppy systemd[1]: Stopped NFS Mount Daemon. ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─nfsserver.conf, options.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: inactive (dead) since Fri 2019-02-01 09:14:55 CET; 1min 16s ago Process: 2615 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) Process: 2614 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 2611 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS) Main PID: 1881 (code=exited, status=0/SUCCESS) Feb 01 09:12:42 guppy systemd[1]: Starting NFS server and services... Feb 01 09:12:43 guppy systemd[1]: Started NFS server and services. Feb 01 09:14:55 guppy systemd[1]: Stopping NFS server and services... Feb 01 09:14:55 guppy systemd[1]: Stopped NFS server and services. ● nfs-idmapd.service - NFSv4 ID-name mapping service Loaded: loaded (/usr/lib/systemd/system/nfs-idmapd.service; static; vendor preset: disabled) Active: inactive (dead) since Fri 2019-02-01 09:14:55 CET; 1min 16s ago Main PID: 1171 (code=killed, signal=TERM) Feb 01 09:12:26 guppy systemd[1]: Starting NFSv4 ID-name mapping service... Feb 01 09:12:27 guppy systemd[1]: Started NFSv4 ID-name mapping service. Feb 01 09:14:55 guppy systemd[1]: Stopping NFSv4 ID-name mapping service... Feb 01 09:14:55 guppy systemd[1]: Stopped NFSv4 ID-name mapping service. manta:~ # mount /MyDisk mount.nfs: requested NFS version or transport protocol is not supported guppy: systemctl restart nfs-server manta:~ # mount /MyDisk manta:~ # mount | grep MyDisk guppy:/MyDisk on /MyDisk type nfs (rw,nosuid,nodev,noexec,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.132,mountvers=3,mountport=20048,mountproto=udp,local_lock=none,addr=192.168.2.132,user) manta:~ # umount /MyDisk So indeed that gets nfsd running again. guppy: boot with debug printk.devkmsg=on guppy: suspend / resume dmesg > file I attached the dmesg output seperately, but i noticed it contains (after the resume): [ 133.181371] nfsd: last server has exited, flushing export cache [ 133.249196] usb 1-1.5: device descriptor read/64, error -32 [ 133.313786] XFS (sdc1): Unmounting Filesystem [ 133.313855] XFS (sdc1): metadata I/O error: block 0x575e22c7 ("xlog_iodone") error 5 numblks 64 [ 133.313860] XFS (sdc1): xfs_do_force_shutdown(0x2) called from line 1245 of file ../fs/xfs/xfs_log.c. Return address = 0xffffffffa056d579 [ 133.313873] XFS (sdc1): Log I/O Error Detected. Shutting down filesystem [ 133.313875] XFS (sdc1): Please umount the filesystem and rectify the problem(s) [ 133.313880] XFS (sdc1): Unable to update superblock counters. Freespace may not be correct on next mount. This amazes me highly because sdc1 is the swap device and doesn't contain an XFS file system. I have: guppy:~ # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.8G 0 2.8G 0% /dev tmpfs 2.9G 8.0K 2.9G 1% /dev/shm tmpfs 2.9G 1.7M 2.9G 1% /run tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup /dev/sdc2 20G 12G 8.9G 56% / /dev/sdb1 1.4T 922G 475G 67% /MyDisk /dev/sda1 4.6T 3.1T 1.6T 67% /MyLib /dev/sdc3 276G 7.8G 269G 3% /home tmpfs 576M 0 576M 0% /run/user/481 tmpfs 576M 0 576M 0% /run/user/0 The MyDisk file system is on sdb1. Just to be sure I ran "xfs_repair -n" on sdc1 and as expected that didn't work: guppy:~ # xfs_repair -n /dev/sdc1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .......................................................^C Anyway, give it your thoughts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121276] New: x-initrd.mount in fstab does not work with overlayfs and x-systemd.requires-mounts-for
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1121276 Bug ID: 1121276 Summary: x-initrd.mount in fstab does not work with overlayfs and x-systemd.requires-mounts-for Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: fbui(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: iforster(a)suse.com, kukuk(a)suse.com Found By: --- Blocker: --- Having entries with "x-initrd.mount" in /etc/fstab means that those will be mounted before switching root, i.e. in the initrd's context. systemd-fstab-generator correctly prefixes the destination path with /sysroot in that case, but forgets to do it for "x-systemd.requires-mounts-for" and overlayfs specific parameters such as "workdir", "upperdir" and "lowerdir". Example: overlay /etc overlay defaults,lowerdir=/etc,upperdir=/var/lib/overlay/etc,workdir=/var/lib/overlay/work-etc,x-systemd.requires-mounts-for=/var,x-initrd.mount 0 0 Does not work, but overlay /etc overlay defaults,lowerdir=/sysroot/etc,upperdir=/sysroot/var/lib/overlay/etc,workdir=/sysroot/var/lib/overlay/work-etc,x-systemd.requires-mounts-for=/sysroot/var,x-initrd.mount 0 does. There is no workaround available, as adding the /sysroot prefix would break mounting outside of the initrd and also once this bug is fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1118862] [Snapshot 20180508] issue-generator doesn't ignore temporary files generating undesired content for /etc/issue
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1118862 http://bugzilla.suse.com/show_bug.cgi?id=1118862#c7 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kukuk(a)suse.com) | --- Comment #7 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Sergio Lindo Mansilla from comment #6) > Even if you don't want to spend time on this. Could you give me a > confirmation if you agree with my proposal so I could take it and provide a > SR? I will always accept useful enhancements. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123898] new rule for libmtp-udev
by bugzilla_noreply＠novell.com 01 Feb '19

01 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123898 http://bugzilla.suse.com/show_bug.cgi?id=1123898#c2 --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- can you run lsusb -v and paste the part from charger mode? I think it will likely just seem to be a "HID" device there, and we would need to know what HID control to send to turn it back on. -- You are receiving this mail because: You are on the CC list for the bug.

1 0