issue getting rid of an unwanted mounting

andykmv · Oct 22nd 2020

i have some confusion on how to get rid of an unwanted mounting so i am seeking some advice...

a bit more background:

the issue came about because when i built the system (replaced omv steoneburner) i did not have the hard disk i am referring to attached to the system. i attached this new 1Tb hard disk to be the subversion repository file system in my omv5 system.

I was manually remounting the file system as needed whilst i installed, configured & tested the svnserve service - i am using the svn protocol to access repositories using tortoiseSVN, and in process of trying to work out a reasonable way to setup the system, i tried using the Filesystem tool to mount the drive but for some reason the file system would not automount on restart (i probably missed a step somewhere as the Filesystem tab listing showed it as unreferenced) .

inevitably i added the file system to the fstab and have it mounting ok on bootup but of course there is the remembered mounting via OMV that i am having difficulty getting rid of.

full fstab is this:

Code

# /etc/fstab: static file system information.
...
# / was on /dev/sdb1 during installation
UUID=d95a8d19-6da0-4ff9-8501-32aac39bb9da /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdb5 during installation
UUID=a1598fbb-8a30-4af3-829e-f7c077697297 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
# Device /dev/sdb 931.51Gb svn data drive
UUID=99d41060-856b-4547-b6ac-cbf7431ed224 /srv/svn ext4 defaults 0 0
# >>> [openmediavault]
/dev/disk/by-label/DATA        /srv/dev-disk-by-label-DATA    ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2        /srv/dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
# <<< [openmediavault]

Display More

the second OMV section entry that begins with "/dev/disk/by-id/ata-WDC_WD10EZEX"

Code

# >>> [openmediavault]
/dev/disk/by-label/DATA        /srv/dev-disk-by-label-DATA    ext4    .....
/dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2        /srv/dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2  .......
# <<< [openmediavault]

is the one i want to get rid of because it duplicates the mounting further up the fstab:

Code

# Device /dev/sdb 931.51Gb svn data drive 
UUID=99d41060-856b-4547-b6ac-cbf7431ed224 /srv/svn ext4 defaults 0 0

and i end up with two copies of the same file system mounted in two separate folders under /srv

Code

root@openmediavault2:/srv# ls svn
aquota.group  aquota.user  config  lost+found  repos

root@openmediavault2:/srv# ls dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2
aquota.group  aquota.user  config  lost+found  repos

the file system mounted to the folder svn matches this item in fstab UUID=99d41060-856b-4547-b6ac-cbf7431ed224 /srv/svn

the file system mounted to the folder "dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2" matches this item in fstab /dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2 /srv/dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2

the omv5 documentation suggests that i can get rid of this second one by editing the config.xml database (partial copy below) but i cant find an entry that matches to second mounting (see below)

any suggestions on where to look next ?

Code

    <storage>
      <!--
            <hdparm>
                <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                <devicefile>/dev/xxx</devicefile>
                <apm>0 = disable|1-255<apm>
                <aam>0|128|254</aam>
                <spindowntime>0 = disabled|1-254</spindowntime>
                <writecache>0|1</writecache>
            </hdparm>
            -->
      <filesystem>
        <!--
                <quota>
                    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                    <fsuuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx</fsuuid>
                    <usrquota>
                        <name>xxx</name>
                        <bsoftlimit>0</bsoftlimit>
                        <bhardlimit>xxx</bhardlimit>
                        <isoftlimit>0</isoftlimit>
                        <ihardlimit>0</ihardlimit>
                    </usrquota>
                    <usrquota>
                        ...
                    </usrquota>
                    <grpquota>
                        <name>xxx</name>
                        <bsoftlimit>0</bsoftlimit>
                        <bhardlimit>xxx</bhardlimit>
                        <isoftlimit>0</isoftlimit>
                        <ihardlimit>0</ihardlimit>
                    </grpquota>
                    <grpquota>
                        ...
                    </grpquota>
                </quota>
                <quota>
                    ...
                </quota>
                -->
      </filesystem>
      <hdparm>
        <uuid>988443fb-c487-49bd-b82b-51dd51652fca</uuid>
        <devicefile>/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN3BRMM</devicefile>
        <apm>254</apm>
        <aam>254</aam>
        <spindowntime>248</spindowntime>
        <writecache>0</writecache>
      </hdparm>
      <hdparm>
        <uuid>b5178d6e-fe34-4098-9273-534a63429d60</uuid>
        <devicefile>/dev/disk/by-id/ata-WDC_WDS120G2G0A-00JH30_182216806310</devicefile>
        <apm>192</apm>
        <aam>0</aam>
        <spindowntime>0</spindowntime>
        <writecache>0</writecache>
      </hdparm>
      <hdparm>
        <uuid>27d7fb60-86a7-4b49-bf18-fc63cf17f142</uuid>
        <devicefile>/dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP</devicefile>
        <apm>1</apm>
        <aam>0</aam>
        <spindowntime>60</spindowntime>
        <writecache>0</writecache>
      </hdparm>
    </storage>
    <fstab>
      <!--
            <mntent>
                <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
                <dir>/xxx/yyy/zzz</dir>
                <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
                <opts></opts>
                <freq>0</freq>
                <passno>0|1|2</passno>
                <hidden>0|1</hidden>
            </mntent>
            -->
      <mntent>
        <uuid>439c8184-e79d-49e7-8f43-2dcea52d38f8</uuid>
        <fsname>/dev/disk/by-label/DATA</fsname>
        <dir>/srv/dev-disk-by-label-DATA</dir>
        <type>ext4</type>
        <opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
        <freq>0</freq>
        <passno>2</passno>
        <hidden>0</hidden>
      </mntent>
      <mntent>
        <uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
        <fsname>/dev/sdc1</fsname>
        <dir>/</dir>
        <type>ext4</type>
        <opts>errors=remount-ro</opts>
        <freq>0</freq>
        <passno>1</passno>
        <hidden>1</hidden>
      </mntent>
    </fstab>

