On OMV 2.x in fstab the identifier is "by-uuid".
Om OMV 3.x the identifier is "by-label."
Is there an environment variable or other method available within OMV that would allow having the identifier set to "by-id."?
On OMV 2.x in fstab the identifier is "by-uuid".
Om OMV 3.x the identifier is "by-label."
Is there an environment variable or other method available within OMV that would allow having the identifier set to "by-id."?
Is there an environment variable or other method available within OMV that would allow having the identifier set to "by-id."?
Nope, not as far as I know.
I wonder if the hand edits I did to fstab within the [openmediavault] section will stick or will OMV wipe them out?
I am going to add a new disk to the machine and see what happens when I configure the new disk within OMV.
I expect OMV to add it in "by-label" and hope to get lucky and not have all my /dev/disk/by-id/...... edits reset.
Edit:
All my hand edits reverted. Oh well.
I wonder if the hand edits I did to fstab within the [openmediavault] section will stick or will OMV wipe them out?
OMV will wipe them out unless you change config.xml. Plugins wouldn't work either because they get the filesystem mount point from config.xml not fstab. Just look in the mntent section if you want to edit them. omv-mkconf fstab will fix fstab with your edits but you will need to create the mountpoint.
Plugins wouldn't work either because they get the filesystem mount point from config.xml not fstab.
I'm not interested in changing the mount points, just the device identifiers.
I have this:
UUID=41991950-4d12-4475-86b8-ba54ec09323b /media/41991950-4d12-4475-86b8-ba54ec09323b ext4 defaults,nofail,user_xattr,noexec..........
But I want this:
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3YP9KRP-part1 /media/41991950-4d12-4475-86b8-ba54ec09323b ext4 defaults,nofail,user_xattr,noexec..........
Where do I submit a feature request?
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3YP9KRP-part1 /media/41991950-4d12-4475-86b8-ba54ec09323b ext4 defaults,nofail,user_xattr,noexec..........
That is what the new method (OMV 3.0.71+) does.
Here is my fstab on my test VM:
# >>> [openmediavault]
UUID=8195fd34-5361-4328-ae5f-59ad44424134 /media/8195fd34-5361-4328-ae5f-59ad44424134 xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=5b325077-8f74-4c83-83ff-8cdf3dc1ff7b /media/5b325077-8f74-4c83-83ff-8cdf3dc1ff7b ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=ced4838e-9cd7-4d3a-9d4b-39b3e11a2e7d /media/ced4838e-9cd7-4d3a-9d4b-39b3e11a2e7d xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=34986429-4072-46b6-8abb-b3304171175a /media/34986429-4072-46b6-8abb-b3304171175a xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=ae3164a2-4cd1-473d-9be4-9c6486553205 /media/ae3164a2-4cd1-473d-9be4-9c6486553205 btrfs defaults,nofail 0 2
/dev/disk/by-label/srvtest /media/5194defe-5d53-4a88-af9c-21da8a57c7f7 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
/dev/disk/by-label/srvtest2 /media/_dev_disk_by-label_srvtest2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
/dev/disk/by-uuid/9A79-C6DD /srv/_dev_disk_by-uuid_9A79-C6DD vfat defaults,nofail,discard 0 2
/dev/disk/by-label/autounlock /srv/dev-disk-by-label-autounlock ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl 0 2
/media/5b325077-8f74-4c83-83ff-8cdf3dc1ff7b:/media/ced4838e-9cd7-4d3a-9d4b-39b3e11a2e7d /srv/a9a50c07-0603-4c89-acf4-20427af6a73d fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=epmfs,minfreespace=4G 0 0
/media/34986429-4072-46b6-8abb-b3304171175a:/media/ae3164a2-4cd1-473d-9be4-9c6486553205:/media/ced4838e-9cd7-4d3a-9d4b-39b3e11a2e7d:/media/5b325077-8f74-4c83-83ff-8cdf3dc1ff7b /srv/e280327f-6031-45e2-8e7f-b99b39c3d9d6 fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=epmfs,minfreespace=4G 0 0
/media/8195fd34-5361-4328-ae5f-59ad44424134/test1 /export/test1 none bind 0 0
/media/ae3164a2-4cd1-473d-9be4-9c6486553205/d4 /export/d4 none bind 0 0
/media/8195fd34-5361-4328-ae5f-59ad44424134/test1 /sftp/aaron/test1 none bind 0 0
# <<< [openmediavault]
Alles anzeigen
If you did need to submit a feature request, it would be here.
I looked closely at all 16 lines of your fstab but I did not see any that say:
/dev/disk/by-id/
I'll submit a feature request.
If the partition has a label then:
dev-disk-by-label-Data1
Without label:
ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3YP9KRP-part1
/dev/disk/by-id/
Sorry missed that small detail.
If the partition has a label then:
dev-disk-by-label-Data1
Without label:
ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3YP9KRP-part1
Not sure what your point is.
What I am after is having a unique device identifier that I can directly relate to the hardware.
"by-label" doesn't do that.
"by-id" does.
Not sure what your point is.
What I am after is having a unique device identifier that I can directly relate to the hardware.
"by-label" doesn't do that.
"by-id" does.
he means if no label is set, by-id will be used. That's actually commented in filesystem.inc source file. So the order is label, fallback to by-id, and finally sdX if no id is found.
If you want to use by-id don't set the labels or delete them before registering in the backend.
I’m struggling with the ID-by-Label naming as my disc names are becoming huge, e.g.:
Whereas in Storage/File Systems this disc has the Label “Back-Up II”.
In contrast, my disc labelled “Slave” has this “simple” ID:
Can I force the Back Up II ID to be the “short form” of:?
The problem with the long name is that is that it gobbles sufficient file name space to overrun Windows’ maximum file length and render files unreadable without moving them to a higher directory.
Additionally, for every “dev-disk-by-id” entry in WinSCP I also have a dead (empty) entry for the UUID. Can I kill this?
Thanks.
ps: it would be even nicer to have, just:
Hi
You can also use openmediavault symlinks!
When I last tried I couldn't get them to work, and it doesn't fix the Windows file-length problem (nor the WinSCP oddity).
Any comments, please?
You can force the label form by assigning a label to the fs. You need then to unregister the disk from the backend and mount it again.
The label assignment can be done at terminal on existing file systems I know that ext4 and btrfs can be changed, not sure about xfs.
Thank you. I'll give it a go when time permits next week.
I have not managed to get my USB discs to be visible by label in WinSCP. By editing config.xmland running omv-mkconf fstab I unwittingly generated a new entry in WinSCP:
Original entry:
/media/dev-disk-by-id-usb-HitachiG_ST_21001205140000007959-0-0-part1
New additional entry:
/media/dev-disk-by-label-Back Up I
The new entry has no sub-folders. I couldn’t work out how to unregister the disc and tried:
echo 1 > /sys/block/sda/device/deleteThis only lost the disc in the OMV GUI.
Can you say what entries/edits I need to do make to achieve the desired result, please?
I said you need to unmount it and mount it again....using the webui.
I did that but there is nothing under:
/media/dev-disk-by-label-Back Up I It's an empty folder.
It is still all under:
/media/dev-disk-by-id-usb-HitachiG_ST_21001205140000007959-0-0-part1
Very puzzled.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!