From owner-cvs-sys  Sun Mar 29 21:53:03 1998
Return-Path: <owner-cvs-sys>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA17015
          for cvs-sys-outgoing; Sun, 29 Mar 1998 21:53:03 -0800 (PST)
          (envelope-from owner-cvs-sys)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16996;
          Sun, 29 Mar 1998 21:52:53 -0800 (PST)
          (envelope-from toor@dyson.iquest.net)
Received: (from root@localhost)
	by dyson.iquest.net (8.8.8/8.8.8) id AAA09044;
	Mon, 30 Mar 1998 00:52:44 -0500 (EST)
	(envelope-from toor)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199803300552.AAA09044@dyson.iquest.net>
Subject: Re: cvs commit: src/sys/kern vfs_syscalls.c
In-Reply-To: <199803300443.UAA05790@rah.star-gate.com> from Amancio Hasty at "Mar 29, 98 08:43:20 pm"
To: hasty@rah.star-gate.com (Amancio Hasty)
Date: Mon, 30 Mar 1998 00:52:44 -0500 (EST)
Cc: dyson@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG,
        cvs-sys@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Hi,
> 
> I managed to crash the system fairly quickly...
> 
> #8  0xf01d66fd in Debugger ()
> #9  0xf0117d9e in panic ()
> #10 0xf01b5e02 in softdep_fsync (vp=0xf3052e20)
>     at ../../ufs/ffs/ffs_softdep_stub.c:3520
> #11 0xf01ba4ec in ffs_fsync (ap=0xf3097db4) at ../../ufs/ffs/ffs_vnops.c:259
> #12 0xf01b069f in ffs_truncate (vp=0xf3052e20, length=0x000000000002c000, 
>     flags=0, cred=0xf06dda80, p=0xf2fc4a80) at vnode_if.h:499
> #13 0xf01be209 in ufs_setattr ()
> #14 0xf01c06e5 in ufs_vnoperate ()
> #15 0xf013b024 in ftruncate ()
> #16 0xf01e15df in syscall ()
> #17 0x2006e671 in ?? ()
> 
> What I do is:
> make world
> tar  -xzf <large-tar-file> something like X
> rm -R large-directory
> 
I think that you have a mixed up system.  The only way that the ffs_fsync
will call softdep_fsync is if you have the MNT_SOFTDEP flag set in your
mount structure.  You shouldn't have that unless you have the softdep
code linked in.  At least that is what it seems like for me.

John