|
Replies:
7
-
Last Post:
Nov 6, 2009 10:19 AM
by: jayd
|
|
|
Posts:
52
From:
Registered:
10/15/08
|
|
|
|
panic on b119 running vscan/c-icap/clamav
Posted:
Aug 31, 2009 11:33 AM
To: Communities » storage » discuss
|
|
I have experienced two panics on a system running b119. Both cases had very similar status messages and stack dumps.
Aug 31 11:33:05 tx4502 genunix: [ID 783603 kern.notice] Deadlock: cycle in blocking chain
vpanic()
turnstile_block+0x799(0, 0, ffffff065a49a508, fffffffffbc06068, 0, 0)
mutex_vector_enter+0x261(ffffff065a49a508)
rfs4_dbe_lock+0x15(ffffff065a49a508)
recall_all_delegations+0x4d(ffffff065a49a558, 0, 0)
deleg_rd_setattr+0x5d(ffffff00201ec930, ffffff00201eca00, 0, ffffff04e06dbd88, 0)
*vhead_setattr+0xc1(ffffff058bacea00, ffffff00201eca00, 0, ffffff04e06dbd88, 0)
fop_setattr+0xad(ffffff058bacea00, ffffff00201eca00, 0, ffffff04e06dbd88, 0)
vscan_svc_setattr+0x108(3, 1800)
vscan_svc_process_scan_result+0xd7(3)
vscan_svc_scan_result+0x6c(ffffff00201ecc30)
vscan_drv_ioctl+0x18c(fe00000000, 4, db503f94, 102001, ffffff04f4aeb850,
ffffff00201edde4)
cdev_ioctl+0x45(fe00000000, 4, db503f94, 102001, ffffff04f4aeb850,
ffffff00201edde4)
spec_ioctl+0x83(ffffff04feefb300, 4, db503f94, 102001, ffffff04f4aeb850,
ffffff00201edde4)
fop_ioctl+0x7b(ffffff04feefb300, 4, db503f94, 102001, ffffff04f4aeb850,
ffffff00201edde4)
ioctl+0x18e(4, 4, db503f94)
sys_syscall32+0xff()
I am running c-icap with ClamAV libraries.
I have not found anything helpful in searches so I'm hoping I can find help here.
I have the full system core files from both panics so I can send them to the Sun supportfiles repository.
Thank you.
|
|
|
Posts:
129
From:
US
Registered:
10/14/05
|
|
|
|
Re: panic on b119 running vscan/c-icap/clamav
Posted:
Aug 31, 2009 11:56 AM
in response to: jayd
To: Communities » storage » discuss
|
|
> I have experienced two panics on a system running
> b119. Both cases had very similar status messages and
> stack dumps.
>
>
> Aug 31 11:33:05 tx4502 genunix: [ID 783603
> kern.notice] Deadlock: cycle in blocking chain
>
>
> vpanic()
> turnstile_block+0x799(0, 0, ffffff065a49a508,
> fffffffffbc06068, 0, 0)
> mutex_vector_enter+0x261(ffffff065a49a508)
> rfs4_dbe_lock+0x15(ffffff065a49a508)
> recall_all_delegations+0x4d(ffffff065a49a558, 0, 0)
> deleg_rd_setattr+0x5d(ffffff00201ec930,
> ffffff00201eca00, 0, ffffff04e06dbd88, 0)
> *vhead_setattr+0xc1(ffffff058bacea00,
> ffffff00201eca00, 0, ffffff04e06dbd88, 0)
> fop_setattr+0xad(ffffff058bacea00, ffffff00201eca00,
> 0, ffffff04e06dbd88, 0)
> vscan_svc_setattr+0x108(3, 1800)
> vscan_svc_process_scan_result+0xd7(3)
> vscan_svc_scan_result+0x6c(ffffff00201ecc30)
> vscan_drv_ioctl+0x18c(fe00000000, 4, db503f94,
> 102001, ffffff04f4aeb850,
> ffffff00201edde4)
> cdev_ioctl+0x45(fe00000000, 4, db503f94, 102001,
> ffffff04f4aeb850,
> ffffff00201edde4)
> spec_ioctl+0x83(ffffff04feefb300, 4, db503f94,
> 102001, ffffff04f4aeb850,
> ffffff00201edde4)
> fop_ioctl+0x7b(ffffff04feefb300, 4, db503f94, 102001,
> ffffff04f4aeb850,
> ffffff00201edde4)
> ioctl+0x18e(4, 4, db503f94)
> sys_syscall32+0xff()
>
> I am running c-icap with ClamAV libraries.
>
> I have not found anything helpful in searches so I'm
> hoping I can find help here.
>
> I have the full system core files from both panics so
> I can send them to the Sun supportfiles repository.
>
> Thank you.
Please file a bug for tracking purposes.
http://www.opensolaris.org/bug/report.jspa
Category Solaris Kernel Subcategory fs
thanks
chuck
|
|
|
|
|
Posts:
453
From:
US
Registered:
12/21/05
|
|
|
|
Re: [storage-discuss] panic on b119 running vscan/c-icap/clamav
Posted:
Aug 31, 2009 12:16 PM
in response to: cebaker
|
|
Sent from my iPhone
On Aug 31, 2009, at 1:56 PM, Charles Baker
<buildmeister at programmer dot net> wrote:
>> I have experienced two panics on a system running
>> b119. Both cases had very similar status messages and
>> stack dumps.
>>
>>
>> Aug 31 11:33:05 tx4502 genunix: [ID 783603
>> kern.notice] Deadlock: cycle in blocking chain
>>
>>
>> vpanic()
>> turnstile_block+0x799(0, 0, ffffff065a49a508,
>> fffffffffbc06068, 0, 0)
>> mutex_vector_enter+0x261(ffffff065a49a508)
>> rfs4_dbe_lock+0x15(ffffff065a49a508)
>> recall_all_delegations+0x4d(ffffff065a49a558, 0, 0)
>> deleg_rd_setattr+0x5d(ffffff00201ec930,
>> ffffff00201eca00, 0, ffffff04e06dbd88, 0)
>> *vhead_setattr+0xc1(ffffff058bacea00,
>> ffffff00201eca00, 0, ffffff04e06dbd88, 0)
>> fop_setattr+0xad(ffffff058bacea00, ffffff00201eca00,
>> 0, ffffff04e06dbd88, 0)
>> vscan_svc_setattr+0x108(3, 1800)
>> vscan_svc_process_scan_result+0xd7(3)
>> vscan_svc_scan_result+0x6c(ffffff00201ecc30)
>> vscan_drv_ioctl+0x18c(fe00000000, 4, db503f94,
>> 102001, ffffff04f4aeb850,
>> ffffff00201edde4)
>> cdev_ioctl+0x45(fe00000000, 4, db503f94, 102001,
>> ffffff04f4aeb850,
>> ffffff00201edde4)
>> spec_ioctl+0x83(ffffff04feefb300, 4, db503f94,
>> 102001, ffffff04f4aeb850,
>> ffffff00201edde4)
>> fop_ioctl+0x7b(ffffff04feefb300, 4, db503f94, 102001,
>> ffffff04f4aeb850,
>> ffffff00201edde4)
>> ioctl+0x18e(4, 4, db503f94)
>> sys_syscall32+0xff()
>>
>> I am running c-icap with ClamAV libraries.
>>
>> I have not found anything helpful in searches so I'm
>> hoping I can find help here.
>>
>> I have the full system core files from both panics so
>> I can send them to the Sun supportfiles repository.
>>
>> Thank you.
>
> Please file a bug for tracking purposes.
>
> http://www.opensolaris.org/bug/report.jspa
>
> Category Solaris Kernel Subcategory fs
The subcategory would be nfsv4.
>
> thanks
> chuck
> --
> This message posted from opensolaris.org
> _______________________________________________
> storage-discuss mailing list
> storage-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
|
|
|
|
|
Posts:
453
From:
US
Registered:
12/21/05
|
|
|
|
Re: [storage-discuss] panic on b119 running vscan/c-icap/clamav
Posted:
Aug 31, 2009 12:14 PM
in response to: jayd
|
|
Jay,
I'm cc'ing nfs-discuss, I can't remember if this is a known bug or
not, but we did change this code in that timeframe.
Thanks,
Tom
Sent from my iPhone
On Aug 31, 2009, at 1:33 PM, Jay Anderson <Jay dot Anderson00 at gmail dot com>
wrote:
> I have experienced two panics on a system running b119. Both cases
> had very similar status messages and stack dumps.
>
>
> Aug 31 11:33:05 tx4502 genunix: [ID 783603 kern.notice] Deadlock:
> cycle in blocking chain
>
>
> vpanic()
> turnstile_block+0x799(0, 0, ffffff065a49a508, fffffffffbc06068, 0, 0)
> mutex_vector_enter+0x261(ffffff065a49a508)
> rfs4_dbe_lock+0x15(ffffff065a49a508)
> recall_all_delegations+0x4d(ffffff065a49a558, 0, 0)
> deleg_rd_setattr+0x5d(ffffff00201ec930, ffffff00201eca00, 0,
> ffffff04e06dbd88, 0)
> *vhead_setattr+0xc1(ffffff058bacea00, ffffff00201eca00, 0,
> ffffff04e06dbd88, 0)
> fop_setattr+0xad(ffffff058bacea00, ffffff00201eca00, 0,
> ffffff04e06dbd88, 0)
> vscan_svc_setattr+0x108(3, 1800)
> vscan_svc_process_scan_result+0xd7(3)
> vscan_svc_scan_result+0x6c(ffffff00201ecc30)
> vscan_drv_ioctl+0x18c(fe00000000, 4, db503f94, 102001,
> ffffff04f4aeb850,
> ffffff00201edde4)
> cdev_ioctl+0x45(fe00000000, 4, db503f94, 102001, ffffff04f4aeb850,
> ffffff00201edde4)
> spec_ioctl+0x83(ffffff04feefb300, 4, db503f94, 102001,
> ffffff04f4aeb850,
> ffffff00201edde4)
> fop_ioctl+0x7b(ffffff04feefb300, 4, db503f94, 102001,
> ffffff04f4aeb850,
> ffffff00201edde4)
> ioctl+0x18e(4, 4, db503f94)
> sys_syscall32+0xff()
>
> I am running c-icap with ClamAV libraries.
>
> I have not found anything helpful in searches so I'm hoping I can
> find help here.
>
> I have the full system core files from both panics so I can send
> them to the Sun supportfiles repository.
>
> Thank you.
> --
> This message posted from opensolaris.org
> _______________________________________________
> storage-discuss mailing list
> storage-discuss at opensolaris dot org
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
|
|
|
|
|
Posts:
52
From:
Registered:
10/15/08
|
|
|
|
Re: [storage-discuss] panic on b119 running vscan/c-icap/clamav
Posted:
Sep 1, 2009 8:07 AM
in response to: tdh
To: Communities » storage » discuss
|
|
Tom,
You mentioned changing the code in that timeframe. Can you recall, was it at b119? I'm wondering if I tried b114 or b117 whether I might have better luck.
Thank you.
> Jay,
>
> I'm cc'ing nfs-discuss, I can't remember if this is a
> known bug or
> not, but we did change this code in that timeframe.
>
> Thanks,
> Tom
>
>
|
|
|
|
|
Posts:
453
From:
US
Registered:
12/21/05
|
|
|
|
Re: [storage-discuss] [nfs-discuss] panic on b119
running vscan/c-icap/clamav
Posted:
Sep 1, 2009 1:23 PM
in response to: tdh
|
|
Thomas Haynes wrote:
> Jay,
>
>
>>
>> I have the full system core files from both panics so I can send them
>> to the Sun supportfiles repository.
>>
Jay,
Could you please submit the core files?
Thanks,
Tom
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
|
|
|
|
|
Posts:
52
From:
Registered:
10/15/08
|
|
|
|
Re: [storage-discuss] [nfs-discuss] panic on b119 running vscan/c-icap/clamav
Posted:
Oct 13, 2009 12:30 PM
in response to: tdh
To: Communities » storage » discuss
|
|
Bug ID 6877669 was created for this problem on 31 August, and its state is still listed as "1-Dispatched (Default State)."
How long will it be before there is some action on this problem?
Thank you.
|
|
|
|
|
Posts:
52
From:
Registered:
10/15/08
|
|
|
|
Re: [storage-discuss] [nfs-discuss] panic on b119 running vscan/c-icap/clamav
Posted:
Nov 6, 2009 10:19 AM
in response to: tdh
To: Communities » storage » discuss
|
|
Bug ID 6877669 is open for this problem, but there is not much more information about it.
Is there any status to report?
Also, is this problem related to the use of c-icap, or clamav, or is it a problem with VSCAN no matter what anti-virus solution is used?
Will VSCAN work with some different anti-virus system?
Are there any work-arounds to be able to use VSCAN without crashing the server?
Thank you.
|
|
|
|
|
