ext3 corruption: "JBD: no valid journal superblock found"

ext3 corruption: "JBD: no valid journal superblock found"

[Jan Niehusmann]

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

Currently, I'm experiencing a strange problem with one of my ext3
filesystems: There seems to be some journal corruption, but up to now I
didn't see any sign of hardware problems, so I wonder if there could be
some filesystem bug involved.

The symptoms are the kernel not mounting the filesystem but giving the
following error message:

Oct 31 19:48:18 knautsch kernel: [17179601.724000] JBD: no valid journal superblock found
Oct 31 19:48:18 knautsch kernel: [17179601.724000] EXT3-fs: error loading journal.


e2fsck -n tells me

e2fsck 1.38 (30-Jun-2005)
Superblock has an invalid ext3 journal (inode 8).
Clear? no

e2fsck: Illegal inode number while checking ext3 journal for /dev/vgnb/compile


There are two things I did with the filesystem which may be related to
this: First, on Oct. 27 I did resize the filesystem (umount, lvextend,
e2fsck -f, resize2fs, mount). But after that I did several reboots
without any problems - this is my notebook and I turn it on and off
several times a day.

The second is an unclean shutdown and reboot at Oct 31 19:19:56. At this
boot, the filesystem was still mountable:

Oct 31 19:19:56 knautsch kernel: [17179602.428000] kjournald starting.  Commit interval 5 seconds
Oct 31 19:19:56 knautsch kernel: [17179602.432000] EXT3 FS on dm-4, internal journal
Oct 31 19:19:56 knautsch kernel: [17179602.432000] EXT3-fs: recovery complete.
Oct 31 19:19:56 knautsch kernel: [17179602.440000] EXT3-fs: mounted filesystem with ordered data mode.

(here, I'm assuming the "dm-4" number is stable between reboots,
correct? - Anyways, there were no error messages on that reboot)

The next reboot was the one at 19:48, with the error message quoted
above. So, to me it looks like the recovery at 19:19 did something wrong
and corrupted the journal.

I am just copying the whole filesystem over to another hard disk, so I
can do further analysis on that, later. If you think this could
really indicate some kind of bug, I hope that I can provide additional
information.

Jan


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

Re: ext3 corruption: "JBD: no valid journal superblock found"

[Jan Niehusmann]

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

On Tue, Nov 01, 2005 at 02:42:33PM +0100, Jan Niehusmann wrote:
> Currently, I'm experiencing a strange problem with one of my ext3
> filesystems: There seems to be some journal corruption, but up to now I

Well, of course I forgot one important detail: The kernel version. This
is a 2.6.14 with additional patches for CardMan 4000 support (as posted
on this list by Harald Welte), updated ipw2200 support (from
ipw2200.sourceforge.net) and btsco bluetooth headset support (from
bluetooth-alsa.sourceforge.net).

By now, I did an e2fsck which removed the ext3 journal and recovered the
ext2 without problems - unfortunately I don't have an easy way to verify
if files are corrupted, but up to now everything looks fine.

Jan


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

Re: ext3 corruption: "JBD: no valid journal superblock found"

[Andreas Schwab]

Jan Niehusmann <jan@gondor.com> writes:

> On Tue, Nov 01, 2005 at 02:42:33PM +0100, Jan Niehusmann wrote:
>> Currently, I'm experiencing a strange problem with one of my ext3
>> filesystems: There seems to be some journal corruption, but up to now I
>
> Well, of course I forgot one important detail: The kernel version. This
> is a 2.6.14

I'm also experiencing ext3 corruptions with 2.6.14:

Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7): ext3_free_inode: bit already cleared for inode 482170
Oct 29 17:46:08 igel kernel: Aborting journal on device sda7.
Oct 29 17:46:08 igel kernel: ext3_abort called.
Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7): ext3_journal_start_sb: Detected aborted journal
Oct 29 17:46:08 igel kernel: Remounting filesystem read-only
Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7) in ext3_delete_inode: IO failure

2.6.14-rc5 has been rock solid so far (running on PowerMac G5).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."