e2fsprogs/tests/f_badprimary/expect.1
Theodore Ts'o 7ae1983a23 Clean up e2fsck problem description messages for typo's and to make them
easier to understand (sorry, translators).

Add new @m (multiply-claimed) and @n (invalid) expansions for e2fsck
problem descriptions.

Add Dutch translation, and update French translation.

Add an explanation of how the @-expansion and %-exapansion works in 
e2fsck/problem.c to make life easier for the translators.

Synchronize and update po files.
2005-06-19 09:45:36 -04:00

28 lines
883 B
Groff

Filesystem did not have a UUID; generating one.
Pass 1: Checking inodes, blocks, and sizes
The primary superblock (1) is on the bad block list.
If the block is really bad, the filesystem can not be fixed.
You can remove this block from the bad block list and hope
that the block is really OK. But there are no guarantees.
Clear? yes
Block 2 in the primary group descriptors is on the bad block list
If the block is really bad, the filesystem can not be fixed.
You can remove this block from the bad block list and hope
that the block is really OK. But there are no guarantees.
Clear? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
test_filesys: 11/32 files (0.0% non-contiguous), 22/100 blocks
Exit status is 1