http://oss.sgi.com/bugzilla/show_bug.cgi?id=289
Summary: Data corruption on XFS Volume on Raid5 Array
Product: Linux XFS
Version: unspecified
Platform: IA32
OS/Version: Linux
Status: NEW
Severity: critical
Priority: High
Component: XFS kernel code
AssignedTo: xfs-master@xxxxxxxxxxx
ReportedBy: stefan.hagendorn@xxxxxxxx
Hi all,
hopefully this is the right way to report a Bug. I use a box with 4 harddisks
with Raid5 and XFS. After writing a File the File appears to change when
reading it. I've done the following to demonstrate the issue:
Created 2 files 100 MB each with /dev/zero as source and compared the files 3
times.
[root@mss archive]# dd if=/dev/zero of=testfile1 bs=1M count=100
100+0 Records in
100+0 Records out
[root@mss archive]# dd if=/dev/zero of=testfile2 bs=1M count=100
100+0 Records in
100+0 Records out
[root@mss archive]# compare testfile1 testfile2 -a
14614544 (0xdf0010) 0x7f != 0x00 ^? ^@
14614545 (0xdf0011) 0xff != 0x00 ~^? ^@
71893008 (0x4490010) 0x00 != 0x7f ^@ ^?
71893009 (0x4490011) 0x00 != 0xff ^@ ~^?
[root@mss archive]# compare testfile1 testfile2 -a
44630032 (0x2a90010) 0x7f != 0x00 ^? ^@
44630033 (0x2a90011) 0xff != 0x00 ~^? ^@
58785808 (0x3810010) 0x7f != 0x00 ^? ^@
58785809 (0x3810011) 0xff != 0x00 ~^? ^@
[root@mss archive]# compare testfile1 testfile2 -a
8716304 (0x850010) 0x7f != 0x00 ^? ^@
8716305 (0x850011) 0xff != 0x00 ~^? ^@
31260688 (0x1dd0010) 0x7f != 0x00 ^? ^@
31260689 (0x1dd0011) 0xff != 0x00 ~^? ^@
31326224 (0x1de0010) 0x7f != 0x00 ^? ^@
31326225 (0x1de0011) 0xff != 0x00 ~^? ^@
85385232 (0x516e010) 0x7f != 0x00 ^? ^@
85385233 (0x516e011) 0xff != 0x00 ~^? ^@
104136720 (0x6350010) 0x00 != 0x7f ^@ ^?
104136721 (0x6350011) 0x00 != 0xff ^@ ~^?
you can see this yields different problems every compare on both sides ...
This looks to me like the data is written correctly to disk and the problem
happens when reading the data.
The Kerne I use is 2.4.22-ac3.
Sometimes when performing reading operations on that array I also get the
problem which is described in "[Bug 274] New: xfs_iunlink_remove: xfs_inotobp()
returned error 22 " This only happends with operations on that drive/array. The
box itself carries another array with raid5 and xfs without this strange
behavior.
xfs_info from that array :
[root@mss root]# xfs_info /mnt/bigarray/
meta-data=/mnt/bigarray isize=256 agcount=86, agsize=1048576 blks
data = bsize=4096 blocks=90040224, imaxpct=25
= sunit=16 swidth=48 blks, unwritten=0
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=10992 version=1
= sunit=0 blks
realtime =none extsz=196608 blocks=0, rtextents=0
If you need anthing else or this is the wrong way to report an error, please
infor me.
Thanks
Stefan Hagendorn
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|