[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: My fault (not ext3's!) and kernel panic on 2.4.7 .



On Sun, Jul 29, 2001 at 06:22:17PM +0200, beevis libero it wrote:
> Unwisely I deleted the .journal file, since I never mounted / as ext3.

I assume the ext3 filesystem was created using old e2fsprogs tools;
the new versions will create it as a hidden file that doesn't appear
in the namespace, as long as the filesystem is unmounted --- and even
if it is mounted, the .journal file is created with the immutable flag
set.

> Jul 29 13:11:36 uno fsck: /dev/hda4: Superblock has a bad ext3 journal
> (inode 20).
> Jul 29 13:12:37 uno xinetd[513]: Started working: 0 available services
> Jul 29 13:11:36 uno fsck: CLEARED.
> Jul 29 13:11:36 uno fsck: *** ext3 journal has been deleted - filesystem
> is now ext2 only ***
> Jul 29 13:11:36 uno fsck: /dev/hda4 was not cleanly unmounted, check
> forced.
> Jul 29 13:11:36 uno fsck: /dev/hda4: 236046/2265408 files (2.1%
> non-contiguous), 1415789/4521984 blocks
> ...
> 
> I was certainly wrong deleting the .journal without changing the
> parameters of the ext3 filesystem. However IMHO the kernel should be
> able to correct the situation and revert to ext2 without intervention
> in this case. Rebuilding the journal file is a matter of 1" (at least
> on this mighty machine...).

The kernel wouldn't care if you just deleted the .journal file, as
long as you were mounting using ext2 and the NEEDS_RECOVERY flag
wasn't set.

What happened here was that fsck noticed that the filesystem was
inconsistent, and therefore finished cleaning up the filesystem.  No
big deal; the right thing happened.

							- Ted





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]