Re: Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Matthias Urlichs: "Re: nasty inode leak in 2.1.125? details"
• Previous message: Andreas Schwab: "Re: halted system still working as router."
• Maybe in reply to: linuxconf@qad-integral.de: "Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"
• Next in thread: Olaf Kirch: "Re: Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"

That's an inode hash collision in the NFS server. It happens. Use knfsd,
or simply do this

$ mv badfile /fsroot/lost+found
$ cp -a /fsroot/lost+found/badfile .

thereby giving badfile a new inode number and thus solving the immediate
problem.

[ Now if only knfsd would traverse mountpoints like the user-level nfsd... ]

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661
The quote was selected randomly. Really.    |      http://www.noris.de/~smurf/
-- 
Fear and dull disposition, lukewarmness and sloth, are not seldom
wont to cloak themselves under the affected name of Moderation.
                        -- John Milton (1608-1674)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/






 Next message: Matthias Urlichs: "Re: nasty inode leak in 2.1.125? details"
 Previous message: Andreas Schwab: "Re: halted system still working as router."
 Maybe in reply to: linuxconf@qad-integral.de: "Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"

 Next in thread: Olaf Kirch: "Re: Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"