From: Alexandre Oliva <oliva@gnu.org>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs\@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
<axboe@kernel.dk>
Subject: Re: I/O errors block the entire filesystem
Date: Wed, 15 May 2013 15:56:48 -0300 [thread overview]
Message-ID: <or61ykqdfz.fsf@livre.home> (raw)
In-Reply-To: <20130515135326.GD1765@localhost.localdomain> (Josef Bacik's message of "Wed, 15 May 2013 09:53:26 -0400")
On May 15, 2013, Josef Bacik <jbacik@fusionio.com> wrote:
> So this should only happen in the case that you are on a dm device it looks
> like, is that how you are running?
That was my first thought, but no, I'm using partitions out of the SATA
disks directly. I even checked for stray dm out of fake raid or
somesuch, but the dm modules were not even loaded, and perusing
/sys/block confirms the “scsi” devices are actual ATA disks.
Further investigation suggested that when individual 512-byte blocks are
read from a disk (that's the block size reported by the kernel), the
underlying disk driver is supposed to inform the upper layer about what
it could read by updating the bio_vec bits in precisely the observed
way.
--
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
next prev parent reply other threads:[~2013-05-15 18:57 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 [this message]
2013-05-15 2:48 ` Liu Bo
2013-05-15 18:45 ` Alexandre Oliva
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=or61ykqdfz.fsf@livre.home \
--to=oliva@gnu.org \
--cc=axboe@kernel.dk \
--cc=jbacik@fusionio.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