All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Travis Shivers <ttshivers@gmail.com>
Cc: cwillu <cwillu@cwillu.com>, Gurudas Pai <gurudas.pai@oracle.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: Btrfs Storage Array Corrupted
Date: Wed, 29 Feb 2012 08:59:26 -0500	[thread overview]
Message-ID: <20120229135926.GB5054@shiny> (raw)
In-Reply-To: <CAPeorG9E0SDXqoa7VeUASxAbtBf+voQVRgfZ_FtOb3d6nbe-ZQ@mail.gmail.com>

On Tue, Feb 28, 2012 at 09:36:35PM -0600, Travis Shivers wrote:
> I upgraded my kernel so my version is now:
> Linux server 3.3.0-030300rc5-generic #201202251535 SMP Sat Feb 25
> 20:36:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>=20
> The problem has not been solved and I still get the previous errors.

Ok,

Step one is to grab the development version of btrfs-progs, which
currently sits in the dangerdonteveruse branch:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git dan=
gerdonteveruse

Run btrfs-debug-tree -R /dev/sdh

and then run btrfs-debug-tree -b 5568194695168 /dev/sdh

and then run btrfsck /dev/sdh

Send the results of all three here, it should tell us which tree that
block belongs to, and from there we'll figure out the best way to fix
it.

-chris

>=20
> # mount /dev/sdh /mnt/main
> mount: wrong fs type, bad option, bad superblock on /dev/sdh,
>        missing codepage or helper program, or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>=20
> # dmesg
> [  232.985248] device fsid 2c11a326-5630-484e-9f1d-9dab777a1028 devid
> 4 transid 43477 /dev/sdi
> [  232.985434] device fsid 2c11a326-5630-484e-9f1d-9dab777a1028 devid
> 3 transid 43477 /dev/sdh
> [  233.027881] device fsid 2c11a326-5630-484e-9f1d-9dab777a1028 devid
> 2 transid 43477 /dev/sdg
> [  233.065675] device fsid 2c11a326-5630-484e-9f1d-9dab777a1028 devid
> 1 transid 43476 /dev/sdf
> [  284.384320] device fsid 2c11a326-5630-484e-9f1d-9dab777a1028 devid
> 3 transid 43477 /dev/sdh
> [  284.427076] btrfs: disk space caching is enabled
> [  284.442565] verify_parent_transid: 2 callbacks suppressed
> [  284.442572] parent transid verify failed on 5568194695168 wanted
> 43477 found 43151
> [  284.442834] parent transid verify failed on 5568194695168 wanted
> 43477 found 43151
> [  284.443151] parent transid verify failed on 5568194695168 wanted
> 43477 found 43151
> [  284.443159] parent transid verify failed on 5568194695168 wanted
> 43477 found 43151
> [  284.445740] btrfs: open_ctree failed
>=20
>=20
> On Tue, Feb 28, 2012 at 9:16 PM, cwillu <cwillu@cwillu.com> wrote:
> > On Tue, Feb 28, 2012 at 9:00 PM, Travis Shivers <ttshivers@gmail.co=
m> wrote:
> >> Where should I grab the source from? The main repo that you have
> >> listed on your main wiki page
> >> (https://btrfs.wiki.kernel.org/articles/b/t/r/Btrfs_source_reposit=
ories.html)
> >> is down: git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs=
-progs-unstable.git
> >
> > The btrfs wiki is at http://btrfs.ipv5.de . =A0The kernel.org one i=
s a
> > static snapshot of the contents made nearly a year ago, prior to th=
e
> > kernel.org break-in, and should be ignored.
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git=
 is
> > the development tree, although the above patch is in mainline as of
> > 3.3rc5, which probably makes that the easiest way to try it.
--
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:[~2012-02-29 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  0:13 Btrfs Storage Array Corrupted Travis Shivers
2012-02-29  0:34 ` Fajar A. Nugraha
2012-02-29  1:41 ` Gurudas Pai
2012-02-29  2:50   ` Chris Mason
2012-02-29  3:00     ` Travis Shivers
2012-02-29  3:16       ` cwillu
2012-02-29  3:36         ` Travis Shivers
2012-02-29 13:59           ` Chris Mason [this message]
2012-02-29 21:57             ` Travis Shivers
2012-02-29 22:14               ` Chris Mason
2012-02-29 23:11                 ` Travis Shivers
2012-02-29 23:44                   ` Chris Mason
2012-02-29 23:58                     ` Travis Shivers
2012-03-16 17:30                       ` Travis Shivers
     [not found]                       ` <CAPeorG-Zrr-fTaYmHHKQ5=0jL9ZqjbTypGzo7je3g=MJDPmXcA@mail.gmail.com>
2012-03-26 23:15                         ` Travis Shivers

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=20120229135926.GB5054@shiny \
    --to=chris.mason@oracle.com \
    --cc=cwillu@cwillu.com \
    --cc=gurudas.pai@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ttshivers@gmail.com \
    /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.