Skip to content
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

Not showing mount point for merged drives #671

Closed
sek0n opened this issue Sep 16, 2023 · 32 comments · Fixed by #753
Closed

Not showing mount point for merged drives #671

sek0n opened this issue Sep 16, 2023 · 32 comments · Fixed by #753

Comments

@sek0n
Copy link

sek0n commented Sep 16, 2023

Type: Bug Report

Your Environment

  • Version used:
    • Docker 0.0.0-master.2b652f8
  • Operating system and version: Linux
  • Torrent client and version: qBittorrent 4.5.5

Summary

Disk usage not showing mount point for drives that are combined via mergerfs

Current Behavior

When trying to add '/media' (int1:s1d1:s1d2:s2d1) to the 'Disk Usage' setting, it doesn't show up.

df -h shows:

❯ docker exec --user node -it flood df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                 226.7G     34.4G    180.8G  16% /
tmpfs                    64.0M         0     64.0M   0% /dev
shm                      64.0M         0     64.0M   0% /dev/shm
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /config
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /downloads
int1:s1d1:s1d2:s2d1      12.4T     10.2T      2.2T  82% /media
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /home/liam
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /etc/resolv.conf
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /etc/hostname
/dev/nvme0n1p2          226.7G     34.4G    180.8G  16% /etc/hosts
tmpfs                     7.7G         0      7.7G   0% /proc/asound
tmpfs                     7.7G         0      7.7G   0% /proc/acpi
tmpfs                    64.0M         0     64.0M   0% /proc/kcore
tmpfs                    64.0M         0     64.0M   0% /proc/keys
tmpfs                    64.0M         0     64.0M   0% /proc/timer_list
tmpfs                     7.7G         0      7.7G   0% /sys/firmware

What's shown in Flood:
vivaldi_sfW1ZU5l3V

Context

If you don't know what mergerfs is, it basically combines multiple mount points into one, while still being able to access the drives individually from their original mounts.

I have it mounted and visible in docker, as you can see from the df -h. I even added another non-merged drive just to test, and it worked (/test in the screenshot), but nothing seems to work to show the /media mount.

It's added in docker as:
/home/USER/media:/media

@AVCaridi
Copy link

Having the same issue here 😕

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

can you run df -T and paste output here?

@AVCaridi
Copy link

Screenshot - 2024 05 29 00 34 12

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

do you have any watchMountPoints config?

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

also please provide a full version of output of this command (in text) so I can test it locally

@AVCaridi
Copy link

do you have any watchMountPoints config?

I don't believe so.

@AVCaridi
Copy link

also please provide a full version of output of this command (in text) so I can test it locally

Run the command in the container or host?

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

also please provide a full version of output of this command (in text) so I can test it locally

Run the command in the container or host?

in the container

@AVCaridi
Copy link

Filesystem           Type       1K-blocks      Used Available Use% Mounted on
overlay              overlay    479079112  22319568 432350152   5% /
tmpfs                tmpfs          65536         0     65536   0% /dev
shm                  tmpfs          65536         0     65536   0% /dev/shm
/dev/sda2            ext4       479079112  22319568 432350152   5% /config
/dev/sda2            ext4       479079112  22319568 432350152   5% /mnt
mergerfs             fuse.mergerfs
                                30879676668 25583157172 3733670076  87% /mnt/mfsPool
/dev/sdg1            ext4       3844549616 2461483184 1187699216  67% /mnt/.mfsd6
/dev/sdd1            ext4       3844549616 3258721948 390460452  89% /mnt/.mfsd4
/dev/sdf1            ext4       3844549616 2708084452 941097948  74% /mnt/.mfsd5
/dev/sdb1            ext4       3844549616 3591697904  57484496  98% /mnt/.mfsd3
/dev/sdc1            ext4       5813176856 5442319624  77814800  99% /mnt/.mfsd2
/dev/sde1            ext4       9688301348 8120850060 1079113164  88% /mnt/.mfsd1
/dev/sda2            ext4       479079112  22319568 432350152   5% /etc/resolv.conf
/dev/sda2            ext4       479079112  22319568 432350152   5% /etc/hostname
/dev/sda2            ext4       479079112  22319568 432350152   5% /etc/hosts
tmpfs                tmpfs        3894804         0   3894804   0% /proc/asound
tmpfs                tmpfs        3894804         0   3894804   0% /proc/acpi
tmpfs                tmpfs          65536         0     65536   0% /proc/kcore
tmpfs                tmpfs          65536         0     65536   0% /proc/keys
tmpfs                tmpfs          65536         0     65536   0% /proc/timer_list
tmpfs                tmpfs        3894804         0   3894804   0% /proc/scsi
tmpfs                tmpfs        3894804         0   3894804   0% /sys/firmware
tmpfs                tmpfs        3894804         0   3894804   0% /sys/devices/virtual/powercap

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

are you sure you parse right output here? info of mergerfs are splited in to 2 lines?

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

consider use df -T | tee output.txt are parse file here

@AVCaridi
Copy link

AVCaridi commented May 28, 2024

Hmm yeah comes up as 1 line on the host but 2 in the container.

/ $ df -T | tee output.txt
tee: output.txt: Permission denied

@AVCaridi
Copy link

Could it just be the name length?

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

df -T | tee /config/output.txt and find file on /config (which is the mounted path in the container, find real path in host)

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

Could it just be the name length?

no. I have longger mount path and they works fine.

@AVCaridi
Copy link

Same result in the output.txt

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

can you paste file?

@AVCaridi
Copy link

output.txt

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

OK, so I should consider using some API to get info of filesystem instead os parsing text...

@trim21 trim21 mentioned this issue May 28, 2024
3 tasks
@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

please try master branch.

@AVCaridi
Copy link

Screenshot - 2024 05 29 03 26 05@2x

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

oops

@trim21 trim21 reopened this May 28, 2024
@AVCaridi
Copy link

Haha that's all good

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

can you run df --exclude-type=devtmpfs --exclude-type=squashfs --exclude-type=tmpfs --exclude-type=overlay command and paste output here?

@AVCaridi
Copy link

Host or container?

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

inside container, always

@AVCaridi
Copy link

df: unrecognized option: exclude-type=devtmpfs
BusyBox v1.36.1 (2024-05-21 13:38:37 UTC) multi-call binary.

Usage: df [-PkmhTai] [-B SIZE] [-t TYPE] [FILESYSTEM]...

Print filesystem usage statistics

	-P	POSIX output format
	-k	1024-byte blocks (default)
	-m	1M-byte blocks
	-h	Human readable (e.g. 1K 243M 2G)
	-T	Print filesystem type
	-t TYPE	Print only mounts of this type
	-a	Show all filesystems
	-i	Inodes
	-B SIZE	Blocksize

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

ok, so some old version df doesn't have --exclude-type......

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

are you using jesec/flood?

@AVCaridi
Copy link

yeah still using the master

@trim21
Copy link
Collaborator

trim21 commented May 28, 2024

should work fine this time.

@AVCaridi
Copy link

Working! Thank you 🙏

@trim21 trim21 closed this as completed May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants