Afshin, > How often do you see these crashes? I have been using the CIFS Server to do backups of a NetApp using rsync for volumes with UFS filesystems, and robocopy for volumes with NTFS filesystems. I have not had any crashes while using the server in this way. When I tried to put the server into production use as the primary storage for this data there were multiple crashes of the smb service (I have 14 core.smbd.xxxx files), and several hangs and panics of the server over a period of about six hours.
> It'd probably be quicker if you can get the stack trace from the > crash dumps and send it to me. That way I can quickly find out > > 1. whether it's a cifs problem or not > 2. whether it's a known and/or fixed problem Here are stack traces from two of the crash dumps: vpanic() mutex_panic+0x73(fffffffffb92db50, ffffff067a8494d8) mutex_vector_enter+0x446(ffffff067a8494d8) smb_odir_close+0x23(ffffff067a8494d0) smb_com_trans2_find_first2+0x1ec(ffffff05f2795888, ffffff052999e208) smb_trans2_dispatch+0x195(ffffff05f2795888, ffffff052999e208) smb_com_transaction2+0x17b(ffffff05f2795888) smb_dispatch_request+0x455(ffffff05f2795888) smb_session_worker+0x4a(ffffff05f2795888) taskq_d_thread+0xb1(ffffff04f8d62d30) thread_start+8() vpanic() mutex_panic+0x73(fffffffffb92db50, ffffff0526e4f9a0) mutex_vector_enter+0x446(ffffff0526e4f9a0) smb_odir_close+0x23(ffffff0526e4f998) smb_com_trans2_find_first2+0x1ec(ffffff04faacc008, ffffff04f97d4208) smb_trans2_dispatch+0x195(ffffff04faacc008, ffffff04f97d4208) smb_com_transaction2+0x17b(ffffff04faacc008) smb_dispatch_request+0x455(ffffff04faacc008) smb_session_worker+0x4a(ffffff04faacc008) taskq_d_thread+0xb1(ffffff04f99e1198) thread_start+8() Thank you for taking a look. Please let me know if you need anything else. Jay -- This message posted from opensolaris.org _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
