All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Daniel Witzel <dannyboy48888@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: parent transid verify failures on 2.6.39
Date: Thu, 23 Jun 2011 17:35:19 -0400	[thread overview]
Message-ID: <4E03B197.3060009@redhat.com> (raw)
In-Reply-To: <loom.20110623T230224-841@post.gmane.org>

On 06/23/2011 05:11 PM, Daniel Witzel wrote:
> Well still no cigar, didnt even change the error output. Thank you though for
> at least trying to help. here goes the error info with your patch applied to
> /fs/btrfs/disk-io.c:
>
> mount -o ro /dev/sdf1 (same for c1,d1,etc) /btrfs (dmesg output)
> [ 1647.330104] btrfs: open_ctree failed
> [ 1683.328038] device label 1TB0 devid 1 transid 2135 /dev/sdf1
> [ 1683.344059] parent transid verify failed on 2206281838592 wanted 2135 found
> 1545
> [ 1683.349109] btrfs: open_ctree failed

You didn't apply it right then, because you shouldn't see these errors 
anymore.  Thanks,

Josef

  reply	other threads:[~2011-06-23 21:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 22:42 parent transid verify failures on 2.6.39 Andrej Podzimek
2011-06-23  1:45 ` Chris Mason
2011-06-23 18:26   ` Daniel Witzel
2011-06-23 19:54   ` Josef Bacik
2011-06-23 21:11     ` Daniel Witzel
2011-06-23 21:35       ` Josef Bacik [this message]
2011-06-24 15:46         ` Daniel Witzel
2011-06-24  1:30     ` Andrej Podzimek
2011-06-28 15:46       ` Daniel Witzel
2011-06-28 16:44         ` Mitch Harder
2011-06-28 17:04           ` Daniel Witzel
2011-06-28 17:31           ` Daniel Witzel
  -- strict thread matches above, loose matches on Subject: below --
2011-05-25 19:06 Craig Johnson
2011-05-25 19:28 ` Josef Bacik
2011-05-25 19:32   ` Craig Johnson
2011-07-03  7:09     ` Skylar

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=4E03B197.3060009@redhat.com \
    --to=josef@redhat.com \
    --cc=dannyboy48888@gmail.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 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.