All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Freitas <sflist@ihonk.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)
Date: Sun, 03 Jan 2010 16:37:54 -0800	[thread overview]
Message-ID: <1262565474.17096.68.camel@phat> (raw)
In-Reply-To: <1262559421.17096.50.camel@phat>

On Sun, 2010-01-03 at 14:57 -0800, Steve Freitas wrote:
> Got some more information. I installed Debian on another disk ("rescue")
> running 2.6.32, pulled the latest btrfs module code from git, applied an
> earlier mentioned patch[1], then compiled and loaded the new module.
> It's able to mount the volume initially...

I've just tried it again with the pure git pull, no patch, and the
result (of an "ls -R /mnt/btrfs_vol") was the same. 'Cept this time it
never gave me a kernel traceback, just unending lines like:

Jan  3 16:36:36 rescue kernel: [ 1046.494252] parent transid verify
failed on 69140480 wanted 28342 found 29646

Steve


  reply	other threads:[~2010-01-04  0:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 23:56 Segfault in btrfsck Steve Freitas
2010-01-03 22:57 ` btrfs volume mounts and dies (was Re: Segfault in btrfsck) Steve Freitas
2010-01-04  0:37   ` Steve Freitas [this message]
2010-01-05 22:55     ` Steve Freitas
2010-01-06  7:52       ` Sander
2010-01-06 15:59         ` Steve Freitas
2010-01-06 17:24           ` Johannes Hirte
2010-01-06 20:11             ` Steve Freitas
2010-01-07  8:23               ` Sander
2010-01-07 18:28             ` What protection does btrfs checksumming currently give? (Was Re: btrfs volume mounts and dies (was Re: Segfault in btrfsck)) Steve Freitas
2010-01-07 19:29               ` jim owens
2010-01-07 21:00                 ` Johannes Hirte

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=1262565474.17096.68.camel@phat \
    --to=sflist@ihonk.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.