public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Kaspar Schleiser <kaspar@schleiser.de>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
Date: Mon, 05 Jan 2009 11:39:36 -0500	[thread overview]
Message-ID: <1231173576.4290.138.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49622BFC.7040105@wpkg.org>

On Mon, 2009-01-05 at 16:49 +0100, Tomasz Chmielewski wrote:
> Kaspar Schleiser schrieb:
> > Hey,
> > 
> > Tomasz Chmielewski wrote:
> >>> This has been bothering me for some time. Why does btrfs need to have 
> >>> a disk greater then 256M? I could see a much smaller limit, say 16M 
> >>> but why so much? The file system itself does not need that much space 
> >>> for its own use.
> >>
> >> In other words, 256M limit rather disqualifies btrfs as a filesystem 
> >> i.e. for /boot, doesn't it?
> > When 1G is just 10c?
> 
> Maybe when talking about traditional HDDs.
> Anything flash-based is still $2-$5 per 1G.
> 
> I have some SAN devices booting off 512MB or 1G builtin flash. Having 
> 256M for /boot there would not leave much more space for the operating 
> system.
> 
> Why separate /boot? It's still needed for encrypted rootfs or more fancy 
> partitioning (like / on LVM, at least until GRUB2 is stable and is 
> shipped by major distros).
> 
> 
> Seriously, what are the technical reasons that btrfs needs so much space 
> for a minimal filesystem?

This is mostly to help prevent crashes on enospc.  As we fixup the
kernel code, the 256MB limit will go away.

-chris



  reply	other threads:[~2009-01-05 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 14:44 [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m Tomasz Chmielewski
     [not found] ` <49622525.80001@schleiser.de>
2009-01-05 15:49   ` Tomasz Chmielewski
2009-01-05 16:39     ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-31  6:12 Shen Feng
2008-12-31  7:41 ` Lee Trager
2008-12-31  9:20   ` Shen Feng
2008-12-31 17:49 ` Zach Brown
2009-01-05  1:23   ` Shen Feng

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=1231173576.4290.138.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=kaspar@schleiser.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.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