<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - backup copy fails when using share / samba" href="https://bugs.documentfoundation.org/show_bug.cgi?id=55004#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - backup copy fails when using share / samba" href="https://bugs.documentfoundation.org/show_bug.cgi?id=55004">bug 55004</a> from <a class="email" href="mailto:iwi900kp@rzmail.uni-erlangen.de" title="iwi900 <iwi900kp@rzmail.uni-erlangen.de>"> iwi900</a> <pre>Still same issue with 6.3.0.4. However, there is a 9 year old (!) report (<a href="http://blog.gresch.de/2010/06/03/openofficesambacifs-probleme-could-not-create-backup-copy/">http://blog.gresch.de/2010/06/03/openofficesambacifs-probleme-could-not-create-backup-copy/</a>) that suggests adding the "nobrl" option (no byte range lock) to the cifs mount options. Given that this bug could not be fixed for a decade, but affects many users and this option bypasses it (at least in my case), wouldn't it make sense to add a hint like "(maybe try mount option nobrl?)" to the error message?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>