On Fri, Oct 21, 2016 at 04:41:09PM -0400, Josef Bacik wrote: > >> > > >> > btrfs inspect inode 130654 mntpoint > >> > >> Interesting, they all return > >> > >> ERROR: ino paths ioctl: No such file or directory > >> > >> So these files got deleted perhaps ? > >> > > Yeah, they must have. > > > > So one thing that will cause spurious csum errors is if you do things like > change the memory while it is in flight during O_DIRECT. Does trinity do that? > If so then that would explain it. If not we should probably dig into it. Thanks, Yeah, that's definitely possible. And it wasn't that long ago I added some code to always open testfiles multiple times with different modes, so the likely of O_DIRECT went up. That would explain why I've started seeing this more. Dave -- 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
