| 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: Tue, 6 Mar 2007 20:41:23 +0100 (MET) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: Bill Davidsen <davidsen@....com> cc: Marc Perkel <mperkel@...oo.com>, linux-kernel@...r.kernel.org Subject: Re: Raid 10 Problems? >> > -b internal -- seems like a good idea to speed up >> > resynchronization. >> >> I'm trying to figure out what the default is. >> > -e 1.0 -- I wonder why the new superblock format >> > is >> > not default in mdadm (0.90 is still used). >> > >> >> Looks interesting for big arrays but not sure it's >> worth starting over for. Trying to get through a 2 >> hour sync using 4 500gb sata 2 drives. > > That's exactly why you want the bitmap. Fortunately you can add it after the > array is created. Now the bad news, you should read and understand the meaning > of the "far" layout. Part of the information is in the mdadm man page under -p, > some in the md man page. Use of "far" layout will effect the performance of the > array, the balance of read vs. write performance, and (maybe) the reliability. So to keep it simple, don't use far unless you have a reason to. Jan -- - 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