Re: Strange umount problem in latest 2.4.0 kernels

[Alexander Viro]

On Thu, 11 Jan 2001, Daniel Phillips wrote:

> "Udo A. Steinberg" wrote:
> > Upon fscking after reboot, I always have errors on a
> > single inode and it's always the same one:
> > 
> > /dev/hdb1: Inode 522901, i_blocks is 64, should be 8. FIXED
> > 
> > Can someone tell me an easy and reliable way of figuring
> > out which file (program) uses said inode? I think that's
> > probably the key to figuring out why the partition is
> > busy on umount.
> 
> ls -iR | grep 12345

find `mount | grep hdb1 | cut -f3 -d' '` -inum 522901 -xdev

- no need to walk through all filesystems.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/