All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Avi Kivity <avi.kivity@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Suddenly, a dead filesystem
Date: Tue, 04 Oct 2011 16:01:06 -0400	[thread overview]
Message-ID: <4E8B6602.8000005@redhat.com> (raw)
In-Reply-To: <CAEbWairdtBX9Rf4XyOreO4BVXp4B0fswKcGw69osj8R6ZGbgsA@mail.gmail.com>

On 10/04/2011 03:50 PM, Avi Kivity wrote:
>> Yup I would love to investigate this, what kind of snapshot?
> 
> LVM snapshot.
> 
>> Did you dd
>> the drive or soemthing?  Let me know where to pull it down.
> 
> Um, it's my /home.  It's not leaving home.  But if you have test
> kernels or btrfscks you want to throw at it, I'm happy to help.

Hah well you can run btrfs-image -c <0-9> -t <number of threads> on your
device it will create a image of the broken fs for me to look at and
doesn't copy any of the data and zero's out any inline extents, the only
thing I'll potentially would be able to see is the file names.  If
that's acceptable just upload it somewhere for me to pull down.  If not
I'll put together a debug patch for you to try out.  Thanks,

Josef

  reply	other threads:[~2011-10-04 20:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 14:15 Suddenly, a dead filesystem Avi Kivity
2011-08-23 14:23 ` Josef Bacik
2011-08-23 21:08   ` Avi Kivity
2011-09-30 21:40     ` Avi Kivity
2011-10-03 14:34       ` Josef Bacik
2011-10-03 15:12         ` Avi Kivity
2011-10-03 18:07           ` Avi Kivity
2011-10-04 14:39             ` Avi Kivity
2011-10-04 19:40               ` Avi Kivity
2011-10-04 19:41                 ` Josef Bacik
2011-10-04 19:50                   ` Avi Kivity
2011-10-04 20:01                     ` Josef Bacik [this message]
2011-10-04 20:06                       ` Avi Kivity
2011-08-23 14:27 ` Hugo Mills
2011-08-23 14:28   ` Hugo Mills
2011-08-23 22:22   ` Avi Kivity

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=4E8B6602.8000005@redhat.com \
    --to=josef@redhat.com \
    --cc=avi.kivity@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.