Hallo Liste,
Loop Detection, Bug oder gibt es eine Lösung?
Trat plötzlich auf:
Beide Systeme:
# uname -a
Linux SERVER 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux
# cat /etc/debian_version
7.0
# dpkg
-l nfs-*
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-=================================-=====================-=====================-========================================================================
un
nfs-client <keine> (keine Beschreibung vorhanden)
ii nfs-common 1:1.2.6-3 amd64 NFS support files common to client and server
ii nfs-kernel-server
1:1.2.6-3 amd64 support for NFS kernel server
un nfs-server <keine> (keine Beschreibung vorhanden)
# dpkg -l
linux-image-3.2.0-4-*
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-=================================-=====================-=====================-========================================================================
ii linux-image-3.2.0-4-amd64
3.2.41-2+deb7u2 amd64 Linux 3.2 for 64-bit PCs
Client:
# rpcdebug -m nfs -s proc
# ls -l /nfsshare/DIR/FILE.txt
-rw-r--r-- 1 root root 13 Mai 21 12:25 FILE.txt
# cat /nfsshare/DIR/FILE.txt
[hängt]
neue Shell:
# cat /var/log/messages
kernel: [60349.587557] <-- nfs4_setup_sequence status=0
....
# rpcdebug -m nfsd -s proc
# cat /var/log/messages
May 22 08:19:18 SERVER kernel: [5263747.978053] NFSD: nfsd4_open_confirm on file FILE.txt
May 22 08:19:18 SERVER kernel: [5263747.978057] NFSD: nfs4_preprocess_seqid_op: seqid=1 stateid = (519b2708/0000094c/4028cedf/00000001)
May 22 08:19:18 SERVER kernel: [5263747.978061] renewing client (clientid 519b2708/0000094c)
May 22 08:19:18 SERVER kernel: [5263747.978065] nfsv4 compound op ffff88010fc30078 opcnt
2 #2: 20: status 10025
May 22 08:19:18 SERVER kernel: [5263747.978068] nfsv4 compound returned 10025
May 22 08:19:18 SERVER kernel: [5263747.978268] nfsv4 compound op #1/7: 22 (OP_PUTFH)
May 22 08:19:18 SERVER kernel: [5263747.978273] nfsv4 compound op ffff88010fc30078 opcnt 7 #1: 22: status 0
May 22 08:19:18 SERVER kernel: [5263747.978275] nfsv4 compound op #2/7: 32 (OP_SAVEFH)
May 22 08:19:18 SERVER kernel: [5263747.978277] nfsv4 compound op ffff88010fc30078 opcnt 7 #2: 32: status 0
May 22 08:19:18 SERVER kernel: [5263747.978278] nfsv4 compound op #3/7: 18 (OP_OPEN)
May 22 08:19:18 SERVER kernel: [5263747.978280] NFSD: nfsd4_open filename FILE.txt op_openowner (null)
May 22 08:19:18 SERVER kernel: [5263747.978304] renewing client (clientid 519b2708/0000094c)
May 22 08:19:18 SERVER kernel: [5263747.979795] nfsd4_process_open2:
stateid=(519b2708/0000094c/4028cee0/00000001)
May 22 08:19:18 SERVER kernel: [5263747.979800] nfsv4 compound op ffff88010fc30078 opcnt 7 #3: 18: status 0
May 22 08:19:18 SERVER kernel: [5263747.979802] nfsv4 compound op #4/7: 10 (OP_GETFH)
May 22 08:19:18 SERVER kernel: [5263747.979803] nfsv4 compound op ffff88010fc30078 opcnt 7 #4: 10: status 0
May 22 08:19:18 SERVER kernel: [5263747.979805] nfsv4 compound op #5/7: 9 (OP_GETATTR)
May 22 08:19:18 SERVER kernel: [5263747.979813] nfsv4 compound op ffff88010fc30078 opcnt 7 #5: 9: status 0
May 22 08:19:18 SERVER kernel: [5263747.979815] nfsv4 compound op #6/7: 31 (OP_RESTOREFH)
May 22 08:19:18 SERVER kernel: [5263747.979817] nfsv4 compound op ffff88010fc30078 opcnt 7 #6: 31: status 0
May 22 08:19:18 SERVER kernel: [5263747.979818] nfsv4 compound op #7/7: 9 (OP_GETATTR)
May 22 08:19:18 SERVER kernel: [5263747.979822] nfsv4 compound op ffff88010fc30078 opcnt 7 #7: 9: status 0
May
22 08:19:18 SERVER kernel: [5263747.979823] nfsv4 compound returned 0
May 22 08:19:18 SERVER kernel: [5263747.980032] nfsv4 compound op #1/2: 22 (OP_PUTFH)
May 22 08:19:18 SERVER kernel: [5263747.980040] nfsv4 compound op ffff88010fc30078 opcnt 2 #1: 22: status 0
May 22 08:19:18 SERVER kernel: [5263747.980042] nfsv4 compound op #2/2: 20 (OP_OPEN_CONFIRM)
May 22 08:19:18 SERVER kernel: [5263747.980044] NFSD: nfsd4_open_confirm on file FILE.txt
May 22 08:19:18 SERVER kernel: [5263747.980046] NFSD: nfs4_preprocess_seqid_op: seqid=1 stateid = (519b2708/0000094c/4028cee0/00000001)
May 22 08:19:18 SERVER kernel: [5263747.980048] renewing client (clientid 519b2708/0000094c)
May 22 08:19:18 SERVER kernel: [5263747.980051] nfsv4 compound op ffff88010fc30078 opcnt 2 #2: 20: status 10025
May 22 08:19:18 SERVER kernel: [5263747.980052] nfsv4 compound returned 10025
May 22 08:19:18 SERVER kernel: [5263747.980242] nfsv4 compound op #1/7: 22
(OP_PUTFH)
May 22 08:19:18 SERVER kernel: [5263747.980248] nfsv4 compound op ffff88010fc30078 opcnt 7 #1: 22: status 0
May 22 08:19:18 SERVER kernel: [5263747.980249] nfsv4 compound op #2/7: 32 (OP_SAVEFH)
May 22 08:19:18 SERVER kernel: [5263747.980251] nfsv4 compound op ffff88010fc30078 opcnt 7 #2: 32: status 0
May 22 08:19:18 SERVER kernel: [5263747.980253] nfsv4 compound op #3/7: 18 (OP_OPEN)
May 22 08:19:18 SERVER kernel: [5263747.980254] NFSD: nfsd4_open filename FILE.txt op_openowner (null)
....
Der Fehler wurde erstmals analysiert.
Wahrscheinlich der gleiche Fehler wurde behoben durch ein Neustart.
Danke im voraus für die Hilfe
MfG
Thorsten