On Mon, Oct 08, 2012 at 08:57:30AM -0600, Richard W.M. Jones wrote: > On Mon, Oct 08, 2012 at 10:27:57AM -0400, Chris Mason wrote: > > On Mon, Oct 08, 2012 at 08:16:42AM -0600, Richard W.M. Jones wrote: > > > > > > I'm tracking this bug here: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=863978 > > > > > > Since approx. last week I'm seeing lots of failures in btrfs. The > > > common factor seems to be that the filesystem is created (mkfs.btrfs > > > /dev/sda1) and then it is immediately used -- eg. mounted or some > > > btrfs subtool is run on it. There is no pause or sync between the > > > operations. > > > > This was a problem on older btrfs-progs, but this commit: > > > > btrfs-progs-0.19.20120817git043a639-1.fc19.i686 > > > > (043a639) has long had the fixes to flush things after mkfs. Is there > > any change the guest you're testing had an ancient progs on it? > > We have a couple of guests where this fails. One has > btrfs-progs-0.19.20120817git043a639-1.fc19.i686. The other has > btrfs-progs-0.19-20.fc18 which appears to be based on > btrfs-progs-0.19.20120817git043a639.tar.bz2 plus some upstream > patches. > > What is the commit which we need? I can't see anything related to > this in the btrfs-progs git log.
Sorry, I was remembering wrong. I fixed this up in the kernel by running invalidate_bdev during mount. I just double checked and the invalidates look right, so something strange must be going on. If it is possible to reproduce this reliably, could you please check and see if syncs do fix it? We saw this often with xfstests in the past, but haven't seen it since the invalidates were added. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
