I don't have the numbers anymore and I tore down the boot environment since.
The test was fairly simple. I have a terabyte hard drive in two partitions -- 400GB and 600GB. The 400GB partition has about 3GB of data, while the 600GB one has about 30. With plymouth disabled, it was easy to see the start of the first fsck and the stop of the last one. I compared elapsed time by wall clock to running the fscks manually from recovery mode. I don't have the numbers anymore but I remember I didn't even need the second hand. Also, the disk heads bouncing back and forth makes a rather disconcerting racket compared to the whisper quiet of one fsck running at a time. -- mountall ignores the pass parameter of /etc/fstab when scheduling fsck https://bugs.launchpad.net/bugs/599624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
