samba - Feb 2004 - More Info: Mac permission problems after Debian update

There seems to be a few people having this problem, but not much response.
I've dug into the logs, and while I don't know exactly what I am looking
at, I think I may have found something that may make sense to someone.

A short recap. Samba was working fine, until I did a Debian security
update, which upgraded my Samba to 2.2.8a. Now, I can create files on a
mounted Samba share in a console, but not in the finder, I get the message
'The operation cannot be completed because you do not have sufficient
privileges for "dilbert030923.gif"', which is the name of the file
being
copied. From what I see in the logs, I think the privileges message is
off.

Once I dismiss the dialog, there is nothing in the directory I am copying
to, but before I dismiss, I find two files: a zero length
dilbert030923.gif, and a 82 byte ._dilbert030923.gif.  One of the files
being non-zero length is a second clue that the privileges message may be
bogus.

Because of the error messages below, I tried turning off posix locking,
and things seem to be working now. So I guess my question has become, will
running without posix locking harm anything? And, I don't believe I
changed that setting during the upgrade. I suppose the default could have
changed, but is there something more sinister going on in the logs below?

I mounted the share, changed logging to level 10, and tried to copy a
file.

Looking in the log, I can see it create the 82 byte file, and
open/read/close it a few times. There are a few of these:

[2004/02/12 00:07:40, 3] smbd/process.c:switch_message(685)
  switch message SMBlockingX (pid 391)
[2004/02/12 00:07:40, 4] smbd/uid.c:change_to_user(119)
  change_to_user: Skipping user change - already user
[2004/02/12 00:07:40, 10] smbd/reply.c:reply_lockingX(4707)      
  reply_lockingX: unlock start=0, len=4294967295 for pid 1, file
mp3/bar/._dilbert030923.gif
[2004/02/12 00:07:40, 10] locking/locking.c:do_unlock(197)
  do_unlock: unlock start=0 len=4294967295 requested for file
mp3/bar/._dilbert030923.gif
[2004/02/12 00:07:40, 10] locking/brlock.c:brl_unlock(432)
  brl_unlock: tdb_fetch failed !
[2004/02/12 00:07:40, 10] locking/locking.c:do_unlock(209)
  do_unlock: returning ERRlock.
[2004/02/12 00:07:40, 3] smbd/error.c:error_packet(129)
  error packet at smbd/reply.c(4712) cmd=36 (SMBlockingX) eclass=1
ecode=158

But things seem to head south around here:

[2004/02/12 00:07:40, 3] smbd/process.c:switch_message(685)
  switch message SMBlockingX (pid 391)
[2004/02/12 00:07:40, 4] smbd/uid.c:change_to_user(119)
  change_to_user: Skipping user change - already user
[2004/02/12 00:07:40, 10] smbd/reply.c:reply_lockingX(4741)
  reply_lockingX: lock start=0, len=4294967295 for pid 1, file
mp3/bar/dilbert030923.gif timeout = 0
[2004/02/12 00:07:40, 10] locking/locking.c:do_lock(113)
  do_lock: lock type WRITE start=0 len=4294967295 requested for file
mp3/bar/dilbert030923.gif
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(969)
  set_posix_lock: File mp3/bar/dilbert030923.gif, offset = 0, count 4294967295,
type = WRITE
[2004/02/12 00:07:40, 10] locking/posix.c:posix_lock_in_range(632)
  posix_lock_in_range: offset_out = 0, count_out = 4294967295
[2004/02/12 00:07:40, 10] locking/posix.c:add_posix_lock_entry(392)
  add_posix_lock: File mp3/bar/dilbert030923.gif: type = WRITE: start=0
size=4294967295: dev=833 inode=19598      
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(1055)
  set_posix_lock: Real lock: Type = WRITE: offset = 0, count = 4294967295
[2004/02/12 00:07:40, 8] locking/posix.c:posix_fcntl_lock(650)
  posix_fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:40, 8] lib/util.c:fcntl_lock(1308)
  fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:40, 3] lib/util.c:fcntl_lock(1319)
  fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data
type)
[2004/02/12 00:07:40, 3] lib/util.c:fcntl_lock(1341)
  fcntl_lock: lock failed at offset 0 count 4294967295 op 13 type 1 (Value
too large for defined data type)
[2004/02/12 00:07:40, 8] locking/posix.c:posix_fcntl_lock(680)
  posix_fcntl_lock: Lock call failed
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(1059)
  set_posix_lock: Lock fail !: Type = WRITE: offset = 0, count 4294967295. Errno
= Value too large for defined data type
[2004/02/12 00:07:40, 10] locking/locking.c:do_lock(113)
  do_lock: lock type WRITE start=0 len=4294967295 requested for file
mp3/bar/dilbert030923.gif
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(969)
  set_posix_lock: File mp3/bar/dilbert030923.gif, offset = 0, count 4294967295,
type = WRITE
[2004/02/12 00:07:40, 10] locking/posix.c:posix_lock_in_range(632)
  posix_lock_in_range: offset_out = 0, count_out = 4294967295
[2004/02/12 00:07:40, 10] locking/posix.c:add_posix_lock_entry(392)
  add_posix_lock: File mp3/bar/dilbert030923.gif: type = WRITE: start=0
size=4294967295: dev=833 inode=19598
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(1055)
  set_posix_lock: Real lock: Type = WRITE: offset = 0, count = 4294967295
[2004/02/12 00:07:40, 8] locking/posix.c:posix_fcntl_lock(650)
  posix_fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:40, 8] lib/util.c:fcntl_lock(1308)
  fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:40, 3] lib/util.c:fcntl_lock(1319)
  fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data
