search for: smb_writepage_sync

...t succesfull. My previos kernel (2.4.24) work correctly. Smbclient work correctly with new kernels. Report error from /var/log/messages for kernel 2.6.11.11 and 2.6.11.12: Jun 15 09:29:03 darkknight kernel: smb_add_request: request [c5595e80, mid=29] timed out! Jun 15 09:29:03 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-5 Jun 15 09:33:48 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-512 Jun 15 09:41:05 darkknight kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-512 Jun 15 09:48:05 darkknight kernel: smb_writepage_sync: failed write...

...sudden (I'm sure it's for a reason, but I can't tell why), this shows up in the logs: Oct 15 10:36:03 mumbai kernel: smb_errno: class ERRDOS, code 112 from command 0xb Oct 15 10:36:03 mumbai kernel: smb_errno: class ERRDOS, code 112 from command 0xb Oct 15 10:36:03 mumbai kernel: smb_writepage_sync: failed write, wsize=512, result=-5 Could anybody tell me if this is something to worry about and what might be causing it? Thanks, Erik Enge.

...second process can't write to it either. It's very much a timing issue. If the requests are spread out just enough, then no one's the wiser. Samba generates the following error (from messages). I believe that means that Samba is getting an EBADF error (bad file number). kernel: smb_writepage_sync: failed write, wsize=4096, result=-9 What exactly is going on in the file system during this? I know what happens in a normal UNIX file system (and the problem does not occur there). I am going to write a test application that creates just plain files without using the PDF library to see if per...

...the SMBfs page write code. It seems that the code in generic_file_write has changed fairly recently, and it is now a bug for the 'updatepage' code to clear the page lock and serve the wait queue. Unfortunately nobody seems to have removed the call to 'smb_unlock_page(page)' in 'smb_writepage_sync'. Would people who've been seeing problems with the smbfs client in 2.2.1 please try the appended one-liner and see if it works? BTW: The reason I noticed this bug is because I actually wanted to revert to the old behaviour for the NFS write-clustering project. Since the smbfs and NF...

...bert/2003-07-28.FULL.galileo.tar.gz': Input/output error I also checked the syslog for the specific time, the copy took place: Aug 11 19:11:36 galileo kernel: smb_get_length: recv error = 5 Aug 11 19:11:36 galileo kernel: smb_request: result -5, setting invalid Aug 11 19:11:36 galileo kernel: smb_writepage_sync: failed write, wsize=4096, result=-5 Aug 11 19:11:36 galileo kernel: smb_retry: successful, new pid=19729, generation=2 Any chance, that the firewall could be the problem (the linux box stands in the dmz and the windows backup server in the internal lan)? For test purposes I opened all ports betwe...

...error=-2, breaking Jun 7 10:19:57 brunettie kernel: smb_errno: class ERRSRV, code 64 from command 0x32 Jun 7 10:20:08 brunettie kernel: smb_proc_readdir_long: error=-2, breaking Jun 7 10:20:37 brunettie kernel: smb_errno: class ERRSRV, code 64 from command 0x2f Jun 7 10:20:37 brunettie kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-5 Jun 7 10:29:21 brunettie kernel: smb_add_request: request [0468ce80, mid=35] timed out! and after this first error, even if i restart smb this is what i get: Jun 11 15:33:28 brunettie kernel: smb_add_request: request [06624e80, mid=32] timed out! Jun 11 15...

...N. The PC wich is backed up mounts the share on the NT WS and starts to write its harddrive-content to a tar on the share. After approx. 250-500 MB written to the target, I will get the following error messages (repeatedly): smb_get_length: recv error = 5 smb_request: result -5, setting invalid smb_writepage_sync: failed write, wsize = 4096, result = -5 smb_file_write: //$workstation/$share/$file, error = 4294967291 smb_retry: successful, new pid = $pid, generation = 2 Okay, the thing is, that samba can't write to the target any more (if I don't understand this completely wrong). But, what the he...

...the thecus and cp large files to it from my local filesystem, I get wildly incomplete files. Using smbclient to 'put' files however is perfect. The thecus doesn't give me any clue whether it recognizes the write errors, in /var/log/messages I can see: >Mar 4 14:48:23 brutus kernel: smb_writepage_sync: failed write, > wsize=4096, write_ret=-512 Things like -osync don't seem to work under smbfs, so I'm at the end of my (small) wits... I also tried to mount the folder as cifs, but there I get totally weird uid and gid, so I didn't pursue. That is another mailing list anyhow, a...

...wardrobe.tar.gz.1 wardrobe.tar.gz_test123 cp: writing `wardrobe.tar.gz_test123': Input/output error Errors from syslog: Sep 10 07:53:06 aslan kernel: smb_get_length: Invalid NBT packet, code=39 Sep 10 07:53:06 aslan kernel: smb_request: result -5, setting invalid Sep 10 07:53:06 aslan kernel: smb_writepage_sync: failed write, wsize=4096, result=-5 Sep 10 07:53:09 aslan kernel: smb_retry: successful, new pid=28697, generation=2 Sep 10 07:53:09 aslan kernel: smb_get_length: recv error = 5 Sep 10 07:53:09 aslan kernel: smb_request: result -5, setting invalid Sep 10 07:53:32 aslan kernel: smb_retry: successfu...

...f it is responsible? ################################################################################ Nov 8 17:15:14 poseidon automount[32023]: failed to mount /win/metal10 Nov 8 17:15:37 poseidon kernel: smb_add_request: request [efeff680, mid=36572] timed out! Nov 8 17:15:37 poseidon kernel: smb_writepage_sync: failed write, wsize=4096, write_ret=-5 Nov 8 17:15:37 poseidon kernel: smb_add_request: request [eb962080, mid=14] timed out! Nov 8 17:21:53 poseidon kernel: Unable to handle kernel paging request at virtual address 0600000 0 Nov 8 17:21:53 poseidon kernel: printing eip: Nov 8 17:21:53 poseid...