Helge Hafting wrote:
On Tue, Jul 04, 2006 at 01:19:11PM +0200, Krzysztof Halasa wrote:
Neil Brown <[email protected]> writes:
With checksums - the filesystem is in a better position to:
- be selective about what is checksummed - no point checksumming
blocks that aren't part of any file. Some blocks (highlevel
metadata) might always be checksummed, while other blocks
(regular data) might not if a 'fast' option was chosen.
The same applies to RAID - for example, why "synchronise" unused area?
Indeed. RAID usually avoid checksumming unused area, it sums on write
and you don't write "unused" stuff.
Not syncing unused area is possible, if there was a way for raid resync
to ask the fs what blocks are not in use. I.e. get the
free block list in disk block order. Then raid resync could skip those.
Current RAID code supports having a bitmap of dirty stripes, and can
just sync those during recovery. I'm sure Neil could explain it better,
but this is available without worrying about fs type. Now. Today.
--
Bill Davidsen <[email protected]>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
-
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]
