Bill Davidsen wrote:
Jan Engelhardt wrote:
On Dec 1 2007 06:26, Justin Piszcz wrote:
I ran the following:
dd if=/dev/zero of=/dev/sdc
dd if=/dev/zero of=/dev/sdd
dd if=/dev/zero of=/dev/sde
(as it is always a very good idea to do this with any new disk)
Why would you care about what's
Justin Piszcz wrote:
The badblocks did not do anything; however, when I built a software raid
5 and the performed a dd:
/usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
[42332.936615] ata5.00: exception Emask 0x2 SAct 0x7000 SErr 0x0 action
0x2 frozen
[42332.936706] ata5.00: spurious
Jeff Breidenbach wrote:
... and all access to array hangs indefinitely, resulting in unkillable zombie
processes. Have to hard reboot the machine. Any thoughts on the matter?
===
# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sde1[6](F) sdg1[1] sdb1[4] sdd1[3] sdc1[2]
On Dec 7, 2007 12:42 AM, NeilBrown [EMAIL PROTECTED] wrote:
Currently and md array with a write-intent bitmap does not updated
that bitmap to reflect successful partial resync. Rather the entire
bitmap is updated when the resync completes.
This is because there is no guarentee that resync
