From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck --repair /dev/sdc (Was: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked)
Date: Mon, 25 Nov 2013 23:18:08 +0000 [thread overview]
Message-ID: <l70lr5$li0$1@ger.gmane.org> (raw)
In-Reply-To: <l6j4c1$a90$1@ger.gmane.org>
On 20/11/13 20:00, Martin wrote:
> On 20/11/13 17:08, Duncan wrote:
>> Martin posted on Wed, 20 Nov 2013 06:51:20 +0000 as excerpted:
>>
>>> It's now gone back to a pattern from a full week ago:
>>>
>>> (gdb) bt #0 0x000000000042d576 in read_extent_buffer ()
>>> #1 0x000000000041ee79 in btrfs_check_node ()
>>> #2 0x0000000000420211 in check_block ()
>>> #3 0x0000000000420813 in btrfs_search_slot ()
>>> #4 0x0000000000427bb4 in btrfs_read_block_groups ()
>>> #5 0x0000000000423e40 in btrfs_setup_all_roots ()
>>> #6 0x000000000042406d in __open_ctree_fd ()
>>> #7 0x0000000000424126 in open_ctree_fs_info ()
>>> #8 0x000000000041812e in cmd_check ()
>>> #9 0x0000000000404904 in main ()
>>>
>>>
>>> I don't know if that has gone through that pattern during the week but
>>> at a-week-a-time, this is not going to finish in reasonable time.
>>>
>>> How come so very slow?
>>>
>>> Any hints/tips/fixes or abandon the test?
>>
>> You're a patient man. =:^)
>
> Sort of... I can leave it running in the background until I come to need
> to do something else with that machine. So... A bit of an experiment.
Until... No more... And just as the gdb bt shows something a little
different!
(gdb) bt
#0 0x000000000041ddc4 in btrfs_comp_keys ()
#1 0x00000000004208e9 in btrfs_search_slot ()
#2 0x0000000000427bb4 in btrfs_read_block_groups ()
#3 0x0000000000423e40 in btrfs_setup_all_roots ()
#4 0x000000000042406d in __open_ctree_fd ()
#5 0x0000000000424126 in open_ctree_fs_info ()
#6 0x000000000041812e in cmd_check ()
#7 0x0000000000404904 in main ()
Nearly done or weeks yet more to run?
The poor thing gets killed in the morning for new work.
Regards,
Martin
next prev parent reply other threads:[~2013-11-25 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:01 [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked Josef Bacik
2013-10-25 18:27 ` Martin
2013-10-25 18:31 ` Josef Bacik
2013-10-26 23:16 ` Martin
2013-10-27 1:44 ` Josef Back
2013-10-28 15:11 ` Josef Bacik
2013-11-07 1:25 ` Martin
2013-11-11 22:52 ` Martin
2013-11-13 12:08 ` Martin
2013-11-13 13:46 ` Duncan
2013-11-15 17:18 ` Martin
2013-11-19 6:34 ` Martin
2013-11-20 6:51 ` btrfsck --repair /dev/sdc (Was: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked) Martin
2013-11-20 17:08 ` Duncan
2013-11-20 20:00 ` Martin
2013-11-25 23:18 ` Martin [this message]
2013-11-27 6:29 ` Martin
2013-11-20 20:03 ` Martin
2013-11-19 6:25 ` [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked Martin
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='l70lr5$li0$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).