From nobody Fri Oct 22 15:21:38 2021 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1DA631804E79 for ; Fri, 22 Oct 2021 15:21:41 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HbSkF08jtz3jhK for ; Fri, 22 Oct 2021 15:21:41 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt1-x832.google.com with SMTP id c28so3769266qtv.11 for ; Fri, 22 Oct 2021 08:21:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=3rDfUGQ163Jtm6t30Fcp+s77Mky11pycd1yaau5FUfk=; b=DytZev44p/CIkQBH3ZtwYc8C8QAWbJjFiCczzBU2FhrIUM/YU1LabPOoo0jiFjNnma QGSDHsWSVgnAUnPpYT+XOv24aF5OedeDob8/dWD0LDNkejExYkk79tbR7IRJlodM8rQ4 ifRDODtFBZ7z9OPPlPwDbyz2AY4BoscQzzd2Hv98u3XbNCy+L+XwPiHEBuopYXamNxSa ZKBh2eC0Nt7kOLvLdIQIxzlg57iwDF26d2VaoLopW9qzKhcS2x3RSh0vOjVj4jUm4CCu Rr9set4ieeLjGO6t1k9iVzt3avcpLu/5kyvR8xrpIj7areseIFgN4d5fA7iyzhxk+eUD vdHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=3rDfUGQ163Jtm6t30Fcp+s77Mky11pycd1yaau5FUfk=; b=L9VgbkIJV4vxTmqXsbQZYtPfJvgz0S6gIxaa+tQXUzKvD1lZ/DBAFHkEW85LWxrlQ5 YHAo+XPcv05p1pFurmpgjXv5OReDsllZ1hi0bMKUINMnLmsF/j9ONtfKmgUWnSJMDZBC KMdm6Ng320+xavF08Z1pzNJKddKspH1CbrlCDDKyjDDH3UeHo4i/BNMukwozSVX1eIrE j3RqYSQon50MlpGMa+HqBr7Vx+3QL7OeBrS57sB7lqg6V85IFvJ28vxcEe233roHeHt0 0z3T4lFjrAZyFMQsIamZx+b/xA8H0DEWejOL9T+UUFblJNo3yAYO9Wwp9DJ3WjPsnLjY pPvQ== X-Gm-Message-State: AOAM533n2uTyzYIEb2v9KvnMRX9vmPeCpYmTNs9dFbKN9qoKB1RCReV3 xZXNYAjTttuXVd4ANlRv2SwueXhomaI= X-Google-Smtp-Source: ABdhPJyBOUWQAnpo6VN2kD4kNyM9P1wFMfqptT2DNG4jChybJ3Q5MOduWAA8SGKuMDE9sKVKGhA2QQ== X-Received: by 2002:a05:622a:346:: with SMTP id r6mr645539qtw.0.1634916100597; Fri, 22 Oct 2021 08:21:40 -0700 (PDT) Received: from nuc ([142.126.186.191]) by smtp.gmail.com with ESMTPSA id l16sm4184560qtp.27.2021.10.22.08.21.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Oct 2021 08:21:40 -0700 (PDT) Date: Fri, 22 Oct 2021 11:21:38 -0400 From: Mark Johnston To: mike tancsa Cc: FreeBSD-STABLE Mailing List Subject: Re: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry Message-ID: References: <9bd8a15d-4800-ee21-2c4b-27c316467f87@sentex.net> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9bd8a15d-4800-ee21-2c4b-27c316467f87@sentex.net> X-Rspamd-Queue-Id: 4HbSkF08jtz3jhK X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, Oct 22, 2021 at 10:36:01AM -0400, mike tancsa wrote: > In one of my VMs, I do a bunch of testing to a nano image on /dev/md0 > and increasingly I am getting a panic on umounting the file system > > The image is just > > truncate -s 5G /tmp/junk.bin > mdconfig -f /tmp/junk.bin > > and then I dd my nano image, mount it, make some configuration changes > and then umount it. > > After cycles of this, unmounts, mounts etc, I get > > > panic: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry > cpuid = 1 > time = 1634912598 > KDB: stack backtrace: > #0 0xffffffff80c77035 at kdb_backtrace+0x65 > #1 0xffffffff80c28a47 at vpanic+0x187 > #2 0xffffffff80c288b3 at panic+0x43 > #3 0xffffffff80f345f7 at ufs_lookup_ino+0xdc7 > #4 0xffffffff80ceae1d at vfs_cache_lookup+0xad > #5 0xffffffff80cf872c at lookup+0x46c > #6 0xffffffff80cf785c at namei+0x26c > #7 0xffffffff80d1c979 at vn_open_cred+0x509 > #8 0xffffffff80d12a3e at kern_openat+0x26e > #9 0xffffffff810b4d3c at amd64_syscall+0x10c > #10 0xffffffff8108bdab at fast_syscall_common+0xf8 > Uptime: 4m48s > > I forced an fsck on reboot, and the file system is clean. I also deleted > /mnt and recreated the directory and still get this issue.  Any idea > what might be causing it or how I can better track it down ? Is the VM image stored on ZFS? Which kernel revision is the host running?