From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Help with Interpretation
Date: Sun, 5 Jan 2020 19:19:56 -0500 [thread overview]
Message-ID: <f6070a52-7f86-a06b-bc9e-8681970e6a39@fjrhome.net> (raw)
In-Reply-To: <4f09726030857bbd2390c3eb6df41e24@gunge.quuxotic.net>
Thanks!
I built the file server using a 32-bit 386 kernel but I think 64-bit
CWFS was used? I will try to figure out somehow which block size was
selected, and that gives me something to work with.
Looks like it is just under 1 GB used if I have the 4K block size, and
just under 2 GB used if I have the 8K block size, of a 64.21 GB worm
partition.
On 1/5/20 10:56 AM, Steven Stallion wrote:
>> I am trying to make sense of these numbers but having some difficulty
>> finding any documentation explaining them.
> Your best bet is to read the source in /sys/src/cmd/cwfs; cwfs is a
> ported version of the original file server, ie. Ken's.
>
>> Can someone either point me to that documentation or walk me through how
>> to interpret this?
> Ken's can be a little terse, but the out put is very meaningful; fsize
> is what you care about in this context. This is the number of blocks
> used by the WORM. Take this number and multiply it by RBUFSIZE to get
> the number of bytes written to disk. Assuming you're using a 64-bit
> fileserver, this will be 8K by default (4K for 32-bit), but this
> depends on the kernel you are using.
>
> HTH,
> Steve
>
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Ta16a4beaa5de93c0-M9d8d0bfc3f8425f269d07178
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
>
next prev parent reply other threads:[~2020-01-06 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 13:25 Frank D. Engel, Jr.
2020-01-05 15:56 ` [9fans] " Steven Stallion
2020-01-06 0:19 ` Frank D. Engel, Jr. [this message]
2020-01-16 17:00 ` Ethan Gardener
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=f6070a52-7f86-a06b-bc9e-8681970e6a39@fjrhome.net \
--to=fde101@fjrhome.net \
--cc=9fans@9fans.net \
/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).