On Tue, 01 Aug 2006, Ric Wheeler wrote:
> Mirroring a corrupt file system to a remote data center will mirror your
> corruption.
>
> Rolling back to a snapshot typically only happens when you notice a
> corruption which can go undetected for quite a while, so even that will
> benefit from having "reliability" baked into the file system (i.e., it
> should grumble about corruption to let you know that you need to roll
> back or fsck or whatever).
>
> An even larger issue is that our tools, like fsck, which are used to
> uncover these silent corruptions need to scale up to the point that they
> can uncover issues in minutes instead of days. A lot of the focus at
> the file system workshop was around how to dramatically reduce the
> repair time of file systems.
Which makes me wonder if backup systems shouldn't help with this. If
they are reading the whole file anyways, they can easily compute strong
checksums as they go, and record them for later use, and check so many
percent of unchanged files every day to complain about corruptions.
--
Matthias Andree
-
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]
