lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f188924b0803111635k42a186c6nc616fa05a830d9b7@mail.gmail.com>
Date:	Wed, 12 Mar 2008 00:35:36 +0100
From:	"Fred ." <eldmannen@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: EXT3-fs error corruption

I am running Ubuntu 8.04 "Hardy Heron" (alpha).

MSI P35 Neo
Samsung SpinPoint T166 500 gb (7200 rpm, SATA-2, 16 mb cache)
Samsung SpinPoint T166 250 gb (7200 rpm, SATA-2, 16 mb cache)

sda1 = Windows XP
sdb1 = Linux

So I am listening to MP3 music in Rhythmbox 0.11.4, and surfing with
Mozilla Firefox 3.0b3 and perhaps doing some other stuff, like maybe
running apt-update && upgrade && clean && autoclean && autoremove or
something in a Terminal or something.

And then my computer becomes unresponsive. The HDD LED shine all the
time on the computer case.

Then I do Ctrl+Alt+F2 and try to login, and I type my username and
press enter, and it waits there for a while, then it start spit some
error messages, and wont let me in.

Like:
EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read node
block - inode=1599522, block=3211298
And it can spam the console with that kind of stuff.

Then I shut down the computer (by PSU switch), restart and it borked out again.
Shut down computer by PSU switch again, and runned HUTIL v2.10 by
Samsung, a disk diagnostic tool that checks SMART, does disk spin up,
spin down, read surface scan, and couple other diagnostic stuff. It
reported no errors, and said the disk were okay.

Then I rebooted into my old Ubuntu 7.04 "Gutsy Gibbon" LiveCD and run
some commands to fix it.
$ sudo e2fsck -pcf /dev/sdb1
$ sudo badblocks -sv /dev/sdb1

After that, computer worked again.
But today (next day), my computer borked out again.
In the same way and started spitting out error messages...

[20061.478996] journal commit I/O error
[numbers] EXT3-fs error (device sdb1): ext3_find_entry: reading
directory #2399041 offset 0

and stuff like:
[numbers] EXT3-fs error (device sdb1): ext3_reserve_inode_write:
Journal has aborted

It happened when I was using the 2.6.24-11-386 kernel.
I am scared, I don't know if my hard disk maybe is broken. Samsung's
HUTIL said the hard disk was okay.
But now it happened more than once, and maybe its a bug in the kernel,
or ext3 file system? I don't know. =/

Mar 9 16:46:06 ubuntu kernel: [ 25.735768] ext3_orphan_cleanup:
deleting unreferenced inode 1485173
Mar 9 16:46:06 ubuntu kernel: [ 25.735786] ext3_orphan_cleanup:
deleting unreferenced inode 1501809
Mar 9 16:46:06 ubuntu kernel: [ 25.735794] ext3_orphan_cleanup:
deleting unreferenced inode 1501680
Mar 9 16:46:06 ubuntu kernel: [ 25.735799] ext3_orphan_cleanup:
deleting unreferenced inode 1501678
Mar 9 16:46:06 ubuntu kernel: [ 25.735803] ext3_orphan_cleanup:
deleting unreferenced inode 1501677
Mar 9 16:46:06 ubuntu kernel: [ 25.735808] ext3_orphan_cleanup:
deleting unreferenced inode 1501676
Mar 9 16:46:06 ubuntu kernel: [ 25.735812] ext3_orphan_cleanup:
deleting unreferenced inode 1501675
Mar 9 16:46:06 ubuntu kernel: [ 25.735816] ext3_orphan_cleanup:
deleting unreferenced inode 1501674
Mar 9 16:46:06 ubuntu kernel: [ 25.735821] ext3_orphan_cleanup:
deleting unreferenced inode 1501673
Mar 9 16:46:06 ubuntu kernel: [ 25.735825] ext3_orphan_cleanup:
deleting unreferenced inode 1501672
Mar 9 16:46:06 ubuntu kernel: [ 25.735830] ext3_orphan_cleanup:
deleting unreferenced inode 1501671
Mar 9 16:46:06 ubuntu kernel: [ 25.735834] ext3_orphan_cleanup:
deleting unreferenced inode 1501669
Mar 9 16:46:06 ubuntu kernel: [ 25.735838] ext3_orphan_cleanup:
deleting unreferenced inode 1501668
Mar 9 16:46:06 ubuntu kernel: [ 25.735843] ext3_orphan_cleanup:
deleting unreferenced inode 1501667
Mar 9 16:46:06 ubuntu kernel: [ 25.746330] ext3_orphan_cleanup:
deleting unreferenced inode 1501666
Mar 9 16:46:06 ubuntu kernel: [ 25.746336] ext3_orphan_cleanup:
deleting unreferenced inode 1338406
Mar 9 16:46:06 ubuntu kernel: [ 25.750996] ext3_orphan_cleanup:
deleting unreferenced inode 1504210
Mar 9 16:46:06 ubuntu kernel: [ 25.751001] ext3_orphan_cleanup:
deleting unreferenced inode 1504199
Mar 9 16:46:06 ubuntu kernel: [ 25.751006] ext3_orphan_cleanup:
deleting unreferenced inode 1504191
Mar 9 16:46:06 ubuntu kernel: [ 25.756010] ext3_orphan_cleanup:
deleting unreferenced inode 2872358
Mar 9 16:46:06 ubuntu kernel: [ 25.756019] ext3_orphan_cleanup:
deleting unreferenced inode 1338610
Mar 9 16:46:06 ubuntu kernel: [ 25.756024] ext3_orphan_cleanup:
deleting unreferenced inode 1338441
Mar 9 16:46:06 ubuntu kernel: [ 25.762751] ext3_orphan_cleanup:
deleting unreferenced inode 2415376

https://bugs.launchpad.net/ubuntu/+bug/200747

I would like to get sent a reply to my email, since i don't subscribe
to this list.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