From owner-freebsd-current@freebsd.org Sat Oct 27 15:34:25 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 39D1E10C738C for ; Sat, 27 Oct 2018 15:34:25 +0000 (UTC) (envelope-from leandro.lupori@gmail.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 B1F876EB06 for ; Sat, 27 Oct 2018 15:34:24 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 77B0B10C738A; Sat, 27 Oct 2018 15:34:24 +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 3DDDA10C7389 for ; Sat, 27 Oct 2018 15:34:24 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDF406EB05 for ; Sat, 27 Oct 2018 15:34:23 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mail-yw1-xc2e.google.com with SMTP id f192-v6so81042ywh.7 for ; Sat, 27 Oct 2018 08:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cre6/v0tjPxqWFYmxw/juNwzFMTiN9N2EX2r4yUQNU8=; b=pPEg/kfoY61a16DcNpaeV46JDNCmiiwj5SEV65slQp32eyM9HgjYTjHHt6P8Vr47Hc ywf96ZkjhFD08svqT68/tEkNeHwdrWtpzYbKkyvIvR+XOgq21421rWAbrDlNWysCPtCa lE1QH2vPFWhN67JYD+DmkzJjug8KELSPpWjE8AszWfPqel5lgda+oFMbn9FhcJslO2E2 MCN6BvS/gBJcTln96KGI4wtmkyUauUUqOiy5bgizyrp+VHg/C4HtzrFYOt6qIuH9XQ4C PXVl0Hx1aGRbN62jt8kMzE5QZqPCzhI9PkkbvqN3oVIVxd+kavYi4F8QRhWq6kNgpEv8 +SwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cre6/v0tjPxqWFYmxw/juNwzFMTiN9N2EX2r4yUQNU8=; b=ldoV7Pj+XwujO9CInmrj3hT5/0ixEP1ZumKbGqIOyMye4f8LE9MMDK5rkW8vcnmqww MSEVvLznMlkfZgUoGYIJYujW/KYeyBNmzcV/4lko1vPV/aI4TPLNhHh2ub0WxMID4Ten P9f2bzAXdYXtiARiiyb1JchBRL3kMqlUEVLUVxYaEF6NqELYjaH5sLygVaL41+ECV3PB rPllElUrUXkLmpmowyu7sOvOLY4+BKlKI5/QCk0yyetjzG/d3yHohsRPgb+8gVrhUZ93 TrZ/TpbI5CLvbncnDqEeOcDS1fyAUVSzGLn7X7CNuJIk/dmikKFmNa7zQ/yC5uxgP0jw fV3A== X-Gm-Message-State: AGRZ1gL5rDnx6UCbjWVlSOtWzHk/wVRFkhR5kkjceIAPW6w+YbeNR98w TTdpNITPWZFSgbUmByQXtHBGXd8ioha9UIZnvpYxUg== X-Google-Smtp-Source: AJdET5eGoVDN54gVwWvmwLyypqtjaHvPUuxVM3EoRmTq/KH0nj+YY5+Bg/m9lHBtRlLO/XPB8mesOgeNhl59GIYDBR0= X-Received: by 2002:a0d:d2c6:: with SMTP id u189-v6mr7203780ywd.97.1540654462929; Sat, 27 Oct 2018 08:34:22 -0700 (PDT) MIME-Version: 1.0 References: <20181027062357.GE75530@funkthat.com> In-Reply-To: <20181027062357.GE75530@funkthat.com> From: Leandro Date: Sat, 27 Oct 2018 12:34:11 -0300 Message-ID: Subject: Re: UFS panics To: current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Sat, 27 Oct 2018 15:36:27 +0000 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 15:34:25 -0000 Yes, I ran fsck in single user mode and it fixed some errors, one of them was the entry that was causing the panic, that was removed. I just wanted to confirm if panics on UFS were expected if the file system had errors, that Sean and Kirk confirmed, or if it should be investigated. On Sat, Oct 27, 2018 at 3:24 AM John-Mark Gurney wrote: > > 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."