On Thursday May 17, [email protected] wrote:
> I tried the patch, same problem show up, but no bug_on report
>
> Is there any other things I can do?
>
What is the nature of the corruption? Is it data in a file that is
wrong when you read it back, or does the filesystem metadata get
corrupted?
Can you try the configuration that works, and sha1sum the files after
you have written them to make sure that they really are correct?
My thought here is "maybe there is a bad block on one device, and the
block is used for data in the 'working' config, and for metadata in
the 'broken' config.
Can you try a degraded raid10 configuration. e.g.
mdadm -C /dev/md1 --level=10 --raid-disks=4 /dev/first missing \
/dev/second missing
That will lay out the data in exactly the same place as with raid0,
but will use totally different code paths to access it. If you still
get a problem, then it isn't in the raid0 code.
Maybe try version 1 metadata (mdadm --metadata=1). I doubt that would
make a difference, but as I am grasping at straws already, it may be a
straw woth trying.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
