From: Tomasz Chmielewski <tch@virtall.com>
To: dsterba@suse.cz
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: CPU: 2 PID: 1543 at fs/btrfs/ctree.c:1322 btrfs_search_old_slot+0x338/0x81d [btrfs]()
Date: Wed, 23 Oct 2013 01:04:11 +0900 [thread overview]
Message-ID: <20131023010411.42d30c97@virtall.com> (raw)
In-Reply-To: <20131022154619.GW1032@twin.jikos.cz>
On Tue, 22 Oct 2013 17:46:19 +0200
David Sterba <dsterba@suse.cz> wrote:
> On Tue, Oct 22, 2013 at 02:50:25AM +0900, Tomasz Chmielewski wrote:
> > I'm getting these every few seconds when running scrub - expected?
>
> The system probably locked up again due to the corrupted data. Looking
> at the stacktraces again, this is due to a BUG_ON in
> btrfs_merge_bio_hook, and it does not look like an easy one to fix.
>
> The filesystem is damaged, but we don't know to what extent. It's
> possible that 'btrfs restore' will be able to get to the data.
Actually it's still working.
If I run this:
# btrfs scrub status /mnt/lxc1
scrub status for 8d08ad6d-4543-4fe5-8b1b-640dc1423d41
scrub started at Tue Oct 22 09:53:34 2013, running for 22101 seconds
total bytes scrubbed: 2.61TB with 0 errors
the number of bytes scrubbed is growing every now and then (still, 0 errors).
However, it's not possible to work with this system via SSH, because these keep popping up few times every minute:
Message from syslogd@bkp010 at Oct 22 16:02:10 ...
kernel:[22219.117012] BUG: soft lockup - CPU#2 stuck for 23s! [btrfs:5673]
Message from syslogd@bkp010 at Oct 22 16:02:38 ...
kernel:[22247.100515] BUG: soft lockup - CPU#0 stuck for 23s! [btrfs:5674]
Message from syslogd@bkp010 at Oct 22 16:02:38 ...
kernel:[22247.100519] BUG: soft lockup - CPU#2 stuck for 23s! [btrfs:5673]
Will wait to see if it finishes or if it locks up at some point.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2013-10-22 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 3:21 WARNING: CPU: 2 PID: 1543 at fs/btrfs/ctree.c:1322 btrfs_search_old_slot+0x338/0x81d [btrfs]() Tomasz Chmielewski
2013-10-21 6:10 ` Tomasz Chmielewski
2013-10-21 6:46 ` Liu Bo
2013-10-21 7:06 ` Tomasz Chmielewski
2013-10-21 12:53 ` David Sterba
2013-10-21 17:50 ` Tomasz Chmielewski
2013-10-22 15:46 ` David Sterba
2013-10-22 16:04 ` Tomasz Chmielewski [this message]
2013-10-22 16:20 ` David Sterba
2013-10-23 4:28 ` Tomasz Chmielewski
2013-10-24 5:54 ` Tomasz Chmielewski
2013-10-24 8:41 ` Tomasz Chmielewski
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=20131023010411.42d30c97@virtall.com \
--to=tch@virtall.com \
--cc=dsterba@suse.cz \
--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).