NFS Server, Mac OS 10.4, and iSCSI = ntfs.sys BSOD
hello everyone!
don't run issue can't take care of, 1 stumping me. able out.
i've got client has interesting storage needs, , deployment little off wall. decided go sbs 2008 machine talks 2 iscsi targets. actual server has 1tb of mirrored storage on ich10r south bridge. both iscsi targets created openfiler, using novell's iscsi stack. in end, newer , faster , bigger iscsi box main storage network, while older iscsi box used backup server backup. i've tested on smaller scale vm's , seems work fine.
catch have several mac os 10.4 machines need access these files also. should know fix upgrade 10.5 , use smb stack, let's face it, 10.5 poo , can't recommend deploying that. so, decided work around smb stack nfs.
have 5 or shares everyone-writeable macs , pcs share, while other shares, usershares, windows. share shares nfs, anonymous, everyone-writeable root-access. had issues getting new iscsi target up, running on single iscsi, , didn't have issues. however, there not many clients using it.
earlier week, finished new iscsi target, , began moving data it. got 500gb or transferred, , started sharing path through nfs, did before. 8 or clients got hooked it, 8 hours later, server began blue-screening, ntfs.sys being affected driver. took me minute piece together, seems high traffic nfs shares culprit. ran dump through windmp, , here's whole output:
now, we're moving rest of data can nfs talking 1 iscsi target, wondering if else has seen , has quick fix. google-ing in world doesn't seem find else particular setup or bsod. main points of interest can see here 2 iscsi targets nfs shares on them, , heavy traffic shares.
help. we'd rather not spend $1500 afp software talk these stupid things.
-nate solberg
owner, nordic pc
don't run issue can't take care of, 1 stumping me. able out.
i've got client has interesting storage needs, , deployment little off wall. decided go sbs 2008 machine talks 2 iscsi targets. actual server has 1tb of mirrored storage on ich10r south bridge. both iscsi targets created openfiler, using novell's iscsi stack. in end, newer , faster , bigger iscsi box main storage network, while older iscsi box used backup server backup. i've tested on smaller scale vm's , seems work fine.
catch have several mac os 10.4 machines need access these files also. should know fix upgrade 10.5 , use smb stack, let's face it, 10.5 poo , can't recommend deploying that. so, decided work around smb stack nfs.
have 5 or shares everyone-writeable macs , pcs share, while other shares, usershares, windows. share shares nfs, anonymous, everyone-writeable root-access. had issues getting new iscsi target up, running on single iscsi, , didn't have issues. however, there not many clients using it.
earlier week, finished new iscsi target, , began moving data it. got 500gb or transferred, , started sharing path through nfs, did before. 8 or clients got hooked it, 8 hours later, server began blue-screening, ntfs.sys being affected driver. took me minute piece together, seems high traffic nfs shares culprit. ran dump through windmp, , here's whole output:
microsoft (r) windows debugger version 6.11.0001.404 amd64can see, looks our little workaround talking these macs issue here.
copyright (c) microsoft corporation. rights reserved.
loading dump file [c:\users\mtadmin\desktop\mini052109-01.dmp]
mini kernel dump file: registers , stack trace available
symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
executable search path is:
windows server 2008/windows vista kernel version 6001 (service pack 1) mp (4 procs) free x64
product: lanmannt, suite: smallbusiness terminalserver smallbusinessrestricted singleuserts
built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
machine name:
kernel base = 0xfffff800`01c4b000 psloadedmodulelist = 0xfffff800`01e10db0
debug session time: thu may 21 09:14:04.067 2009 (gmt-4)
system uptime: 0 days 16:35:11.209
loading kernel symbols
...............................................................
................................................................
................
loading user symbols
loading unloaded module list
...
error: findplugins 80070005
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
use !analyze -v detailed debugging information.
bugcheck 50, {fffffa60091cd000, 0, fffffa600121ef94, 0}
not read faulting driver name
caused : nfssvr.sys ( nfssvr!nfsntquerydirectoryfile+b9 )
followup: machineowner
---------
3: kd> !analyze -v
error: findplugins 80070005
*******************************************************************************
* *
* bugcheck analysis *
* *
*******************************************************************************
page_fault_in_nonpaged_area (50)
invalid system memory referenced. cannot protected try-except,
must protected probe. typically address plain bad or it
pointing @ freed memory.
arguments:
arg1: fffffa60091cd000, memory referenced.
arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
arg3: fffffa600121ef94, if non-zero, instruction address referenced bad memory
address.
arg4: 0000000000000000, (reserved)
debugging details:
------------------
not read faulting driver name
read_address: getpointerfromaddress: unable read fffff80001e74080
fffffa60091cd000
faulting_ip:
ntfs!memcpy+124
fffffa60`0121ef94 4c8b540a08 mov r10,qword ptr [rdx+rcx+8]
mm_internal_code: 0
customer_crash_count: 1
default_bucket_id: driver_fault_server_minidump
bugcheck_str: 0x50
process_name: system
current_irql: 0
trap_frame: fffffa60091cc050 -- (.trap 0xfffffa60091cc050)
note: trap frame not contain registers.
register values may zeroed or incorrect.
rax=0000000000000015 rbx=0000000000000000 rcx=fffff880157dfc40
rdx=000001dff39ed3b2 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa600121ef94 rsp=fffffa60091cc1e8 rbp=fffffa80100e2c60
r8=00000000ffffffb4 r9=0000000000000000 r10=0000000000000000
r11=fffff880157df180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv ei pl nz na pe nc
ntfs!memcpy+0x124:
fffffa60`0121ef94 4c8b540a08 mov r10,qword ptr [rdx+rcx+8] ds:f140:fffffa60`091ccffa=????????????????
resetting default scope
last_control_transfer: fffff80001cae671 fffff80001c9f650
stack_text:
fffffa60`091cbf58 fffff800`01cae671 : 00000000`00000050 fffffa60`091cd000 00000000`00000000 fffffa60`091cc050 : nt!kebugcheckex
fffffa60`091cbf60 fffff800`01c9e1d9 : 00000000`00000000 fffff880`007bc000 00000000`00000000 00000000`00000050 : nt!mmaccessfault+0x1371
fffffa60`091cc050 fffffa60`0121ef94 : fffffa60`012cb6e2 fffffa80`0a693b50 fffff880`10e6e2a0 fffff880`08eff140 : nt!kipagefault+0x119
fffffa60`091cc1e8 fffffa60`012cb6e2 : fffffa80`0a693b50 fffff880`10e6e2a0 fffff880`08eff140 fffff880`10b312c0 : ntfs!memcpy+0x124
fffffa60`091cc1f0 fffffa60`012ca251 : 00000000`00000000 fffffa60`091cc6d0 00000000`00000000 fffffa80`100e2c60 : ntfs!ntfsquerydirectory+0x882
fffffa60`091cc590 fffffa60`012ca15f : fffffa80`0a693b50 00000000`00000000 fffffa80`100e2c60 00000000`00000000 : ntfs!ntfscommondirectorycontrol+0xa1
fffffa60`091cc5d0 fffffa60`00ecae17 : fffffa80`100e2f28 fffffa80`100e2c60 fffffa80`0a693b50 fffffa60`091cc5f8 : ntfs!ntfsfsddirectorycontrol+0x10f
fffffa60`091cc640 fffffa60`00eca0dd : fffffa80`074f9100 fffffa80`09f56950 fffffa80`08373d00 00000000`00000000 : fltmgr!fltplegacyprocessingafterprecallbackscompleted+0x227
fffffa60`091cc6b0 fffff800`01f2d85c : 00000000`00000001 fffffa80`0f193bb0 fffffa80`09f56950 00000000`00000000 : fltmgr!fltpdispatch+0xcd
fffffa60`091cc710 fffff800`01f0a8a0 : ffffffff`80003dc0 ffffffff`80001960 fffffa80`09f56950 fffff880`13b6f020 : nt!iopsynchronousservicetail+0x13c
fffffa60`091cc770 fffffa60`0a2920c1 : ffffffff`80003dc0 fffff880`13b6f000 fffff880`19e6caa0 00000000`00000000 : nt!ntquerydirectoryfile+0xd0
fffffa60`091cc830 fffffa60`0a24e240 : fffff880`13b70020 ffffffff`80001960 fffff880`13b70020 ffffffff`80003dc0 : nfssvr!nfsntquerydirectoryfile+0xb9
fffffa60`091cc8d0 fffffa60`0a24cef1 : fffff880`19e6ca00 fffff880`19e6caa0 00000000`00000000 fffff880`13b6f020 : nfssvr!rememberlastcookieposition+0x10c0
fffffa60`091cc9d0 fffffa60`0a268ad2 : fffffa60`091ccb00 fffffa80`0a674d44 fffff880`08d72000 fffff880`19e6caa0 : nfssvr!getreaddirdata+0x24d
fffffa60`091ccaa0 fffffa60`0a2577fa : fffffa80`0f193bb0 fffff880`08d72000 fffffa60`0a2993c0 fffff880`08d72001 : nfssvr!nfsv3readdir+0x30a
fffffa60`091ccbe0 fffffa60`0a256ae0 : fffffa80`0f9e9920 00000000`00000000 fffffa60`07fd9301 00000000`00000003 : nfssvr!nfsinpacket+0xd46
fffffa60`091cccc0 fffffa60`07fd037b : fffffa80`0a674550 fffffa60`07fd9350 00000000`a7a31a04 fffffa80`0a674550 : nfssvr!nfsinpacket+0x2c
fffffa60`091cccf0 fffff800`01ec3fd3 : 00000000`00000001 00000000`0000000d 00000000`00000000 fffffa80`0a674550 : rpcxdr!rxworkthread+0x3f3
fffffa60`091ccd50 fffff800`01cd9816 : fffffa60`019d8180 fffffa80`0f193bb0 fffffa60`019e1d40 00000000`00000001 : nt!pspsystemthreadstartup+0x57
fffffa60`091ccd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!kistartsystemthread+0x16
stack_command: kb
followup_ip:
nfssvr!nfsntquerydirectoryfile+b9
fffffa60`0a2920c1 3d03010000 cmp eax,103h
symbol_stack_index: b
symbol_name: nfssvr!nfsntquerydirectoryfile+b9
followup_name: machineowner
module_name: nfssvr
image_name: nfssvr.sys
debug_flr_image_timestamp: 47919154
failure_bucket_id: x64_0x50_nfssvr!nfsntquerydirectoryfile+b9
bucket_id: x64_0x50_nfssvr!nfsntquerydirectoryfile+b9
followup: machineowner
---------
now, we're moving rest of data can nfs talking 1 iscsi target, wondering if else has seen , has quick fix. google-ing in world doesn't seem find else particular setup or bsod. main points of interest can see here 2 iscsi targets nfs shares on them, , heavy traffic shares.
help. we'd rather not spend $1500 afp software talk these stupid things.
-nate solberg
owner, nordic pc
hello,
according error message, it seems to crash issue. we may need analyze crash dump file narrow down root cause of bsod issue. not effective debug crash dump file here in forum, if want know root cause , resolution, please contact microsoft customer service , support (css) further help.
http://support.microsoft.com/default.aspx?scid=fh;en-us;offerprophone#faq607
hope issue resolved soon.
this posting provided "as is" no warranties, , confers no rights.
Windows Server > File Services and Storage
Comments
Post a Comment