Il giorno Mer 09 Giu 2010 10:04:39 CET, Neil Brown ha scritto:
[...]
Seems unlikely ... "exportfs -f" flushes all the export caches in the kernel
thus letting go of any filesystems.
I guess an active NFS request could still hold the fs active, but that should
complete fairly quickly.
file locking might be an issue. Might a client have a lock on some file in
the filesystem? Failover of locks is rather more complicated that simple
file-access fail-over. I don't recall what the status of this is currently.
When the umount files, check the content of
/proc/net/rpc/nfsd.export/content
and
/proc/locks
to check what is actually using the filesystem.
Note that I'm mounting from the client with nolock option.
Here is the output of the two cat:
/proc/net/rpc/nfsd.export/content:
#path domain(flags)#012#
/share-a#011192.168.1.0/24(rw,no_root_squash,sync,wdelay,crossmnt,no_subtree_check,fsid=1,uuid=7c80c4af:2a244b39:af
adb554:8c8e0574)
/proc/locks:
1: POSIX ADVISORY WRITE 753 00:11:3923 0 EOF#0122: FLOCK ADVISORY
WRITE 739 00:11:3916 0 EOF#0123: POSIX ADVISORY WRITE 522 00:11:3049
0 EOF
What do you think about it?
Thanks a lot!
--
RaSca
Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene!
rasca@xxxxxxxxxxxxxxxxxxxx
http://www.miamammausalinux.org
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
