Error remote shares

  • Hi,
    I have a problem with the creation of a "remote shares"
    After I created the "remote shares" I get this error:




    I want my Synologic NAS (NSF Shared Folders) to embed on a backup to create.



    Can me there please times a elucidating how can I fix this error?


    Thank you in advance.


    and now a screenshots of my config:


    remote shares:


    [img=http://abload.de/thumb/01remoteshareshmy94.jpg]

  • Hi, subzero79..Thanks for your answer...


    Soo ... everything now again reconfigured, with the same resultsThe error message states, and I agree with you that I mount on my mhddfs pool.
    But that is not so. My mount point is an empty and only hard drive with a single empty shared folder.the UUID is c9c36eb8-334c-4d7c-bc24-7be9140274a8.


    Here my filesystems config:




    Here my shared folders config:
    http://abload.de/image.php?img…esharessharedfolfvk8j.jpg



    Here my smb config:




    Here my remote shares config:



    and here the error:



    the same error as above. I can see that again shows the mount point on Mhddfs pool.
    Why?



    Thank you for assistance

  • Hi,
    @subzero79..Thanks for your answer...


    ohh..ich see that my answer has overlapped with yours.
    Sorry for that.


    Zitat

    Does it say the same error now that your trying to mount to a single folder in single hdd or is a different error ?


    it is the same error ... see above


    Code
    mhddfs: mount to: /media/c4e31f03-6327-4e23-86bb-871a1df07914


    mhddfs: mount to: /media/c4e31f03-6327-4e23-86bb-871a1df07914 ---> Mhddfs pool


    Thank you for assistance

  • Hi,@subzero79..Thanks for your answer...


    Zitat

    And don't use it in samba yet....let's check if it mounts first.


    the same error


    Code
    Can you please not use the pool, use a member disk directly.


    I don't understand? I do have an own empty harddrive. Not a pool.



    Zitat

    Create a share in one the filesystems that are member of the pool and use that one to mount the remote nfs


    yes ... it works.


    But only once, and now I can no longer delete the share.
    The same error message.




    ????




    Error above

  • Have now all want to clear, and the Mhddfs pool.
    Got a message saying that the pool is in use.
    All hard disks I had removed.
    Now I still have the pool and get it not deleted from the file system.



    Thank you for assistance

    • Offizieller Beitrag

    When you want to disassemble the pool you need to delete all shares connected to the pool from services (samba for example).


    next to shared folders there is a tab that displays what service is using what share. Go to their respective service and delete the shares.




    after that you can delete the sharrd folders in the shared folder section, be careful deleting because if you press the wrong button you can delete data.


    finally with no shared folders from the pool you can delete the mhdfs fs.

  • No matter if i use a branch or a pool im always getting this error when im trying to create a smb share. (with drives in a pool share or a pool share)


    seems that its currently not possible to use remote-fs plugin with a pool or drives (branches/leafs) in the pool.


    my setup:
    https://dl.dropboxusercontent.com/u/13344648/setup.PNG
    https://dl.dropboxusercontent.com/u/13344648/setup2.PNG


    Createing share-folder "backup_buffalo" in d6 to use it with remote-fs plugin. (d6 is member of poolshare)


    error:
    https://dl.dropboxusercontent.com/u/13344648/error.PNG


    you cannot pass the error without to rollback witch deletes remote-fs entry and shared-folder from webui..
    but:
    -fstab entry created
    -smb share is still successfully mounted to folder


    mhh now i have to remove a drive from the pool to use remote-fs plugin? or should i mount cifs manually in fstab to poolshare?


    whats the best option?


    regards
    firsttris

    • Offizieller Beitrag

    It must your setup on the remote box or omv. I have no problem using an aufs pool with a remote samba share. I guess I could add the option for non-empty but you really should have a dedicated, empty shared folder. Just make another one inside the pool.


    And are you really trying to mount a samba share over the internet??? Please DON'T! Samba is not made for the internet.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • hello,


    not over the internet ;) local area network. i use to often the word remote - sorry. (my fault).


    i think this problem or lets say "warning" is cause by FUSE filesystem.


    First i was using mhddfs now im using mergeFS.


    remote-fs smb on mergeFs Poolshare (error): https://dl.dropboxusercontent.com/u/13344648/mergeFs.PNG
    remote-fs ftp on single disk not in any poolshare (error): https://dl.dropboxusercontent.com/u/13344648/d1.PNG


    fstab:
    https://dl.dropboxusercontent.com/u/13344648/fstab


    root@tvserv:/media/other# mount -a
    fuse: mountpoint is not empty
    fuse: if you are sure this is safe, use the 'nonempty' mount option
    fuse: mountpoint is not empty
    fuse: if you are sure this is safe, use the 'nonempty' mount option


    on 2 different omv installs with FUSE filesystem (poolshare) i see this issue, i have another without FUSE filesystem in fstab and i dont have this issue in remote-fs plugin

    • Offizieller Beitrag

    I didn't get internet from the word remote. I got it from the screenshot where the ip address started with 20.x.x.x. That isn't a local IP address.


    You need to create a new shared folder using a new, empty folder. Otherwise, you need to add nonempty to the options in fstab. I really don't like mounting filesystems with nonempty because you don't know which filesystem the files are on and it may cause issues.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • This LAN uses historically an IP range in 20.x.x.x i have no clue which specialist invented this ;)


    but i have left it like this because there are so many systems and clients with fixed adresses.. and for now i have no issue with any device in this ip-range.


    how do they say: never change a running system.



    But back to topic..


    thats what i did - new freshly created empty shared folders, which i specially created to use as mountpoint with cifs/smb

    • Offizieller Beitrag

    Is the shared folder the root of the drive?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    That is the problem. While you think it is empty, the lost&found directory always exists in the root of the drive. So, that folder will never be empty.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!