Hi,
I had the same error message doing while fsck'ing one of my disks.
I did not understand well the cause of the problem. Is fsck what caused the file-system corruption? (because of an "extent-mapped inode getting written (or copied) to a different/wrong place in the inode table"?)
This ticket is labelled e2fsprogs. May you explain if the planned fix is:
- to avoid file-system corruption
- to enable fsck to fix it
(- something else?)
please?
Hi,
I had the same error message doing while fsck'ing one of my disks.
I did not understand well the cause of the problem. Is fsck what caused the file-system corruption? (because of an "extent-mapped inode getting written (or copied) to a different/wrong place in the inode table"?)
This ticket is labelled e2fsprogs. May you explain if the planned fix is:
- to avoid file-system corruption
- to enable fsck to fix it
(- something else?)
please?