[PATCH] Btrfs: make sure logged extents complete in the current transaction V3

2014-11-21 Thread Josef Bacik
Liu Bo pointed out that my previous fix would lose the generation update in the scenario I described. It is actually much worse than that, we could lose the entire extent if we lose power right after the transaction commits. Consider the following write extent 0-4k log extent in log tree commit

[PATCH] Btrfs: make sure logged extents complete in the current transaction V2

2014-11-19 Thread Josef Bacik
Liu Bo pointed out that my previous fix would lose the generation update in the scenario I described. It is actually much worse than that, we could lose the entire extent if we lose power right after the transaction commits. Consider the following write extent 0-4k log extent in log tree commit

Re: [PATCH] Btrfs: make sure logged extents complete in the current transaction

2014-11-19 Thread Liu Bo
On Tue, Nov 18, 2014 at 05:19:41PM -0500, Josef Bacik wrote: > Liu Bo pointed out that my previous fix would lose the generation update in > the > scenario I described. It is actually much worse than that, we could lose the > entire extent if we lose power right after the transaction commits. Co

[PATCH] Btrfs: make sure logged extents complete in the current transaction

2014-11-18 Thread Josef Bacik
Liu Bo pointed out that my previous fix would lose the generation update in the scenario I described. It is actually much worse than that, we could lose the entire extent if we lose power right after the transaction commits. Consider the following write extent 0-4k log extent in log tree commit