[Bug 1120087] NFS server fails after a suspend system
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@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.
participants (1)
-
bugzilla_noreply@novell.com