On Sun, Oct 28, 2012 at 02:36:24PM +0100, Martin Steigerwald wrote: > Am Sonntag, 28. Oktober 2012 schrieb Hugo Mills: > > On Sun, Oct 28, 2012 at 02:23:51PM +0100, Martin Steigerwald wrote: > > > Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson: > > > > In a raid1 situation, it will also rewrite the effected data, on > > > > the drive that failed the checksum > > > > > > Will it do so without an explicit scrub? > > > > If a failed checksum is detected, yes. > > > > If there's a bad block, and the FS happens to read the good copy > > first, it won't fix it, because it hasn't tried reading the bad copy > > yet. > > Ah, okay. I think I read some while ago in a case of bad checksum detected > it won´t repair automatically. Has this been changed?
It was changed some time ago -- the kernel release after scrub went in, IIRC. > Anyway, a regular scrub still makes sense, as BTRFS only reads files that > applications demand and BTRFS may read from a good copy as you pointed > out. Indeed. I have a cron job in /etc/cron.monthy for my main FS to do just that. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- ... one ping(1) to rule them all, and in the --- darkness bind(2) them.
signature.asc
Description: Digital signature
