Bug#768162: fsck.ext4 -n should not just quit at the first error, else user will think there is only one error

2014-11-06 Thread Theodore Ts'o
On Thu, Nov 06, 2014 at 07:53:16AM +0800, 積丹尼 Dan Jacobson wrote: OK next trip to Taichung I will pick up some 'real brand name' cards and card readers and promise to stop complaining until then! See the Fake Cards in Linaro's Flash Card Survey:

Bug#768162: fsck.ext4 -n should not just quit at the first error, else user will think there is only one error

2014-11-05 Thread 積丹尼 Dan Jacobson
Package: e2fsprogs Version: 1.42.12-1 Severity: wishlist File: /sbin/e2fsck User would like to cautiously examine the situation before chaning anything, so does: # fsck.ext4 -vn -B 1024 -b 8193 /dev/sde2 e2fsck 1.42.12 (29-Aug-2014) Superblock has an invalid journal (inode 8). Clear? no

Bug#768162: fsck.ext4 -n should not just quit at the first error, else user will think there is only one error

2014-11-05 Thread Theodore Ts'o
retitle 768162 e2fsck should check to see if the number of inodes is insanely small thanks The e2fsck program in general does not exit with a fatal_error after the first error. However, there are a certain class of file system inconsistencies where it simply isn't safe or there simply isn't

Bug#768162: fsck.ext4 -n should not just quit at the first error, else user will think there is only one error

2014-11-05 Thread 積丹尼 Dan Jacobson
TT == Theodore Ts'o ty...@mit.edu writes: TT In general it's safe to quit using ^C. In your particular case, the TT superblock was clearly corrupted before e2fsck started, and so I see TT no justification of your assertion that this left your filesystem TT even more wrecked. Actually comparing