Am Fri, 1 Apr 2016 07:57:25 +0200 schrieb Marc Haber <mh+linux-bt...@zugschlus.de>:
> On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote: > > Am Thu, 31 Mar 2016 23:00:04 +0200 > > schrieb Marc Haber <mh+linux-bt...@zugschlus.de>: > > > I find it somewhere between funny and disturbing that the first > > > call of btrfs check made my kernel log the following: > > > Mar 31 22:45:36 fan kernel: [ 6253.178264] EXT4-fs (dm-31): > > > mounted filesystem with ordered data mode. Opts: (null) Mar 31 > > > 22:45:38 fan kernel: [ 6255.361328] BTRFS: device label fanbtr > > > devid 1 transid 67526 /dev/dm-31 > > > > > > No, the filesystem was not converted, it was directly created as > > > btrfs, and no, I didn't try mounting it. > > > > I suggest that your partition contained ext4 before, and you didn't > > run wipefs before running mkfs.btrfs. > > I cryptsetup luksFormat'ted the partition before I mkfs.btrfs'ed it. > That should do a much better job than wipefsing it, shouldnt it? Not sure how luksFormat works. If it encrypts what is already on the device, it would also encrypt orphan superblocks. If it actually wipes the device, the orphan superblock should be gone. This suggests it does not wipe the device: https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption: > Encryption options for LUKS mode > The cryptsetup action to set up a new dm-crypt device in LUKS > encryption mode is luksFormat. Unlike the name implies, it does not > format the device, but sets up the LUKS device header and encrypts > the master-key with the desired cryptographic options. Thus, I may very well have an orphan superblock lying around. -- Regards, Kai Replies to list-only preferred. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