Display More

gderf · Oct 22nd 2020

You should be deleting the mount from within Filesystems in the OMV GUI. Is there some reason you can't?

andykmv · Oct 22nd 2020

Thanks for the reply, (and i added a bit more background to the original post above):

because the documentation states that "The delete button actually deletes filesystems, using wipefs -a. This will flush filesystem, raid or partition-table signatures (magic strings). Be careful using this. "

At this point in time I do not want to wipe the disk volume, hence i have not used the Delete button on the Filesystems page.

andykmv · Oct 22nd 2020

i did a bit more reading and found the "Filesystem Environmental Variables" page and the reference to running a salt process. there was a reference i saw that salt was the bridge between the config.xml and the fstab , therefore i ran the command "omv-salt deploy run fstab". Did not seem to do anything substantial, so i'll reboot and check again.:

Diff

debian:
----------
ID: create_filesystem_mountpoint_439c8184-e79d-49e7-8f43-2dcea52d38f8
Function: file.accumulated
Result: True
Comment: Accumulator create_filesystem_mountpoint_439c8184-e79d-49e7-8f43-2dcea52d38f8 for file /etc/fstab was charged by text
Started: 11:31:12.435040
Duration: 0.527 ms
Changes:
----------
ID: mount_filesystem_mountpoint_439c8184-e79d-49e7-8f43-2dcea52d38f8
Function: mount.mounted
Name: /srv/dev-disk-by-label-DATA
Result: True
Comment: Target was already mounted
Started: 11:31:12.435934
Duration: 161.665 ms
Changes:
----------
umount:
Forced remount because options (user_xattr) changed
----------
ID: append_fstab_entries
Function: file.blockreplace
Name: /etc/fstab
Result: True
Comment: Changes were made
Started: 11:31:12.599679
Duration: 15.037 ms
Changes:
----------
diff:
---
+++
@@ -14,5 +14,4 @@
UUID=99d41060-856b-4547-b6ac-cbf7431ed224 /srv/svn ext4 defaults 0 0
# >>> [openmediavault]
/dev/disk/by-label/DATA              /srv/dev-disk-by-label-DATA     ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl       0 2
-/dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2               /srv/dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2   ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl      0 2
# <<< [openmediavault]


Summary for debian
------------
Succeeded: 3 (changed=2)
Failed:    0
------------
Total states run:     3
Total run time: 177.229 ms

Display More

andykmv · Oct 22nd 2020

actually, running the command "omv-salt deploy run fstab" fixed the fstab and mounting issue (no longer a duplicated mounting in the OMV section of FSTAB) so i deleted the "/srv/dev-disk-by-id-ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F7SH5ZHP-part2" folder and the issue is all nicely cleaned up! file system is still listed in the Filesystems tab which is ok.

issue getting rid of an unwanted mounting

andykmv Oct 22nd 2020

Participate now!

Tags