Created attachment 62011 [details] Requester showing the error "during shared access" when saving Saving any LibeOffice-Document to a NFSv3 mounted share fails. Error Message is (see attachment) Error saving the document xxx Error during shared access to /mnt/.../xxx.odt The file will be created with zero bytes size. Client: libreoffice-core-3.4.4.2-0.3.mga1 Server: Linux station 2.6.31.8 #14 Tue Apr 5 09:27:42 JST 2011 armv5tel GNU/Linux Debian Squeeze (6.0.5) Additionally this bug has already been described for a QNAP-server in 2010 at <http://kefk.org/blog/2010/10/20/networking_mit_dem_qnap_ts_859_pro_turbo_nas#Zugriffsprobleme> This seams to be related to bug 46157 and Bug 36852, both about loading files from NFSv3.
Steps to reproduce: 1. Install Libreoffice. 2. Attempt to save a doc to the NFSv3 network mount. 3. Error saying "Error during shared access" Current behavior: Error saying "Error during shared access" Expected behavior: Files to open like any other application.
I found the reason: Loading/saving fails if the share is mounted using the "lock" option. Reasoning: 1) My $HOME is mounted from the same server. Loading and saving from there works like a charm. Mount-entry for this: server:/export/home on /home type nfs (rw,nosuid,soft,nolock,addr=192.168.1.1) 2) Loading/saving from my home-dir mounted to a different mount-point does *not work*. Mount-entry for this: server:/export on /mnt/server type nfs (rw,nosuid,soft,addr=192.168.1.1) ==>> The failing share is mounted with "lock" (as no "nolock" is given). Proof: I remounted the failing share with "nolock" and loading/saving works.
(In reply to comment #2) Bug 36852 comment 0 points to a workaround: Not setting "SAL_ENABLE_FILE_LOCKING" at all in the file/script `soffice`. I can confirm this workaround to work.
(In reply to comment #3) Marking as duplicate of bug 36852 as per your previous comments. Re-open it if you have other opinion. *** This bug has been marked as a duplicate of bug 36852 ***
I disagree. bug 36852 is about FILEOPEN, while this one is about FILESAVE. I doubt a fix for bug 36852 will automatically fix this one, too.
h.goebel, check that NFS locks in your system works normal. In my /var/log/syslog was errors about locks. I fixed them and problem disappeared.
NEEDINFO per comment 6 @Alexander, perhaps you could confirm Bug 36852 too?
Dear Bug Submitter, Please read the entire message before proceeding. This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO