Cannot create Shared Folder - follow up of known issue in OMV 0.x

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Cannot create Shared Folder - follow up of known issue in OMV 0.x

      Hello!

      I'm facing the issue that I cannot create shared folders via WebUI.
      I reported this issue for OMV release 0.5 already here.

      However, with the latest OMV release 1.1 (Kralizec) the issue still occurs.
      Please check attached screenshot.

      I have a NAS with multiple devices and different filesystems. In fact only the OMV installation is running on EXT4, all other partitions are formatted with BTRFS.

      Question:
      Is it (still) true that OMV WebUI will not create a shared folder until BTRFS support is implemented?

      THX
      Images
      • Auswahl_033.png

        78.78 kB, 1,160×647, viewed 541 times
    • The btrfs filesystem backend is registered in OMV. I would think you should be able to mount. That would be a question for @votdev.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      The btrfs filesystem backend is registered in OMV. I would think you should be able to mount. That would be a question for @votdev.

      Look here and on the rest of the switch statement to see why it won't mount. That is the only place I know that can prevent btrfs from being mounted. I would really appreciate the ability to at least mount btrfs for the moment being myself instead of having to edit the code :)
    • I missed that part. Thanks :)

      If you create a mntent entry with the hidden flag set, does it work?
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • It works....add the mount parameters and entry to at /etc/fstab in between omv tags, and then mount -a, make sure you have the destination dir. Then replicate the mntent entry at config.xml with same parameters and hidden flag to 1 (no idea if it makes a difference), change uuid dir and uuid FS. The fs type can be btrfs

      This set of parameters of others ext4 disk didn't work

      usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2

      so i used only btrfs defaults,nofail,acl

      You can unmount but then they will dissapear from fstab and mntent and you're back to the same place. But in general it works. It should be reboot persistant I guess
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Hello!

      I'm not a software developer and therefore only have the view of the end user.

      What I'd like to understand is why you write something about an OMV specific /etc/fstab... or do I get something wrong here?

      In my case I have a "standard" Debian-like /etc/fstab with multiple devices, partitions and subvolumes.
      This means I configured a "multi-device" BTRFS volume with multiple subvolumes.
      Hereby I don't need to maintain dedicated partitions and can extend the available storage very easily.

      And I still don't understand why I cannot define a shared folder in OMV?
      Is BTRFS now supported?
      If no, when is it planned to support BTRFS?

      THX
    • Btrfs is not supported yet in omv. You may find your way around adding the entries in config.xml, but is not going to be smooth since the entry will vanish for every unmount action in omv. But once your there you should have any problems creating the shares. Omv adds custom entries to fstab. That is the file that gets all drives mounted at boot. You can put the line off those tags in fstab so your drives get mounted and omv doesn't delete them.
      Mi have no idea when support is coming to omv. Maybe it has some extra features that need to be implemented in the webui.
      You can file a request or a question at the bugtracker. I do remember that it was intended to come at the wheezy upgrade.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Hi!
      I don't intend to umount a partition / device, and therefore I'm interested in the modification of config-fiel config.xml.
      Means that my /etc/fstab remains manually modified, but stable:

      Source Code

      1. root@nas:~# cat /etc/fstab
      2. # /etc/fstab: static file system information.
      3. #
      4. # Use 'blkid' to print the universally unique identifier for a
      5. # device; this may be used with UUID= as a more robust way to name devices
      6. # that works even if disks are added and removed. See fstab(5).
      7. #
      8. # <file system> <mount point> <type> <options> <dump> <pass>
      9. tmpfs /tmp tmpfs defaults 0 0
      10. ## root Samsung HD103UJ
      11. UUID=e4213a90-0c50-4811-9bc8-e2aac36bc8dc / ext4 errors=remount-ro 0 1
      12. ## swap Samsung HD103UJ
      13. UUID=4f8370ab-9c95-4b1e-93df-f0b40da67d25 none swap sw 0 0
      14. ## /dev/sde1 WD30EFRX-68E
      15. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /media/btrfs btrfs defaults 0 1
      16. ## BTRFS Subvolumes
      17. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/musik btrfs defaults,subvol=@musik 0 1
      18. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/videos btrfs defaults,subvol=@videos 0 1
      19. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/bilder btrfs defaults,subvol=@bilder 0 1
      20. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/software btrfs defaults,compress,subvol=@software 0 1
      21. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/hardware btrfs defaults,compress,subvol=@hardware 0 1
      22. UUID=243609b2-c51b-4d5e-bb8b-2f01d4349f9a /mnt/downloads btrfs defaults,compress,subvol=@downloads 0 1
      Display All


      So, what is the proposal to move on?

      THX
    • at /etc/openmediavault/config.xml at fstab section are all the fs managed by omv. Once you get your entries there, they should be available as volumes for shared folders, this is my raid for example, you'll need to accomodate yours properly.
      Make sure you backup your config.xml file in case you accidently delete a line or delete it.

      Source Code

      1. <mntent>
      2. <uuid>1c164bb7-c1ec-44c7-92ae-d4936310a985</uuid>
      3. <fsname>751abbe2-c527-43a0-9e9f-4f250f53245c</fsname>
      4. <dir>/media/46e48dd3-8f8a-42f4-a503-0084368be19e</dir>
      5. <type>ext4</type>
      6. <opts>defaults,acl,user_xattr,noexec
      7. <freq>0</freq>
      8. <passno>2</passno>
      9. <hidden>0</hidden>
      10. </mntent>
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server