Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.

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

 



On Wed, 18 Apr 2012 18:37:56 +0300 Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
wrote:

> Hi Neil,
> 
> > This could result in the shutdown happening when array is marked
> > dirty, thus forcing a resync on reboot.  However if you reboot
> > without performing a "sync" first, you get to keep both halves.
> Can you pls clarify the last statement?

"If you break it, you get to keep both halves" is a colloquial phrase meaning
that that the person saying it takes no responsibility for any damage that
the person being spoken to causes.
When applied to software issues it is ironic (because when a thing 'breaks' it
doesn't result in two pieces like, for example, when a plate breaks) and so
funny (I hope).
(when applied to a RAID mirror, it is doubly ironic :-)

If you force a fast shutdown without allowing a sync to happen 
(e.g. reboot -f -n) there could be data on the way out to the array when the
system actually reboots, so the array will be dirty, so a resync will be
required when the system restarts.
This might be undesirable, but that isn't my problem and is not the problem
of md/raid.  Rather the cause of the problem is the "reboot -f -n".  i.e.
"your" problem.   "You" broke it, you get to keep both halves.

Does that help?

NeilBrown

Attachment: signature.asc
Description: PGP signature


[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