On Thu, Dec 08 2016, Artur Paszkiewicz wrote: >> >> How about we call it "resync_policy" which describes how to cope with >> unexpected shutdown. Options include: >> >> full regenerate all redundancy info after a crash >> bitmap only regenerate redundancy info indicated by bitmap >> (both these suseptible to write-hole on raid456) >> journal raid456 only, though could theoretically be extended >> to raid1, raid10 : log transactions and replay after crash >> ppl raid456 only: log partial-parity before writes. >> >> With external metadata, this must be set explicitly. With internal >> metadata, it is set best on flags etc. >> >> Thoughts? I'm not really happy with "full", but I cannot think of a >> better name. > > I'm OK with this approach. A corresponding option will also be needed in > mdadm. But won't this name be a little misleading because this option is > not just about unexpected shutdown (where resync applies), but also > degraded array unexpected shutdown. So maybe something like > "consistency_policy" and "resync" option instead of "full"? "consistency_policy" and "resync" sounds good to me. Thanks. NeilBrown
Attachment:
signature.asc
Description: PGP signature
