Wolfgang Rosner:
> The last signs of life of my NFS client look like
:::
It shows these sequences.
- nfs client sent WRITE
+ nfs server returned OK
- nfs client sent CLOSE
+ nfs server didn't return anything
- nfs client sent READ
+ nfs server didn't return anything
According to the protocol of nfsv4, the server should return OK or error
for CLOSE, which looks like the beginning of this problem.
Still I don't know why, but I agree aufs is the first candidate of this
problem.
> I haven't build a kernel for a decade or so, and back in "good-old-SuSE-tim=
> es"=20
> things (distribution specific patching) worked quite different than in debi=
> an=20
> now. I'm afraid, this will cost me some other days to get it working.
Recently I've post the steps "how to re-build and re-install ubuntu
kernel".
http://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg05005.html
As you might know, the commands on ubuntu is very similar to debian, so
these steps will help you hopefully.
And people who followed this sequence posted about the errors in it, so
you should read the follow-ups too.
And what is the fs-type of your branches?
- /cluster/nfs/nfsroot/wheezy_cow/cow_*
- /cluster/nfs/nfsroot/wheezy_root_config
- /cluster/nfs/nfsroot/wheezy_root_mask
- /cluster/nfs/nfsroot/wheezy
J. R. Okajima
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
