lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 09 Aug 2006 11:01:55 +0200 From: Helge Hafting <helge.hafting@...el.hist.no> To: Michael Tokarev <mjt@....msk.ru> CC: Neil Brown <neilb@...e.de>, Alexandre Oliva <aoliva@...hat.com>, linux-raid <linux-raid@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: modifying degraded raid 1 then re-adding other members is bad Michael Tokarev wrote: > Why we're updating it BACKWARD in the first place? > Don't know this one... > Also, why, when we adding something to the array, the event counter is > checked -- should it resync regardless? If you remove a drive and then add it back with no changes in the meantime, then you don't want a resync to happen. Some people reboot their machine every day (too much noise, heat or electricity at night), a daily resync is excessive. An which drive would you consider the "master copy" anyway, if the event counts match? Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists