Package: e2fsprogs Version: 1.42.9-3 Severity: wishlist
Hi. I just wondered about missing /lost+found, and whether it couldn't be handled as a "non-failure" issue... Like when cheking an fs and not creating it: /dev/sdb1 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity /lost+found not found. Create<y>? no Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sdb1: ********** WARNING: Filesystem still has errors ********** that fsck, doesn't call that an error? Moreover, and it seems this might be actually a bug... when an filesystem was not cleanly unmounted and a check is forced, as in the example above, then even if no further failure was found but the /lost+found is not created, then the fs will still be marked as unclean, and a full check will be enforced when running fsck on it again. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
