On Wed, Apr 1, 2015 at 12:16 PM, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > On Wed, Apr 1, 2015 at 2:04 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> When I had this same btrfs check error, it was the exact inode number >> and same /etc/shadow file. I didn't diff the two shadow files, but I > > That's too bizarre for words. Two folks, on two different systems, > getting btrfs problems on similar kernels on the exact same filepath. > In my case, the file was last frobbed by yum/rpm. Do we have a strange > interaction between a kernel regression and yum/rpm rubbing the > filesystem the wrong way? No idea, but it happened to me more than once, same inode number, same file. > BTW, I did not change/touch the file at all. My only "fix" action was > the btrfs check --repair mentioned earlier. That won't fix it. Once errors 400 appears, at this point you have to replace the affected file. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
