On 05/11/2015 08:59 PM, Tal Nisan wrote:
On 05/11/2015 12:48 PM, Yuko Katabami wrote:
On 05/11/2015 07:02 PM, Tal Nisan wrote:
Hi Yoku,
For some connection types we have certain mount options that the
engine manages itself [1].
If the user has added to the custom mount options of this connection
one of these options, the operation will fail since they should be
specified directly from the connection properties rather than within
the mount options.
[1] Managed options for NFS:
timeo, retrans, vfs_type, protocol_version, nfsvers, vers,
minorversion, addr, clientaddr
Managed options for POSIX:
vfs_type, addr, clientaddr
Hi Tal,
Thank you very much for answering my question.
I think I understand it now.
So "duplicate" means the *same* options between managed options and
the custom mount options and that need to be specified using the former?
Exactly, an option that you can specify directly in the connection
properties, specifying it again within the mount option might send a
duplicate option and thus fail the mount.
Many thanks Tal.
It's all clear now.
Kind regards,
Yuko
Kind regards,
Yuko
On 05/11/2015 01:17 AM, Yuko Katabami wrote:
Hi all,
Could anyone clarify the following?
*File:***AppErrors
*Resource
ID:***VALIDATION_STORAGE_CONNECTION_MOUNT_OPTIONS_CONTAINS_MANAGED_PROPERTY*
**String:***Cannot ${action} ${type}. Custom mount options contain
the following duplicate managed options: ${invalidOptions}.
*Question:* Could you please explain what "duplicate managed
options" are?
Thanks in advance,
Yuko
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
