From owner-freebsd-fs@FreeBSD.ORG Mon Mar 23 14:55:18 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD2C9C12 for ; Mon, 23 Mar 2015 14:55:18 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49A50942 for ; Mon, 23 Mar 2015 14:55:17 +0000 (UTC) X-AuditID: 1209190f-f79d16d000000d3d-4a-55102820993c Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id E2.94.03389.02820155; Mon, 23 Mar 2015 10:50:09 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id t2NEo83i028308; Mon, 23 Mar 2015 10:50:08 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t2NEo5Jf025932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 23 Mar 2015 10:50:07 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t2NEo5In014604; Mon, 23 Mar 2015 10:50:05 -0400 (EDT) Date: Mon, 23 Mar 2015 10:50:05 -0400 (EDT) From: Benjamin Kaduk To: Da Rock Subject: Re: Delete a directory, crash the system In-Reply-To: <551007DD.5020109@herveybayaustralia.com.au> Message-ID: References: <551007DD.5020109@herveybayaustralia.com.au> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixCmqrKuoIRBq0LKLyeLY459sFt9/vmB2 YPKY8Wk+i8frjQvZA5iiuGxSUnMyy1KL9O0SuDL+7t3KXDCTt2LL3kdsDYw3uboYOTgkBEwk 1izK6GLkBDLFJC7cW8/WxcjFISSwmEni2JK37BDORkaJg2ePMkM4h5gklrS+YoJwGhglttw8 zwTSzyKgLbH0xRowm01ARWLmm41sILaIgJHE/CvPmUDWMQtISdxZWwESFhYwlFh3opEFxOYU sJSYsfkLM4jNK+Ao8eHPHkaI+ZOZJS7d3AdWJCqgI7F6/xQWiCJBiZMzn4DZzAJaEsunb2OZ wCg4C0lqFpLUAkamVYyyKblVurmJmTnFqcm6xcmJeXmpRbomermZJXqpKaWbGMGhKsm/g/Hb QaVDjAIcjEo8vBUB/KFCrIllxZW5hxglOZiURHk3qAmECvEl5adUZiQWZ8QXleakFh9ilOBg VhLhrQfJ8aYkVlalFuXDpKQ5WJTEeTf94AsREkhPLEnNTk0tSC2CycpwcChJ8PKrAzUKFqWm p1akZeaUIKSZODhBhvMADf8PNry4IDG3ODMdIn+KUVFKnPcnSEIAJJFRmgfXC0slrxjFgV4R 5tUGWcEDTENw3a+ABjMBDT6XzwcyuCQRISXVwJgr+Upt6RGNTywCiQYbVy4Kq9Ha/bR88uI3 EvW7mlknZR8vvrzZa+WHRQGCMs/zM1r0z4iohAf8vmf9O2zLh0sB2uoXX7sVv1YLPavD7HNF +8G91zVmR78x3eP+4c97XN8hyk8pdsflhdcWT7tcsOL+msNu1tFK7md2fv0hO8Mm/sekHWZR fX1KLMUZiYZazEXFiQDSLSVsAAMAAA== Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 14:55:18 -0000 On Mon, 23 Mar 2015, Da Rock wrote: > On 27/07/2013 22:58, David Noel wrote: > > > Post the stack trace of the core and maybe someone can help you. > > panic: ufs_dirrem: Bad link count 2 on parent > > cpuid = 0 > > KDB: stack backtrace: > > #0 0xffffffff808680fe at kdb_backtrace+0x5e > > #1 0xffffffff80832cb7 at panic+0x187 > > #2 0xffffffff80a700e3 at ufs_rmdir+0x1c3 > > #3 0xffffffff80b7d484 at VOP_RMDIR_APV+0x34 > > #4 0xffffffff808ca32a at kern_rmdirat+0x21a > > #5 0xffffffff80b17cf0 at amd64_syscall+0x450 > > #6 0xffffffff80b03427 at Xfast_syscall+0xf7 > I know this is an old one, but I'm running 10 and I'm still getting this > problem. > > kernel: panic: ufs_dirrem: Bad link count 2 on parent > kernel: cpuid = 1 > kernel: KDB: stack backtrace: > kernel: #0 0xffffffff808e7e90 at kdb_backtrace+0x60 > kernel: #1 0xffffffff808af975 at panic+0x155 > kernel: #2 0xffffffff80afe7d7 at ufs_rmdir+0x1d7 > kernel: #3 0xffffffff80d994f8 at VOP_RMDIR_APV+0x98 > kernel: #4 0xffffffff80952a68 at kern_rmdirat+0x1b8 > kernel: #5 0xffffffff80c8f127 at amd64_syscall+0x357 > kernel: #6 0xffffffff80c7581b at Xfast_syscall+0xfb > kernel: Uptime: 2h36m59s > > Is there a fix or one in the works at all? This also not the first time I've > had this issue crop up since I've been running 10. I am using ssd hdds if that > helps. I don't think there can be a fix in the works until the problem is understood. Given the present data (i.e., lack of other reports), the most likely explanation seems to be that your filesystem is corrupt or your SSD is buggy. A full foreground fsck may be helpful at detecting latent corruption, though. -Ben Kaduk