April 18, 201511 yr I'm running an xfs_repair on a drive with a small amount of filesystem corruption and it's repeatably segfaulting in Phase 6 of the repair. The filesystem corruption showed up immediately after another drive had just been rebuilt from parity. I've tried increasing memory for the repair. Command used: xfs_repair -m 8192 -P /dev/sdl1 result: - 21:38:18: check for inodes claiming duplicate blocks - 1728 of 2048 inodes done Phase 5 - rebuild AG headers and trees... - 21:38:18: rebuild AG headers and trees - 4 of 4 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... leaf block 8388608 for directory inode 164 bad header rebuilding directory inode 164 bad hash table for directory inode 186 (no data entry): rebuilding rebuilding directory inode 186 bad hash table for directory inode 4308015060 (no data entry): rebuilding rebuilding directory inode 4308015060 bad hash table for directory inode 4308015068 (no data entry): rebuilding rebuilding directory inode 4308015068 bad hash table for directory inode 4308015100 (no data entry): rebuilding rebuilding directory inode 4308015100 bad hash table for directory inode 4323051962 (no data entry): rebuilding rebuilding directory inode 4323051962 bad hash table for directory inode 4323051999 (no data entry): rebuilding rebuilding directory inode 4323051999 bad hash table for directory inode 8663574760 (no data entry): rebuilding rebuilding directory inode 8663574760 bad hash table for directory inode 8663574782 (no data entry): rebuilding rebuilding directory inode 8663574782 bad hash table for directory inode 8717925978 (no data entry): rebuilding rebuilding directory inode 8717925978 bad hash table for directory inode 8717926007 (no data entry): rebuilding rebuilding directory inode 8717926007 bad hash table for directory inode 8720814355 (no data entry): rebuilding rebuilding directory inode 8720814355 bad hash table for directory inode 8741930193 (no data entry): rebuilding rebuilding directory inode 8741930193 bad hash table for directory inode 8774083241 (no data entry): rebuilding rebuilding directory inode 8774083241 bad hash table for directory inode 8774083285 (no data entry): rebuilding rebuilding directory inode 8774083285 bad hash table for directory inode 8786453287 (no data entry): rebuilding rebuilding directory inode 8786453287 bad hash table for directory inode 8786453326 (no data entry): rebuilding rebuilding directory inode 8786453326 bad hash table for directory inode 8923519551 (no data entry): rebuilding rebuilding directory inode 8923519551 bad hash table for directory inode 12904850684 (no data entry): rebuilding rebuilding directory inode 12904850684 bad hash table for directory inode 12904850706 (no data entry): rebuilding rebuilding directory inode 12904850706 bad hash table for directory inode 12921513711 (no data entry): rebuilding rebuilding directory inode 12921513711 bad hash table for directory inode 13002341600 (no data entry): rebuilding rebuilding directory inode 13002341600 bad hash table for directory inode 13010972385 (no data entry): rebuilding rebuilding directory inode 13010972385 bad hash table for directory inode 13010972395 (no data entry): rebuilding rebuilding directory inode 13010972395 bad hash table for directory inode 13037887593 (no data entry): rebuilding rebuilding directory inode 13037887593 bad hash table for directory inode 13037887634 (no data entry): rebuilding rebuilding directory inode 13037887634 bad hash table for directory inode 13055671176 (no data entry): rebuilding rebuilding directory inode 13055671176 bad hash table for directory inode 13066632083 (no data entry): rebuilding rebuilding directory inode 13066632083 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 4308015060, Segmentation fault I've got a dump of the metadata if anyone wants to take a look. For the moment I'm just going to replace the drive and try to rebuild it from parity.
April 18, 201511 yr I'm running an xfs_repair on a drive with a small amount of filesystem corruption and it's repeatably segfaulting in Phase 6 of the repair. The filesystem corruption showed up immediately after another drive had just been rebuilt from parity. I've tried increasing memory for the repair. Command used: xfs_repair -m 8192 -P /dev/sdl1 result: - 21:38:18: check for inodes claiming duplicate blocks - 1728 of 2048 inodes done Phase 5 - rebuild AG headers and trees... - 21:38:18: rebuild AG headers and trees - 4 of 4 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... leaf block 8388608 for directory inode 164 bad header rebuilding directory inode 164 bad hash table for directory inode 186 (no data entry): rebuilding rebuilding directory inode 186 bad hash table for directory inode 4308015060 (no data entry): rebuilding rebuilding directory inode 4308015060 bad hash table for directory inode 4308015068 (no data entry): rebuilding rebuilding directory inode 4308015068 bad hash table for directory inode 4308015100 (no data entry): rebuilding rebuilding directory inode 4308015100 bad hash table for directory inode 4323051962 (no data entry): rebuilding rebuilding directory inode 4323051962 bad hash table for directory inode 4323051999 (no data entry): rebuilding rebuilding directory inode 4323051999 bad hash table for directory inode 8663574760 (no data entry): rebuilding rebuilding directory inode 8663574760 bad hash table for directory inode 8663574782 (no data entry): rebuilding rebuilding directory inode 8663574782 bad hash table for directory inode 8717925978 (no data entry): rebuilding rebuilding directory inode 8717925978 bad hash table for directory inode 8717926007 (no data entry): rebuilding rebuilding directory inode 8717926007 bad hash table for directory inode 8720814355 (no data entry): rebuilding rebuilding directory inode 8720814355 bad hash table for directory inode 8741930193 (no data entry): rebuilding rebuilding directory inode 8741930193 bad hash table for directory inode 8774083241 (no data entry): rebuilding rebuilding directory inode 8774083241 bad hash table for directory inode 8774083285 (no data entry): rebuilding rebuilding directory inode 8774083285 bad hash table for directory inode 8786453287 (no data entry): rebuilding rebuilding directory inode 8786453287 bad hash table for directory inode 8786453326 (no data entry): rebuilding rebuilding directory inode 8786453326 bad hash table for directory inode 8923519551 (no data entry): rebuilding rebuilding directory inode 8923519551 bad hash table for directory inode 12904850684 (no data entry): rebuilding rebuilding directory inode 12904850684 bad hash table for directory inode 12904850706 (no data entry): rebuilding rebuilding directory inode 12904850706 bad hash table for directory inode 12921513711 (no data entry): rebuilding rebuilding directory inode 12921513711 bad hash table for directory inode 13002341600 (no data entry): rebuilding rebuilding directory inode 13002341600 bad hash table for directory inode 13010972385 (no data entry): rebuilding rebuilding directory inode 13010972385 bad hash table for directory inode 13010972395 (no data entry): rebuilding rebuilding directory inode 13010972395 bad hash table for directory inode 13037887593 (no data entry): rebuilding rebuilding directory inode 13037887593 bad hash table for directory inode 13037887634 (no data entry): rebuilding rebuilding directory inode 13037887634 bad hash table for directory inode 13055671176 (no data entry): rebuilding rebuilding directory inode 13055671176 bad hash table for directory inode 13066632083 (no data entry): rebuilding rebuilding directory inode 13066632083 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 4308015060, Segmentation fault I've got a dump of the metadata if anyone wants to take a look. For the moment I'm just going to replace the drive and try to rebuild it from parity. Thank you for the report. Will investigate from our side as well.
April 21, 201511 yr Author Still going ahead with the rebuild from parity. I'm 90% sure that the corruption only showed up when the array was stopped so parity would still be correct.
April 21, 201511 yr I really don't know if it matters, but it looks like you are using one of the beta14's, not beta15. You might consider upgrading to beta15, in case something is fixed there that you need.
Archived
This topic is now archived and is closed to further replies.