Hello, On 05/06/2017, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: > On 6/2/17 6:21 PM, Péter András Felvégi wrote: >> Hello, >> >> after a power outage, the mount replayed the journal and no errors >> were reported, but the mounted XFS volume had suspiciously little free >> space. > > Did it happen to be your root filesystem, or some other? Some other. It's a raid+lvm+luks volume. >> So I unmounted, and ran xfs_repair which crashed in phase 5 > > Did it happen to find corruption before that? I ran xfs_repair twice, it crashed each time in phase 5 with the same message. I don't recall it found corruption, but the log zeroing printed different numbers. If I run xfs_repair 4.11 with -n, it skips phase 5 altogether :S > # xfs_metadump -o /dev/dm-2 - | xfs_mdrestore - dm-2.img Metadata corruption detected at block 0x2dd04801/0x200 xfs_metadump: cannot init perag data (117). Continuing anyway. Metadata CRC error detected at block 0x20b95802/0x200 Metadata CRC error detected at block 0x23ff1402/0x200 Metadata CRC error detected at block 0x2744d002/0x200 Metadata CRC error detected at block 0x2a8a8c02/0x200 Metadata corruption detected at block 0x2dd04801/0x200 Metadata CRC error detected at block 0x2dd04802/0x200 Metadata CRC error detected at block 0x31160402/0x200 Metadata CRC error detected at block 0x345bc002/0x200 Metadata corruption detected at block 0x37a17c01/0x200 Metadata CRC error detected at block 0x37a17c02/0x200 Metadata CRC error detected at block 0x3ae73802/0x200 Metadata CRC error detected at block 0x3e2cf402/0x200 Metadata CRC error detected at block 0x4172b002/0x200 Metadata CRC error detected at block 0x44b86c02/0x200 Metadata CRC error detected at block 0x47fe2802/0x200 Metadata CRC error detected at block 0x4b43e402/0x200 Metadata CRC error detected at block 0x4e89a002/0x200 Metadata CRC error detected at block 0x51cf5c02/0x200 Metadata CRC error detected at block 0x55151802/0x200 Metadata CRC error detected at block 0x585ad402/0x200 Metadata CRC error detected at block 0x5ba09002/0x200 Metadata CRC error detected at block 0x5ee64c02/0x200 Metadata CRC error detected at block 0x622c0802/0x200 Metadata CRC error detected at block 0x6571c402/0x200 Isn't this too many blocks for this kind of failure? There was no activity on the volume except for compressing a single large file. > # xfs_repair dm-2.img Phase 5 ran without error. After Phase 7 it printed this: Maximum metadata LSN (11:170112) is ahead of log (1:64). Format log to cycle 14. > # mkdir -p mnt/ > # mount -o loop dm-2.img mnt/ > and see how that looks (metadata only, the image created > above will contain no file data) Seems OK :) After running the repair on dm-2, the mount failed, my heart dropped, but luckily this was just due to the duplicate fs UUIDs, as the dumped meta image was still mounted. So the fs is mounted, everything looks OK so far. THANK YOU! Kind regards, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
