Thanks! A configurable limit would be nice, but p will do just fine. My mistake was thinking that my mounted file system's root would be my btrfs's root, which

Thanks! A configurable limit would be nice, but p will do just fine. My mistake was thinking that my mounted file system's root would be my btrfs's root, which of course it is not, it's itself a subvolume (a standard configuration has @system and @home, i think). When I re-ran btdu on the separately mounted root volume it worked flawlessly. Maybe I'm the only one making this mistake, but maybe it makes sense to remind people of this. Especially since currently btdu doesn't fail with an error, but seems to try to navigate up to the root volume (it shows my @-subvolumes from wherever I start) but then presents a broken result.