Date: Fri, 5 Dec 2008 20:11:02 +0100 From: Frode Nordahl <frode@nordahl.net> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't Message-ID: <A207B9ED-D388-434A-AF63-C16EAF08DBCB@nordahl.net> In-Reply-To: <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <F88AD2CD-04BA-46E5-93B9-A06558136D31@nordahl.net> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4. des.. 2008, at 13.20, Frode Nordahl wrote:
> On 4. des.. 2008, at 13.07, Kostik Belousov wrote:
>
>> On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote:
>>> Got it!
>>>
>>> panic: dqget: free dquot isn't dq=0xffffff00b3d27000
>>> (kgdb) p/x *(struct dquot *)0xffffff00b3d27000
>>> $1 = {dq_hash = {le_next = 0x0, le_prev = 0xffffff010b9da700},
>>> dq_freelist = {
>>> tqe_next = 0xffffff0055e2de00, tqe_prev = 0xffffffff80b03710},
>>> dq_lock = {
>>> lock_object = {lo_name = 0xffffffff8088c21c, lo_type =
>>> 0xffffffff8088c21c,
>>> lo_flags = 0x1030000, lo_witness_data = {lod_list = {stqe_next
>>> = 0x0},
>>> lod_witness = 0x0}}, mtx_lock = 0x4, mtx_recurse = 0x0},
>>> dq_flags = 0xc, dq_type = 0x0, dq_cnt = 0x0, dq_id = 0x16a37d,
>>> dq_ump = 0xffffff00038e1600, dq_dqb = {dqb_bhardlimit = 0x0,
>>> dqb_bsoftlimit = 0x0, dqb_curblocks = 0x0, dqb_ihardlimit = 0x0,
>>> dqb_isoftlimit = 0x0, dqb_curinodes = 0x1, dqb_btime = 0x493ef2b5,
>>> dqb_itime = 0x493ef2b5}}
>>>
>>> Let me know if I can provide any more information!
>>>
>>> Updated the crashinfo archive you got an URL to yesterday if you
>>> want
>>> to poke around yourself.
>>
>> Please, try the patch below, it should fix a race I see. Quite
>> possible,
>> this is what you tripped over.
>
> Thanks! I will apply the patch and retry the steps that lead to the
> panic!
Good news! I have run through two and have started on the third
iteration of the test that lead to the panic without your patch, and
no panic so far!
I will let it run through the weekend, it prooves usefull as a burn-in-
test as well :-)
Will this patch make it into 7.1-RELEASE?
--
Frode Nordahl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A207B9ED-D388-434A-AF63-C16EAF08DBCB>