Please close, as that server no longer exists and it doesn't happen
elsewhere. It very possibly could just have been hardware issues.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615899
Titl
Without more information, should we close this particular bug as
unreproducible?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615899
Title:
fsck.ext4 marks FS clean when still damaged
To manage no
There are around 100 tests in e2fsprogs which test various file system
corruptions. Please they are in the e2fsprogs/tests/f_* sub
directories. Each include a smallish file system, and then the
expected output after the first and second fsck run.
Note that Ubuntu saves fsck output in /var/log/
Thanks. This was certainly standalone (root fsck failed during bootup
sequence), so either HW or SW bug. I will be swapping the server out in
about a week, and will look at putting a second drive in so I can dd an
image before fsck'ing. Then, assuming it's SW and not HW, I should be
able to repr
The regression testing for e2fsck already involves running it a second
time to make sure the file system is truly clean.
That is certainly something we strive for. If you get errors after
running e2fsck -y (i.e., you say yes to fix all corruptions), then one
of the following is true: (a) the ha
