Hi list, back when I was using XFS, there was an option to put one particular piece of metadata -- the journal -- onto separate physical device. The speed-up was very significant, especially for operations on lots of files. For example, with external journal removing whole kernel source tree on XFS would take less time than on ext2 or ext3; with internal it would be much longer than ext2 or 3. The journal was needed only in case of unclean unmount, as only then it contained any information not applied yet; if the unmount was clean, the journal contained no important information. XFS journals only metadata changes, btw. My question is, would it be feasible to move some part of NILFS2 metadata onto separate device for R/W/GC speed-up? Perhaps some of metadata could even be considered `recoverable' -- that is, if the other device gets broken or lost, the metadata on it could be re- constructed from content of the main device. Regards, -- dexen deVries [[[â][â]]] For example, if the first thing in the file is: <?kzy irefvba="1.0" rapbqvat="ebg13"?> an XML parser will recognize that the document is stored in the traditional ROT13 encoding. (( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt )) -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
