From: Chris Mason <chris.mason@oracle.com>
To: cwillu <cwillu@cwillu.com>
Cc: Geoff Ritter <geoff.ritter@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs seed with luks encrypted devices
Date: Thu, 05 May 2011 19:42:37 -0400 [thread overview]
Message-ID: <1304638900-sup-2004@think> (raw)
In-Reply-To: <BANLkTim013vB+PicvYCziBoyMctX2_jreQ@mail.gmail.com>
Excerpts from cwillu's message of 2011-05-03 21:50:53 -0400:
> On Tue, May 3, 2011 at 7:32 PM, Geoff Ritter <geoff.ritter@gmail.com>=
wrote:
> > Not sure where to report bugs or even find a coherent list of them.=
=C2=A0Sorry
> > if this is already well known.
> >
> > When attempting to use an unlocked encrypted device as either a see=
d device
> > or the writeable device, a kernel bug will be displayed at
> > fs/btrfs/volumes.c:2402 after attempting to add the writeable devic=
e to the
> > mounted read-only seed.
> >
> > STR:
> > 1. =C2=A0cryptsetup luksFormat /dev/sdx1
> > 2. =C2=A0cryptsetup luksOpen /dev/sdx1 luksSeed
> > 3. =C2=A0mkfs.btrfs /dev/mapper/luksSeed
> > 4. =C2=A0mount and add files if you want, then unmount
> > 5. =C2=A0btrfstune -S 1 /dev/mapper/luksSeed
> > 6. =C2=A0mount /dev/mapper/luksSeed /mnt/luksSeed
> > 7. =C2=A0btrfs device add /dev/sdx2 /mnt/luksSeed
> > 8. =C2=A0Observe kernel BUG.
> >
> > I would hope to expect to see an error message if this is never int=
ended to
> > be possible. =C2=A0But normal btrfs file systems appear to function=
normally
> > under both encrypted and lvm partitions.
> >
> > This attached kernel message was from two LVM logical volumes on a =
luks
> > encrypted partition. =C2=A0However, I also tested this with two reg=
ular
> > partitions between endrypted-seed/unencrypted-rw,
> > =C2=A0endrypted-rw/unencrypted-seed, and both encrypted.
Ok, looks like I busted the seed support when I fixed up some of the
chunk allocations. I'll reproduce this and work out a fix.
-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
next prev parent reply other threads:[~2011-05-05 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 1:32 btrfs seed with luks encrypted devices Geoff Ritter
2011-05-04 1:50 ` cwillu
2011-05-05 23:42 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 22:13 Geoff Ritter
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=1304638900-sup-2004@think \
--to=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=geoff.ritter@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.