Date: Sat, 14 Apr 2001 13:50:21 +1000 From: "Chris Knight" <chris@aims.com.au> To: <freebsd-current@freebsd.org> Cc: <nitehawk-freebsd@1ststep.net> Subject: RE: Problems with -CURRENT Message-ID: <018b01c0c496$07ed13d0$020aa8c0@aims.private> In-Reply-To: <20010413180506.A4590@1ststep.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Howdy, I thought it was just me that had the problem, but it appears to be the recent dirpref commit. I managed to get a working system by booting to single user, fsck'ing all partitions, then using tunefs to specify the number of files per directory to be greater than zero. I also specified the -A flag to update all superblock entries, as subsequent fsck's errored with first superblock different to first alternate. In summary: fsck all partitions tunefs -A -s <n> all partitions, where n > 0 Hope this helps. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of > Matthew Schlegel > Sent: Saturday, 14 April 2001 4:05 > To: freebsd-current@FreeBSD.ORG > Subject: Problems with -CURRENT > > > 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. > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?018b01c0c496$07ed13d0$020aa8c0>