public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: linux-kernel@vger.kernel.org
Subject: Ext2 descriptor corruption in 2.4.0
Date: Mon, 08 Jan 2001 15:50:12 +0100	[thread overview]
Message-ID: <3A59D3A4.AEE91B1@innominate.de> (raw)

After 3 days up doing fairly normal things with an unremarkable
configuration and a vanila 2.4.0 kernel (nfs) I tried to log out of KDE 
and hung in 'preparing session for logout'.  In a text console, dmesg
showed an infinite number of "Free blocks count corrupted" messages:

  EXT2-fs error (device ide0(3,66)): ext2_new_block: Free blocks count
corrupted for block group 93
  EXT2-fs error (device ide0(3,66)): ext2_new_block: Free blocks count
corrupted for block group 93                                             

and gdb showed all the processes under X waiting in poll or select, not
surprising considering the way ext2 handles this:

  if (j >= EXT2_BLOCKS_PER_GROUP(sb)) {
         ext2_error (sb, "ext2_new_block",
                     "Free blocks count corrupted for block group %d",
i);
         goto out;
  }

I shut down and restarted hoping to get an fsck, but instead continued
past the ext2 mount.  I interrupted that, restarted and fscked, which
turned up a single special file with size 0 and no other problems.

So I think this may be a cache problem.

--
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-08 14:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3A59D3A4.AEE91B1@innominate.de \
    --to=phillips@innominate.de \
    --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