
This is a multi-part message in MIME format. --------------070909000902060305090002 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
--------------070909000902060305090002 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <br> <div class="moz-cite-prefix">On 05/11/2015 08:59 PM, Tal Nisan wrote:<br> </div> <blockquote cite="mid:55508B9E.2020508@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <br> <br> <div class="moz-cite-prefix">On 05/11/2015 12:48 PM, Yuko Katabami wrote:<br> </div> <blockquote cite="mid:55507AE5.7050601@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <br> <div class="moz-cite-prefix">On 05/11/2015 07:02 PM, Tal Nisan wrote:<br> </div> <blockquote cite="mid:5550700D.4030401@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> Hi Yoku,<br> For some connection types we have certain mount options that the engine manages itself [1].<br> 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.<br> <br> [1] Managed options for NFS:<br> timeo, retrans, vfs_type, protocol_version, nfsvers, vers, minorversion, addr, clientaddr<br> Managed options for POSIX:<br> vfs_type, addr, clientaddr<br> </blockquote> <br> Hi Tal,<br> <br> Thank you very much for answering my question.<br> I think I understand it now. <br> So "duplicate" means the *same* options between managed options and the custom mount options and that need to be specified using the former?<br> </blockquote> 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.<br> </blockquote> Many thanks Tal.<br> It's all clear now.<br> <br> Kind regards,<br> <br> Yuko<br> <blockquote cite="mid:55508B9E.2020508@redhat.com" type="cite"> <blockquote cite="mid:55507AE5.7050601@redhat.com" type="cite"> <br> Kind regards,<br> <br> Yuko<br> <blockquote cite="mid:5550700D.4030401@redhat.com" type="cite"> <br> <br> <div class="moz-cite-prefix">On 05/11/2015 01:17 AM, Yuko Katabami wrote:<br> </div> <blockquote cite="mid:554FD8FF.9050600@redhat.com" type="cite"> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> Hi all,<br> <br> Could anyone clarify the following?<br> <br> <div class="moz-signature"><b>File:</b><b> </b>AppErrors<br> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <b>Resource ID:</b><b> </b>VALIDATION_STORAGE_CONNECTION_MOUNT_OPTIONS_CONTAINS_MANAGED_PROPERTY<b><br> </b><b>String:</b><b> </b>Cannot ${action} ${type}. Custom mount options contain the following duplicate managed options: ${invalidOptions}.<br> <b>Question:</b> Could you please explain what "duplicate managed options" are?<br> <br> Thanks in advance,<br> <br> Yuko<br> <font size="2" color="#000000" face="arial, sans-serif"> </font> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Devel mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Devel@ovirt.org">Devel@ovirt.org</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a></pre> </blockquote> <br> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Devel mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Devel@ovirt.org">Devel@ovirt.org</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/devel">http://lists.ovirt.org/mailman/listinfo/devel</a></pre> </blockquote> <br> <div class="moz-signature"><font size="2" color="#000000" face="arial, sans-serif"><br> </font> </div> </blockquote> <br> </blockquote> <br> <div class="moz-signature"><font size="2" color="#000000" face="arial, sans-serif"><br> </font> </div> </body> </html> --------------070909000902060305090002--