From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Unix v6 File System information
Date: Mon, 22 Feb 2016 12:58:35 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1602221223300.79948@aneurin.horsfall.org> (raw)
In-Reply-To: <20160221172101.GH2332@mercury.ccil.org>
On Sun, 21 Feb 2016, John Cowan wrote:
> The RSX-11 file system, later known as ODS-1, was similar in this
> respect: the root directory contained entries for the bad-block file
> (BADBLK.SYS), the inode-file-equivalent (INDEXF.SYS) and even itself
> (000000.DIR).
Ah, but my idea (never implemented, because disk drives got beyond ye olde
RK-05) was that it never appeared as a directory entry.
Thus, Shell utilities would never see those blocks, and "dump" would never
see them either, because it "knew" that inodes started at 1... The only
way you would see them was via a raw disk copy.
But, as I said, times moved on from the RK-05 (and the RP-04, and other
air-exposed packs), thus my idea was dead.
Mind you, these "IBM PC" thingie drives are pretty awful at times :-)
And as for SSDs, don't ask, because they won't tell you about bad blocks;
they are merely quietly remapped on the side[*].
[*]
I've been doing a fair bit of reading on these things. Did you know that,
for example, up to half the available silicon is dedicated towards the bad
sectors that always crop up? And the thing won't even tell you when it
remaps a bad sector[#]? It's because, amongst other things, that what you
and I think of as a "block" is actually a huge chunk, so one bad bit in a
cell could cause up to something like 64KB to be remapped.
In other words, if you knew how SSDs worked, you wouldn't stake your balls
on them; they're just a large USB stick (and we know how cheaply they're
made).
[#]
Because the proprietary on-board controller is saying "Everything's OK,
boss!" whilst madly emptying a swampful of alligators.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-02-22 1:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 11:44 Noel Chiappa
2016-02-21 13:34 ` Dave Horsfall
2016-02-21 15:21 ` Will Senn
2016-02-21 17:21 ` John Cowan
2016-02-22 1:58 ` Dave Horsfall [this message]
2016-02-22 2:32 ` Lyndon Nerenberg
2016-02-22 12:30 ` Tony Finch
2016-02-21 15:36 ` Will Senn
2016-02-21 20:24 ` Warren Toomey
2016-02-21 17:31 ` Random832
2016-02-21 17:36 ` ron
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 1:54 Norman Wilson
2016-02-22 3:02 ` Larry McVoy
2016-02-21 21:51 Noel Chiappa
2016-02-21 18:27 Noel Chiappa
2016-02-21 18:59 ` Clem Cole
2016-02-21 19:31 ` arnold
2016-02-21 20:45 ` Will Senn
2016-02-21 21:06 ` Clem Cole
2016-02-21 21:05 ` Will Senn
2016-02-21 21:21 ` Clem Cole
2016-02-22 2:20 ` Warren Toomey
[not found] ` <2D41A491-40CD-41DB-B3BA-0ACBD831E2C7@gmail.com>
2016-02-22 7:27 ` Warren Toomey
2016-02-21 17:50 Noel Chiappa
2016-02-21 18:36 ` Random832
2016-02-22 13:10 ` ron
2016-02-21 9:45 Will Senn
2016-02-21 10:01 ` Dave Horsfall
2016-03-04 19:10 ` Jacob Ritorto
2016-03-10 8:51 ` Dave Horsfall
2016-03-10 9:31 ` SPC
2016-02-21 10:27 ` arnold
2016-02-21 12:29 ` Dave Horsfall
2016-02-21 13:54 ` arnold
2016-02-21 14:40 ` Clement T. Cole
2016-03-04 9:27 ` Dave Horsfall
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=alpine.BSF.2.11.1602221223300.79948@aneurin.horsfall.org \
--to=dave@horsfall.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).