mirror of https://github.com/vitalif/e2fsprogs
6e3c3b7552
If an inode fails checksum verification during pass 1 and the user doesn't fix or clear the inode as part of the regular inode checks, ensure that e2fsck remembers to ask the user if he simply wants to correct the checksum. We weren't capturing all the ways out of an interation of the inode scanning loop, which means that not all errors were caught. Also, we might as well clear the 'failed csum' flag if we write the inode directly from the inode scanning loop. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> |
||
|---|---|---|
| .. | ||
| expect.1 | ||
| expect.2 | ||
| image.gz | ||
| name | ||