Am Thu, 31 Mar 2016 23:00:04 +0200 schrieb Marc Haber <mh+linux-bt...@zugschlus.de>:
> On Thu, Mar 31, 2016 at 10:31:49AM +0800, Qu Wenruo wrote: > > Would you please try the following patch based on v4.5 btrfs-progs? > > https://patchwork.kernel.org/patch/8706891/ > > This also fixes the "bad metadata crossing stripe boundary" on my pet > patient. > > 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. Now, the ext4 superblock is still detected because no btrfs structure or block did overwrite it. I had a similar problem when I first tried btrfs. I think there is some magic dd-fu to damage the ext4 superblock without hurting the btrfs itself. But I leave this to the fs devs, they could properly tell you. -- 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
