[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fatal Disk Error urgency [1]

To: Dodds@Riverside.scrc.symbolics.com (Douglas Dodds)
Subject: Fatal Disk Error urgency [1]
From: RWK@FUJI.ILA.Dialnet.Symbolics.COM (Robert W. Kerns)
Date: Mon, 11 Jun 1990 23:43:00 -0400
Cc: pan%athena.pangaro.dialnet.symbolics.com@Riverside.SCRC.Symbolics.COM, customer-reports@Riverside.SCRC.Symbolics.COM, slug%Warbucks.AI.SRI.COM@Riverside.SCRC.Symbolics.COM
In-reply-to: <19900606173316.5.DODDS@SWAN.SCRC.Symbolics.COM>

    Date: Wed, 6 Jun 90 13:33 EDT
    From: Douglas Dodds <Dodds@yukon.scrc.symbolics.com>
    The documentation states, and I agree, that for safety, you should never
    use SI:FIX-FEP-BLOCK or SI:FIX-FEP-FILE on LMFS partitions.  Instead,
    use LMFS:FIX-FILE, which gives you the right pathname-based handles on
    the file, and limits the options to those that are safe for the
    integrity of LMFS partitions.

I don't remember LMFS:FIX-FILE doing anything about adding bad blocks to
the bad blocks file.  Is this an undetected error in my memory?

References:
- Fatal Disk Error urgency [1]
  - From: Dodds@YUKON.SCRC.Symbolics.COM (Douglas Dodds)

Prev by Date: 8.0: Timers; Scheduler Sluggishness; Remote Terminal Status Line
Next by Date: Fatal Disk Error urgency [1]
Previous by thread: Fatal Disk Error urgency [1]
Next by thread: Fatal Disk Error urgency [1]
Index(es):
- Date
- Thread