On Tue, Jan 24, 2017 at 11:56 AM, Omar Sandoval <osan...@osandov.com> wrote:
> Yup, definitely doesn't look like memory corruption. I set up a Fedora
> VM yesterday to try to repro with basically those same steps but it
> didn't happen. I'll try again, but is there anything special about your
> Fedora installation?
Default mkfs. Default mount options.
However, due to subsequent suboptimal situation (installing Windows 10
after Fedora), this Btrfs volume is actually a two device volume: two
partitions with Windows 10 in between them.
[chris@f25h ~]$ sudo btrfs fi show
Label: 'fedora' uuid: c45caf39-a048-4c44-90c9-535dc8003c71
Total devices 2 FS bytes used 51.37GiB
devid 1 size 25.00GiB used 21.03GiB path /dev/nvme0n1p4
devid 2 size 48.83GiB used 43.00GiB path /dev/nvme0n1p6
[chris@f25h ~]$ sudo gdisk -l /dev/nvme0n1
[...snip...]
Number Start (sector) End (sector) Size Code Name
1 2048 411647 200.0 MiB EF00 EFI System Partition
2 411648 2508799 1024.0 MiB 8300
3 2508800 16873471 6.8 GiB 8200
4 16873472 69302271 25.0 GiB 8300 Linux filesystem
5 69302272 229046271 76.2 GiB 0700 Microsoft basic data
6 229046272 331446271 48.8 GiB 8300 Linux filesystem
7 331446272 500118158 80.4 GiB 8E00 Linux LVM
p4 was made to small when adding in Windows; so I shrank Windows to
make p6, and then added p6 to p4. Hence p4 and p6 are the same Btrfs
volume (single profile for metadata and data).
--
Chris Murphy
--
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
