-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi
I'm using nilfs2 on a debian (lenny machine) using kernel 2.6.26-1-686 and nilfs version 2.0.6. Currently I have a 250 Gb single partition drive connected via USB2, which I have formatted for nilfs2. I have noticed that when extracting a large archive onto the the file system that it seems to "burst", that is, it will extract for 5 seconds then halt for 1 and then repeat this cycle faithfully for the duration. If I switch (kill) off the GC then the "bursting" effect disappears. I can remove checkpoints more efficiently using rmcp, however am I right in thinking that the GC does more than just remove checkpoints ? Is the behaviour that I am witnessing typical of the nilfs GC or is being highlighted because I am using usb instead of directly attached ide / sata ? I'm hoping to apply nilfs in production environment for our print unit at work because they would like self service recovery and because they have large amounts of graphical data that is updated daily but could only be safely backed up using a snaphot technology. However I am concerned that any large file / archive extracts onto a nilfs file system with the GC switched on would impede efficiency. It is safe to say that I wont be using USB attached storage in the production environment, but I thought it might be worth mentioning my findings as the behaviour may still be present in a very muted form on IDE / SATA based storage devices. I guess I could run GC at off peak times as a workaround, but would it ever catch up ? I would be most interested in your comments. Thanks (for nilfs) Tom. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl7WbUACgkQBX2gJWUv0is23gCeJ4cdHUxnkKcOoffc5Ic1Qdco 8HYAn3Lt7MsFIbxX+ayZwbfaeTBTLVXY =sytK -----END PGP SIGNATURE----- _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
