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: Tue, 22 Oct 2013 02:50:25 +0900 [thread overview]
Message-ID: <20131022025025.169941de@virtall.com> (raw)
In-Reply-To: <20131021125317.GK1032@twin.jikos.cz>
On Mon, 21 Oct 2013 14:53:17 +0200
David Sterba <dsterba@suse.cz> wrote:
> On Mon, Oct 21, 2013 at 03:10:32PM +0900, Tomasz Chmielewski wrote:
> > Note the "BTRFS critical (device sdd1): unable to find logical
> > 7598242613674844160 len 4096" there; after that, the fs freezes and
> > system won't reboot; has to be power cycled.
>
> From the first mail:
> [67893.390592] BTRFS critical (device sdb5): unable to find logical
> 69225652694147072 len 4096
>
> > [ 9138.480011] BTRFS critical (device sdd1): unable to find logical
> > 7598242613674844160 len 4096
>
> 69225652694147072 = 0xf5f05d462de000 = something that looks like
> inctruction fragments 7598242613674844160 = 0x6972616661532000 =
> "irafaS" -> Safari?
>
> Something has corrupted the memory and stored the bytes on disk where
> btrfs finds the garbage and chokes. Try read-only mount and run scrub.
I'm getting these every few seconds when running scrub - expected?
kernel:[ 3809.964073] BUG: soft lockup - CPU#6 stuck for 23s! [btrfs:13127]
Message from syslogd@bkp010 at Oct 21 17:49:22 ...
kernel:[ 3809.964075] BUG: soft lockup - CPU#3 stuck for 23s! [btrfs:13128]
Message from syslogd@bkp010 at Oct 21 17:49:30 ...
kernel:[ 3817.959359] BUG: soft lockup - CPU#4 stuck for 22s! [btrfs:13189]
Message from syslogd@bkp010 at Oct 21 17:49:30 ...
kernel:[ 3817.959362] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs:13190]
Message from syslogd@bkp010 at Oct 21 17:49:50 ...
kernel:[ 3837.947582] BUG: soft lockup - CPU#6 stuck for 22s! [btrfs:13127]
Message from syslogd@bkp010 at Oct 21 17:49:50 ...
kernel:[ 3837.947585] BUG: soft lockup - CPU#3 stuck for 22s! [btrfs:13128]
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2013-10-21 17:50 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 [this message]
2013-10-22 15:46 ` David Sterba
2013-10-22 16:04 ` Tomasz Chmielewski
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=20131022025025.169941de@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 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.