type)
[2004/02/12 00:07:40, 3] lib/util.c:fcntl_lock(1341)
  fcntl_lock: lock failed at offset 0 count 4294967295 op 13 type 1 (Value
too large for defined data type)
[2004/02/12 00:07:40, 8] locking/posix.c:posix_fcntl_lock(680)
  posix_fcntl_lock: Lock call failed
[2004/02/12 00:07:40, 5] locking/posix.c:set_posix_lock(1059)
  set_posix_lock: Lock fail !: Type = WRITE: offset = 0, count 4294967295. Errno
= Value too large for defined data type
[2004/02/12 00:07:41, 10] locking/locking.c:do_lock(113)
  do_lock: lock type WRITE start=0 len=4294967295 requested for file
mp3/bar/dilbert030923.gif
[2004/02/12 00:07:41, 5] locking/posix.c:set_posix_lock(969)
  set_posix_lock: File mp3/bar/dilbert030923.gif, offset = 0, count 4294967295,
type = WRITE
[2004/02/12 00:07:41, 10] locking/posix.c:posix_lock_in_range(632)
  posix_lock_in_range: offset_out = 0, count_out = 4294967295
[2004/02/12 00:07:41, 10] locking/posix.c:add_posix_lock_entry(392)
  add_posix_lock: File mp3/bar/dilbert030923.gif: type = WRITE: start=0
size=429
4967295: dev=833 inode=19598
[2004/02/12 00:07:41, 5] locking/posix.c:set_posix_lock(1055)
  set_posix_lock: Real lock: Type = WRITE: offset = 0, count = 4294967295
[2004/02/12 00:07:41, 8] locking/posix.c:posix_fcntl_lock(650)
  posix_fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:41, 8] lib/util.c:fcntl_lock(1308)
  fcntl_lock 22 13 0 4294967295 1
[2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1319)
  fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data
type)
[2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1341)
  fcntl_lock: lock failed at offset 0 count 4294967295 op 13 type 1 (Value
too large for defined data type)
[2004/02/12 00:07:41, 8] locking/posix.c:posix_fcntl_lock(680)
  posix_fcntl_lock: Lock call failed
[2004/02/12 00:07:41, 5] locking/posix.c:set_posix_lock(1059)
  set_posix_lock: Lock fail !: Type = WRITE: offset = 0, count 4294967295. Errno
= Value too large for defined data type
[2004/02/12 00:07:41, 3] smbd/error.c:error_packet(94)
  error string = Value too large for defined data type
[2004/02/12 00:07:41, 3] smbd/error.c:error_packet(129)
  error packet at smbd/reply.c(4786) cmd=36 (SMBlockingX) eclass=1
ecode=33
[2004/02/12 00:07:41, 5] lib/util.c:show_msg(275)

The size of the file being copied is 17093 bytes.

Do the error messages in this log snippet provide any real clues?

Thank you,

-Michael


__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Hallo Michael,
> [2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1319)
>   fcntl_lock: fcntl lock gave errno 75 (Value too large for defined data
> type)
> [2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1341)
>   fcntl_lock: lock failed at offset 0 count 4294967295 op 13 type 1 (Value
> too large for defined data type)
this is a typical error if using a samba package compiled on a system with 64Bit
locking structs (Linux-Kernel 2.4.x) on a system with 32Bit locking structs
(Linux 2.2.x). Compile samba on the machine, on which samba should running.
I would also prefere a samba, which makes it easier to crosscompile...

der tom
______________________________________________________________________________
Nachrichten, Musik und Spiele schnell und einfach per Quickstart im 
WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110

Rather than recompile Samba for the 2.2 kernel, I built and installed a
2.4.X kernel. I turned posix locks back on, and it works like a champ!

Hopefully this solution will work for the others who have also had this
problem with Mac OS X.

Thanks!

-Michael

--- Thomas Bork <TomBork@web.de> wrote:
> Hallo Michael,
> 
> > [2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1319)
> >   fcntl_lock: fcntl lock gave errno 75 (Value too large for defined
> data
> > type)
> > [2004/02/12 00:07:41, 3] lib/util.c:fcntl_lock(1341)
> >   fcntl_lock: lock failed at offset 0 count 4294967295 op 13 type 1
> (Value
> > too large for defined data type)
> 
> this is a typical error if using a samba package compiled on a system
> with 64Bit locking structs (Linux-Kernel 2.4.x) on a system with 32Bit
> locking structs (Linux 2.2.x). Compile samba on the machine, on which
> samba should running.
> I would also prefere a samba, which makes it easier to crosscompile...
> 
> der tom

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Hi Michael,
> Rather than recompile Samba for the 2.2 kernel, I built and installed a
> 2.4.X kernel. I turned posix locks back on, and it works like a champ!
> 
> Hopefully this solution will work for the others who have also had this
> problem with Mac OS X.
this has nothing to do with MacOSX. I had similar errors with win clients. Samba
2.2.8a self compiled on kernel 2.4.23 running on kernel 2.2.19.

It would be very usefull to have an parameter like 'locking base= xx'
with 'xx' is 32 or 64 in global smb.conf. This would allow to manually
changing this compile time parameter. Where the behaviour is this:

locking base (default, use result from configure at compile time)

locking base = 32
(use 32 bit locking base, override result from configure at compile time)

locking base = 64
(use 64 bit locking base, override result from configure at compile time)

Shure, the answer of developers will be:
"Send patches."

But: Sorry, I don't speaking C...

der tom
______________________________________________________________________________
Ein Grund zum Feiern: Die PC Praxis ermittelt zwischen 10 grossen
Mailprovidern WEB.DE FreeMail als Testsieger http://f.web.de/?mc=021190