From owner-freebsd-current Fri Apr 13 11:18: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4119137B505; Fri, 13 Apr 2001 11:18:00 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3DIHiG77122; Fri, 13 Apr 2001 11:17:44 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010413180506.A4590@1ststep.net> Date: Fri, 13 Apr 2001 11:17:11 -0700 (PDT) From: John Baldwin To: Matthew Schlegel Subject: RE: Problems with -CURRENT Cc: freebsd-current@FreeBSD.org, imp@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Apr-01 Matthew Schlegel wrote: > I have been working on doing an update to the latest -CURRENT (last cvsup for > this upgrade attempt was this morning at about 9:30 PDT) for the last > couple days from : > FreeBSD msops.crossgain.com 5.0-CURRENT FreeBSD 5.0-CURRENT >#0: Wed Jun 28 13:23:44 PDT 2000 > > Right now I can boot into single user mode just fine, but the moment any > process requests an inode on my / partition, I get a kernel panic (page > fault). Right now the world consistantly falls apart in ffs_valloc, but I'm > not sure how to further track it down at this point. > > I am able to get inodes on another partition that was created using the newfs > from the new world, so I'm wondering if there may have been some filesystem > change between June of last year and now that could be causing the problems. > I would appreciate it if someone could point me in the right direction with > this so I can get moved over. Rebuild and install fsck and fsck your filesystems. This is the dirpref stuff most likely biting you. Warner, we should probably add a warning about the dirpref changes to UPDATING since if you fsck a filesystem with the old fsck and new kernel and you overwrite your superblock with the alternate you hose the filesystem resuling in these panics. :( > Stack trace with pointers resolved: > ffs_valloc(0, 8180, 21, vcp_create_desc 8) > ufs_makeinode > ufs_create > ufs_vnoperate > vn_open > open > > The config I am using is attached to this email as well. > > -- > Matthew Schlegel > Give yourself a raise.. Every month: > http://www.ezinfocenter.com/290234.10/FREE > > Encryption Keys: > Type KeyID Created Fingerprint > PGP DSS 0x30AFD26D 1998-08-20 FC89 1E36 353E BDAA FF81 DD30 A7B0 3942 > 30AF D26D -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message