public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles-Edouard Ruault <cruault@724.com>
To: linux-kernel@vger.kernel.org
Subject: ext2 corruption in 2.4.0 (again)
Date: Wed, 24 Jan 2001 14:40:09 -0800	[thread overview]
Message-ID: <3A6F59C9.52740813@724.com> (raw)

I've seen on Kernel Traffic that some people have reported an ext2
corruption with kernel 2.4.0.
It happened to me yesterday with a different configuration than the one
reported on the original posting so i just want to report the problem
again :
I was doing some standard work on my system and after issuing a ls in /
i saw some weird info displayed ( very huge files, strange permissions
etc ... ),
after a while i had a kernel panic with the following message :

ext2-fs panic ( device ide0(3,1)) : load_block_bitmap : block_group >=
groups_count - block_group =302292 group_count=226
and the system died.
I tried to reboot, i did not work ( unable to mount root partition )
I booted in redhat-rescue mode and tried to run fsck on my root
filesystem, it did not recognized the superblock so  i used another
superblock and it was reporting almost all the inodes corrupted. I tried
to repair what could be repaired without success. I ended up
reformatting my HD and reinstalling the system ( first time it happens
to me in 6 years of Linux ).

Here's some info on my system :

Hardware :
Pentium III 550Mhz
384 MB RAM
IDE hard drive : FUJITSU MPC3064AT ( /dev/hda )

here's the content of /proc/pci :
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel 440BX - 82443BX Host (rev 3).
      Medium devsel.  Master Capable.  Latency=64.
      Prefetchable 32 bit memory at 0xf8000000 [0xf8000008].
  Bus  0, device   1, function  0:
    PCI bridge: Intel 440BX - 82443BX AGP (rev 3).
      Medium devsel.  Master Capable.  Latency=128.  Min Gnt=140.
  Bus  0, device   7, function  0:
    ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No
bursts.
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.
Latency=64.
      I/O at 0x1060 [0x1061].
  Bus  0, device   7, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master
Capable.  Latency=64.
      I/O at 0x1040 [0x1041].
  Bus  0, device   7, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
      Medium devsel.  Fast back-to-back capable.
  Bus  0, device  12, function  0:
    Multimedia audio controller: Unknown vendor Unknown device (rev 3).
      Vendor id=1073. Device id=c.
      Medium devsel.  IRQ 10.  Master Capable.  Latency=64.  Min
Gnt=5.Max Lat=25.
      Non-prefetchable 32 bit memory at 0xf4000000 [0xf4000000].
  Bus  0, device  15, function  0:
    Ethernet controller: Intel 82557 (rev 8).
      Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master
Capable.  Latency=66.  Min Gnt=8.Max Lat=56.
      Non-prefetchable 32 bit memory at 0xf4008000 [0xf4008000].
      I/O at 0x1000 [0x1001].
      Non-prefetchable 32 bit memory at 0xf4100000 [0xf4100000].
  Bus  1, device   0, function  0:
    VGA compatible controller: Intel Unknown device (rev 33).
      Vendor id=8086. Device id=7800.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
Capable.  No bursts.
      Prefetchable 32 bit memory at 0xf5000000 [0xf5000008].
      Non-prefetchable 32 bit memory at 0xf4200000 [0xf4200000].

Software:
kernel 2.4.0 on a redhat 7.0 (compiled with kgcc).
I upgraded the following packages ( following the
/usr/src/linux/Documentation/Changes document ) :
e2fsprogs-1.19-0.2.i386.rpm
iptables-1.1.1-2.i386.rpm
util-linux-2.10p-2.i386.rpm
e2fsprogs-devel-1.19-0.2.i386.rpm
modutils-2.4.0-1.i386.rpm

that's about it ....
I hope this helps !
keep on the great work !

regards
Charles-Edouard Ruault

-
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-24 22:38 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=3A6F59C9.52740813@724.com \
    --to=cruault@724.com \
    --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