Article View: comp.sys.intel
Article #328Re: INTEL 310
From: Brad Morrison
Date: Tue, 19 Sep 1989 15:49
Date: Tue, 19 Sep 1989 15:49
44 lines
2584 bytes
2584 bytes
In article <4874@uhccux.uhcc.hawaii.edu>, bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) writes: > Got an upgrade to Intel XENIX 3.5 but haven't loaded it yet. Ahh, it's not worth the time & trouble incurred by having to nurse the upgrade along unless you go as far as 3.5.2, where some tools have been expanded. There's also a few new ones, but nothing necessary. > Has anybody ever gotten fixbb to actually fix a bad block and not screw up > some other part of the partition in the process? I think it worked once. We've had several problems with this utility, not the least of which is the fact that the block number is stored as an integer. Imagine what happens when you try to run 'fixbb' to exclude block #98062, for example. Yep, integer overflow, and subsequent exclusion of the wrong block (!). Intel shipped us a replacement which uses a long to store the block number (yep, it's exactly two bytes larger than the original), and informed us that it wasn't being officially shipped to anyone else. Also, 'fixbb' only works on data blocks, so if your bad block is an inode block or a cylinder group header, you're out of luck, unless o you have a CRC error--we've had quite a bit of luck writing a block of nulls atop these. We usually try this before using 'fixbb', because 'fixbb' makes the block forever inaccessible, and necessitates an 'fsck' to fix the DUP block left behind. o you have some way to save/restore the rest of the track, in which case you can re-format the track and put everything else back. > Anyways, please follow-up to comp.sys.intel.ipsc310... In article <806@sdrc.UUCP>, mustard@sdrc.UUCP (Sandy Mustard) writes: : The comp.sys.intel.ipsc310 conference is for discussion of Intel's ipsc : hypercube computer. So I followed up to comp.sys.intel . . . -- Brad Morrison (713) 274-5449 | "Ha, Ha!! I've killed the Devil! Ferranti International Controls Corporation | Now we may all do as we like." uunet!ficc!morrison morrison@ficc.uu.net | --Punch in 'The Dominion of Fancy'
Technical Details
Message-ID:
<6208@ficc.uu.net>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!ficc!morrisonReferences:
<806@sdrc.UUCP> <4874@uhccux.uhcc.hawaii.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!ficc!morrison
From: morrison@ficc.uu.net (Brad Morrison)
Newsgroups: comp.sys.intel
Subject: Re: INTEL 310
Summary: Intel XENIX 3.5 upgrade, fixbb
Keywords: Intel XENIX
Message-ID: <6208@ficc.uu.net>
Date: 19 Sep 89 15:49:45 GMT
References: <806@sdrc.UUCP> <4874@uhccux.uhcc.hawaii.edu>
Distribution: na
Organization: {xe,u}nix Support
Lines: 44