Topic: Is anyone using SME 6 with SuSE 9.1?

[abovett]

Hi

Can anyone tell me if they are using SME server with SuSE 9.1 client PCs? If so, are you having problems writing to the server or does it work OK for you? A recent SuSE update seems to have broken SMB access to the iBays - I can save a new file, but I can't re-save to an existing file. A collegue who is also using SuSE 9.1 and SME is having the same problem.

Thanks

Andy

[guest22]

Hi,

please post more specific info please.

[abovett]

Hi

> please post more specific info please.

I use SME as a server for a mixed network of Windows and Linux PCs. I regularly update the client PCs using their respective online updates. After a recent update to a SuSE 9.1 box (a few weeks ago, not sure exactly when) I started having trouble writing to shares (ibays) on the SME server. Basically any attempt to write to a pre-existing file fails. Here's an example ("mnt/SOL/copying" is a mount point for ibay "copying" on SME server "SOL"):

Code: [Select]


[andrew@europa-fc3 ~]$ touch test.txt
[andrew@europa-fc3 ~]$ cp test.txt mnt/SOL/copying
[andrew@europa-fc3 ~]$ cp test.txt mnt/SOL/copying
cp: cannot create regular file mnt/SOL/copying/test.txt': Input/output error
[andrew@europa-fc3 ~]$

Note - the first copy - to a non-existant file - succeeds. The second
fails (after pausing for several seconds).

I have another SuSE box which I had not yet updated, and that was working fine. However, when I did the update I found that it started having the same problem.

The update was to a new kernel, and I noted that the release notes said that it fixed some security issues when accessing SMB file systems.

The problem kernel is:

SuSE Linux 9.1, kernel 2.6.5-7.111.5-default

The problem goes further. I have a collegue who uses SuSE and SME server, and he has reported the same problem. Recent updates to Fedora Core 3 and Ubuntu test boxes (both of which have included kernel updates) have resulted in the same problems with those boxes, so it's not just SuSE. Mandrake is currently OK, but maybe they just haven't applied that kernel patch yet.

Any suggestions or help appreciated. If more info or tests are required to track it down, please let me know. If I can't solve this soon I'm going to have to dump SME

Andy B