Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
mds: propagate error encountered during opening inode by number #12749
This is quite subtle, so it could do with a test (I'm having a hard time being completely sure that the EIO really gets returned in the end). I think that the new TestDamage.test_corrupt_backtrace that I just added in master is almost the same case. You could just copy that test and instead of corrupting the backtrace, remove the dirfrag object for the inode that the hardlink points to.