Interestingly ... the Journal appears to be NOT automatic -- at least on REGULAR NASLite ( I never used M2 ). On a test-environment-server with a beta copy of the soon to be released NASLite 2.6 I just did a re-format (of an existing NL2 ext3 (with journal) in-use data disk), set it to RW, reboot, then listed the "Filesystem features:" and "has_journal" was not set. Followed this by option 7 (Apply a Journal) ... and there it was ... now it's "has_journal". But then I also created a Mirror on this disk. Because the "Filesystem state:" said "not_clean" (unexpectedly -- I had expected the "Apply a Journal" to set the "clean" flag) I also rebooted and was surprised to see the system do a filecheck during restart. Now the system has "Filesystem features: has_journal", plus "Filesystem state: clean" and its Mirror (set to start in about 45 minutes).
Moral: If you prefer the journal (and I would recommend that -- the space & performance overhead is small for most environments) always check your "Filesystem Features" and do that additional reboot (with system-auto-initiated filecheck) before you add major amounts of data to the disk.
|