crash NFS v3 Squeeze depuis client NFS v3 Jessie
Bonjour,
Je rencontre un problème qui fait crasher le service rpc.statd et rend inutilisable le serveur. Seule solution, rebooter. Est-ce que vous pouvez m'aider à troubleshooter?
Configuration :
Serveur NFS :
Debian 6.0.4 , kernel : 2.6.32-5-amd64 #1 SMP Mon Jan 16 16:22:28 UTC 2012 x86_64 GNU/Linux
nfs-kernel-server 1:1.2.2-4squeeze2
cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/home IP_CLIENT(rw,sync,insecure,no_subtree_check,no_root_squash)
cat /etc/default/nfs-kernel-server
# Number of servers to start up
RPCNFSDCOUNT=8
# Runtime priority of server (see nice(1))
RPCNFSDPRIORITY=0
# Options for rpc.mountd.
# If you have a port-based firewall, you might want to set up # a fixed port here using the --port option. For more information, # see rpc.mountd(8) or http://wiki.debian.org/?SecuringNFS
RPCMOUNTDOPTS="-p 32767 --manage-gids"
# Do you want to start the svcgssd daemon? It is only required for Kerberos # exports. Valid alternatives are "yes" and "no"; the default is "no".
NEED_SVCGSSD=
# Options for rpc.svcgssd.
RPCSVCGSSDOPTS=
#desactive version4
RPCNFSDARGS="-N 4"
Le filesystem du serveur NFS est EXT3. Le FS /home exporté en NFS est un cluster OCFS2
Client NFS:
Debian 8.1, kernel : Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux
Client NFS: nfs-common 1:1.2.8-9 amd64
Nfs-common :
STATDOPTS="--port 32765 --outgoing-port 32766"
Le client NFS vient d'être mis à jour en Debian 8.1. Le filesystem est EXT4.
Le crash se produit lors d'un accès NFS par le client en debian 8.1. Aucun problème avec les versions antérieures.
Logs syslog du serveur NFS :
kernel: [ 2830.015303] statd: server rpc.statd not responding, timed out
kernel: [ 2830.015332] lockd: cannot monitor HOSTNAME
kernel: [ 7609.529427] RPC: Want update, refage=1800, age=756
kernel: [29263223.563903] INFO: task photoget:23178 blocked for more than 120 seconds.
kernel: [29263223.564059] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: [29263223.564145] photoget D 0000000000000000 0 23178 22831 0x00000000
kernel: [29263223.564149] ffff8801bf0af100 0000000000000086 0000000000000000 ffffffffa02648a6
kernel: [29263223.564152] 000000000003adac 00000000fffffff5 000000000000f9e0 ffff88014d70bfd8
kernel: [29263223.564154] 0000000000015780 0000000000015780 ffff8801bbd14db0 ffff8801bbd150a8
kernel: [29263223.564157] Call Trace:
kernel: [29263223.564177] [<ffffffffa02648a6>] ? rpc_sleep_on+0x2e2/0x31d [sunrpc]
kernel: [29263223.564182] [<ffffffffa0260297>] ? xprt_transmit+0x17b/0x25a [sunrpc]
kernel: [29263223.564189] [<ffffffffa02e7e60>] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
kernel: [29263223.564193] [<ffffffff812fb9ca>] ? io_schedule+0x73/0xb7
kernel: [29263223.564198] [<ffffffffa02e7e69>] ? nfs_wait_bit_uninterruptible+0x9/0xd [nfs]
kernel: [29263223.564201] [<ffffffff812fbed7>] ? __wait_on_bit+0x41/0x70
kernel: [29263223.564204] [<ffffffff81192154>] ? __lookup_tag+0xad/0x11b
kernel: [29263223.564209] [<ffffffffa02e7e60>] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
kernel: [29263223.564212] [<ffffffff812fbf71>] ? out_of_line_wait_on_bit+0x6b/0x77
kernel: [29263223.564215] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23
kernel: [29263223.564221] [<ffffffffa02ebe0b>] ? nfs_sync_mapping_wait+0xfa/0x227 [nfs]
kernel: [29263223.564227] [<ffffffffa02ec5f2>] ? nfs_write_mapping+0x69/0x8e [nfs]
kernel: [29263223.564231] [<ffffffffa02df429>] ? nfs_do_fsync+0x1c/0x44 [nfs]
kernel: [29263223.564234] [<ffffffff810ed3ea>] ? filp_close+0x37/0x62
kernel: [29263223.564236] [<ffffffff810ed4a9>] ? sys_close+0x94/0xcd
kernel: [29263223.564239] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
Cordialement,
Anthony
Pensez environnement, n'imprimez que si nécessaire.
Reply to: