On Thu, Jun 29, 2006 at 06:01:54PM -0400, Josef Sipek wrote: > On Thu, Jun 29, 2006 at 05:54:53PM -0400, Josef Sipek wrote: > > Where exactly is unionfs in this? On the clients? > > > > > File/Directory accesses on the diskless client > > > give "Stale File handle" errors. > > > > NFS doesn't like the inode numbers changing on it. You might want to give > > persistent inodes a try. > > > > Which version of unionfs are you using? > > Ah, a snapshot. Try using 1.2.
Thanks, linux-2.6.16-2 from debian, plus unionfs 1.2 with persistent inodes fixes the "fileid changed" problem. However, now I have another problem: Post failover, it seems the NFS client gives a load of "permission denied" errors when accessing *some* (where some can be a small, or large number) files/directories. Failing back doesnt help. I've also tried the nfsro option when mounting the union. Further investigation via ls -l (when ls wasnt impacted...) showed that the file type character was a '?' rather than the usual '-' or 'd'. 'cat'ing a text file in this state made it appear to be an empty file. Best Regards Iain PS, as an aside, I also tried 2.6.17.1 mainline, with unionfs 1.3, but that just gave me permission denied errors on the client when attempting to mount the filesystem, despite everything being correct in /etc/exports etc. I was able to mount non unionfs exports. _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
