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 19/04/2012 10:57, NeilBrown wrote:
On Thu, 19 Apr 2012 12:11:43 +0300 Alexander Lyakas<alex.bolshoy@xxxxxxxxx>
wrote:

Hi Neil,
Thanks for the clarification.
However, from your commit message, it stems that during a normal
reboot (without -f -n), writes can still arrive after your reboot
notifier has cleaned the array. In such case, array might be dirty
after reboot. Is that so? If yes, then that's kind of regression.

Why do you think that?

I don't think that is the case.

That's what I had thought too, because in your original message describing the patch, you wrote:

It seems that with recent kernel, writeback can still be happening
while shutdown is happening, and consequently data can be written
after the md reboot notifier switches all arrays to read-only.

I understand that to mean that someone somewhere has patched the kernel so that writes (writeback?) can still be happening after the array is supposed to be read-only. This sounds like a regression to me, though not one you have created.

Cheers,

John.

--
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