|
I am running Ubuntu 10.04 connecting to a samba server (version 3.0.33-3.28.el5) running on CentOS. Right now I'm experiencing strange problems accessing the server via smb. Issue 1: After upgrading CentOS from 5.4 to 5.5, I'm encountering errors on the samba server when editing files on the home directory from my Ubuntu machine. The home directory is mounted via fstab. The file will still open and close but only after a long delay. The strange thing is that these errors occur when editing on the home share but not on the other shares. Error log on samba server: smb.conf configuation on server: fstab entry on Ubuntu PC: Issue 2: When I mount shares via nautilus, I am not able to open openoffice.org files. Instead, the files are opened with file roller showing an empty list. I am able to open the files if they are located on local drives or shares mounted via fstab. Running Fedora 13 from VirtualBox in Ubuntu, there were no issues or errors at all. Any idea where I should look at? What do the errors mean? |
|
For issue 2: Right click on the file, select 'open with another application'. In the resulting window, there should be an option to select an application, including OpenOffice, from a list, and a check box to make this the default for this file type. For issue 1: I have no experience with this, but have you tried disabling the 'veto files' feature (at least just for troubleshooting)? I can't imagine why else the server would care about the file types. 1
The file association does not work on the samba share. Doing so will open up an empty document in OpenOffice instead of the file I selected. As I've mention, it works if it is mounted with fstab but not through Nautilus via the "Connect To Server" option.
(02 Jun '10, 06:02)
Ricky Wee
|
|
Issue 1: have you fsck'ed the partitions on the Samba server, just to be on the safe side? I've not fsck'ed the samba server as the error does not appear with other clients on Windows and Fedora. With the error, the file opens and closes fine even though it takes 4 times longer.
(02 Jun '10, 06:50)
Ricky Wee
aside from the usual suggestion of increasing the logging level of samba, you could try to report it here https://bugzilla.samba.org/ as at the moment searching the base of existing ones doesn't report any with "448" or "unix_filetype" so it must be new to them too
(02 Jun '10, 11:06)
pmarini
|
Please accept an answer so the question/answer can be finished. Or provide more details so we can help.