On Wed, Oct 2, 2019 at 2:56 PM Josef Bacik wrote:
>
> On Wed, Oct 02, 2019 at 11:22:40AM +0100, Filipe Manana wrote:
> > On Wed, Oct 2, 2019 at 5:29 AM Josef Bacik wrote:
> > >
> > > From: Josef Bacik
> > >
> > > I discovered a problem in btrfs where we'd end up pointing at a block we
> > > hadn
On Wed, Oct 02, 2019 at 11:22:40AM +0100, Filipe Manana wrote:
> On Wed, Oct 2, 2019 at 5:29 AM Josef Bacik wrote:
> >
> > From: Josef Bacik
> >
> > I discovered a problem in btrfs where we'd end up pointing at a block we
> > hadn't written out yet. This is triggered by a race when two different
On Wed, Oct 2, 2019 at 5:29 AM Josef Bacik wrote:
>
> From: Josef Bacik
>
> I discovered a problem in btrfs where we'd end up pointing at a block we
> hadn't written out yet. This is triggered by a race when two different
> files on two different subvolumes fsync. This test exercises this path
From: Josef Bacik
I discovered a problem in btrfs where we'd end up pointing at a block we
hadn't written out yet. This is triggered by a race when two different
files on two different subvolumes fsync. This test exercises this path
with dm-log-writes, and then replays the log at every FUA to v
