From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: 810d4rk <810d4rk@gmail.com>
Cc: "Fajar A. Nugraha" <list@fajar.net>,
"Chris Mason" <chris.mason@oracle.com>,
"Jérôme Carretero" <cJ-ko@zougloub.eu>,
sander@humilis.net, linux-btrfs@vger.kernel.org
Subject: Re: btrfs encryption problems
Date: Thu, 15 Dec 2011 17:49:17 -0600 [thread overview]
Message-ID: <CAKcLGm_scJ57cC1hHY4rmqTrqwOdndQDbBtj09UYMYYABLb2Tw@mail.gmail.com> (raw)
In-Reply-To: <CAAVfQjm03u6ZZTyvLGrz8VC7MebEkBzQ8Mo_Sqw2kmuEx427vg@mail.gmail.com>
On Thu, Dec 15, 2011 at 1:44 PM, 810d4rk <810d4rk@gmail.com> wrote:
> Is anyone there trying to reproduce the bug??
>
I've been using btrfs and luks encryption on my Acer netbook for about
a year now. I haven't had an unmountable corruption on that computer
yet.
What are your goals now?
Are you trying to recover data from this disk, or are you trying to
accomplish some debugging?
Reviewing the thread, I don't see where you've run btrfsck on the
/dev/mapper/<entry>.
Although btrfsck won't fix anything, it might give some insight as the
the extent of the corruption.
next prev parent reply other threads:[~2011-12-15 23:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 10:38 btrfs encryption problems 810d4rk
2011-11-23 11:09 ` Sander
2011-11-23 19:38 ` 810d4rk
2011-11-24 20:56 ` 810d4rk
2011-11-24 21:06 ` Jérôme Carretero
2011-11-24 21:43 ` 810d4rk
2011-11-24 21:54 ` Jérôme Carretero
2011-11-25 10:40 ` 810d4rk
2011-11-30 11:36 ` 810d4rk
2011-11-30 13:48 ` Chris Mason
2011-11-30 22:15 ` 810d4rk
2011-12-13 6:52 ` 810d4rk
2011-12-13 6:56 ` Fajar A. Nugraha
2011-12-13 11:58 ` 810d4rk
2011-12-15 19:44 ` 810d4rk
2011-12-15 23:49 ` Mitch Harder [this message]
2011-12-23 14:25 ` 810d4rk
2012-03-13 15:50 ` 810d4rk
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=CAKcLGm_scJ57cC1hHY4rmqTrqwOdndQDbBtj09UYMYYABLb2Tw@mail.gmail.com \
--to=mitch.harder@sabayonlinux.org \
--cc=810d4rk@gmail.com \
--cc=cJ-ko@zougloub.eu \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
--cc=sander@humilis.net \
/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;
as well as URLs for NNTP newsgroup(s).