From: random832@fastmail.com (Random832)
Subject: [TUHS] Unix v6 File System information
Date: Sun, 21 Feb 2016 13:36:19 -0500 [thread overview]
Message-ID: <1456079779.724937.527519010.4FC5154D@webmail.messagingengine.com> (raw)
In-Reply-To: <20160221175008.13FB518C0ED@mercury.lcs.mit.edu>
On Sun, Feb 21, 2016, at 12:50, Noel Chiappa wrote:
> > From: Random832
>
> > They're 24 bits, aren't they?
>
> Not according to the source:
>
> typedef long daddr_t;
>
> daddr_t s_fsize; /* size in blocks of entire volume */
> short s_nfree; /* number of addresses in s_free */
> daddr_t s_free[NICFREE];/* free block list */
>
> (from param.h and filsys.h respectively).
That's the superblock. Look in ino.h.
/*
* the 40 address bytes:
* 39 used; 13 addresses
* of 3 bytes each.
*/
Which means you can't actually have a filesystem of more than 2^24-1
blocks.
next prev parent reply other threads:[~2016-02-21 18:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 17:50 Noel Chiappa
2016-02-21 18:36 ` Random832 [this message]
2016-02-22 13:10 ` 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 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
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
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=1456079779.724937.527519010.4FC5154D@webmail.messagingengine.com \
--to=random832@fastmail.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;
as well as URLs for NNTP newsgroup(s).