From: "Chris Samuel" <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Bug in mkfs.btrfs?!
Date: Sun, 23 Jan 2011 09:54:34 +1100 [thread overview]
Message-ID: <c4e20f24127699d27aca4fa8c56f4d33.squirrel@csamuel.org> (raw)
In-Reply-To: <20110122155612.GA3664@scooter>
On Sun, January 23, 2011 2:56 am, Felix Blanke wrote:
> It was a simple:
>
> mkfs.btrfs -L backup -d single /dev/loop2
>
> But it also happens without the options, like:
>
> mkfs.btrfs /dev/loop2
>
>
> /dev/loop2 is a loop device, which is aes encrypted. The output of
> "losetup /dev/loop2":
>
> /dev/loop2: [0010]:5324
> (/dev/disk/by-id/ata-WDC_WD6400AAKS-22A7B2_WD-WCASY7780706-part3)
> encryption=AES128
I'm not familiar with losetup, is /dev/loop2 a symlink ?
If so could you post an ls -l of /dev/loop2 please ?
cheers,
Chris
--
Chris Samuel, Melbourne, Australia
http://www.csamuel.org/
next prev parent reply other threads:[~2011-01-22 22:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 14:45 Bug in mkfs.btrfs?! Felix Blanke
2011-01-22 14:52 ` Felix Blanke
2011-01-22 15:11 ` Hugo Mills
2011-01-22 15:45 ` Hugo Mills
2011-01-22 15:56 ` Felix Blanke
2011-01-22 22:54 ` Chris Samuel [this message]
2011-01-22 23:03 ` Felix Blanke
2011-01-23 18:18 ` Hugo Mills
2011-01-23 22:02 ` Goffredo Baroncelli
2011-01-23 23:15 ` Felix Blanke
2011-01-24 7:42 ` Helmut Hullen
2011-01-24 9:41 ` Felix Blanke
2011-01-23 23:27 ` Hugo Mills
2011-01-23 23:58 ` Felix Blanke
2011-01-24 1:53 ` Fajar A. Nugraha
2011-01-24 9:38 ` Felix Blanke
2011-01-24 13:01 ` Felix Blanke
2011-01-24 13:13 ` Hugo Mills
2011-01-24 13:53 ` Felix Blanke
2011-01-24 14:29 ` Hugo Mills
2011-01-24 14:34 ` Hugo Mills
2011-01-24 14:44 ` Felix Blanke
2011-01-24 16:52 ` Felix Blanke
2011-01-24 17:00 ` Hugo Mills
2011-01-24 21:04 ` Felix Blanke
2011-01-24 21:14 ` Felix Blanke
2011-01-24 14:35 ` Felix Blanke
2011-01-25 0:15 ` LOOP_GET_STATUS(64) truncates pathnames to 64 chars (was Re: Bug in mkfs.btrfs?!) Chris Samuel
2011-02-10 12:29 ` Petr Uzel
2011-02-11 13:04 ` Felix Blanke
2011-02-11 13:04 ` Felix Blanke
2011-02-11 18:59 ` Milan Broz
[not found] ` <AANLkTi=Arg-09F0DXsWNhsYgyPar=rKs7G_OQG2uMm4f@mail.gmail.com>
2011-02-11 19:31 ` Milan Broz
2011-02-11 19:41 ` Felix Blanke
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=c4e20f24127699d27aca4fa8c56f4d33.squirrel@csamuel.org \
--to=chris@csamuel.org \
--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.