omv-extras plugins - porting progress to OMV 6.x (done)

Zitat von ryecoaaron

Post a screenshot of your job. I am guessing you are leaving a field empty.

Aha, you are right. I didn't need a comment so left the field empty. Filling it with any character does the job right. It doesn't leave a notice that it needs to be filled. Thx for the plugin and pointing that out

Edit: the commentfield needs to be activated and filled with a character. Deleting the character (because you don't need it) still makes it possible to save the job. Without activation of the field it results in error 400.

brand new installation. I just test everything is still perfect. until then i use omv5.

route is just as good: / srv / example hdd /

folder cannot be mounted does not work:

/ srv / example hdd / folder

Working thank you for the work.

Zitat von ryecoaaron

6.0.2 is in the repo. It is possible you were getting this error because the pool directory (/srv/mergerfs) did not exist and the mount file is not creating it.

Complete reinstallation Now it works great.

Thank you very much

I reinstalled from scratch again but now things are worse. I cannot mount any filesystems. The "select filesystems" input doesn't show anything to chose from. All the disks are present in the Disks section.

Is it possible to go back to OMV 5 on Bullseye? Nothing is working here for me.

Zitat von ryecoaaron

where are you looking?

Are they mounted by OMV?

No. OMV 5 only works on Buster. OMV 6 only works on Bullseye.

Browser cache? I have omv6 on six VMs and I am going to upgrade my main server soon. I don't know why things would be so much worse now.

Alles anzeigen

I hadn't removed all the desktop packages from the Bulleyes installation so I think the drives were automounted on boot. It works now that I mounted them directly in OMV after removing the desktop environment.

Zitat von ryecoaaron

The only reason I can think that would happen is if it has something to do with capital letters (which I never use) or it didn't mount for some reason. If the mount isn't in /proc/mounts, it won't be able to find it.

After a reinstall i tried again. My "TVALL" works fine and I can share it.
I created my MOVIEALL merge and it works but I cannot share it. The ability to browse for filesystems in the "Shared Folders" section is broken.
I get a 500 error saying it cannot extract the UUID for MOVIEALL.

Here is the result of mounts in proc

TVALL:2dababce-a736-4dd9-ac19-554ef3245199 /srv/mergerfs/TVALL fuse.mergerfs rw,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0

MOVIEALL:0990ecc3-5f49-4b57-a3ea-199b72b9c876 /srv/mergerfs/MOVIEALL fuse.mergerfs rw,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0

ryecoaaron: Thank you very much for porting mergerfs, it was the last plugin I was waiting for.

to those who upgraded: What's the best way of handling mergerfs when going from 5 to 6? I imagine the best way would be to disable mergerfs in 5 and re-enable it in 6. Any other suggested steps? Thank you in advance.

Zitat von ryecoaaron

I spent days getting the upgrade to work. If you have to disable it, I wasted a lot of time. https://github.com/OpenMediaVa…f.service.mergerfs_6.0.sh

I haven't gone through the upgrade process yet, just wanted to be prepared. I simply assumed disabling and reenabling mergerfs plugin after upgrade was the safer option. Your work is hugely appreciated, even more so if the transition from 5 to 6 is that smooth. Thank you once again.

Zitat von ryecoaaron

Why are you using a desktop image?

I'll have to look. I hate capital letters and that is the only thing I can think of.

I spent days getting the upgrade to work. If you have to disable it, I wasted a lot of time. https://github.com/OpenMediaVa…f.service.mergerfs_6.0.sh

I am using the desktop image because it's the only image I can find that is arm64 for the Raspberry pi. This worked perfectly fine with OMV5.

Why would capital letters be a problem? It also worked perfectly fine with OMV5. I guess i can try without though. Why would one merge work and not the other? They are both capital letters.

Zitat von inertia

I am using the desktop image because it's the only image I can find that is arm64 for the Raspberry pi

You need to look better:

http://downloads.raspberrypi.o…os_lite_arm64-2021-11-08/

Zitat von ryecoaaron

More info would be helpful. And just to remind people, this is a complete rewrite. I really hope people are just installing it on their main systems and then expect me to help fix something that might have broke.

I reinstalled OMV6. It's a new fresh, but not updated from OMV5. The omv-extras and mergerfs plugin is also fresh.

I tried to merge 4 partitions, named media, so I wrote path like this:

/srv/dev-disk-by-uuid-00000000-1234-5678-0000-123456789010
/srv/dev-disk-by-uuid-10000000-1234-5678-0000-123456789011
/srv/dev-disk-by-uuid-20000000-1234-5678-0000-123456789012
/srv/dev-disk-by-uuid-30000000-1234-5678-0000-123456789013

But I got the notice: 500 - Internal Server ErrorCouldn't extract an UUID from the provided path '/srv/mergerfs/media'.

I tried to add "/" after path, such as:

/srv/dev-disk-by-uuid-00000000-1234-5678-0000-123456789010/
/srv/dev-disk-by-uuid-10000000-1234-5678-0000-123456789011/
/srv/dev-disk-by-uuid-20000000-1234-5678-0000-123456789012/
/srv/dev-disk-by-uuid-30000000-1234-5678-0000-123456789013/

But I got the same ERROR notice.

I checked the path /srv/, and found there's no "mergerfs" folder. Even I make a folder named "mergerfs", it still replied the 500 ERROR notice.

Zitat von ryecoaaron

Did you miss the part about a complete rewrite? What worked in OMV 5 is irrelevant. It isn't mergerfs having the problem. It is the plugin. There are many times case breaks things. I'm not saying that is the issue. I was just guessing. It could an RPi thing too. I still need to look but I am still putting out fires with other omv 6.x users. New release time is my favorite........

I did not miss that part but I have gone into this upgrade to OMV 6 without due diligence. I was only trying to say that with the previous plugin capitalization was not a problem not that I expected this plugin to work flawlessly because v5 did.

I thought OMV 6 was released as a stable version and went ahead and installed it so did not take the time to look for issues.

I appreciate that the mergerfs plugin is brand new and buggy but why capital letters works with one merge and not the other clearly means its not capitalization per se that's the problem. Maybe it's just creating more than one merge that is the problem?

I appreciate you are frustrated with users not knowing what they are doing or asking questions without research but I didn't think to read through 10 pages of information before I installed OMV 6 just to check if the mergerfs plugin is stable.

I have gone back to OMV 5 now and everything is working as I want. There's far too many problems still and unfortunately i dont have a spare system to help out and test further and report all the bugs.

+1 with an error that the File name is too long (and I am not using capital characters) while restart the mergerfs Pool.

It's no big thing at the moment as I am running MergerFS in fstab anyway without the plugin but just wanted to give it a go...

ID: restart_pool_mergerfs
Function: module.run
Result: False
Comment: An exception occurred in this state: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/state.py", line 2171, in call
ret = self.states[cdata["full"]](
File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
return self.loader.run(run_func, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
return _func_or_method(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2316, in wrapper
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 746, in _decorate
return self._call_function(kwargs)
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 377, in _call_function
six.reraise(*sys.exc_info())
File "/usr/lib/python3/dist-packages/salt/ext/six.py", line 693, in reraise
raise value
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 360, in _call_function
return self._function(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/states/module.py", line 427, in run
func_ret = _call_function(
File "/usr/lib/python3/dist-packages/salt/states/module.py", line 473, in _call_function
mret = salt.utils.functools.call_function(__salt__[name], *func_args, **func_kwargs)
File "/usr/lib/python3/dist-packages/salt/utils/functools.py", line 159, in call_function
return salt_function(*function_args, **function_kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
return self.loader.run(run_func, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
return _func_or_method(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/modules/systemd_service.py", line 956, in restart
raise CommandExecutionError(_strip_scope(ret["stderr"]))
salt.exceptions.CommandExecutionError: Failed to restart srv-mergerfs-pool.mount: Unit srv-mergerfs-pool.mount failed to load properly: File name too long.
See system logs and 'systemctl status srv-mergerfs-pool.mount' for details.