From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felix Blanke Subject: Re: Bug in mkfs.btrfs?! Date: Sun, 23 Jan 2011 00:03:26 +0100 Message-ID: <20110122230326.GA20398@scooter> References: <20110122144513.GA2539@scooter> <20110122145222.GB2539@scooter> <20110122151124.GC29985@carfax.org.uk> <20110122155612.GA3664@scooter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: List-ID: Hi, no :) loop2 is the decrypted device. A small example: /dev/sda1 is encrypted. Then you run losetup with some options and /dev/sda1, enter the password and after that /dev/loop1 will be created. >>From now on you're using /dev/loop1 as your device node, e.g. fdisk -l /dev/loop1 If you would use /dev/sda1 instead you would just see garbage, because of the encryption :) Regards, Felix On 23. January 2011 - 09:54, Chris Samuel wrote: > Date: Sun, 23 Jan 2011 09:54:34 +1100 > From: Chris Samuel > To: linux-btrfs@vger.kernel.org > Subject: Re: Bug in mkfs.btrfs?! > > > 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/ > > -- > 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 ---end quoted text---