From: Tobias Grosser <tobias@grosser.es>
To: aagaande@gmail.com, linux-btrfs@vger.kernel.org
Subject: Re: dm-crypt + btrfs preformance - long lockups during io
Date: Wed, 09 Apr 2014 09:45:09 +0200 [thread overview]
Message-ID: <5344FA85.1030802@grosser.es> (raw)
In-Reply-To: <CANOdGizDdNvBjFu+LSGpUdpbO+PeuRLE=Qa-3eQRXhzDtpyFDw@mail.gmail.com>
On Sat, Apr 5, 2014 at 10:54 AM, Anders Aagaard <aagaande@xxxxxxxxx> wrote:
> Hi
>
> I just recently repartitioned my harddrive, and in the process
switched from
> ext4+ecryptfs to dm-crypt and btrfs. I'm on ubuntu 14.04, using kernel
> 3.14.0-031400-generic. I'm using a intel ssd, which btrfs detects
(ssd mode
> enabled according to dmesg).
I also saw and still see lockups on linux 3.8 with a similar
configuration. btrfs on dm-crypt with SSD mode. I use slightly different
mount options:
/dev/mapper/sda4_crypt on /home type btrfs
(rw,noatime,flushoncommit,subvol=@home)
/dev/mapper/sda4_crypt on /store type btrfs (rw,subvol=@store)
/dev/mapper/sda4_crypt on /home/grosser type btrfs
(rw,noatime,flushoncommit,subvol=@grosser)
(I previously also used compression. This is disabled at the moment, but
compressed files are still around)
latencytop gives the following information:
firefox: 22909.8 ms latency, cause fsync() on a file
The corresponding backtrace is:
btrfs_log_inode_parent
[btrfs]
btrfs_log_dentry_safe
[btrfs]
btrfs_sync_file
[btrfs]
do_fsync
sys_fsync
system_call_fastpath
There are also 6 processes called
btrfs-endio-wri?? with 1050-1391 ms latency due to [sleep_on_page].
The corresponding backtraces are (3x):
sleep_on_page
wait_on_page_bit
read_extent_buffer_pages
[btrfs]
btree_read_extend_buffer_pages.constprop.119
[btrfs]
read_tree_block
[btrfs]
read_node_slot
[btrfs]
push_leaf_right
[btrfs]
split_leaf
[btrfs]
btrfs_search_slot
[btrfs]
btrfs_csum_file_blocks
[btrfs]
add_pending_csums.isra.42
[btrfs]
btrfs_finish_ordered_io
[btrfs]
1x:
sleep_on_page
wait_on_page_bit
read_extent_buffer_pages
[btrfs]
btree_read_extend_buffer_pages.constprop.119
[btrfs]
read_tree_block
[btrfs]
read_block_for_search.isra.51
[btrfs]
btrfs_search_slot
[btrfs]
btrfs_insert_empty_items
[btrfs]
run_clustered_refs
[btrfs]
btrfs_run_delayed_refs
[btrfs]
__btrfs_end_transaction
[btrfs]
btfs_end_transaction
[btrfs]
1x
sleep_on_page
wait_on_page_bit
read_extent_buffer_pages
[btrfs]
btree_read_extend_buffer_pages.constprop.119
[btrfs]
read_tree_block
[btrfs]
read_node_slot
[btrfs]
push_leaf_left
[btrfs]
split_leaf
[btrfs]
btrfs_search_slot
[btrfs]
btrfs_insert_empty_items
[btrfs]
btrfs_csum_file_blocks
[btrfs]
add_pending_csums.isra.42
[btrfs]
1x
sleep_on_page
wait_on_page_bit
read_extent_buffer_pages
[btrfs]
btree_read_extend_buffer_pages.constprop.119
[btrfs]
read_tree_block
[btrfs]
read_node_slot
[btrfs]
push_leaf_right
[btrfs]
split_leaf
[btrfs]
btrfs_search_slot
[btrfs]
btrfs_csum_file_blocks
[btrfs]
add_pending_csums.isra.42
[btrfs]
btrfs_finish_ordered_io
[btrfs]
At the moment of deadlock, I am just running normal desktop applications
like thunderbird and firefox.
Cheers,
Tobias
Any idea where such long delays may come from.
prev parent reply other threads:[~2014-04-09 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANOdGizDdNvBjFu+LSGpUdpbO+PeuRLE=Qa-3eQRXhzDtpyFDw@mail.gmail.com>
2014-04-05 9:02 ` dm-crypt + btrfs preformance - long lockups during io Anders Aagaard
2014-04-09 7:45 ` Tobias Grosser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5344FA85.1030802@grosser.es \
--to=tobias@grosser.es \
--cc=aagaande@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.