NetBSD Problem Report #52120

From Manuel.Bouyer@lip6.fr  Tue Mar 28 11:43:54 2017
Return-Path: <Manuel.Bouyer@lip6.fr>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 3193C7A20E
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 28 Mar 2017 11:43:54 +0000 (UTC)
Message-Id: <20170328114348.9E7D8A90C@armandeche.soc.lip6.fr>
Date: Tue, 28 Mar 2017 13:43:48 +0200 (MEST)
From: Manuel.Bouyer@lip6.fr
Reply-To: Manuel.Bouyer@lip6.fr
To: gnats-bugs@NetBSD.org
Subject: dump -X can panic the system
X-Send-Pr-Version: 3.95

>Number:         52120
>Category:       kern
>Synopsis:       dump -X can panic the system
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 28 11:45:00 +0000 2017
>Last-Modified:  Tue Mar 28 14:45:01 +0000 2017
>Originator:     Manuel Bouyer
>Release:        NetBSD 6.1_STABLE
>Organization:
>Environment:
System: NetBSD armandeche.soc.lip6.fr 6.1_STABLE NetBSD 6.1_STABLE (ADMIN_DOM0) #9: Thu Mar 23 15:53:15 MET 2017  bouyer@disco.soc.lip6.fr:/home/bouyer/src-6/src/sys/arch/amd64/compile/ADMIN_DOM0 amd64
Architecture: x86_64
Machine: amd64
>Description:
	while running backups with dump -X (via amanda-client), I got this
	panic:
login: panic: itrunc3
cpu0: Begin traceback...
printf_nolog() at netbsd:printf_nolog
ffs_truncate() at netbsd:ffs_truncate+0x1082
ufs_inactive() at netbsd:ufs_inactive+0x2df
VOP_INACTIVE() at netbsd:VOP_INACTIVE+0x54
vrelel() at netbsd:vrelel+0x246
fss_ioctl() at netbsd:fss_ioctl+0x214
fss_close() at netbsd:fss_close+0x9f
spec_close() at netbsd:spec_close+0x110
VOP_CLOSE() at netbsd:VOP_CLOSE+0x51
vn_close() at netbsd:vn_close+0x37
closef() at netbsd:closef+0x54
fd_free() at netbsd:fd_free+0x11d
exit1() at netbsd:exit1+0x11a
sys_exit() at netbsd:sys_exit+0x3e
syscall() at netbsd:syscall+0xc4
cpu0: End traceback...

	It's not the first time I run into panics because of dump -X on the
	netbsd-6 branch, because I periodically forget to rebuild amamda
	without amanda-dump-snap.

>How-To-Repeat:
	run dump -X on a netbsd-6 host. It's not 100% reproductible,
	it's probably dependant on other filesystem activity.
>Fix:
	workaround: don't use -X with dump

>Audit-Trail:
From: "Manuel Bouyer" <bouyer@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/52120 CVS commit: pkgsrc/sysutils
Date: Tue, 28 Mar 2017 12:50:27 +0000

 Module Name:	pkgsrc
 Committed By:	bouyer
 Date:		Tue Mar 28 12:50:26 UTC 2017

 Modified Files:
 	pkgsrc/sysutils/amanda-client: Makefile
 	pkgsrc/sysutils/amanda-common: options.mk

 Log Message:
 Remove amanda-dump-snap from suggested options for NetBSD <= 6.x, as
 a workaround for PR kern/52120.
 Bump amanda-client PKGREVISION


 To generate a diff of this commit:
 cvs rdiff -u -r1.61 -r1.62 pkgsrc/sysutils/amanda-client/Makefile
 cvs rdiff -u -r1.12 -r1.13 pkgsrc/sysutils/amanda-common/options.mk

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

From: "J. Hannken-Illjes" <hannken@eis.cs.tu-bs.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/52120: dump -X can panic the system
Date: Tue, 28 Mar 2017 16:30:23 +0200

 > login: panic: itrunc3
 > cpu0: Begin traceback...
 > printf_nolog() at netbsd:printf_nolog
 > ffs_truncate() at netbsd:ffs_truncate+0x1082

 Could you give some information about the file system
 in question (UFS1/UFS2, WAPBL, Size, ...)

 If you have a core dump, which list of ovp->v_cleanblkhd and
 ovp->v_dirtyblkhd is not empty and what is the value of error
 and allerror?

 --
 J. Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)

From: Manuel Bouyer <manuel.bouyer@lip6.fr>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/52120: dump -X can panic the system
Date: Tue, 28 Mar 2017 16:42:34 +0200

 On Tue, Mar 28, 2017 at 02:35:01PM +0000, J. Hannken-Illjes wrote:
 > The following reply was made to PR kern/52120; it has been noted by GNATS.
 > 
 > From: "J. Hannken-Illjes" <hannken@eis.cs.tu-bs.de>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/52120: dump -X can panic the system
 > Date: Tue, 28 Mar 2017 16:30:23 +0200
 > 
 >  > login: panic: itrunc3
 >  > cpu0: Begin traceback...
 >  > printf_nolog() at netbsd:printf_nolog
 >  > ffs_truncate() at netbsd:ffs_truncate+0x1082
 >  
 >  Could you give some information about the file system
 >  in question (UFS1/UFS2, WAPBL, Size, ...)

 /dev/raid0a       99215      73351      20904  77% /
 /dev/raid0f     5040238     123622    4664606   2% /var
 /dev/raid0e     5040238    1228536    3559692  25% /usr
 /dev/raid0g    10079822    2012288    7563544  21% /home

 no WAPBL, all FFSv1


 >  
 >  If you have a core dump, which list of ovp->v_cleanblkhd and
 >  ovp->v_dirtyblkhd is not empty and what is the value of error
 >  and allerror?

 no core dump, unfortunably

 -- 
 Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
      NetBSD: 26 ans d'experience feront toujours la difference
 --

Home	PR Database Search