Running e2fsck twice gives the same / different errors
Jump to:
| Project: | Linux software |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Related pages: | #94: fsck: file system check |
Description
Running e2fsck -vyfFC0 /dev/sdc1 twice in a row gives the same count of block errors (with the same inode numbers).
Is there a way to run e2fsck in a way that known bad blocks are ignored and to see if the disk is deteriorating further (compared to a previous run)?
Comments
#1
Actually no. Consecutive runs give different numbers of inodes, some the same, some different.