linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext2 optimal partition size
Date: Tue, 17 May 2005 00:01:56 +0200	[thread overview]
Message-ID: <20050516220156.GA8032@hh.idb.hist.no> (raw)
In-Reply-To: <20050515171437.GC248@DervishD>

On Sun, May 15, 2005 at 07:14:37PM +0200, DervishD wrote:
>     Hi Helge :)
> 
>     That's was just an example, and anyway I can create an ext2/3
> filesystem on a file.

Sure.  It won't be a "partition" though.
>  
> > Just make sure your partition is a whole number of blocks,
> > ext2/ext3 should then be able to utilize the partition fully to the
> > last block.
> 
>     Do that means that metadata (disk structures, block groups
> structs and the like) all fits in block-size chunks???

fs-blocksize chunks, yes.  (i.e. 1K or 4K blocks, not the
512 byte disk blocks.)

I don't know if aøll metadata fits iarbitrary number of block-sized chunks, 
but that cannot matter.  Any "extra" block can surely be utilized for
file data.


>  
> > Using a blocksize equal to the pagesize (i.e. 4096) is usually optimal.
> 
>     Thanks, I'll try it :) My main doubt was if the metadata was
> managed in block-sized chunks, it seems so.

Managing everything in block-sized chunks is a common design in unix filesystems.
It avoids many problems and allows arbitrary filesystem sizes.
Of course some structures will need quite a few blocks, but the number
of blocks will depend on the size of the filesystem and will therefore
always fit in the available space.  (Well, unless you try creating
something silly like a 1-block fs. :-)

Helge Hafting

      reply	other threads:[~2005-05-16 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 16:00 ext2 optimal partition size DervishD
2005-05-15 16:43 ` Helge Hafting
2005-05-15 17:14   ` DervishD
2005-05-16 22:01     ` Helge Hafting [this message]

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=20050516220156.GA8032@hh.idb.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    /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).