Posts by chudak


    I still see these errors on R Pi4

    cat /etc/default/rrdcached

    # This file is auto-generated by openmediavault (

    # WARNING: Do not edit this file, your changes will get lost.

    # /etc/default file for RRD cache daemon

    # Full path to daemon


    # Optional override flush interval, in seconds.


    # Where database files are placed. If left unset, the default /tmp will

    # be used. NB: The daemon will reject a directory that has symlinks as

    # components. NB: You may want to have -B in BASE_OPTS.


    # Where journal files are placed. If left unset, journaling will

    # be disabled.


    # FHS standard placement for process ID file.


    # FHS standard placement for local control socket.


    # Any other options not specifically supported by the script (-P, -f,

    # -F, -B).

    BASE_OPTIONS="-B -F -f 3600"

    and running omv-salt deploy run rrdcached did not help.

    Any clues?



    When my proxmox is connecting to a OMV samba share, I see this in the logs:

    [ 25.961611] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
    [ 25.963214] FS-Cache: Duplicate cookie detected
    [ 25.963219] FS-Cache: O-cookie c=00000000de694e05 [p=00000000142e9662 fl=222 nc=1 na=1]
    [ 25.963221] FS-Cache: O-cookie d=00000000666963be n=000000008baf5ac3
    [ 25.963223] FS-Cache: O-key=[8] '020001bdc0a85a02'
    [ 25.963225] FS-Cache: N-cookie c=00000000b44dfe22 [p=00000000142e9662 fl=2 nc=0 na=1]
    [ 25.963227] FS-Cache: N-cookie d=00000000666963be n=00000000d8e14f66
    [ 25.963228] FS-Cache: N-key=[8] '020001bdc0a85a02'

    I don't see any harm done by that (guessing), but wanted to ask if other users had seen this and maybe there is a way to configure my share better/differently so no such errors pop up?


    A suggestion. Run Emby in a docker on the same machine that has the media files on it. This would be your OMV machine, right?

    That's not an option for me, I run on R Pi so it maybe overloaded.

    I am interested about delete files failure in general, but it's not that I can't live without :)

    If I use say 3d party file managers (say from iOS iPad) I have no issues to delete any file.

    In addition I want to touch OMV as little as possible and have it do NAS functions only as found that maybe fragile, maybe because my ignorance.

    You mentioned user and group ID number, hmm..

    In my case on OMV I see:

    uid=1002(emby) gid=100(users) groups=100(users)

    and on emby server:

    id emby

    uid=998(emby) gid=998(emby) groups=998(emby),0(root),44(video),107(render),1000(yuriw)

    So then are not equal ...


    That's cool and helps me get overall permissions settings into good order.

    That's goal #1

    Goal #2 - how do I allow a process/user on a different system using my share to delete files ? (W/R) in general case?

    I can add that user in OMV but so far it did make any difference

    This is def not a high priority issue, but very interesting ...

    My opinion is that the root user ownership of your Videos folder is a poor choice.

    I can't say anything about the files because you haven't shown the permissions and ownership of them yet.

    Files are the same:

    drwxrwsrwx 2 root users

    I did not do anything about permissions, connected a new drive, formatted, added shares etc.

    It could be that rsync kept the permissions.

    Ok and thx.

    Then - what permissions would you use and how would you change them ?

    Is ACL in OMV a good way to do so ?

    (the reason I am asking those details, so I want o do it right!)

    root doesn't own a single file on my system it doesn't need to. What is your use case that needs that?

    How can I find out answer to your questions "What user owns your media files and folders." ?

    Use case:

    emby user on a VM#1 steams video files

    video files live on a samba share on R Pi

    emby needs to be able able to delete video files

    What do you mean by "a samba share controlled by OMV server"?

    It means that a samba shared folder is part of OMV NAS and as such OMV has full control over it.

    Can you please then describe what you do in such situation?

    This is not OMV directly related question, but it’s somewhat connected to OMV and I’m sure smart people here better then others positioned to know the answer to this.

    Say you use Emby server and it reads video files from a samba share controlled by OMV server, I wonder how do you solve an issue with allowing Emby to be able to delete videos directly from the Emby UI ?

    I think there maybe more then one way, I feel modifying ACL is one of them, but looking for best practices...

    Thx in advance.