Finding the correct mntent UUID for a filesystem not in config.xml

christiscarborough · 18. April 2018

This is related to my difficulties with the recent failed backport kernel upgrade, but posting here also, as this is a more general question.

I have two zfs filesystems which show up in my list of file systems, but do not have usage information available. This appears to be because they lack associated mntent entries in config.xml. I would like to create mntent entries manually for them, but I do not know how to acquire the correct UUID for the filesystems. (I tried using a UUID that was valid before the zfs kernel module rebuild that was necessary, but this did not work, and OMV removed it from my config.xml, so it must be that the OMV UUID is created based upon an external filesystem identifier.)

How, given a mounted ZFS filesystem, do I generate a UUID for putting in a config.xml mntent entry which OMV will recognise as being connected to that file system? Thanks

sbocquet · 18. April 2018

Hi,

I think that for a reason or another, I have the same problem here, as my pool is continuously deleted from the config.xml file.

Disk usage tab for my ZFS pool has vanished from GUI !

Code

# blkid
/dev/sda1: LABEL="System" UUID="052263f1-d951-4a32-bdbf-052649fe60da" TYPE="ext4" PARTUUID="6e22f66d-01"
/dev/sda5: LABEL="Download" UUID="2cc50fbd-d0ca-4630-8666-abcd673cb0ac" TYPE="ext4" PARTUUID="6e22f66d-05"
/dev/sdb1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="5945670909528118790" TYPE="zfs_member" PARTLABEL="zfs-a90ee14998274abf" PARTUUID="7823f4e0-e2ab-1846-9e35-2567fb0c1a2a"
/dev/sdc1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="7058580712103882004" TYPE="zfs_member" PARTLABEL="zfs-452618e126cbaf9c" PARTUUID="c7893407-ba06-624e-bc57-45cdcc19aeb7"
/dev/sdd1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="6289169578989793690" TYPE="zfs_member" PARTLABEL="zfs-12da7fa4cbe8bc2a" PARTUUID="abc55c93-af69-5d41-a098-2e584108650a"
/dev/sde1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="7541299262285119423" TYPE="zfs_member" PARTLABEL="zfs-d8ba02f7ffb6adf3" PARTUUID="bf7a2959-117b-3b45-bb7e-134566bc959c"
/dev/sdg1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="14196844790818571510" TYPE="zfs_member" PARTLABEL="zfs-8416ee6dcd5877f3" PARTUUID="67740bbd-2fd7-3e4d-a44e-750b2b61650b"
/dev/sdf1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="8797145933635699092" TYPE="zfs_member" PARTLABEL="zfs-acd1f819e48e1417" PARTUUID="a661c2ac-4c6d-f347-87c7-7dcda5f1a7fe"
/dev/sdh1: LABEL="StoragePool" UUID="7167265556556760854" UUID_SUB="6314580578775894372" TYPE="zfs_member" PARTLABEL="zfs-a423a48ffffa523f" PARTUUID="42af989a-7bbc-3440-9149-ef8257dc304c"
/dev/sdb9: PARTUUID="11e12ba3-37eb-0640-9796-2dc78f1f7532"
/dev/sdc9: PARTUUID="5bd64fbc-6423-d440-8c6a-c06d88034850"
/dev/sdd9: PARTUUID="7bfdd059-ba5c-5f4b-b42f-bdd0ddca54f4"
/dev/sde9: PARTUUID="7e503ab4-1517-0549-9c6d-568357ec4efc"
/dev/sdg9: PARTUUID="8272402e-0b94-224b-9b20-3a3376527c7b"
/dev/sdf9: PARTUUID="1a7fa353-c251-7846-b2e5-bb38e794aaea"
/dev/sdh9: PARTUUID="fad86b37-ff5b-5f42-a4ee-85e964957e48"

Alles anzeigen

Code

# diff /etc/openmediavault/config.sav /etc/openmediavault/config.xml
882,891d881
<       <mntent>
<         <uuid>864e8b70-edf9-48fb-a2fc-7fe7dbab1c2f</uuid>
<         <fsname>StoragePool</fsname>
<         <dir>/StoragePool</dir>
<         <type>zfs</type>
<         <opts>rw,relatime,xattr,noacl</opts>
<         <freq>0</freq>
<         <passno>0</passno>
<         <hidden>1</hidden>
<       </mntent>

Alles anzeigen

sbocquet · 18. April 2018

From what I can see, the UUID in config.xml seems to have no link with some disk UUID at all.

Blkid:

Code

/dev/sda5: LABEL="Download" UUID="2cc50fbd-d0ca-4630-8666-abcd673cb0ac" TYPE="ext4" PARTUUID="6e22f66d-05"

config.xml

Code

<mntent>
        <uuid>a6b1d550-c75f-484b-a8e5-1ee12f860450</uuid>
        <fsname>/dev/disk/by-id/ata-SAMSUNG_MZ7LN512HCHP-000L1_S1ZKNXAG526958-part5</fsname>
        <dir>/srv/dev-disk-by-id-ata-SAMSUNG_MZ7LN512HCHP-000L1_S1ZKNXAG526958-part5</dir>
        <type>ext4</type>
        <opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl</opts>
        <freq>0</freq>
        <passno>2</passno>
        <hidden>0</hidden>
      </mntent>

I think it is just a random UUID. But it needs to be referenced by each <sharefolder>/<mntentref> to link those two.

ryecoaaron · 18. April 2018

Zitat von sbocquet

I think it is just a random UUID. But it needs to be referenced by each <sharefolder>/<mntentref> to link those two.

Correct. A unique UUID is generated every time a mntent entry is created. sharedfolders and other things reference that uuid.

sbocquet · 18. April 2018

Do you have any idea what can "clean" the ZFS mntent section in config.xml ?

ryecoaaron · 18. April 2018

As you already read in another thread - ZFS device(s) not listed in devices dropdown

sbocquet · 18. April 2018

Yes, let's all move the infos to that one...

Jetzt mitmachen!