Date: Sat, 27 Jul 2013 18:17:20 +0200 From: cpghost <cpghost@cordula.ws> To: freebsd-questions@freebsd.org Subject: Re: Delete a directory, crash the system Message-ID: <51F3F290.9020004@cordula.ws> In-Reply-To: <CAHAXwYCnRDQqgRcvaEE1BmSJYYOidoQzzUoHX_QWdyJzYO3kKw@mail.gmail.com> References: <CAHAXwYDPMrdY-TP-5T1_6M_ot4gY09jo2_Wi_REOmE=%2Bu%2B_QuQ@mail.gmail.com> <CAGwOe2byRc4LVsyxvTJgxNGCbhvOEaeDXjmFJ7DoXThPQe1bcQ@mail.gmail.com> <CAHAXwYCj9AV8ZcDffNNGx-ivL=h_TK9zLQRTPknArX25HSfEag@mail.gmail.com> <CAGwOe2YCDRqHudovDB_Kz9WHppvB8v2L%2B0gkDnWgG88bgZTKSA@mail.gmail.com> <CAHAXwYCnRDQqgRcvaEE1BmSJYYOidoQzzUoHX_QWdyJzYO3kKw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/27/13 14: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 So the system panics in ufs_rmdir(). Maybe the filesystem is corrupt? Have you tried to fsck(8) it manually? Even if the filesystem is corrupt, ufs_rmdir() shouldn't panic(), IMHO, but fail gracefully. Hmmm... -cpghost. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F3F290.9020004>