From owner-freebsd-current@freebsd.org Sat Oct 27 06:24:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E3610DBB11 for ; Sat, 27 Oct 2018 06:24:07 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D8342806EA for ; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9B21E10DBB10; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89E5510DBB0F for ; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE30A806E6 for ; Sat, 27 Oct 2018 06:24:05 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w9R6NvVj083980 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Oct 2018 23:23:58 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w9R6Nv3c083979; Fri, 26 Oct 2018 23:23:57 -0700 (PDT) (envelope-from jmg) Date: Fri, 26 Oct 2018 23:23:57 -0700 From: John-Mark Gurney To: Leandro Cc: current@freebsd.org Subject: Re: UFS panics Message-ID: <20181027062357.GE75530@funkthat.com> Mail-Followup-To: Leandro , current@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Fri, 26 Oct 2018 23:23:58 -0700 (PDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2018 06:24:07 -0000 Leandro wrote this message on Wed, Oct 24, 2018 at 12:22 -0300: > I'm seeing a kernel panic when trying to move a specific file. > > panic: Bad effnlink fip 0xc0000004a2c69a00, fdp 0xc000000497093be0, > tdp 0xc0000004be6295a0 > cpuid = 72 > time = 1540283798 > KDB: stack backtrace: > 0xe0000000adb8dcc0: at .kdb_backtrace+0x5c > 0xe0000000adb8ddf0: at .vpanic+0x1b4 > 0xe0000000adb8deb0: at .panic+0x38 > 0xe0000000adb8df40: at .ufs_readdir+0x2f24 > 0xe0000000adb8e1b0: at .VOP_RENAME_APV+0x190 > 0xe0000000adb8e240: at .kern_renameat+0x3c0 > 0xe0000000adb8e540: at .sys_rename+0x2c > 0xe0000000adb8e5c0: at .trap+0x65c > 0xe0000000adb8e780: at .powerpc_interrupt+0x290 > 0xe0000000adb8e820: user SC trap by 0x81010b7b8: srr1=0x900000000000f032 > r1=0x3fffffffffffc490 cr=0x34000028 xer=0x20000000 > ctr=0x81010b7b0 r2=0x8102c5950 > KDB: enter: panic > > Using 'ls' or 'rm' on the file gives a "Bad file descriptor" error. > Using 'cat', I get another panic, but now during open. > Everything indicates that the file system is in an inconsistent state. > > Therefore, I would just like to ask the following: is it expected for > kernel panics to happen when there are errors in the file system? Have you unmounted the file system, and tried to do a fsck on it? That you're getting a bad file descriptor sounds like it might be a directory entry pointing to a bad inode. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."