From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:20:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5714D106564A for ; Thu, 4 Dec 2008 12:20:38 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id 148BD8FC1E for ; Thu, 4 Dec 2008 12:20:38 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from ws24.ns5.powertech.no (ws24.ns5.powertech.no [195.159.6.24]) by smtp3.powertech.no (Postfix) with ESMTP id C7371C6082; Thu, 4 Dec 2008 13:20:36 +0100 (CET) Message-Id: <576BB990-78D8-4CE8-9660-55EB989EE3BA@nordahl.net> From: Frode Nordahl To: Kostik Belousov In-Reply-To: <20081204120736.GC2038@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Thu, 4 Dec 2008 13:20:19 +0100 References: <3B675385-956D-4A26-8E09-E338DF7D7244@nordahl.net> <20081203173939.GA2401@deviant.kiev.zoral.com.ua> <20081203194348.GB2401@deviant.kiev.zoral.com.ua> <8A6A8FA5-07A6-4A12-B9AD-6E77E534CED7@nordahl.net> <20081204120736.GC2038@deviant.kiev.zoral.com.ua> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.1-PRERELEASE-p1, panic: dqget: free dquot isn't X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 12:20:38 -0000 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! > On the other hand, dq_id == 1483645 looks very suspicious. Do you > actually have such large uid in the system ? Could it be that you have > file on fs owned by such uid ? Yes. The system has uids ranging from 0 to 3152039 :-) -- Frode Nordahl