Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: “bio too big” regression and silent data corruption in 3.0
Date: Tue, 09 Aug 2011 10:02:25 -0400	[thread overview]
Message-ID: <4E413DF1.4090809@redhat.com> (raw)
In-Reply-To: <or1uwv7cjz.fsf@livre.localdomain>

On 08/08/2011 06:39 PM, Alexandre Oliva wrote:
> On Aug  7, 2011, Alexandre Oliva <oliva@lsd.ic.unicamp.br> wrote:
>=20
>> tl;dr version: 3.0 produces =E2=80=9Cbio too big=E2=80=9D dmesg entr=
ies and silently
>> corrupts data in =E2=80=9Cmeta-raid1/data-single=E2=80=9D configurat=
ions on disks with
>> different max_hw_sectors, where 2.6.38 worked fine.
>=20
> FWIW, I just got the same problem with 2.6.38.  No idea how I hadn't =
hit
> it before, but it's not a 3.0 regression, just a regular (but IMHO ve=
ry
> serious) bug.
>=20

This is worriesome, I will try and find a usb disk with a small
sectorsize and see if I can reproduce.  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-08-09 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  1:00 “bio too big” regression and silent data corruption in 3.0 Alexandre Oliva
2011-08-08 22:39 ` Alexandre Oliva
2011-08-09 14:02   ` Josef Bacik [this message]
2011-08-09  2:53 ` Alexandre Oliva
2011-08-09 14:01   ` Josef Bacik
2011-08-09  4:04 ` Alexandre Oliva
2011-08-09 19:05 ` Josef Bacik
2011-08-16 16:56 ` 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=4E413DF1.4090809@redhat.com \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=oliva@lsd.ic.unicamp.br \
    /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