> It's also possible that the filesystem somehow got re-corrupted between the runs. For my case, the write back SSD caching device was removed permanently. Somehow the xfs_repair did not fix all problems after the first pass. Best regards, Patrick On Thu, Feb 2, 2017 at 3:58 AM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: > On 2/1/17 12:53 PM, Patrick Dung wrote: >> Hi guys, >> >> The problem happened in last year. I do not have the corrupted file >> system now. But I would like to discuss it. Any comment is welcomed. >> >> I was using Fedora 24. I had an XFS file system in an hard drive. I >> had used some kind of SSD write back caching on top of the hard >> drive. >> >> Somehow the SSD was removed and when the system is rebooted, the XFS >> file system could not be mounted. >> >> I run xfs_repair, it reported some files are corrupted. It had >> completed the repair of file system and some files were corrupted. >> Then I could mount the filesystem. I started using the existing files >> that did not have corruption. After sometime, the file system stopped >> again because it detected XFS file system is corrupted. >> >> Then I run xfs_repair again and it found additional files were still corrupted. >> >> So I have a question if xfs_repair is able to fully detect all files >> that are corrupted by running xfs_repair only once. > > Yes, xfs_repair is intended to fix everything on the first pass. Rarely, > there are bugs when it does not. > > It's also possible that the filesystem somehow got re-corrupted between > the runs. > > -Eric > >> Best regards, >> Patrick -- 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
