localhost: openSuse v11.2, linux 2.6.31.8-0.1-desktop x86_64
server: os/2 v4.50 fp3
This was not a problem on v11.1; GBs of data were (and are for hosts not upgraded) written to the os/2 server.
The host has two samba-mounted resources on the remote server; both are storage (disk).
Any attempt to write to the samba resources generates a bunch of write failure messages; it renders the system unstable. Here are the fstab entries.
//sma-server1/pub-data /t cifs credentials=/home/sma-user3/.smb/.smbpw,uid=sma-user3,gid=users,sec=lanman,file_mode=0664,dir_mode=0775,servern=SMA-SERVER1,nocase 0 0
//sma-server1/graphics /w cifs credentials=/home/sma-user3/.smb/.smbpw,uid=sma-user3,gid=users,sec=lanman,file_mode=0664,dir_mode=0775,servern=SMA-SERVER1,nocase 0 0
If the attempt to write data is performed from a GUI application, say Firefox or Thunderbird, the app becomes completely non-responsive. It must be terminated. Unfortunately that does not release the open socket created for the write operation. A system reboot is needed to clear that.
Subsequent attempts to perform the same operation by the app are guaranteed to crash linux. The system becomes completely non-responsive.
Else the GUI becomes unstable, leaving behind artifacts of other windows and mouse bits, and slowly degrades to non-functionality. When that happens, a hardware reset is necessary.
Here is an entry in /log/messages:
Jan 14 15:43:10 sma-station13l kernel: 236.993456] Pid: 4309, comm: thunderbird-bin Not tainted 2.6.31.8-0.1-desktop
#1 System Product Name
Jan 14 15:43:10 sma-station13l kernel: 236.993467] RIP: 0010:<ffffffff810fdd61>] <ffffffff810fdd61>] iov_iter_advance+0x41/0xb0
Jan 14 15:43:10 sma-station13l kernel: 236.993484] RSP: 0018:ffff880048ee5ad8 EFLAGS: 00210287
Jan 14 15:43:10 sma-station13l kernel: 236.993494] RAX: 0000000000000fb6 RBX: 0000000000bcc000 RCX: ffff880048ee5aa0
Jan 14 15:43:10 sma-station13l kernel: 236.993504] RDX: 0000000000bc0fb6 RSI: 0000000000bc0fb6 RDI: ffff880048ee5bb8
Jan 14 15:43:10 sma-station13l kernel: 236.993514] RBP: ffff880048ee5ae8 R08: 0000000000000000 R09: 0000000000000000
Jan 14 15:43:10 sma-station13l kernel: 236.993525] R10: 00000000ffffffff R11: 0000000000000001 R12: 0000000000000fb6
Jan 14 15:43:10 sma-station13l kernel: 236.993535] R13: ffff880048ee5bb8 R14: 0000000000000000 R15: ffff88004e0ad6c8
Jan 14 15:43:10 sma-station13l kernel: 236.993545] FS: 00007f9dc05fe910(0000) GS:ffff880005466000(0063) knlGS:00000000f6426a40
Jan 14 15:43:10 sma-station13l kernel: 236.993555] CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Jan 14 15:43:10 sma-station13l kernel: 236.993565] CR2: 00000000c68f9000 CR3: 0000000048ed1000 CR4: 00000000000006e0
Jan 14 15:43:10 sma-station13l kernel: 236.993575] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 14 15:43:10 sma-station13l kernel: 236.993585] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 14 15:43:10 sma-station13l kernel: 236.993597] Process thunderbird-bin (pid: 4309, threadinfo ffff880048ee4000, task ffff880048ee2840)
Jan 14 15:43:10 sma-station13l kernel: 236.993607] Stack:
Jan 14 15:43:10 sma-station13l kernel: 236.993614] 0000000000000000 0000000074a1f316 ffff880048ee5b88 ffffffff81100e09
Jan 14 15:43:10 sma-station13l kernel: 236.993622] <0> 0000000000bc8000 000004e84e0ad6c8 0000000000bc0fb6 00000fb600000000
Jan 14 15:43:10 sma-station13l kernel: 236.993635] <0> ffffffffa0493740 ffff88009b154cc0 0000000000004000 0000000000001000
Jan 14 15:43:10 sma-station13l kernel: 236.993652] Call Trace:
Jan 14 15:43:10 sma-station13l kernel: 236.993670] <ffffffff81100e09>] generic_perform_write+0x169/0x220
Jan 14 15:43:10 sma-station13l kernel: 236.993684] <ffffffff81100f50>] generic_file_buffered_write+0x90/0x160
Jan 14 15:43:10 sma-station13l kernel: 236.993697] <ffffffff8110170f>] __generic_file_aio_write_nolock+0x28f/0x4d0
Jan 14 15:43:10 sma-station13l kernel: 236.993710] <ffffffff81101aaf>] generic_file_aio_write+0x7f/0x110
Jan 14 15:43:10 sma-station13l kernel: 236.993731] <ffffffffa046515b>] cifs_file_aio_write+0x2b/0x60 [cifs]
Jan 14 15:43:10 sma-station13l kernel: 236.993751] <ffffffff8114bb12>] do_sync_write+0x102/0x160
Jan 14 15:43:10 sma-station13l kernel: 236.993764] <ffffffff8114be98>] vfs_write+0xd8/0x1c0
Jan 14 15:43:10 sma-station13l kernel: 236.993775] <ffffffff8114c82b>] sys_write+0x5b/0xa0
Jan 14 15:43:10 sma-station13l kernel: 236.993788] <ffffffff8104bd6f>] cstar_dispatch+0x7/0x2e
Jan 14 15:43:10 sma-station13l kernel: 236.993803] <00000000ffffe425>] 0xffffe425
Jan 14 15:43:10 sma-station13l kernel: 236.993811] Code: c0 48 8b 47 18 48 39 f0 72 21 48 83 7f 08 01 75 23 48 01 77
10 48 29 77 18 48 8b 45 f8 65 48 33 04 25 28 00 00 00 75 07 c9 90 c3 <0f> 0b eb fe e8 86 d3 f6 ff 48 8b 0f 48 8b 57 10 48 85 f6 75 0e
Jan 14 15:43:10 sma-station13l kernel: 236.993869] RIP <ffffffff810fdd61>] iov_iter_advance+0x41/0xb0
Jan 14 15:43:10 sma-station13l kernel: 236.993880] RSP <ffff880048ee5ad8>
Jan 14 15:43:10 sma-station13l kernel: 236.993889] --- end trace 9a05be4e5e7d1f29 ]---
And a bit from log.smbd:
[2010/01/14 15:39:34, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
This is a serious defect.