The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] mkfs somewhere else?
Date: Sun,  8 Feb 2015 15:20:35 -0500 (EST)	[thread overview]
Message-ID: <20150208202035.E3D391DE414@lignose.oclsc.org> (raw)

Dave Horsfall:

  I also wrote a paper on a "bad block" system, where something like inum
  "-1" contained the list of bad sectors, but never saw it through.

====

During the file system change from V6 to V7, the i-number of
the root changed from 1 to 2, and i-node 1 became unused.
At least some versions of the documentation (I am too harried
to look it up at the moment) claimed i-node 1 was reserved
for holding bad blocks, to keep them out of the free list,
but that the whole thing was unimplemented.

I vaguely remember implementing that at some point: writing
a tool to add named sectors to i-node 1.  Other tools needed
fixing too, though: dump, I think, still treated i-node 1
as an ordinary file, and tried to dump the contents of
all the bad blocks, more or less defeating the purpose.

I left all that behind when I moved to systems with MSCP disks,
having written my own driver code that implemented DEC's
intended port/class driver split, en passant learning how
to inform the disk itself of a bad block so it would hide it
from the host.

I'd write more but I need to go down to the basement and look
at one of my modern* 3TB SATA disks, which is misbehaving
even though modern disks are supposed to be so much better ...

Norman Wilson
Toronto ON

* Not packaged in brass-bound leather like we had in the old days.
You can't get the wood, you know.



             reply	other threads:[~2015-02-08 20:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 20:20 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-08 20:12 Norman Wilson
2015-02-08 20:10 Norman Wilson
2015-02-12 15:29 ` Dave Horsfall
2015-02-12 15:50   ` cowan
2015-02-12 19:18     ` random832
2015-02-08  6:22 Jacob Ritorto
2015-02-08  6:36 ` Dave Horsfall
2015-02-08  7:03   ` Jacob Ritorto
2015-02-08  7:15     ` Jacob Ritorto
2015-02-08 17:34       ` Dave Horsfall
2015-02-08 18:52         ` Jacob Ritorto

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=20150208202035.E3D391DE414@lignose.oclsc.org \
    --to=norman@oclsc.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).