Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I get "General input/output error while accessing" when trying to open a file on an NFS share

I'm running LibreOffice 4.0.2.2 on Xubuntu (Linux) 13.04 64-bit.

I have a Windows 7 x64 box that provides NFSv3 shares on my LAN via haneWIN NFS Server 1.2.11.

My Linux boxes mount these shares via fstab. Example:

jarvis:/Shared /mnt/jarvis/Shared nfs udp 0 0

When I try to open a .ods spreadsheet on the share (which was created in LibreOffice on Windows), I get an error popup that says "General input/output error while accessing" followed by the filename.

Why is this happening? It's not a general share issue, as I can open the file in Gnumeric just fine.

I've read that it may be a locking issue, and that commenting out the following lines in /usr/lib/libreoffice/program/soffice may help:

# file locking now enabled by default
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING

In fact, it does help, but why is it necessary to make such an arcane change to a system-level file?

click to hide/show revision 2
add response to oweng's answer

I get "General input/output error while accessing" when trying to open a file on an NFS share

I'm running LibreOffice 4.0.2.2 on Xubuntu (Linux) 13.04 64-bit.

I have a Windows 7 x64 box that provides NFSv3 shares on my LAN via haneWIN NFS Server 1.2.11.

My Linux boxes mount these shares via fstab. Example:

jarvis:/Shared /mnt/jarvis/Shared nfs udp 0 0

When I try to open a .ods spreadsheet on the share (which was created in LibreOffice on Windows), I get an error popup that says "General input/output error while accessing" followed by the filename.

Why is this happening? It's not a general share issue, as I can open the file in Gnumeric just fine.

I've read that it may be a locking issue, and that commenting out the following lines in /usr/lib/libreoffice/program/soffice may help:

# file locking now enabled by default
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING

In fact, it does help, but why is it necessary to make such an arcane change to a system-level file?

Update: Mounting with oweng's fstab options does not solve the issue for me. This may be because of a difference with HaneWIN, such as the fact that it only implements up to NFSv3.

I get "General input/output error while accessing" when trying to open a file on an NFS share

I'm running LibreOffice 4.0.2.2 on Xubuntu (Linux) 13.04 64-bit.

I have a Windows 7 x64 box that provides NFSv3 shares on my LAN via haneWIN NFS Server 1.2.11.

My Linux boxes mount these shares via fstab. Example:

jarvis:/Shared /mnt/jarvis/Shared nfs udp 0 0

When I try to open a .ods spreadsheet on the share (which was created in LibreOffice on Windows), I get an error popup that says "General input/output error while accessing" followed by the filename.

Why is this happening? It's not a general share issue, as I can open the file in Gnumeric just fine.

I've read that it may be a locking issue, and that commenting out the following lines in /usr/lib/libreoffice/program/soffice may help:

# file locking now enabled by default
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING

In fact, it does help, but why is it necessary to make such an arcane change to a system-level file?

Update: Mounting with oweng's fstab options does not solve the issue for me. This may be because of a difference with HaneWIN, such as the fact that it only implements up to NFSv3.