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 15:41:32 -0400 [thread overview]
Message-ID: <4E8B616C.1030103@redhat.com> (raw)
In-Reply-To: <CAEbWaioOMeVeACT4wMceP=obyjwrNGd7H8Rs77QrC1d=iCSgqA@mail.gmail.com>
On 10/04/2011 03:40 PM, Avi Kivity wrote:
> On Tue, Oct 4, 2011 at 4:39 PM, Avi Kivity <avi.kivity@gmail.com> wrote:
>> On Mon, Oct 3, 2011 at 8:07 PM, Avi Kivity <avi.kivity@gmail.com> wrote:
>>>>>
>>>>> Thats -EIO, is there any messages before the bug? Thanks,
>>>>>
>>>>
>>>> Not that I recall. I'll check again when I'm near the poor thing again.
>>>>
>>>
>>> Confirmed - that's the first relevant message.
>>>
>>> As to -EIO, I dd'ed the entire volume and no errors were found.
>>>
>>
>> btw, is there a new version of fsck.btrfs I can try? The one I have
>> segfaults immediately.
>>
>
> Meanwhile, I used btrfs-zero-log and was able to remount. I have a
> snapshot of the dead filesystem, if someone wants to investigate.
Yup I would love to investigate this, what kind of snapshot? Did you dd
the drive or soemthing? Let me know where to pull it down. Thanks,
Josef
next prev parent reply other threads:[~2011-10-04 19:41 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 [this message]
2011-10-04 19:50 ` Avi Kivity
2011-10-04 20:01 ` Josef Bacik
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=4E8B616C.1030103@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox