similar to: smb_request: result -104, setting invalid

Why do I keep getting these messages? (from /var/log/messages) I use RedHat 7.1 and have a coupple of shares on the machine on a bizzy samba network. Oct 10 04:03:50 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10 04:03:50 n243 kernel: smb_retry: successful, new pid=5506, generation=47 Oct 10 04:44:03 n243 kernel: smb_trans2_request: result=-104, setting invalid Oct 10

While using smbmounted shares I get the following errors in my syslog: ---<snip>-- Nov 27 18:27:45 cayman kernel: smb_request: result -104, setting invalid Nov 27 18:27:46 cayman kernel: smb_retry: successful, new pid=529, generation=2 --</snip>-- Is this something I should worry about? I am using RH 6.2, linux 2.4.16 and samba-2.0.10-0.62 installed from RPM. Regards, Peter

Greetings, About 2 months ago, we decided to backup our Oracle test servers via samba rather than nfs -- the backups were just taking too long using nfs. No problem mounting the remote file share to the server and the backup took about one-third of the time. Yep, worked good...and still continues to out perform nfs hands down. Problem is - I'm receiving errors on both of the test servers.

Forgot to provide errors from my samba.log [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) <shrug>, oplocks is turned off, so

Hi guys, I hope I've reached the correct mailinglist. I'm experiencing a problem with smbfs. You can mount shares, but after a while, the connection is broken and all sorts of strange stuff happens. I've got a share called /mnt/ntshare which remotely mounts an NT host: [arnow@foo /mnt]$ ls ls: ntshare: Input/output error cdrom/ floppy/ [arnow@foo /mnt]$ [arnow@foo /mnt]$ dmesg |

Found these messages in /var/log/dmesg on a Redhat 7.1 machine running Samba 2.2.2 accessing a Win 2000 share. Actually, there are a bunch of tasks accessing the same share, complete with file locking, etc. Any docs on what that error code means? ...Thanks, ...Kenneth smb_get_length: recv error = 113 smb_trans2_request: result=-113, setting invalid smb_file_write: syndex/csafe.log validation

Dear Sirs: I wish to report my experience with the package. I have compiled and used Samba 2.0.7pre 2, pre3, and pre4. I have not had any trouble connecting to Samba's shares (from an NT client), but I would like to report a problem with SMBFS and SMBMOUNT. NT4, SP5 shares mounted into the filespace of the Linux box can disconnect over time with two possible outcomes. The activity is

Hi, I am running samba 3.0.4 on my fedora box and I have been noticing a message like this showing up in /var/log/messages every hour, on the hour. May 16 10:01:00 box kernel: smb_request: result -104, setting invalid May 16 10:01:00 box kernel: smb_retry: successful, new pid=21347, generation=9 I assume that this message is being caused somehow by a cron job (diskcheck) that is going through

Hi there. I'm having a very odd problem with samba. I have a Mandrake 7.2 linux distro, though I've compiled a 2.4.2 kernel for it (with samba support compiled in - not a module), and I've also compiled Samba 2.0.7. When I mount shares from my win98 machines, if I try to list a large directory or open a large file, the terminal freezes. I'm able to log in another, but if I

smb_request: result -104, setting invalid this repeatedly occurs in the messages log and the kernel log. does anyone know how i can look this up and find out what it means? samba appears to be working fine but i'd like to get to the bottom of it. cheers, kev

Hi! We're experiencing a really weird problem with our linux smb client. We map four directories to a NT4-share from our linux-box (2.2.12). The problem is that the mount goes through just fine with no complaints and I can see the files on that share, but, I can't see new files created with ls on the nt4-server on the linuxbox but if I run more <filename> I can see the contents of

Every morning at 2:02am, and 6:25am, I get the following two lines in my /var/log/messages: Nov 6 06:25:15 borgCube kernel: smb_trans2_request: result=-104, setting invalid Nov 6 06:25:16 borgCube kernel: smb_retry: successful, new pid=28929, generation=37 The pid always stays the same, and generation increases by 1 everytime it happens. Currently I got one share from a W2K computer mounted

My current smb.conf http://mdew.orcon.net.nz/samba/smb.conf , isnt showing up in windows b0xes (Win2k) I can however mount my drive from the linux router, and it shows this error (maybe unrelated/related to this..) mount /sharing/ryan smb_get_length: recv error = 5 smb_trans2_request: result=-5 setting invalid smb_retry: succesful, new pid=32382, generation=2 My drive is browsable from the

Hello everyone. I have two linux servers* that each have four directories mounted as SMBFS shares from a Windows 2000 Server. For the most part, this set-up is working great, however, there have been occasional hiccups. Every so often, one of the servers, LINUX-ONE, logs a couple of Samba-related errors. The following is an example: Jun 30 06:30:45 mx-two kernel: smb_trans2_request:

Hi, I'm using samba-2.0.6-19991110 on Redhat 6.1 in order to mount a NT-filesystem. The mount command is: smbmount //ISDN/CoTel /mnt/NT-Bank/ -o username=serv,password=serv,workgroup=WORK,uid=root,gid=users,ro everything works fine, except that after one or two days the mount disappears. A simple 'ls /mnt/NT-Bank/MCCWIN' results in 'Input/output error'. In

Hello, I am running Samba-2.2.0alpha-2 on a OpenLinux 2.3 (Caldera) system, and I was wondering if this error message is NORMAL behavior for a NT Server share mounted with the following command: //inet_server_1/C /mnt/server1 -o username=xxxxxxxx,password=xxxxxx,ip=x.x.x.2 here is what is in /var/log/messages: Mar 15 09:51:59 htmlodds kernel: smb_trans2_request: result=-32, setting invalid

A friend of mine is running Samba (samba-2.0.3-8) on a couple RedHat Linux 6.0 machines. He is sharing files bilaterally at work with a WinNT machine and at home with a Win9x machine. In both places, he is getting a large number of SMB error messages. I'm not sure whether these are from the smbfs (smbmount) or from the Windoze machines accessing the Linux drives, though I suspect the

I keep seeing this in my logs: Jul 5 12:37:29 gateway kernel: smb_trans2_request: result=-32, setting invalid What have I screwed up? Also, any news on when the search stuff will be back up?

After posting to samba-nt and samba-technical I was told that this was the place. Running 2.0.7-21 Feb 22 12:42:41 server1 kernel: smb_trans2_request: result=-32, setting invalid Feb 22 12:42:41 server1 kernel: smb_retry: sucessful, new pid=32561, generation=4 I have removed the system from the domain, erased the SID's, reset the computer account, rejoined the domain and still get this

Hi - My messages may not be reaching this list. Would someone at least confirm receipt of this message even if you have no suggestions/ comments re its content? I have sent several messages concerning mount.smbfs and I guess no one is using smbfs to mount a Windows machine -or- no one has encountered my problem. To recap the problem and give a solution: [problem] mount.smbfs is not working on