From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: georgn@somanetworks.com, yodaiken@fsmlabs.com
Cc: Larry McVoy <lm@work.bitmover.com>,
Rob Landley <landley@trommello.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Alright, I give up. What does the "i" in "inode" stand for?
Date: Mon, 22 Jul 2002 08:10:25 -0500 (CDT) [thread overview]
Message-ID: <200207221310.IAA10575@tomcat.admin.navo.hpc.mil> (raw)
In-Reply-To: <1027174927.1702.11.camel@keller>
--------- Received message begins Here ---------
>
>
> --=-JpG6tr/3TXNgZxkgIDvS
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> On Fri, 2002-07-19 at 10:20, yodaiken@fsmlabs.com wrote:
> > On Thu, Jul 18, 2002 at 09:38:57PM -0700, Larry McVoy wrote:
> > > On Thu, Jul 18, 2002 at 06:33:54PM -0400, Rob Landley wrote:
> > > > I've been sitting on this question for years, hoping I'd come across =
> the=20
> > > > answer, and I STILL don't know what the "i" is short for. Somebody h=
> ere has=20
> > > > got to know this. :)
> > >=20
> > > Incore node, I believe. In the original Unix code there was dinode and
> > > inode if I remember correctly, for disk node and incore node.
> >=20
> > So what was that program that was used to fix file system errors called? =
> Started
> > with a "d". I remembered the name up until a few years ago when I said
> > something about fixing filesystems with whatever it was and adb in front =
> of Dave Miller
> > who seemed ready to rush me off to the museum to be exhibited in the pale=
> ology section.
> > Now I'm too old to even remember the name.
>
> Sure you're not thinking of "fsdb"?
No - this was done before fsck - though fsdb did exist - for manual
interaction with the disk structure on a block by block basis.
I believe he is referring to
dcheck - which did directory traversals looking for lost files
Associated with this is:
ncheck - which checked the structure of each file.
The functions of fsck were combined from these two utilities (and added
some more) when bitmap allocation was being added to the file system.
Previous to this, all documentation I've seen for disk structure used a
"free list" chain of unused blocks, where deleted files were put. The
disk free list was used in a LIFO structure to minimise fragmentation, and
preserve the largest free disk segment for new file allocations.
You have to go back to UNIX release 6 or 7 for the last real uses of these
commands before fsck. They did exist in UNIX System V release 2, but only
as "depreciated" utilities not to be used anymore. They did work, but were
superceeded, and did not exist in the next release as I understand. (I had
release 1/2 but did not get 3).
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2002-07-22 13:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 22:33 Rob Landley
2002-07-19 4:38 ` Kelledin
2002-07-19 4:38 ` Larry McVoy
2002-07-19 4:45 ` CaT
2002-07-18 23:34 ` Rob Landley
2002-07-19 5:40 ` Thunder from the hill
2002-07-19 0:21 ` Rob Landley
2002-07-19 12:38 ` Kelledin
2002-07-19 13:09 ` Ryan Cumming
2002-07-19 7:00 ` dalecki
2002-07-19 19:58 ` Måns Rullgård
2002-07-19 20:17 ` Cort Dougan
2002-07-20 1:06 ` Kelsey Hudson
2002-07-26 14:15 ` [OT] Why Stallman says GNU/Linux (was Re: Alright, I give up. What does the "i" in "inode" stand for?) Rob Landley
2002-07-19 14:20 ` Alright, I give up. What does the "i" in "inode" stand for? yodaiken
2002-07-20 14:22 ` Georg Nikodym
2002-07-20 14:31 ` yodaiken
2002-07-22 13:10 ` Jesse Pollard [this message]
2002-07-20 6:01 ` John Kacur
2002-07-19 4:52 ` Albert D. Cahalan
2002-07-22 22:23 ` Joe DiMartino
2002-07-22 22:49 ` Hiten Pandya
2002-07-25 0:24 ` Daniel Mose
2002-07-25 1:16 ` Andrew Rodland
2002-07-25 2:43 ` jw schultz
2002-07-25 3:18 ` Christian Lavoie
2002-07-25 5:30 ` Ross Vandegrift
2002-07-25 11:08 ` Alan Cox
2002-07-25 6:03 ` Thunder from the hill
2002-07-26 8:24 ` jbradford
2002-07-28 9:01 ` Thunder from the hill
2002-08-04 15:11 ` Gert Menke
2002-07-26 12:54 ` Rob Landley
2002-07-25 18:06 ` Kevin Buhr
2002-07-26 23:39 ` Daniel Mose
2002-07-19 5:08 Mohamed Ghouse , Gurgaon
2002-07-19 13:21 Nicholas Berry
2002-07-19 13:32 Jesse Pollard
2002-07-30 20:07 ` Mark H. Wood
[not found] <fa.m2aun2v.khulp2@ifi.uio.no>
2002-07-20 2:20 ` Kevin Buhr
2002-07-20 2:51 Kevin Puetz
2002-07-25 13:54 Jesse Pollard
2002-07-30 20:58 Jesse Pollard
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=200207221310.IAA10575@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=georgn@somanetworks.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=yodaiken@fsmlabs.com \
/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
Powered by JetHome