NetBSD Problem Report #47730

From cheusov@tut.by  Mon Apr  8 10:53:54 2013
Return-Path: <cheusov@tut.by>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id C191D63E5A8
	for <gnats-bugs@gnats.netbsd.org>; Mon,  8 Apr 2013 10:53:53 +0000 (UTC)
Message-Id: <s93fvz1i98u.fsf@cheusov.imb.invention.com>
Date: Mon, 08 Apr 2013 13:53:37 +0300
From: cheusov@tut.by
To: gnats-bugs@gnats.NetBSD.org
Subject: umount -f nfsdir; mount nfsdir => kernel panic (layerfs_statvfs)
X-Send-Pr-Version: 3.95

>Number:         47730
>Category:       kern
>Synopsis:       umount -f nfsdir; mount nfsdir => kernel panic (layerfs_statvfs)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 08 10:55:00 +0000 2013
>Closed-Date:    Thu May 25 04:15:24 +0000 2017
>Last-Modified:  Thu May 25 04:15:24 +0000 2017
>Originator:     Aleksey Cheusov
>Release:        NetBSD 6.0.1_PATCH
>Organization:
>Environment:
System: NetBSD cheusov.imb.invention.com 6.0.1_PATCH NetBSD 6.0.1_PATCH (GENERIC) #4: Wed Mar 13 17:27:04 FET 2013 cheusov@cheusov.imb.invention.com:/srv/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
My 6.0.1_PATCH system paniced immediately after

   umount -f /nfs/dir
   mount /nfs/dir

nfs mount option (if it matters) are tcp,intr.

#0  0xc05afd78 in maybe_dump (howto=260)
    at /srv/src_netbsd6/sys/arch/i386/i386/machdep.c:878
#1  cpu_reboot (howto=260, bootstr=0x0)
    at /srv/src_netbsd6/sys/arch/i386/i386/machdep.c:899
#2  0xc0788d4b in vpanic (fmt=0xc0ba72f2 "trap",
    ap=0xdc2c7a24 "Äz,ÜÄz,Ü\310\240\207\300\b")
    at /srv/src_netbsd6/sys/kern/subr_prf.c:308
#3  0xc0788def in panic (fmt=0xc0ba72f2 "trap")
    at /srv/src_netbsd6/sys/kern/subr_prf.c:205
#4  0xc07cee5b in trap (frame=0xdc2c7ac4)
    at /srv/src_netbsd6/sys/arch/i386/i386/trap.c:396
#5  0xc010cfb8 in ?? ()
#6  0xc0569ee7 in layerfs_statvfs (mp=0xc5d13008, sbp=0xc5654008)
    at /srv/src_netbsd6/sys/miscfs/genfs/layer_vfsops.c:160
#7  0xc087a0cb in VFS_STATVFS (mp=0xc5d13008, a=0xc5654008)
    at /srv/src_netbsd6/sys/kern/vfs_subr.c:1036
#8  0xc087c460 in dostatvfs (mp=0xc5d13008, sp=0xc5654008, l=0xce2d9020, flags=1, root=0)
    at /srv/src_netbsd6/sys/kern/vfs_syscalls.c:1030
#9  0xc087c777 in do_sys_getvfsstat (l=0xce2d9020, sfsp=0xbb9173b0, bufsize=220572,
    flags=1, copyfn=0xc0100820, entry_sz=2228, retval=0xdc2c7d1c)
    at /srv/src_netbsd6/sys/kern/vfs_syscalls.c:1184
#10 0xc087c92b in sys_getvfsstat (l=0xce2d9020, uap=0xdc2c7cf4, retval=0xdc2c7d1c)
    at /srv/src_netbsd6/sys/kern/vfs_syscalls.c:1236
#11 0xc07a18ad in sy_call (rval=0xdc2c7d1c, uap=0xdc2c7cf4, l=0xce2d9020, sy=0xc0c2b9d0)
    at /srv/src_netbsd6/sys/sys/syscallvar.h:61
#12 syscall (frame=0xdc2c7d48) at /srv/src_netbsd6/sys/arch/x86/x86/syscall.c:179
#13 0xc010056d in ?? ()

>How-To-Repeat:
Unsure, but maybe it can be reproducible, see above

>Fix:

Unknown
>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 13 Jul 2014 04:08:07 +0000
State-Changed-Why:
If the filesystem in question was nfs, where does layerfs come into it?
Was the mount point a layerfs? (And if so, what was it layering on top of?)


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Thu, 25 May 2017 04:15:24 +0000
State-Changed-Why:
critical questions unanswered since 2014.
happy to look into this further if someone can either reproduce it or
if the submitter resurfaces and explains what the circumstances were.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.