I googled a bit this error (unable to parse branches) and this thing popped up.
mergerfs - help!
-
- gelöst
- OMV 6.x
- k4ZzTBG7Gk
-
-
It shouldn't be using relative paths. What is the output of: sudo omv-showkey mergerfs
-
root@pozz:~# sudo omv-showkey mergerfs
<mergerfs><pools/></mergerfs></services>
-
Create a new pool and save it but don't apply. Then run the omv-showkey command again.
-
root@pozz:~# sudo omv-showkey mergerfs
Code
Alles anzeigen<mergerfs> <pools> <pool> <uuid>9ccbd3de-0f36-454f-bc9e-e8b1c2d15d5a</uuid> <name>test</name> <mntentref>906dc690-88c4-411a-a2a2-da7907e1ec4c</mntentref> <paths>/srv/dev-disk-by-label-Media/Media:/srv/dev-disk-by-label-Media2/Media2</paths> <createpolicy>epmfs</createpolicy> <minfreespace>4</minfreespace> <minfreespaceunit>G</minfreespaceunit> <options>defaults,allow_other,cache.files=off,use_ino</options> </pool> </pools> </mergerfs>
-
And now this:
sudo salt-call -l debug --local --retcode-passthrough state.apply omv.deploy.mergerfs
-
errors out in the last step, same as in error log
Code
Alles anzeigen---------- ID: restart_pool2_mergerfs Function: cmd.run Name: systemctl restart srv-mergerfs-pool2.mount Result: False Comment: Command "systemctl restart srv-mergerfs-pool2.mount" run Started: 01:47:29.568695 Duration: 26.793 ms Changes: ---------- pid: 15904 retcode: 1 stderr: Job failed. See "journalctl -xe" for details. stdout: Summary for local ------------ Succeeded: 6 (changed=6) Failed: 1
-
Code
Alles anzeigenThe job identifier is 540. Sep 15 01:47:29 pozz mount[15908]: * ERROR: unable to parse 'branches' - pool2:cc74f63d-ee78-4ffe-858f-f68a23acdcf9 Sep 15 01:47:29 pozz mount[15908]: * ERROR: mountpoint not set Sep 15 01:47:29 pozz systemd[1]: srv-mergerfs-pool2.mount: Mount process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An n/a= process belonging to unit srv-mergerfs-pool2.mount has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Sep 15 01:47:29 pozz systemd[1]: srv-mergerfs-pool2.mount: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit srv-mergerfs-pool2.mount has entered the 'failed' state with result 'exit-code'. Sep 15 01:47:29 pozz systemd[1]: Failed to mount MergerFS mount for pool2.
-
-
Ok. delete the pool in the plugin and apply. Then try this from the command line:
sudo mkdir /mnt/test
sudo mount -t fuse.mergerfs /srv/dev-disk-by-label-Media/Media:/srv/dev-disk-by-label-Media2/Media2 /mnt/test
-
Ok, I did that. No output in the console and no pools in the mergerfs gui appear.
Should I check something?
-
Yes, the folder is populated, but the mergerfs doesn't show in the gui.
I checked with filezilla, all files are inside.
so to be clear, /mnt/test gets populated and has inside all my folders that you merged (Media and Media2)
It is not however present in the GUI, nor in /srv/mergerfs.
So even if I cannot use the gui, now the problem is solved?
-
A manual mount command shouldn't show up in the gui. I was hoping for an error message. That command is not using the options you specified though. So, it must an option but not sure what. Are the filesystems bigger than 100G?
-
My dear Aaron,
It's 2:13 here and in 4 hours I need to wake up.
Thank you very much for your support, you are really awesome.
If you do think of a solution that could work natively with the plugin in the OMV gui, please write it, if not, I will use it how you made it now.
What I would like to know though, in case I want to rename from /mnt/test to /mnt/pool
Have a good night/day
Thanks again
-
Yes, filesystems are 10TB (media) and 12 TB (media2). The hdd I mean. The files, I don't know for sure maybe 1 remux I have is over 100gb, but I am not sure.
-
Tomorrow....
try:
sudo mkdir /mnt/pool
sudo mount -t fuse.mergerfs test1:pool1 /mnt/pool -o branches=/srv/dev-disk-by-label-Media/Media:/srv/dev-disk-by-label-Media2/Media2,category.create=mfs,minfreespace=4G,fsname=test1:pool1,defaults,allow_other,cache.files=off,use_ino -
Hi Aaron,
root@pozz:~# sudo mount -t fuse.mergerfs test:pool1 /mnt/pool -o branches=/srv/dev-disk-by-label-Media/Media:/srv/dev-disk-by-label-Media2/Media2,category.create=mfs,minfreespace=50G,fsname=test:pool1,defaults,allow_other,cache.files=off,use_ino
* ERROR: unable to parse 'branches' - test:pool1
* ERROR: mountpoint not set
Please note I used test:pool1 instead of test1:pool1 as the folder is /mnt/test (I thought that was a typo).
Should I run it with test1 how you instructed?
LE: also ran the command like yours, same error
root@pozz:~# sudo mount -t fuse.mergerfs test1:pool1 /mnt/pool -o branches=/srv/dev-disk-by-label-Media/Media:/srv/dev-disk-by-label-Media2/Media2,category.create=mfs,minfreespace=50G,fsname=test1:pool1,defaults,allow_other,cache.files=off,use_ino
* ERROR: unable to parse 'branches' - test1:pool1
* ERROR: mountpoint not set
-
Also I read in one thread that you recommand not using mergerfs in docker.
For me, this is the main purpose, since all my software is dockerized.
Mainly I'd want to migrate from
Codevolumes: - /srv/dev-disk-by-label-Media/Media/Drone:/data/drone - /srv/dev-disk-by-label-Media2/Media2/Drone2:/data/drone2
to
- /srv/mergerfs/pool1/Media/Drone:/data/drone
Or I shouldn't use it at all in docker?
ZitatI also wouldn't use a mergerfs pool for your docker path.
-
Please note I used test:pool1 instead of test1:pool1 as the folder is /mnt/test (I thought that was a typo).
Should I run it with test1 how you instructed?
It is just a label. Shouldn't matter.
I can't get this to fail even if the branch directories don't exist. What is the output of: dpkg -l | grep mergerfs
Also I read in one thread that you recommand not using mergerfs in docker.
For me, this is the main purpose, since all my software is dockerized.
We don't recommend using it for docker storage (path set in omv-extras) but it should be ok for docker volumes.
-
Hi Aaron
root@pozz:~# dpkg -l | grep mergerfs
ii mergerfs 2.31.0-1 amd64 another FUSE union filesystem
ii openmediavault-mergerfs 6.3.3 all mergerfs plugin for openmediavault.
We don't recommend using it for docker storage (path set in omv-extras) but it should be ok for docker volumes.
Thanks for the clarification
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!