Hi Mark, On 04/26/2011 01:22 PM, Mark Knecht wrote: > On Mon, Apr 25, 2011 at 6:30 PM, Mark Knecht <markknecht@xxxxxxxxx> wrote: [trim /] > OK, I don't know exactly what I'm looking for a problem here. I ran > the repair, then rebooted. Mismatch count was zero. It seemed the > repair had worked. > > I then used the system for about 4 hours. After 4 hours I did another > check and found the mismatch count had increased. > > What I need to get a handle on is: > > 1) Is this serious? (I assume yes) Maybe. Are you using a file in this filesystem as swap in lieu of a dedicated swap partition? I vaguely recall reading that certain code paths in the swap logic can abandon queued writes (due to the data no longer being needed by the VM), such that one or more raid members are left inconsistent. Supposedly only affecting mirrored raid, and only for swap files/partitions. I don't know if this was ever fixed. or even if anyone tried to fix it. > 2) How do I figure out which drive(s) of the 3 is having trouble? Don't know. Failing drives usually give themselves away with warnings in dmesg, and/or ejection from the array. There's nothing in the kernel or mdadm that'll help here. You'd have to do three-way voting comparison of all blocks on the member partitions. > 3) If there is a specific drive, what is the process to swap it out? mdadm /dev/mdX --fail /dev/sdXY mdadm /dev/mdX --remove /dev/sdXY (swap drives) mdadm /dev/mdX --add /dev/sdZY HTH, Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
