mkfs bug?

Article View: comp.sys.masscomp

Article #106

#106

From: bcx
Date: Tue, 09 Feb 1988 07:35

17 lines
1182 bytes

I may have detected a possible bug with "mkfs". When mkfs assigns bad
blocks from the raw file system's bad block list, to the bad block
inode 1 in the logical file system, it only assigns individual blocks,
rather than the entire cluster associated with that block.  The kernel,
for efficiency, buffers blocks by reading whole clusters (8 blocks
beginning on a mod 8 boundry).  As a result, blocks from the bad block
file are read, despite their forbidden status. Continually accessing
bad blocks can, at times, cause a disk to slowly degrade and develope
more bad blocks.

Is this a bug or am I completely misunderstanding the way RTU 3.1
operates?

Bryan Costales, Senior Systems Programmer, EEG Systems Laboratory
1855 Folsom St Rm610, San Francisco, Ca 94103 (415) 621-8343
{ihnp4,sun,bellcore,lll-crg,dual,qantel,pyramid}!ptsfa!eeg!bcx

Technical Details

Message-ID: <3327@soma.bcm.tmc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!burl!codas!killer!academ!soma!masscomp-request

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!burl!codas!killer!academ!soma!masscomp-request
From: bcx@eeg.UUCP
Newsgroups: comp.sys.masscomp
Subject: mkfs bug?
Message-ID: <3327@soma.bcm.tmc.edu>
Date: 9 Feb 88 07:35:27 GMT
Sender: masscomp@soma.bcm.tmc.edu
Lines: 17
Approved: masscomp@soma.bcm.tmc.edu
Status: RO