[Bug 615899] Re: fsck.ext4 marks FS clean when still damaged

[Theodore Ts'o]

Without more information, should we close this particular bug as
unreproducible?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/615899

Title:
  fsck.ext4 marks FS clean when still damaged

Status in “e2fsprogs” package in Ubuntu:
  New

Bug description:
  Binary package hint: e2fsprogs

  During repair of a corrupted root filesystem (a whole other story), on
  a whim due to my old UNIX experiences I re-ran fsck.ext4 on the
  filesystem a second time.  The filesystem was found to contain more
  corruption.  Because I was running without my filesystem available, I
  was unable to grab a log of the fsck output, but the corruption
  generally involves blocks allocated to more than one file, with file
  cloning involved during the repairs.

  I suggest that regression testing for fsck.ext4 include running it a
  second time (with -f, natch) to verify that the FS is truly clean.  In
  this case it made it much harder to detect new corruption during debug
  of the corruption bug, since it turns out I might have been seeing
  residual corruption from an incomplete repair.  But in general it
  means that you'll mark a FS clean and put it back into operation when
  it still has problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/615899/+subscriptions