From: Chris Mason <chris.mason@ORACLE.COM>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Broken btrfs; btrfsck and btrfs-debug-tree core dumps
Date: Wed, 17 Feb 2010 09:11:12 -0500 [thread overview]
Message-ID: <20100217141112.GG29430@think> (raw)
In-Reply-To: <20100216101543.GA11570@alea.gnuu.de>
On Tue, Feb 16, 2010 at 11:15:44AM +0100, J=F6rg Sommer wrote:
> Hi,
>=20
> I've an utterly broken btrfs that makes btrfsck and btrfs-debug-tree
> (version 0.19) die with a core dump. Are you interested in this
> filesystem? Unfortunely, it has a size of 1TB and contains the backup=
s of
> our customers. Hence, I can't publish it. How can we come together?
I'm most interested in how it got corrupted. Was there a specific even=
t
that you think caused this?
-chris
--
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
prev parent reply other threads:[~2010-02-17 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 10:15 Broken btrfs; btrfsck and btrfs-debug-tree core dumps Jörg Sommer
2010-02-17 14:11 ` Chris Mason [this message]
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=20100217141112.GG29430@think \
--to=chris.mason@oracle.com \
--cc=joerg@alea.gnuu.de \
--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