(high on my list to learn is ssh-ing to another machine - not today...)
at the same large desk are the 2 machines i'm using, so no worries for now.
Yes, the file is definitely being created as confirmed by ls. I have
successfully had this access working in the past, this has become an
issue since the change from suse 9.1 to 9.3. There have been no changes
to the file permissions or quotas introduced, or other changes made on
the windows box. I have also checked from my notebook so can confirm it
happens with both win2k & xp, and office 2000 & office xp. Any file can
be renamed, or deleted.
However the saving problem seems to be limited to word and excel files.
I have since found that ppt, jpg, txt, html files can all be created, or
existing ones edited and saved. To blame this on word or excel is easy
but not correct in my opinion due to this working fine under 9.1 in
recent weeks. Having said that, there are numerous references in google
to a particular message I can get with word - "the save failed due to
out of memory or disk space" - but no solutions. The common point to
the posts is that the file resides on a network drive.
This posting I thought to be particularly interesting/relevant (though
beyond me in terms of what it means or what I should do), suggesting a
recent issue with samba perhaps?
http://lists.samba.org/archive/samba-technical/2002-August/023397.html
Roger
Nick Rout wrote:
More random questions (and some comments interspersed in your answer):
which share are you having problems with?
is any file actually being created on the linux box at any stage? (don't
believe what windows tells you, use ls on the command line of the linux
box. It is handy to be ssh'd in via putty while doing this from the
windows box then you don't need to leave your seat)
what are the permissions of the directory where the share resides? can
the windows user (roger I assume) make a file there from the command
line in linux ("touch filename" on the command line).
I see that some of your shares are on non-linux filesystems (ie the ones where
the directory is named /windows/G/whatever). What is the native
filesystem on those partitons, and how are they mounted? (read only?)
I have never actually served up windows partition mounted in linux over
samba - at least i don't recall doing it. There seems to ba a LOT of
layers of permissions and ownerships to check.
Are there any quotas in place on linux or windows?
On Fri, 09 Sep 2005 13:04:47 +1200
Roger Searle wrote:
OK I have tidied up the capitalisation of the paths making them all
consistent.
The file is mostly created by suse. I had added a few lines... I see
that on enlarging the text in kate that all the lines that appeared to
say "read only - no" is actually "read only = no".
Next time please cut and paste it, its much more reliable!
My mistake - so I
had added some lines that were incorrect, and see that log.nmbd was
complaining about them too. Some of the lines must have been fixed by
testparm before I ran it myself. I believe it is all correct now.
Despite this, I still have the same problem.
I tested using the smb.conf file from my previous 9.1 install which did
work, no difference (except the folder names appear different on the
windows machine), still get the same "disk full" or "memory full"
outcomes from the windows machine. (and yes I am restarting samba each
time I make these changes)
Same outcome if I go through the users/roger (where I have a link to the
same files) folder rather than through the data folder.
This all seems to be pointing to an issue with something other than
smb.conf then?
You could try upping the log level in the smb.conf
here's the tail output of log.smbd on opening and saving to a txt file:
[2005/09/09 11:57:08, 1] smbd/service.c:make_connection_snum(642)
aquarius (192.168.1.65) signed connect to service software initially
as user roger (uid=1000, gid=100) (pid 7634)
[2005/09/09 11:57:08, 1] smbd/service.c:make_connection_snum(642)
aquarius (192.168.1.65) signed connect to service users initially as
user roger (uid=1000, gid=100) (pid 7634)
[2005/09/09 11:57:14, 1] smbd/service.c:close_cnum(830)
aquarius (192.168.1.65) closed connection to service software
[2005/09/09 11:57:14, 1] smbd/service.c:close_cnum(830)
aquarius (192.168.1.65) closed connection to service users
here's opening a file that won't save:
[2005/09/09 12:04:34, 1] smbd/service.c:make_connection_snum(642)
aquarius (192.168.1.65) signed connect to service software initially
as user roger (uid=1000, gid=100) (pid 7634)
[2005/09/09 12:04:34, 1] smbd/service.c:make_connection_snum(642)
aquarius (192.168.1.65) signed connect to service users initially as
user roger (uid=1000, gid=100) (pid 7634)
[2005/09/09 12:04:38, 1] smbd/service.c:close_cnum(830)
aquarius (192.168.1.65) closed connection to service software
[2005/09/09 12:04:38, 1] smbd/service.c:close_cnum(830)
aquarius (192.168.1.65) closed connection to service users
Basically identical. At the point of attempting to save that file,
nothing added to the log file. But nor is anything added when the first
file is successfully written to.
Does this help? Any further ideas?
