From: Paul Winalski <paul.winalski@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] /crp
Date: Wed, 7 Nov 2018 11:43:04 -0500 [thread overview]
Message-ID: <CABH=_VRAL+_fxKerFOV744LJzD8txRT-oXNkrRsOEzCFcFxcWA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1811070844190.78183@aneurin.horsfall.org>
On 11/6/18, Dave Horsfall <dave@horsfall.org> wrote:
>
> Bad blocks? I think I have an article in AUUGN where I proposed that bad
> blocks be assigned (somehow) to a pseudo-file as inode #0 (or -1?); that
> way, the "dump" utility would not see it, and neither would the FS tools
> (but a disk image would, of course).
That is how VMS handles bad blocks. When the system detects them,
they are allocated to file BADBLK.SYS;1 in the volume's root
directory. Of course, these days the disk hardware controller handles
bad blocks. The VMS engineering group once got a bug report
complaining that when a privileged user issued the command "type
dba0:[000000]badblk.sys" there were scads and scads of bad block error
messages.
"Doctor, it hurts when I do this...."
-Paul W.
next prev parent reply other threads:[~2018-11-07 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 17:09 Angelo Papenhoff
2018-11-06 19:22 ` ron
2018-11-06 19:25 ` ron
2018-11-06 21:51 ` Dave Horsfall
2018-11-07 12:18 ` ron
2018-11-07 15:14 ` Clem Cole
2018-11-07 23:40 ` Greg 'groggy' Lehey
2018-11-08 3:04 ` Warner Losh
2018-11-07 16:43 ` Paul Winalski [this message]
2018-11-08 16:55 ` Mary Ann Horton
2018-11-09 5:30 ` Lars Brinkhoff
2018-11-06 23:31 Norman Wilson
2018-11-07 15:08 ` Clem Cole
2018-11-07 23:30 ` Rob Pike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABH=_VRAL+_fxKerFOV744LJzD8txRT-oXNkrRsOEzCFcFxcWA@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).