On Thursday June 21, [email protected] wrote:
> I didn't get a comment on my suggestion for a quick and dirty fix for
> -assume-clean issues...
>
> Bill Davidsen wrote:
> > How about a simple solution which would get an array on line and still
> > be safe? All it would take is a flag which forced reconstruct writes
> > for RAID-5. You could set it with an option, or automatically if
> > someone puts --assume-clean with --create, leave it in the superblock
> > until the first "repair" runs to completion. And for repair you could
> > make some assumptions about bad parity not being caused by error but
> > just unwritten.
It is certainly possible, and probably not a lot of effort. I'm not
really excited about it though.
So if someone to submit a patch that did the right stuff, I would
probably accept it, but I am unlikely to do it myself.
> >
> > Thought 2: I think the unwritten bit is easier than you think, you
> > only need it on parity blocks for RAID5, not on data blocks. When a
> > write is done, if the bit is set do a reconstruct, write the parity
> > block, and clear the bit. Keeping a bit per data block is madness, and
> > appears to be unnecessary as well.
Where do you propose storing those bits? And how many would you cache
in memory? And what performance hit would you suffer for accessing
them? And would it be worth it?
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
