On Fri, 11 Jan 2002, "zeroK" <[EMAIL PROTECTED]> wrote:
>
> Using Linux Kernel 2.2.19 Ext2 [Slackware 8.0], I notice that
> after making major changes or after a *crash* [due to numerous
> power outages here], at startup filesystem check I will get a
> "(3% non-contiguous)" message [percentages vary, but are small].
> Then at next reboot and file system check it will have been fixed
> (I assume the absence of said message implies that).
I believe that is output from the e2fsck command:
# e2fsck -f /dev/hda1
e2fsck 1.12, 9-Jul-98 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda1: 17274/128520 files (0.5% non-contiguous), 235988/514048 blocks
^^^^^^^^^^^^^^
If the filesystem is clean (i.e. after a normal shutdown+reboot), I don't
think it will report the fragmentation. It may just say something like:
# e2fsck /dev/hda1
e2fsck 1.12, 9-Jul-98 for EXT2 FS 0.5b, 95/08/09
/dev/hda1: clean, 17274/128520 files, 235988/514048 blocks
I don't know how much time it takes to compute the fragmentation,
it may choose to skip the computation if the filesystem is clean...
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
