9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt <mattmobile@proweb.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Regarding venti block size
Date: Mon, 16 Feb 2009 11:52:46 +0000	[thread overview]
Message-ID: <4999538E.7070705@proweb.co.uk> (raw)
In-Reply-To: <fd01f51d-65fc-4fb2-ac68-3b30cfa3b631@b16g2000yqb.googlegroups.com>

anooop.anooop@gmail.com wrote:
> Hello All,
>
> I want to store some big files on venti.  size range around 200MB.  Is
> there any way to do this?
>
> This is what I get when I try to store files of size around 300KB :
> "write: input too big: max block size is 57344"
>
> I was wondering may be if increase the block size in arena partition
> this can be done. so I tried to format arena with block size 200M but
> it gave the error below.
>
> "anoop@allatoona:/usr/local/plan9/bin$ venti/fmtarenas -a 3800M -b
> 200M  arenas0. /dev/sda6 &
> [1] 32604
> anoop@allatoona:/usr/local/plan9/bin$ block size too large, max 65536"
>

why are you choosing such a big block size ?

Blocks size and file size are related such that ceil(filesize /
blocksize) = numberofblocks

The larger the blocksize the less likely you are of coalescing any (or
that's what my intuition says). Sure, there's a tradeoff but the
research has been done already and < 64k blocks looks to have been found
appropriate.


If your file is 300Kb and your blocksize 200M then every distinct 300kB
file will occupy 200Mb of actual disk.


Also, 200Mb is not a big file!!









  reply	other threads:[~2009-02-16 11:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 10:25 anooop.anooop
2009-02-16 11:52 ` matt [this message]
2009-02-16 14:16   ` erik quanstrom
2009-02-16 14:20 ` erik quanstrom
2009-02-16 15:56 ` anooop.anooop
2009-02-16 16:17   ` matt
2009-02-16 17:03   ` Russ Cox
2009-02-16 17:11     ` erik quanstrom
2009-02-16 17:17 ` roger peppe
2009-02-16 17:28 ` anooop.anooop
2009-02-16 19:08   ` lucio
2009-02-16 19:24     ` ron minnich
2009-02-17  9:53     ` anooop.anooop
2009-02-17  0:17   ` matt
2009-02-17  9:53 ` anooop.anooop
     [not found] ` <2c60577b-edf1-4f3c-bdd9-d8b1b2859a5b@x38g2000yqj.googlegroups.co>
2009-02-17 13:38   ` erik quanstrom

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=4999538E.7070705@proweb.co.uk \
    --to=mattmobile@proweb.co.uk \
    --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).