Chris Murphy posted on Tue, 09 Aug 2016 20:25:39 -0600 as excerpted: > 1 size 50.93TiB used 22.67TiB path /dev/sda1 > > What is the exact nature of this block device? > > If getting this back up and running is urgent I suggest inquiring on IRC > what the next steps are. > > In the meantime I'd get a btrfs-image (which is probably going to be > quite large given metadata is 60GiB), if that pukes then see if 'btrfs > inspect-internal dump-tree /dev/sda1 > dumptree.log' which may also fail > but before it fails might contain something useful. Obviously btrfs > check shouldn't crash so that's a bug already. I'd suggest that at 50+ TB size, 22+ TB used, given btrfs check's known memory usage, the crash may well simply be due to lack of memory. It's very likely that will require well over the 16 GiB memory that's reasonably common these days, and if there's no swap to fill in the gap... There's a low memory mode check under development right now, but it's not complete yet. (FWIW my usage is at the other extreme, quarter TB SSDs and partitioned down beyond that, so the largest btrfs is well under 50 GiB usable, tho it's pair-device raid1 so about 50 GiB total. That's too small to be practical for many, but at least until the low-memory btrfs check or until 32 and 64 GiB RAM becomes common, single filesystems in the double- digit TB may arguably be too big to be practical, at least for other than the lucky few with the sort of memory required, as well.) -- 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
