public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>,
	linux-kernel@vger.kernel.org
Subject: Re: Strange umount problem in latest 2.4.0 kernels
Date: Thu, 11 Jan 2001 19:33:08 +0100	[thread overview]
Message-ID: <3A5DFC64.2969D25E@innominate.de> (raw)
In-Reply-To: <3A5DF9CC.2F614F2A@Hell.WH8.TU-Dresden.De>

"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

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-11 18:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 18:22 Strange umount problem in latest 2.4.0 kernels Udo A. Steinberg
2001-01-11 18:33 ` Daniel Phillips [this message]
2001-01-11 18:41   ` Alexander Viro
2001-01-11 19:24     ` Udo A. Steinberg
2001-01-11 19:32       ` Alexander Viro
2001-01-11 20:26         ` Udo A. Steinberg
2001-01-11 20:56       ` Udo A. Steinberg
2001-01-11 21:34         ` Alan Cox
2001-01-11 23:04         ` David Ford
2001-01-11 21:42       ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11 22:34 Andries.Brouwer
2001-01-11 22:46 ` Udo A. Steinberg
2001-01-11 23:23 ` J . A . Magallon
2001-01-12  8:05   ` Christoph Rohland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A5DFC64.2969D25E@innominate.de \
    --to=phillips@innominate.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sorisor@Hell.WH8.TU-Dresden.De \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox