public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kurt Roeckx <Q@ping.be>
To: bert hubert <ahu@ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: fsck on ext3 after 20 mounts reports i_blocks=n should be m
Date: Sat, 6 Apr 2002 02:11:09 +0200	[thread overview]
Message-ID: <20020406021109.A391@ping.be> (raw)
In-Reply-To: <20020405235647.A29670@outpost.ds9a.nl>

On Fri, Apr 05, 2002 at 11:56:47PM +0200, bert hubert wrote:
> Hi people,
> 
> My laptop which runs 2.5.6 today decided to fsck / because it had been
> mounted 20 times. During those 20 times I think it had in the order of 5
> unclean shutdowns (empty battery mostly), all of them running 2.5.6
> according to 'last'.
> 
> The fsck reports, from what I can recall:
> 
> inode X i_blocks=n, should be m. FIXED

This happens when your fs was full.  Andrew Morton mailed a patch
to the list a few days ago.


Kurt


  reply	other threads:[~2002-04-06  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 21:56 fsck on ext3 after 20 mounts reports i_blocks=n should be m bert hubert
2002-04-06  0:11 ` Kurt Roeckx [this message]
2002-04-06 11:51   ` bert hubert

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=20020406021109.A391@ping.be \
    --to=q@ping.be \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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