Problems still abound in smbfs. I had a chance to do some testing this
weekend, and here's what happens:
2.1.62 (no patches):
-- Server: WfW 3.11 on Intel -----
iozone or Bonnie creates file but fails with "Error reading block 0".
I am able to copy files to the server, but the file mtime is not
preserved.
Nov 9 17:16:28 cy kernel: smb_newconn: server not locked, count=1
Nov 9 17:16:28 cy kernel: smb_offerconn: server not locked, count=1
Nov 9 17:16:28 cy kernel: smb_offerconn: state valid, pid=3311
--- Server: NT Workstation 4.0 on Alpha ----
iozone and Bonnie are fine.
Unable to umount smb directory even when zero activity has occurred after
the mount operation!
**************************************************************************
2.1.62 w/ smbfs_62-patch:
--- Server: WfW 3.11 on Intel 486DX4/100 ----
Neither Bonnie nor iozone can even begin to write. A zero-length
file is left on the server. It is not possible to even copy files
to the server - same messages and results.
Nov 9 17:11:25 amd kernel: smb_newconn: server not locked, count=1
Nov 9 17:11:25 amd kernel: smb_offerconn: server not locked, count=1
Nov 9 17:11:25 amd kernel: smb_offerconn: state valid, pid=179
Nov 9 17:11:34 amd kernel: smb_request_ok: verify failed, result=-5
Nov 9 17:11:47 amd last message repeated 2 times
Nov 9 17:11:58 amd kernel: smb_proc_create: BENCH/iozone.tmp created,\
fileid=5
Nov 9 17:11:58 amd kernel: smb_proc_open: BENCH/iozone.tmp open failed,\
error=-26, retrying R/O
Nov 9 17:12:12 amd kernel: smb_proc_create: BENCH/iozone.tmp created, fileid=8
Nov 9 17:12:12 amd kernel: smb_proc_open: BENCH/iozone.tmp open failed,\
error=-26, retrying R/O
Nov 9 17:12:16 amd kernel: smb_proc_create: BENCH/test created, fileid=11
Nov 9 17:12:25 amd kernel: smb_request_ok: verify failed, result=-5
Nov 9 17:12:38 amd kernel: smb_proc_create: BENCH/iozone.tmp created,\
fileid=12
Nov 9 17:12:38 amd kernel: smb_proc_open: BENCH/iozone.tmp open failed,\
error=-26, retrying R/O
Nov 9 17:12:44 amd kernel: smb_proc_create: BENCH/Bonnie.194 created,\
fileid=15
Nov 9 17:12:44 amd kernel: smb_proc_open: BENCH/Bonnie.194 open failed,\
error=-26, retrying R/O
Nov 9 17:13:01 amd kernel: smb_request_ok: verify failed, result=-5
Nov 9 17:13:12 amd kernel: smb_request_ok: verify failed, result=-5
--- Server: NT Workstation 4.0 on Alpha ----
Iozone with reclen = 2048 is an order-of-magnitude slower than with
all other lengths:
(hirsch@amd) ~/smb/TEMP : iozone auto
IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94)
By Bill Norcott
Operating System: POSIX 1003.1-1990 -- using fsync()
IOZONE: auto-test mode
MB reclen bytes/sec written bytes/sec read
1 512 127408 14979657
1 1024 214872 14979657
1 2048 10067 14979657
^^^^^^
1 4096 435093 14979657
1 8192 476625 14979657
2 512 125577 1335765
2 1024 207228 1519675
2 2048 10073 1426634
^^^^^^^
2 4096 433295 1497965
2 8192 496955 1651300
IOZONE: interrupted
deleting file: iozone.tmp
exiting IOzone
Bonnie works fine.
Logs from both the above:
Nov 9 18:27:34 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=2054
Nov 9 18:27:36 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=2056
Nov 9 18:27:38 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=2058
Nov 9 18:27:57 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=2061
Nov 9 18:28:08 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=4096
Nov 9 18:31:38 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=4099
Nov 9 18:31:44 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=4102
Nov 9 18:31:50 amd kernel: smb_proc_create: TEMP/iozone.tmp created, fileid=4105
Nov 9 18:35:56 amd kernel: smb_proc_create: TEMP/Bonnie.294 created, fileid=4108
Nov 9 18:36:18 amd kernel: smb_proc_create: TEMP/Bonnie.294 created, fileid=4111
*** Unable to umount the smb directory:
(hirsch@amd) ~ : smbumount smb
Could not umount /net/air/home/hirsch/smb: Device or resource busy
(Had to reboot for this to clear..)
********************************************************************************
Summary:
umount problems are particular to the NT server.
Unsure what other conclusions to draw, except that smbfs needs further work..
Please let me know what you would like to focus on? I do not have access
to an actual NT server. All my work is done by mounting shares from
workstation.
Steve