Non-contiguous means that the data blocks are not stored contiguously on disk. Yes, that means "fragmented". Keep in mind that a certain amount of fragmentation isn't going to hurt performance. If a file is badly fragmented, yes, that can hurt performance (at least until we all switch to solid state disks in a few years :-). The ext3 filesystem is fragmentation resistent, which means it has algorithms which try to avoid fragmentation, and try to keep fragmentation from affecting performance as much. Ext4 is much better at this, BTW. One of the reasons why I used the terminology non-contiguous is that many people from the windows world misinterpret the message, and start hyperventilating as soon as they see anything that involves the word "fragmentation". In fact, there are various design tradeoffs where having a little bit of fragmentation is far better than monomanically trying to avoid fragmentation at all costs. It's a complex issue. E2fsck can easily connect a single number which can give an expert some idea about how well the filesystem is aging; and since it can easily collect that information "for free" while it is doing a full check, it does so. Of course, that single number can be deceiving, too. But it certainly wasn't an error message. If it had been an actual error message, it would have told you that something was specifically wrong, and offered to fix it.
-- Intrepid: e2fsck in rescue menue does not repair problems https://bugs.launchpad.net/bugs/270458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
