e2fsprogs/tests/f_okgroup/expect.1

Filesystem did not have a UUID; generating one.

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
test_filesys: 11/2048 files (0.0% non-contiguous), 274/8193 blocks
Exit status is 0
Many files: Checked in e2fsprogs 1.05 1997-04-29 18:53:37 +04:00			`Filesystem did not have a UUID; generating one.`

Many files: Checked in e2fsprogs 0.5c 1997-04-26 18:00:26 +04:00			`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`
Many files: Checkin of e2fsprogs 1.02. 1997-04-26 18:37:06 +04:00			`test_filesys: 11/2048 files (0.0% non-contiguous), 274/8193 blocks`
e2fsck: avoid unnecessary reboots in some cases when checking the root fs If e2fsck modifies certain superblock fields which the kernel doesn't look at, mark the superblock as dirty without marking the file system as changed. This will avoid e2fsck signalling the init scripts that a reboot is necessary. This is safe, because the kernel doesn't actually look at these superblock fields. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 2011-10-01 04:59:17 +04:00			`Exit status is 0`