On Wed, Apr 1, 2015 at 1:23 PM, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > On Wed, Apr 1, 2015 at 2:54 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> Re-run the btrfs check. The error is still there even after a --repair. > > Bingo! You are right the error persists. > > It has no effect on my use of the system right now. Is anyone > interested in debugging this further? 400 errors, nbytes wrong, isn't repaired by current btrfs check https://bugzilla.kernel.org/show_bug.cgi?id=90071 What's interesting in that bug report that I'd forgotten about? ># btrfs inspect inode 804 /mnt/root >/mnt/root/etc/shadow- Different inode number, but the shadow file is affected. In every single case I've had now (about 1/2 dozen) with this errors 400 message, it's involved the shadow file. I have no idea what's going on between Btrfs and the shadow file, but something seems to be. Or it's quite a coincidence. -- 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
