From: Andreas Dilger <adilger@sun.com>
To: "J�rg Sommer" <joerg@alea.gnuu.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 fails on ext2 filesystems
Date: Tue, 20 Jan 2009 07:30:59 +0800 [thread overview]
Message-ID: <20090119233059.GH3286@webber.adilger.int> (raw)
In-Reply-To: <20090118013516.GA4876@alea.gnuu.de>
On Jan 18, 2009 02:35 +0100, J�rg Sommer wrote:
> I've an ext2 filesystem as root filesystem, because it's mounted readonly
> for the most part. I've built in the support for ext[234] in the kernel.
> Ext4 takes precedence over ext2 and it mounts the root filesystem:
Hmm, probably an unintended consequence of the newly-added patch to
allow ext4 to mount ext2 filesystems.
> But when remounting the filesystem read/write and changing a file, the
> changes are written to the filesystem, but it's remounted readonly
> immediatly. I've set the mount option remount-ro.
>
> [ 203.082300] EXT4 FS on hda3, no journal
> [ 205.746713] EXT4-fs error (device hda3): ext4_free_data: circular indirect block detected, inode=165056, block=184476
> motherboard : PowerBook6,3 MacRISC3 Power Macintosh
Hmm, looks like it might be a bug in the endian conversion?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-19 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 1:35 ext4 fails on ext2 filesystems Jörg Sommer
2009-01-18 2:38 ` Theodore Tso
2009-01-18 10:04 ` Jörg Sommer
2009-01-20 14:51 ` Theodore Tso
2009-01-21 18:45 ` Jörg Sommer
2009-01-21 19:58 ` Theodore Tso
2009-01-19 23:30 ` Andreas Dilger [this message]
2009-01-20 13:56 ` Jörg Sommer
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=20090119233059.GH3286@webber.adilger.int \
--to=adilger@sun.com \
--cc=joerg@alea.gnuu.de \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.