Bug 232677
Summary: | ext2/3 filesystem corruption with writable loopback devices on s390 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Bryn M. Reeves <bmr> | ||||||
Component: | kernel | Assignee: | Jan Glauber <jglauber> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Martin Jenner <mjenner> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 5.0 | CC: | dhoward, dzickus, esandeen | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | s390x | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-05-30 13:58:05 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Bryn M. Reeves
2007-03-16 16:11:05 UTC
Hmm maybe you can bzip2 the /tmp/img0 image & attach it? Does an image created on s390 check ok on x86, or vice versa? The whole sequence works fine for me on x86 It's odd that you see an inode 25 on a fresh fs with no files.... It's s390 specific - I hit it while reproducing bug 232663 (big endian specific) and found I couldn't reproduce it on ppc. It sounds a lot like 236605 - fixed in 2.6.18-8.1.3.el5. I've run through about five mkfs/mount/fsck cycles now without seeing it. Created attachment 153232 [details]
currupt file system image
Corrupt file system image (2M uncompressed)
Thanks Bryn. What exactly was done to create this image? As described in comment #1: a dd from /dev/zero to set up the image (bs=1M count=2), then losetup, then mke2fs -j on the loop device. It should be quite easy to reproduce on s390 (at least with a kernel prior to 2.6.18-8.1.3.el5). I've still not seen it on the later kernel, but I'll keep testing for now. I'm fairly certain this is just another instance of the page_mkclean problem from bug 236605. When I first saw this it seemed to happen every time, but running a script 1000 times just now gave me 236 failures on 2.6.18-8.el5. The same script on 2.6.18-8.1.3.el5 didn't see any corruption in 1000 runs. Created attachment 153245 [details]
reproducer script
Thanks Bryn. If you're pretty sure this is already resolved by 236605, I'm happy to wait 'til I hear otherwise... :) This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Eventually got back to testing this with 2.6.18-8.el5 plus the patch for bug 236605 - same result. I see errors around 25% of the time without it which disappear when it's applied - I think it's safe to close this as a dup. *** This bug has been marked as a duplicate of 236605 *** |