Cannot create shared folder: no volume

    • OMV 1.0

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

    • Cannot create shared folder: no volume

      Note: I've installed the OpenMediaVault v1.0.8 package on a quite fresh Debian Wheezy (7.6) and I'm using ZFS on Linux to add ZFS file system support for my storage disks (system disks are in ext4).

      OMV, Debian and ZFS work great except I cannot create a Shared folder via OMV Web GUI because no volume is listed in the "Volume" drop down menu of the create shared folder form.

      I understand it's most likely related to my storage disk using ZFS (it's not even listed on WebGUI): but how can I circumvent this? Is there a way to manually tell OMV I have a volume so he'll let me add a shared folder on the ZFS FS?
    • The ZFS Plugin is still under development. The core of the plugin is mostly done but the GUI part still has a lot of things to finish. Until then you're unable to use ZFS volumes within the WebGUI I guess.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • The right way (what the ZFS plugin does): Add a new class to the storage function which describes how to work with a ZFS filesystem/volume (I was using volume, but I meant filesystem). Then it will be detected in the WebGUI and you can use it.

      The hacky way: mount the zfs filesystem to /media/UUIDofyourZFSfilesystem/ and put it into the /etc/openmediavault/config.xml - this 'could' work and allow you to use the filesystem, but I'm not 100% sure - its up to you to try it out.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Create a shared folder on a different drive and bind mount the zfs volume to that.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • davidh2k wrote:

      The right way (what the ZFS plugin does): Add a new class to the storage function which describes how to work with a ZFS filesystem/volume (I was using volume, but I meant filesystem). Then it will be detected in the WebGUI and you can use it.

      The hacky way: mount the zfs filesystem to /media/UUIDofyourZFSfilesystem/ and put it into the /etc/openmediavault/config.xml - this 'could' work and allow you to use the filesystem, but I'm not 100% sure - its up to you to try it out.
      Right way:
      Could not find the right place to add some PHP class. I've found OMVFilesystems::enumerate() in "/usr/share/php/openmediavault/system.inc" that might seems to be a ugly starting point (it parses the output of command blkid -o full).

      Hacky way:
      blkid command returns:
      $ blkid
      /dev/sdc1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="8076597734574968212" TYPE="zfs_member"
      /dev/sdd1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="3435428460824043642" TYPE="zfs_member"
      /dev/sde1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="17615302571643361007" TYPE="zfs_member"
      /dev/sdf1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="15140204519545450510" TYPE="zfs_member"
      /dev/sdg1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="6967421667606088857" TYPE="zfs_member"
      /dev/sda1: UUID="ebf2ce26-202e-7a3a-c5f4-86e605d812d3" UUID_SUB="96e75199-71c4-e24a-849b-bd55dc1e5e01" LABEL="nas-box:0" TYPE="linux_raid_member"
      /dev/sda2: UUID="6d58c9bf-cc64-689e-d5db-21235a59d714" UUID_SUB="87014e82-0c5e-914a-b658-666a909c3256" LABEL="nas-box:1" TYPE="linux_raid_member"
      /dev/sda3: UUID="741a4382-a855-45bd-845d-50cfe84e12a0" TYPE="swap"
      /dev/sdb1: UUID="ebf2ce26-202e-7a3a-c5f4-86e605d812d3" UUID_SUB="5f43b461-9ce4-027e-1d32-86f183bb001f" LABEL="nas-box:0" TYPE="linux_raid_member"
      /dev/md0: UUID="f4ef3068-6b28-410e-a051-fc5caf74b20c" TYPE="ext4"
      /dev/md1: UUID="6oZ7uv-6BiH-xSSC-X7RQ-K3Hc-W0z1-4031R2" TYPE="LVM2_member"
      /dev/mapper/system-fsroot: UUID="7ccb72a6-1e3b-4a69-a55c-b24fad1fc370" TYPE="ext4"
      /dev/mapper/system-usr: UUID="3ecd38aa-a5de-4fc6-b8ce-0ccfb8af3550" TYPE="ext4"
      /dev/mapper/system-root: UUID="b4cd5b7c-01a3-4083-a168-0bd2f73c56e8" TYPE="ext4"
      /dev/mapper/system-tmp: UUID="e272f24d-e5e1-4222-ab2a-47abc8024052" TYPE="ext4"
      /dev/mapper/system-var: UUID="ab9b6c30-6c7b-4a2c-a18d-c53afe371056" TYPE="ext4"
      /dev/sdh1: LABEL="mainVolume" UUID="9626336108252084626" UUID_SUB="8477587448113775876" TYPE="zfs_member"
      /dev/sdb2: UUID="6d58c9bf-cc64-689e-d5db-21235a59d714" UUID_SUB="02826ddb-60ae-190a-eca3-ab188870b550" LABEL="nas-box:1" TYPE="linux_raid_member"
      /dev/sdb3: UUID="2b4dc56f-f3ba-49d4-8a0f-00575f0108da" TYPE="swap"


      So I've added

      Source Code

      1. <quota>
      2. <uuid>9626383561025520466</uuid>
      3. <fsuuid>9626383561025520466</fsuuid>
      4. </quota>
      to node /system/storage/filesystem of file /etc/openmediavault/config.xml and restarted openmediavault-engined daemon but it didn't helped the FS to show up on OMV WebGUI.
      Is it the right place and procedure?

      ryecoaaron wrote:

      Create a shared folder on a different drive and bind mount the zfs volume to that.
      I cannot create any Shared folder because there is not a single (ZFS or not) Volume listed:
      [IMG:http://img11.hostingpics.net/pics/773096OMVNovolumeavailable.png]
    • You got PM.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.