linux-kernel - Re: Ext3 mounted as ext2 but journal still in effect.

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1168585021.9707.25.camel@w100>
Date:	Fri, 12 Jan 2007 00:57:01 -0600
From:	Alberto Alonso <alberto@...ys.net>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Ext3 mounted as ext2 but journal still in effect.

You were right, even after making the changes, it seems to be 
telling lies:

# mount
/dev/hda2 on / type ext2 (rw,usrquota)
[...]

However, I think I am still not mounting as ext2:

# dmesg | grep 'Kernel command'
Kernel command line: ro root=/dev/hda2 rootfstype=ext2

# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw 0 0
/proc /proc proc rw,nodiratime 0 0
/sys /sys sysfs rw 0 0
none /dev/pts devpts rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/hda1 /boot ext2 rw 0 0
none /dev/shm tmpfs rw,noexec 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0

Do I need to mess with the initrd? My grub lines look like
this:

title Fedora Core (2.6.5-1.358smp)
        root (hd0,0)
        kernel /vmlinuz-2.6.5-1.358smp ro root=/dev/hda2 rootfstype=ext2
        initrd /initrd-2.6.5-1.358smp.img
title Fedora Core-up (2.6.5-1.358)
        root (hd0,0)
        kernel /vmlinuz-2.6.5-1.358 ro root=/dev/hda2 rootfstype=ext2
        initrd /initrd-2.6.5-1.358.img


Thanks,

Alberto


On Thu, 2007-01-11 at 21:25 -0800, Andrew Morton wrote:
> On Thu, 11 Jan 2007 23:08:16 -0600
> Alberto Alonso <alberto@...ys.net> wrote:
> 
> > I have an ext3 filesystem that has been having problems
> > with its journal. The result is that the file system
> > remounts internally as read-only and the server becomes
> > unusable, even shutdown does not work, using up 100% of
> > the CPU but not rebooting.
> > 
> > I found some postings indicating that mounting it as
> > ext2 should fix the problem, as it doesn't appear to be
> > a hardware issue.
> > 
> > So, I decided to mount everything as ext2. Mount shows this:
> > 
> > # mount
> > /dev/hda2 on / type ext2 (rw,usrquota)
> > none on /proc type proc (rw)
> > none on /sys type sysfs (rw)
> > none on /dev/pts type devpts (rw,gid=5,mode=620)
> > usbfs on /proc/bus/usb type usbfs (rw)
> > /dev/hda1 on /boot type ext2 (rw)
> > none on /dev/shm type tmpfs (rw,noexec)
> > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > 
> > But now I still get the error:
> > 
> > # dmesg
> > [...]
> > EXT3-fs error (device hda2) in start_transaction: Journal has aborted
> > EXT3-fs error (device hda2) in start_transaction: Journal has aborted
> > EXT3-fs error (device hda2) in start_transaction: Journal has aborted
> > EXT3-fs error (device hda2) in start_transaction: Journal has aborted
> > [...]
> > 
> > 
> > The kernel is:
> > 
> > # uname -a
> > Linux hyperweb.net 2.6.5-1.358smp #1 SMP Sat May 8 09:25:36 EDT 2004
> > i686 i686 i386 GNU/Linux
> > 
> > 
> > Any ideas?
> > 
> 
> mount(8) tells lies.  Look in /proc/mounts and you'll see that it's really
> mounted as ext3.
> 
> You probably want to add `rootfstype=ext2' to the kernel boot command line.
> 
-- 
Alberto Alonso                        Global Gate Systems LLC.
(512) 351-7233                        http://www.ggsys.net
Hardware, consulting, sysadmin, monitoring and remote backups

-
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/