ebox 1.4 samba 3.4.6 read/write problems on shares

[maxter]

i've encountered some strange problems reading and writing files on samba shares from xp and win2000.
it is possible to write a file to the mounted share, and copy the file back to the local pc or delete it, but trying to read or write this file on the share is impossible.
every application report a different error.
notepad opens the file but trying to save after some changes report that 'there is not enough memory'.
open office can't open the file and trying to save a file directly to the share report an I/O error.
image preview simply can't open any image.
and so on.

there are no  errors on the logs.

i downgraded to the hardy default samba versions, and now all works fine.

the downgrade  also removed the ebox-samba package, and now i can't manage users and group from the ebox interface, so any suggestion to solve this problem is really appreciated

many thanks

[maxter]

bump!

i now that the information i provided are generic, but really i don't know how further investigate and provide more information.

the problem is surely related with the the samba version, but the lack of errors in log stops my efforts to provide more informations.


i must solve this problem, i don't need the last version of samba so i will be happy also if i'll manage to reinstall samba management in ebox or even if i'll know how to add new users samba settings from command line...

so any suggestion is really appreciated

many thanks

[kg_esser]

I have a similar problem with the current ebox-release.

When I try to access a samba share from a Vista-PC (havn't tried with other OS yet) some Tools (e.g. Total Commander) report "Not enough space on disk" when copying a file to the share.
With explorer everything looks fine on the first look, but when I tried to open the files some seem corrupted (e.g. pdf-files).

This is a very serious problem and it is absolutely not possible to use the machine in a productive environment without this problem fixed.

I have installed the system just a few days ago with online updates enabled, so it should be the very ltest release of ebox.

[leeman]

I have just installed my first E-box and I have this problem exactly.

Most annoying are the images and PDF-files.

And if I copy the files from the share to my desktop, I can open it just fine.
I have checked the rights and such and it looks perfect.

I can open word files thou.

Just adding that the clients are WinXP with the latest updates.

[sidmax]

I've spent one day figthing with the same issue. It was (at least in my case) an issue related with the samba vfs object full audit.

Try this (and don't touch the web interface during the proces or it will overwrite your changes):

open /etc/samba/smb.conf and comment all the references to full audit:

# vfs objects = full_audit
# full_audit:success = connect opendir open disconnect unlink mkdir rmdir rename
# full_audit:failure = none
.
.
[homes]
 comment = Home Directories
 valid users = %S
 read only = No
 browseable = No
# vfs objects = full audit
.
.
[myshare]
.
.

Then restart samba (/etc/init.d/samba restart) and check if the problem is solved.

If everything works, to prevent the web interface from re-introducing the problem, look at this page:

http://trac.ebox-platform.com/changeset/15674

and apply the changes to:

 /usr/share/ebox/stubs/samba/smb.conf.mas


Good luck!

[leeman]

Thank you!! 

This helped me at least.
In due time too since I couldn't even load the profiles logging in.

[flashbios]

Same with Ebox 1.4.1 !!!

After the changes which are described here: it works !!

Strange anyway, I have installed the same Ebox 1.4.1 version on a different computer some days ago: doesn't have this problem...  I will check the smb.conf files on the other server too.

Anyway: this is a really nasty (but known) bug, I hope the Ebox company makes a new Ebox-version asap...

thanks again !

;-) Arthur

[kerridge0]

Yep, really nasty  (nearly ruined weekend level) I'm never going to just download the latest ISO and blindly install it again! let alone update without waiting first.

Obviously I should have come here first to check when I had the error. here's what I was searching for in the wider Google:

"Not enough server storage is available to process this command" samba

EDIT: thank you sidmax you just saved my bacon! and possibly my weekend although probably too late for that :-)

[thiagotgc]

Friends all right? Me not very well because I was 3 days with company failure, as the samba was accusing error.

In the end, I got through the help of our friend here on the forum.

My question is!

Do not have a patch to fix the same?

I really need to use the full functions of the audit / vfs

Thank you all.

[philmills]

Woah!!!!

Dude, you're a lifesaver!  exactly what I needed, some Vista PCs just didn't wanna play nicely. Now they're happy!

[philmills]

admins - please patch this.

i don't know if its related, but backups don't run at the moment. anyone else have that problem since applying this fix?

[philmills]

my bad - there was a config problem with my ftp backup server

[habee]

@sidmax

Thank you, i had the same isssues, your solution works also for me. 

In my case it was the logon-script which did not work anymore (after upgrading from 1.2 to 1.4.1).
I could read it, change it and save it, but it was not executed when a user logged in, although it has the correct permissions set.

Now everything seems to be fine again ...

[maxter]

@sidmax
many many thanks

it seems that this full_audit problem was reported also in samba mailing list, and that it appears randomly, so there is no way for the programmers to reproduce the bug.
really strange.

anyway i think that such a problem  that affect some people should at least  to be mentioned in the documentation/faq.

any ebox developer/manteiner here?

[J. A. Calvo]

@sidmax
many many thanks

it seems that this full_audit problem was reported also in samba mailing list, and that it appears randomly, so there is no way for the programmers to reproduce the bug.
really strange.

anyway i think that such a problem  that affect some people should at least  to be mentioned in the documentation/faq.

any ebox developer/manteiner here?

You are right, I've tested it lots of times and I can't reproduce it. I could reproduce it always with samba 3.4.5, but samba 3.4.6 seems to fix the problem as stated in the changelog.

Anyway, we are not forgetting this and we'll do something about it as soon as possible.