public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Gustavo Alves <gjalves@gjalves.com.br>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: assertion failures
Date: Fri, 26 Feb 2010 16:10:50 -0500	[thread overview]
Message-ID: <20100226211050.GN12841@think> (raw)
In-Reply-To: <69e11d1f1002261157x1b305776w96f6bfcef4b8ae2f@mail.gmail.com>

On Fri, Feb 26, 2010 at 04:57:27PM -0300, Gustavo Alves wrote:
> In my case, kernel 2.6.32-0.51.rc7.git2.fc13.i686.PAE and BTRFS under=
 LVM2.
>=20

Did you also have power-off based reboots?  Depending on the
configuration LVM (anything other than a single drive) won't send barri=
ers to
the device.

-chris

> ----
> Gustavo Junior Alves
> Specchio Solu=E7=F5es em TI
>=20
>=20
> On Fri, Feb 26, 2010 at 1:15 PM, Chris Mason <chris.mason@oracle.com>=
 wrote:
> > On Fri, Feb 26, 2010 at 11:13:32AM -0500, Chris Mason wrote:
> >> On Thu, Feb 25, 2010 at 03:28:19PM -0300, Gustavo Alves wrote:
> >> > I've got the same error before in a similar situation (24 partit=
ions,
> >> > only two with problems). Unfortunally I erased all data after th=
is
> >> > error. Strange that all I've done was shutdown and poweron the
> >> > machine.
> >>
> >> Basically it looks like the tree of data checksums isn't right. =A0=
Which
> >> kernels were you running when you had these problems?
> >
> > Sorry, I mixed up this corruption with one farther down. =A0The sam=
e
> > question stands though, this error generally means that IO either d=
idn't
> > happen or happened in the wrong place.
> >
> > So, the more details you can give about your config the easier it w=
ill
> > be to nail it down.
> >
> > -chris
> >
> >
> --
> 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
--
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:[~2010-02-26 21:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 13:45 assertion failures Bill Pemberton
2010-02-25  0:40 ` Chris Mason
2010-02-25 14:04   ` Bill Pemberton
2010-02-25 18:28     ` Gustavo Alves
2010-02-26 16:13       ` Chris Mason
2010-02-26 16:15         ` Chris Mason
2010-02-26 19:57           ` Gustavo Alves
2010-02-26 21:10             ` Chris Mason [this message]
2010-02-26 21:26               ` Gustavo Alves
2010-02-26 16:17     ` Chris Mason
2010-02-26 16:41       ` Bill Pemberton
2010-02-26 17:59         ` Chris Mason
2010-02-26 18:11           ` Bill Pemberton
2010-02-26 19:09             ` Chris Mason
2010-02-26 20:43               ` Bill Pemberton
2010-02-26 20:49               ` Diego Calleja
2010-02-26 21:08                 ` Chris Mason
2010-02-28  3:05                   ` Cláudio Martins
2010-02-26 19:11             ` Mike Fedyk
2010-02-26 19:15               ` Chris Mason
2010-02-26 20:45                 ` Bill Pemberton
2010-02-26 20:53                   ` Chris Mason
2010-02-27 22:56                     ` Bill Pemberton
2010-02-26 20:44               ` Bill Pemberton

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=20100226211050.GN12841@think \
    --to=chris.mason@oracle.com \
    --cc=gjalves@gjalves.com.br \
    --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