I deleted the file from the thread, as it might contain sensitive information.
Is this the folder "Musik"?
Delete this section starting with line 714.
Again: keep a copy of the file in case something goes wrongCode
And this one starting from line 1195Code
If you edit this file on WIndows, use Notepad++
I have send you the file by "conversations"
Forgot: after you changed the file run
omv-salt stage run prepare
omv-salt stage run deploy
If there are any errors, post them here.
Thank you so much.
- For the heads up with sensitive information (wasn't aware, checked briefly but bein noob, what do I know...)
- For all the help
- For the friendly conversations assist.
I downloaded the file.
How do I go about:
- Rename old file via WinSCP
- Upload new file properly named
- Reboot OMV
Does that sound correct?
Do the steps in #28 after uploading the file.
No need to reboot.
The shares are all back!!!
GREAT MANY THANKS!!!
Now as for the symlink approach, maybe you can shed a little light or rather tell me if this makes sense. I plan to
- Create an empty folder on the main SSD holding only OMV partition and a second one for docker images
- Inside this folder, I want three more folders for altogether three user scenarios
- Inside these folders I create symlinks pointing to folders these scenarios need (essentially a subset of what is on all the drives)
- I set up permissions via the SMB "Edit share" options (such as "Read only")
- In addition to that, the folders are being shared to users who are given permissions in Acess Rights Management / User
Does that make sense? Or how would you go about this?
The main goal is pooling together contents from various disks in a sensible manner so that I don't have to share a lot of drives inside windows but only see one or two shares per machine
I assume you don't want to go back to mergerfs / unionfs?
What was the issue you had?
I think it would make things easier.
I created the folder you deleted ("Musik"), consisting of folders on two separate drives.
This drive works not read-only on one of the accounts: listening is one, but adding new music another scenario. I thought I set up everything in such a way as to make mergerfs make use of the exisitng folder structure. I added a few albums and from the player I use (foobar), everything looked great. I have set up another acces at the same time (the entire 2 drives that the mergerfs volume had taken a subset of) in order to check what is happening on the disk level.
There I saw that the music I had added was not in the right place buton the other drive. The setup goes like:
now instead of copying the new music to folder 3 on drive 1. OMV had added created a new folder 3 on drive 2, copying the new album there. At the same time, an entire set of empty folders were structured in the same way on the other drive.
I sorted everything out manually but in the end decided that mergerfs was a little too complex for me to understand and use - especially to sort out in case something goes wrong.
Why do you think that symlinks are more complicated?
Ok, now this symlink business through OMV really annoys me. I tried about 10 times now without even getting a single one right.
Is there a good explanation as to how to set these things up?
are you talking about the "Symlinks" section under "Services"?
This is what I have been using, I think:
If not: Where can I find this plugin?
Yes, that is the one I thought of.
Have you tried to create the symlink from CLI with the link I posted?
Yes, I know that post, thank you.
I tried creating symlinks with CLI. It does work on a CLI level and I see the symlinks created in WinSCP. There, they also work.
But these symlinks never show up in Windows.
Try to add
follow symlinks = yes
to the extra options of smb service in the GUI of OMV.
Then save + apply