On Tue, Jun 24, 2014 at 3:34 AM, Satoru Takeuchi
takeuchi_sat...@jp.fujitsu.com wrote:
Hi Filipe,
(2014/06/23 20:58), Filipe David Borba Manana wrote:
Often when starting a transaction we commit the currently running
transaction,
which can end up writing block group caches when the current
Hi Filipe,
(2014/06/24 17:29), Filipe David Manana wrote:
On Tue, Jun 24, 2014 at 3:34 AM, Satoru Takeuchi
takeuchi_sat...@jp.fujitsu.com wrote:
Hi Filipe,
(2014/06/23 20:58), Filipe David Borba Manana wrote:
Often when starting a transaction we commit the currently running transaction,
On 06/24/2014 03:29 AM, Filipe David Manana wrote:
On Tue, Jun 24, 2014 at 11:22 AM, Miao Xie mi...@cn.fujitsu.com wrote:
CC Josef
On Mon, 23 Jun 2014 12:58:59 +0100, Filipe David Borba Manana wrote:
Often when starting a transaction we commit the currently running transaction,
which can end
Often when starting a transaction we commit the currently running transaction,
which can end up writing block group caches when the current process has its
journal_info set to NULL (and not to a transaction). This makes our assertion
at btrfs_check_data_free_space() (current_journal != NULL) fail,
Hi Filipe,
(2014/06/23 20:58), Filipe David Borba Manana wrote:
Often when starting a transaction we commit the currently running transaction,
which can end up writing block group caches when the current process has its
journal_info set to NULL (and not to a transaction). This makes our
