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 13:28:44 +0900 [thread overview]
Message-ID: <20131023132844.2a206238@virtall.com> (raw)
In-Reply-To: <20131022162019.GY1032@twin.jikos.cz>
On Tue, 22 Oct 2013 18:20:19 +0200
David Sterba <dsterba@suse.cz> wrote:
> > However, it's not possible to work with this system via SSH, because
> > these keep popping up few times every minute:
>
> Probably only some of the files that get accessed during ssh login is
> corrupted, but the scrub does not get far enough to let you know the
> filenames. You can try to look into 'lsof' output which files are open
> by sshd or it's children.
It's not the case.
Files in btrfs mount are not accessed in any way - the scrub was
started after restart, and there is no way anything on this system can
accidentally access data there. This is further confirmed by lsof
output.
> > kernel:[22219.117012] BUG: soft lockup - CPU#2 stuck for 23s!
> > [btrfs:5673] kernel:[22247.100515] BUG: soft lockup - CPU#0 stuck
> > for 23s! [btrfs:5674] kernel:[22247.100519] BUG: soft lockup -
> > CPU#2 stuck for 23s! [btrfs:5673]
>
> Cpus 0 and 2 are stuck and every other attempt to access the broken
> files will pin another cpu.
Scrub was running for some time; after scrubbung about 2.8 TB, the
system was so slow, that it was barely possible to launch any command.
"reboot" issued via ssh took ~8 hours to execute.
A new scrub started after the reboot immediately begins to show "BUG:
soft lockup - CPU#2 stuck for 23s!".
Anyway, it is RAID-1 - I would expect the scrub to either correct
corrupt data (from a copy on the other disk), or mark it as invalid
(both copies corrupt), but not "nearly hang" the server, or?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2013-10-23 4:28 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
2013-10-22 16:20 ` David Sterba
2013-10-23 4:28 ` Tomasz Chmielewski [this message]
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=20131023132844.2a206238@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.