> >
> > Could you look up what inode was involved here? Knowing which fs
> > was involved may give information on
> > the usage pattern. These messages usually indicate a bug in the
> > fs -- inodes aren't supposed to be
> > released with any locks or dentries still attached.
>
> Exactly how would one go about doing that? I don't know of any program which
> shows me what one particular inode is.
OK, start with which fs was using the device in question. Then the inode number
can be found using ls -i or dumpe2fs if it's an ext2 volume.
Regards,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html