From owner-freebsd-questions  Thu Jul 30 16:03:39 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA13770
          for freebsd-questions-outgoing; Thu, 30 Jul 1998 16:03:39 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13760
          for <freebsd-questions@FreeBSD.ORG>; Thu, 30 Jul 1998 16:03:34 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id QAA21899;
          Thu, 30 Jul 1998 16:03:09 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 30 Jul 1998 16:03:09 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Rob McIntyre <rob@perihelion.co.uk>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: fsck errors: partially allocated inodes
In-Reply-To: <199807300838.JAA28894@betty.perihelion.co.uk>
Message-ID: <Pine.BSF.4.00.9807301602280.17630-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Thu, 30 Jul 1998, Rob McIntyre wrote:

> To my potential saviour,
> 
> I am trying to debug a version of newfs that has been ported to the 
> Helios operating system. 
> After running  newfs on the ide device, I get spurious errors including 
> the following:
> 
> partially allocated inode = 0x68
> 
> unknown file type inode = 0x9a
> 
> in blkerror
> 
> The errors seem to come in blocks of partially allocated inodes 
> followed by an arbitrary amount of unknown file types messages. 
> 
> I have experimented useing various disk layouts and still the errors 
> occcur in the same place on the ide disk.

Would't that suggest to you that there's a problem with the disk itself?

> I would be grateful for any advice on the true meaning of these errors 
> and for debugging newfs and fsck which is not a very pleasent task 
> with 214MB devices.

If you think it's unpleasant with 214MB, try an 8 gig array.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message