Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
NFS oddities with MacOX X clients
Hello
I have a NFS server that has frequent crashes which I suspect to be
caused by MacOS X NFS client.
Last problem encountered: a directory gets inaccssible:
ls -ld directory fails with "bad file descriptor", so does stat(1).
hexdump directory shows only zeros. cd says that the directory does not
exist.
I tried to unmount to run fsck, the umount command got stuck (in vnode)
and was unkillable by kill -9. The filesystem was unmounted anyway, but
fsck would hang without doing anything on it. It was possible to kill
fsck, though.
Dropping in single user does not improve. An attempt to reboot caused an
attempt to sync the disks (it gave up) , and ended with the machine
frozen on its console. It was still possible to get into ddb, but a
reboot from ddb did not manage to restart the machine.
After reboot, the filesystem is in an ugly shape and needs a manual
fsck. See below. Isn't it horrible?
Anyone experiencing the same troubles? This is netbsd-5 from 2008/11/08
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=14866827 (240 should be 224)
PARTIALLY ALLOCATED INODE I=14979364
PARTIALLY ALLOCATED INODE I=14979367
UNKNOWN FILE TYPE I=14979368
UNKNOWN FILE TYPE I=14979369
UNKNOWN FILE TYPE I=14979371
UNKNOWN FILE TYPE I=14979372
PARTIALLY ALLOCATED INODE I=14979380
PARTIALLY ALLOCATED INODE I=14979381
UNKNOWN FILE TYPE I=14979382
UNKNOWN FILE TYPE I=14979383
UNKNOWN FILE TYPE I=14979384
UNKNOWN FILE TYPE I=14979385
UNKNOWN FILE TYPE I=14979386
PARTIALLY ALLOCATED INODE I=14979387
UNKNOWN FILE TYPE I=14979388
UNKNOWN FILE TYPE I=14979389
UNKNOWN FILE TYPE I=14979390
UNKNOWN FILE TYPE I=14979391
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost
Home |
Main Index |
Thread Index |
Old Index