search for: cleanup_transaction

...); + btrfs_scrub_continue_super(root); return ret; } diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c index 277fe81..3ebcbbd 100644 --- a/fs/btrfs/transaction.c +++ b/fs/btrfs/transaction.c @@ -1892,7 +1892,9 @@ int btrfs_commit_transaction(struct btrfs_trans_handle *trans, goto cleanup_transaction; } + btrfs_scrub_pause_super(root); ret = write_ctree_super(trans, root, 0); + btrfs_scrub_continue_super(root); if (ret) { mutex_unlock(&root->fs_info->tree_log_mutex); goto cleanup_transaction; -- 1.7.11.7 -- To unsubscribe from this list: send the line "unsubscribe...

...my machine all the time. I tested the patch, but it didn't seem to help. Basically, I was running a kernel compile, and copying files into a different ext3 filesystem (both on LVs), and running pvscan (i.e. invalidate_buffers) repeatedly. At one point, I got several free buffers reported in cleanup_transaction. After that (this is the first time it happened) my kernel compile deadlocked and the kernel is stuck on: ext3_create journal_start start_this_handle log_wait_for_space log_do_checkpoint cleanup_transaction* __wake_up* The last 2 (*) functions appear and disappear from the KDB "bt" out...

...file write is in progress when invalidate_buffers() is called, I get an oops: [[[LVM is in the process of calling PV_FLUSH ioctl => invalidate_buffers()]]] Attempt to refile free buffer Unable to handle kernel NULL pointer dereference at virtual address 00000000 <kdb stuff> refile_buffer cleanup_transaction log_do_checkpoint log_wait_for_space start_this_handle journal_start ext3_file_write do_readv_writev sys_write The oops is from "*(char *)0 = 0" added by the ext3 patch, but I take it that trying to refile a free buffer is fundamentally a bad thing. The oops is caused from __invalidate...

...ve looked at don't seem to lock the kernel. Lastly, I was still getting an assertion generating the "Attempt to refile free buffer", but this one was actually caused by an ext3 journaling function calling refile_buffer(), not derived from invalidate_buffers(). In fs/jfs/checkpoint.c/cleanup_transaction(), you'll note it does some buffer_head bit checks and then calls refile_buffer(). Mine currently looks like the following: if (!buffer_dirty(bh) && !buffer_jdirty(bh) && !buffer_journaled(bh) && bh->b_list !=...

...r_trans, btrfs_destroy_delayed_inodes(root); btrfs_assert_delayed_root_empty(root); - btrfs_destroy_pending_snapshots(cur_trans); - btrfs_destroy_marked_extents(root, &cur_trans->dirty_pages, EXTENT_DIRTY); btrfs_destroy_pinned_extent(root, @@ -3894,6 +3892,8 @@ int btrfs_cleanup_transaction(struct btrfs_root *root) if (waitqueue_active(&root->fs_info->transaction_blocked_wait)) wake_up(&root->fs_info->transaction_blocked_wait); + btrfs_evict_pending_snapshots(t); + t->blocked = 0; smp_mb(); if (waitqueue_active(&root->fs_info->transa...

...2006>] ? __kthread_parkme+0x5e/0x5e kernel: ---[ end trace b584e8ceb6422945 ]--- kernel: BTRFS error (device sdf) in btrfs_save_ino_cache:471: error 28 kernel: btrfs is forced readonly kernel: BTRFS warning (device sdf): Skipping commit of aborted transaction. kernel: BTRFS error (device sdf) in cleanup_transaction:1391: error 28 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

...52986>] [<c0120176>] [<c0139638>] [<c0129067>] [<c01329bc>] [<c0129e40>] [<c012a08e>] [<c010a034>] Code: c6 05 00 00 00 00 00 e9 a6 00 00 00 90 80 7e 29 01 76 0a bb >>EIP; c012c25f <refile_buffer+17/d0> <===== Trace; c015f9bb <cleanup_transaction+12b/158> Trace; c015fbae <log_do_checkpoint+1c6/220> Trace; c015f86d <log_wait_for_space+8d/b0> Trace; c015c98b <start_this_handle+307/3a8> Trace; c015caa3 <journal_start+77/a0> Trace; c0152986 <ext3_notify_change+14a/360> Trace; c0120176 <do_generic_file_read+8d...

Hi all, we got a new test system here and I just also tested btrfs raid6 on that. Write performance is slightly lower than hw-raid (LSI megasas) and md-raid6, but it probably would be much better than any of these two, if it wouldn''t read all the during the writes. Is this a known issue? This is with linux-3.9.2. Thanks, Bernd -- To unsubscribe from this list: send the line

...6/0x1b [32021.732995] ---[ end trace 1fde2d3b6a07b44a ]--- [32021.732998] BTRFS error (device sdb) in btrfs_sync_log:2149: IO failure [32021.733000] btrfs is forced readonly [32021.733076] BTRFS warning (device sdb): Skipping commit of aborted transaction. [32021.733079] BTRFS error (device sdb) in cleanup_transaction:1284: IO failure [32023.378823] r8169 0000:04:00.0: p5p1: link up [32023.378840] IPv6: ADDRCONF(NETDEV_CHANGE): p5p1: link becomes ready [32023.382579] btrfs no csum found for inode 1003377 start 520192 [32024.425378] btrfs no csum found for inode 1003377 start 520192 [32029.383487] btrfs no csum f...