Martin Steigerwald posted on Mon, 26 May 2014 14:13:28 +0200 as excerpted: > I donŽt know where this unknown, single chunk came from: > > merkaba:~> btrfs fi df /home > Data, RAID1: total=145.97GiB, used=125.69GiB > System, RAID1: total=32.00MiB, used=48.00KiB > Metadata, RAID1: total=4.00GiB, used=2.65GiB > unknown, single: total=512.00MiB, used=0.00 > merkaba:~> btrfs fi sh /home > Label: 'home' uuid: [ ] > Total devices 2 FS bytes used 128.34GiB > devid 1 size 150.00GiB used 150.00GiB path /dev/dm-0 > devid 2 size 150.00GiB used 150.00GiB path /dev/dm-4 > > Btrfs v3.14.1 > > > Last scrub from last week was okay, but I will rescrub after installing > 3.15-rc7. Answering this aspect (not much help on the larger question, tho)... Kernel 3.15 splits out a subtype of (I think) metadata into a separate type that btrfs-progs 3.14.1 and earlier doesn't know anything about, so it simply lists it as "unknown". Presumably there will be a btrfs 3.15 userspace release shortly after kernel 3.15.0 releases, that will identify this new category properly. It should be harmless, tho. In btrfs-progs 3.14.1, balance, etc, should work with "unknown" as part of metadata. This came up on the list previously, but I've a personal project going on ATM that I've been focusing on and thus didn't do my usual rc2 or so switch, and am still on 3.14 ATM, and I don't remember the exact details. But FWIW, on SSD-backed btrfs raid1 here (still on 3.14 as mentioned), and haven't seen any of these hangs. However, I'm not using LVM or device-mapper at all here, and indeed, don't have it installed. A further difference is that I have the SSDs partitioned and am running multiple independent btrfs, one per partition pair (one on each device), with my largest btrfs being only 24 gig (per device). So if the problem is either LVM or larger size related, I'd not see it. The SSDs are Corsair Neutron 256-gig BTW (not Neutron GTX), only about half partitioned so plenty of unallocated space for the firmware to do its thing. The firmware has as a bullet point feature that it doesn't do anything funny with compression or the like, so if it's some btrfs interaction with compressing firmware or something, I'd not see it either. --- [1] Personal project: Catching up 8 or 9 months of LWN weekly editions, as it happens. I'm on January 30's edition now, so about half done and progressing a month or two per week, so should be caught up in 2-3 weeks at the current rate. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
