From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] KFS magic size?
Date: Sat, 10 Aug 2002 11:31:55 -0400 [thread overview]
Message-ID: <20020810154250.E22BE19A27@mail.cse.psu.edu> (raw)
the design of kfs is such that the maximum file size is
derived from the block size. i believe the following are
correct for finding the max size from a given block size:
max_in_blocks = 6 + iba + iba*iba
iba = (blocksize - 8)/sizeof(ulong)
multiply by (blocksize -8) to get size in bytes.
so the simplest way to answer your question is "use a
bigger block size" (which, of course, involves reformating
your kfs partition, and makes it a bit less efficient with
space).
my solution to this problem, since i wasn't willing to
reformat my existing partition, was to simply buy enough
ram to hold a CD image.
ア
next reply other threads:[~2002-08-10 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 15:31 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-10 20:54 Geoff Collyer
2002-08-10 10:44 Lucio De Re
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=20020810154250.E22BE19A27@mail.cse.psu.edu \
--to=anothy@cosym.net \
--cc=9fans@cse.psu.edu \
/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).