Re: [PATCH md ] md: allow degraded raid1 array to resync after an unclean shutdown.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> The following is (I think) appropriate for 2.4.30.  The bug it fixes
> can result in data corruption in a fairly unusual circumstance (having
> a 3 drive raid1 array running in degraded mode, and suffering a system
> crash).

What's unusual?  Having a 3 drive raid1 array?

It's not unusual for a system to crash after a RAID array gets sent to
degraded mode.  Happens a lot on a system I administer.  Probably
caused by a linux-si3112-ide bug which first results in read errors, then
(after md has been told to resync) results in a complete system crash...

Another topic:
Just noticed MD usage in a screenshot:
  http://linuxdevices.com/files/misc/ravehd_screenshot.png
>From this article:
  http://linuxdevices.com/news/NS8217660071.html
Just in case anybody cares :-).
-
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux