Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7BIT
MIME-Version: 1.0
From: "dan carpenter" <error27@email.com>
To: linux-kernel@vger.kernel.org
Cc: sct@redhat.com
Date: Fri, 05 Nov 2004 14:30:31 -0500
Subject: ext2/3 issue 2.6 vs 2.4 kernels
Message-Id: <20041105193031.8D8924BE65@ws1-1.us4.outblaze.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1463
Lines: 41

I seem to get filesystem corruption whenever I mount a Fedora 
Core 2 (2.6.5 kernel) with a RedHat 9 rescue CD (2.4.20) or my
other 2.4.18 rescue media and try to chroot to the system image.
I've tried on a few systems so it's not a hardware issue.

Here are the messages I get in dmesg.  They seem file system 
related.

EXT3-fs: mounted filesystem with ordered data mode.
attempt to access beyond end of device
08:02: rw=0, want=1219858868, limit=15767797
attempt to access beyond end of device
08:02: rw=0, want=1219858868, limit=15767797

I haven't been able to reliably reproduce the actual file 
system corruption that I've seen.  Sometimes ls doesn't work
in /bin/ or once I lost everything under /usr.

I've googled for this and I found a redhat bug that might be
related.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126730

I have tried with both ext2 and ext3 partitions formatted 
under the 2.6 kernel and I get the same results in both cases.

Has something changed in ext2 and ext3 to make them not 
backward compatible to 2.4 kernels?

regards,
dan carpenter

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/