-
-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bind mounts should be in the list of special devices #46
Comments
bind-mounts should be detected already and hidden by default. If that's not the case, could you please paste your |
I can paste one mount, if that helps:
Thanks |
Odd, there should be a |
Really odd, I can reproduce this exact same issue on Ubuntu 20.04 server. this is before doing anything (I got duf using go get):
The /snapd/* directories shouldn't be there, I think. let's try a bind mount:
|
Also seeing this on Kubuntu 20.04 LTS and Raspbian (Debian) 10, duf build from source commit eefe880. I'm wondering if it might be a parsing bug that's also causing filesystems mounted through /dev/mapper, e.g. LUKS volumes, not to be displayed properly in the filesystem column. On both systems I'm seeing incorrect strings, such as |
Similar issue on NixOS unstable, with bind mounts involving btrfs subvolumes. fstab excerpt:
duf excerpt:
/proc/self/mountinfo excerpt:
|
On Arch Linux, 6.8.2 kernel, ext4 bind mounts are not being hidden by |
I have some entries in my /etc/fstab which are bind mounts:
duf
shows them in the list of normal, non-special devices, but I think they should be either hidden or shown in the special devices section. There doesn't seem to be a good way to detect a bind mount other than parsing /etc/fstab.The text was updated successfully, but these errors were encountered: