fsname: Failed to match exactly one schema when trying to create NFS

  • I'm getting an error when I try to set up a NFS for a file system. I have two others that went without error. I tried deleting this file system and rebuilding it as some other posts related to this error suggested that the name might have a space in it. For reference, one of the successful NFS was 5tbbackup and this particular one with the error is 8tbbackup.


    Error #0:OMV\Json\SchemaValidationException: fsname: Failed to match exactly one schema. in /usr/share/php/openmediavault/json/schema.inc:691Stack trace:#0 /usr/share/php/openmediavault/json/schema.inc(375): OMV\Json\Schema->checkOneOf('/srv/dev-disk-b...', Array, 'fsname')#1 /usr/share/php/openmediavault/json/schema.inc(297): OMV\Json\Schema->validateString('/srv/dev-disk-b...', Array, 'fsname')#2 /usr/share/php/openmediavault/json/schema.inc(257): OMV\Json\Schema->validateType('/srv/dev-disk-b...', Array, 'fsname')#3 /usr/share/php/openmediavault/config/datamodel.inc(155): OMV\Json\Schema->validate('/srv/dev-disk-b...', 'fsname')#4 /usr/share/php/openmediavault/config/configobject.inc(189): OMV\Config\DataModel->validateProperty('fsname', '/srv/dev-disk-b...')#5 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('fsname', '/srv/dev-disk-b...', true)#6 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, true, false)#7 /usr/share/openmediavault/engined/rpc/nfs.inc(192): OMV\Config\ConfigObject->setAssoc(Array)#8 [internal function]: OMVRpcServiceNfs->setShare(Array, Array)#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setShare', Array, Array)#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('NFS', 'setShare', Array, Array, 1)#12 {main}


    Any help, much appreciated as I am trying to get completely away from SMB/CIFS shares.


    Ryan

  • Here's the output of "omv-confdbadm read conf.system.filesystem.mountpoint | jq"


    [
    {
    "fsname": "aca4f31f-6c7b-483c-b092-df5e853b8b0c",
    "type": "ext4",
    "freq": 0,
    "hidden": false,
    "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
    "passno": 2,
    "uuid": "8086fc0d-c039-4f6a-adec-ac9a147f0e4e",
    "dir": "/media/aca4f31f-6c7b-483c-b092-df5e853b8b0c"
    },
    {
    "fsname": "/dev/disk/by-uuid/7020-0734",
    "type": "vfat",
    "freq": 0,
    "hidden": false,
    "opts": "defaults,nofail",
    "passno": 2,
    "uuid": "4cda4408-5492-44d7-8e59-71e6ba8ca728",
    "dir": "/media/7020-0734"
    },
    {
    "fsname": "/media/aca4f31f-6c7b-483c-b092-df5e853b8b0c/",
    "type": "none",
    "freq": 0,
    "hidden": false,
    "opts": "bind,nofail",
    "passno": 0,
    "uuid": "bb5d73b3-f3f6-4e89-9d95-825b314854a7",
    "dir": "/export/5tbbackup"
    },
    {
    "fsname": "/dev/disk/by-label/8tbbackupcopy",
    "type": "ext4",
    "freq": 0,
    "hidden": false,
    "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
    "passno": 2,
    "uuid": "a1b674ef-8e7f-4840-b17f-1bd0ec6ad2c3",
    "dir": "/srv/dev-disk-by-label-8tbbackupcopy"
    },
    {
    "fsname": "/dev/disk/by-id/usb-Seagate_Backup+_Desk_NA7DZ3AE-0:0-part1",
    "type": "ext4",
    "freq": 0,
    "hidden": false,
    "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
    "passno": 2,
    "uuid": "5ae304c1-5955-4b77-9d2d-004dd84d2a8e",
    "dir": "/srv/dev-disk-by-id-usb-Seagate_Backup+_Desk_NA7DZ3AE-0-0-part1"
    },
    {
    "fsname": "/srv/dev-disk-by-label-8tbbackupcopy/",
    "type": "none",
    "freq": 0,
    "hidden": false,
    "opts": "bind,nofail",
    "passno": 0,
    "uuid": "2408ea54-0aa7-4009-9467-a4bfcb43824c",
    "dir": "/export/8tbbackupcopy"
    }
    ]



    Notice the two entries for the same named location "8tbbackup". Very strange. Anyway, I deleted shared folders "8tbbackup" and "8tbbackupcopy" and then added back in shared folder "8tbbackup", and this is the output of "omv-confdbadm read conf.system.filesystem.mountpoint | jq". Notice no entry for "8tbbackup"....



    [
    {
    "type": "ext4",
    "uuid": "8086fc0d-c039-4f6a-adec-ac9a147f0e4e",
    "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
    "fsname": "aca4f31f-6c7b-483c-b092-df5e853b8b0c",
    "hidden": false,
    "passno": 2,
    "dir": "/media/aca4f31f-6c7b-483c-b092-df5e853b8b0c",
    "freq": 0
    },
    {
    "type": "vfat",
    "uuid": "4cda4408-5492-44d7-8e59-71e6ba8ca728",
    "opts": "defaults,nofail",
    "fsname": "/dev/disk/by-uuid/7020-0734",
    "hidden": false,
    "passno": 2,
    "dir": "/media/7020-0734",
    "freq": 0
    },
    {
    "type": "none",
    "uuid": "bb5d73b3-f3f6-4e89-9d95-825b314854a7",
    "opts": "bind,nofail",
    "fsname": "/media/aca4f31f-6c7b-483c-b092-df5e853b8b0c/",
    "hidden": false,
    "passno": 0,
    "dir": "/export/5tbbackup",
    "freq": 0
    },
    {
    "type": "ext4",
    "uuid": "5ae304c1-5955-4b77-9d2d-004dd84d2a8e",
    "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
    "fsname": "/dev/disk/by-id/usb-Seagate_Backup+_Desk_NA7DZ3AE-0:0-part1",
    "hidden": false,
    "passno": 2,
    "dir": "/srv/dev-disk-by-id-usb-Seagate_Backup+_Desk_NA7DZ3AE-0-0-part1",
    "freq": 0
    }
    ]



    When I try to add the NFS share to "8tbbackup", I get the fsname error again as before.

  • i don't know if there is still an issue with omv5, but i encountered "fsname: failed to match exactly one schema" problem on my fresh omv4 installation today and i've solved it

    i suspected that it's the "+" char in the disk id that causes the problem since i also have usb 3.0 external seagate drive and since there was a similar problem with spaces in the path (Error Adding NFS share - OMV\Json\SchemaValidationException)

    the solution is to label the partition, so it will be mounted by label, not by id:


    >sudo e2label /dev/sda1 somelabel


    so there is no more stupid /srv/dev-disk-by-id-usb-Seagate_Backup+bla-bla-bla junk and an nfs share could be created successfully!

    i hope this will help someone

    cheers!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!