On Fri, 2003-05-16 at 09:46, Nicolas Kowalski wrote:
> Nicolas Kowalski <Nicolas.Kowalski@xxxxxxx> writes:
>
> > Nicolas Kowalski <Nicolas.Kowalski@xxxxxxx> writes:
> >
> >> Hello.
> >>
> >> I am experiencing a very weird behaviour on our main fileserver,
> >> running a 2.4.21-rc2-xfs (cvs yesterday) :
>
> I finally found what was wrong. One of our ~30 Linux NFS clients, with
> a "Stale NFS file handle" which occured during the server reboot was
> causing the errors on the Server.
>
> I still think this is a weird behaviour (nfsd or xfs related, I do not
> know), but this does not matter, as I know now how to resolve it.
>
> Sorry for the noise.
What you saw was an internal trace message from xfs due to an fs
consistency check. Looks like the bad fid was coming down to a
disk block which was not inodes.
These stack traces are intended to diagnose problems with corrupt
filesystems, but they appear to be coming out in a couple of spots
where we do not want them to.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|