From: Alexandre Oliva <oliva@gnu.org>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: I/O errors block the entire filesystem
Date: Wed, 15 May 2013 15:45:05 -0300 [thread overview]
Message-ID: <ora9nwqdzi.fsf@livre.home> (raw)
In-Reply-To: <20130515024857.GB20202@liubo.jp.oracle.com> (Liu Bo's message of "Wed, 15 May 2013 10:48:58 +0800")
On May 14, 2013, Liu Bo <bo.li.liu@oracle.com> wrote:
>> In one of the failures that caused machine load spikes, I tried to
>> collect info on active processes with perf top and SysRq-T, but nothing
>> there seemed to explain the spike. Thoughts on how to figure out what's
>> causing this?
> Although I've seen your solution patch in this thread, I'm still curious
> about this senario, could you please share the reproducer script or
> something?
I'm afraid I don't have one. I just use the filesystem on various
disks, with ceph osds and other non-ceph subvolumes and files, and
occasionally I run into one of these bad blocks and the filesystem gets
into these odd states.
> I guess that you're using '-l 64k -n 64k' for mkfs.btrfs
That is correct, but IIUC this should only affect metadata, and metadata
recovery from the DUP block works. It's data (single copy) that fails
as described.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
prev parent reply other threads:[~2013-05-15 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:10 I/O errors block the entire filesystem Alexandre Oliva
2013-05-11 7:16 ` Alexandre Oliva
2013-05-15 13:53 ` Josef Bacik
2013-05-15 18:56 ` Alexandre Oliva
2013-05-15 2:48 ` Liu Bo
2013-05-15 18:45 ` Alexandre Oliva [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=ora9nwqdzi.fsf@livre.home \
--to=oliva@gnu.org \
--cc=bo.li.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox