linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Gehring <markus.gehring@infinia.de>
To: linux-raid@vger.kernel.org
Cc: Paul Clements <paul.clements@steeleye.com>
Subject: Re: RAID1 Corruption
Date: Mon, 17 Jan 2005 20:42:10 +0100	[thread overview]
Message-ID: <41EC1512.10907@infinia.de> (raw)
In-Reply-To: <41EC0E7F.5090303@steeleye.com>

Paul Clements wrote:
> Hi,
> 
> Markus Gehring wrote:
> 
>> I have a reproducable problem with corrupted data read from a 
>> RAID1-array.
>>
>> Setup:
>>  HW:
>>   2 S-ATA-Disks (160GB each) -> /dev/md4 RAID1
>>   Promise S150 TX4 - Controller
>>   AMD Sempron 2200+
>>
>>  SW:
>>   Fedora Core 3
>>   Kernel 2.6.10 unpatched
>>   Samba (for read/write-accesses)
>>   SW-Raid
>>
>> Everything works fine with only one drive in the array. If the second is
>> synced up read accesses return corrupted data.
>>
>> Interesting: If you remove again the second disk. The same files will be
>>  read correctly again (no matter if written while only one disk is in
>> the array or two are synced!)!
> 
> 
> This makes it sound like bad data is getting written to the second disk 
> during resync. Could you give more details about your test procedure (a 
> script or list of steps that reproduces the problem would be great)?
1. Setup Array (mdadm -C /dev/md4 -l 1 -n 2 /dev/sdc1 /dev/sdd1)
2. ... resync running (as i can see with cat /proc/mdstat)
3. mke2fs /dev/md4
4. mount /dev/md4 /home2
5. Copy ~100M JPGs (~800k each) via samba to array (/home2/test1/)
6. See the JPGs all okay
7. after resync has finished: Copy same ~100M JPGs to array (/home2/test2)
8. See the JPGs (at least in /home2/test2... i didn't check them in 
..test1) damaged
9. remove one disk again (mdadm /dev/md4 -f /dev/sdd1
mdadm /dev/md4 -r /dev/sdd1 ... or ../dev/sdc1!!!)
10. see (from the Win Client) the JPGs in /home2/test2 okay again!


> I don't think samba is the culprit, but just to be sure, is there any 
> chance you could reproduce the problem without samba in the equation? 
> (From what you say above, I assume all reads and writes are coming from 
> a samba client of some sort?)
I did a quick test:
Copyied my test-JPG-dir from /home/test (where i can see the pics okay) 
to /home2/test9 and see the pics damaged. After i copied them back to 
/home/test9 the stay damaged.

Remarks:
I also saw here that the pics on the syncing /dev/md4 = /home2 are 
damaged (read?) while the drive is syncing (new compared to point 6 
above) but this happens definitly not so often as if the drive has 
finished syncing (saw this the first time while dealing with the problem 
for over 2 weeks now).
I have all mounts on SW-Raid1 arrays, but i have never seen problems 
with md0 (/boot), md1 (/), md2 (swap), md3 (/var).
I have seen ext3-fs errors also (see also Sven Andras's posting from 
today and 5.1.2005).

Many Thanks,
  Markus


  parent reply	other threads:[~2005-01-17 19:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-17 15:22 RAID1 & 2.6.9 performance problem Janusz Zamecki
2005-01-17 15:39 ` Gordon Henderson
2005-01-17 15:51   ` Hans Kristian Rosbach
2005-01-17 16:46     ` Peter T. Breuer
2005-01-18 13:18       ` Hans Kristian Rosbach
2005-01-18 13:43         ` Peter T. Breuer
2005-01-17 20:49     ` Janusz Zamecki
2005-01-17 16:24   ` Andrew Walrond
2005-01-17 16:51     ` Is this hdparm -t output correct? (was Re: RAID1 & 2.6.9 performance problem) Andy Smith
2005-01-17 17:04       ` Andrew Walrond
2005-01-17 18:26         ` RAID1 Corruption Markus Gehring
2005-01-17 19:14           ` Paul Clements
2005-01-17 19:35             ` Tony Mantler
2005-01-17 19:42             ` Markus Gehring [this message]
2005-01-17 19:21           ` Sven Anders
2005-01-18 17:32 ` RAID1 & 2.6.9 performance problem J. Ryan Earl
2005-01-18 17:34   ` J. Ryan Earl
2005-01-18 18:41     ` Janusz Zamecki
2005-01-18 19:18       ` J. Ryan Earl
2005-01-18 19:34         ` Janusz Zamecki
2005-01-18 19:12   ` Janusz Zamecki

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=41EC1512.10907@infinia.de \
    --to=markus.gehring@infinia.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=paul.clements@steeleye.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).