All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
	Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, chandan@mykolab.com
Subject: Re: [PATCH] generic/224: Increase filesystem instance size to 1.5 GiB
Date: Mon, 31 Aug 2015 15:19:22 -0400	[thread overview]
Message-ID: <55E4A8BA.2050908@gmail.com> (raw)
In-Reply-To: <20150831181127.GB7642@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On 2015-08-31 14:11, Theodore Ts'o wrote:
> On Sun, Aug 30, 2015 at 08:16:21PM +0530, Chandan Rajendra wrote:
>> For small filesystem instances (i.e. size <= 1 GiB), mkfs.btrfs fails when
>> "data block size" does not match with the "metadata block size" specified on
>> the mkfs.btrfs command line. This commit increases the size of filesystem
>> instance created so that the test can be executed on subpagesize-blocksize
>> Btrfs instances which have different values for data and metadata blocksizes.
>
> Stupid question --- why isn't this considered a bug in mkfs.btrfs?
> Does btrfs simply not support file systems <= 1 GB?  So if someone has
> a 1GB USB disk or SD card, what's the official advice from the btrfs
> developers?  Use xfs or ext4?
AFAIK, it shouldn't be failing that way, and should automatically switch 
to mixed mode allocation.  A 1G filesystem should work fine for BTRFS, 
but smaller ones will have higher chances of ENOSPC issues (inversely 
proportional to the size of the FS).  I would advise against using BTRFS 
on such a small disk (I avoid using it on anything smaller than 4G 
personally), but I'm not one of the developers, and the fact that I feel 
it isn't a good idea doesn't mean it shouldn't work.



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-08-31 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30 14:46 [PATCH] generic/224: Increase filesystem instance size to 1.5 GiB Chandan Rajendra
2015-08-31 18:11 ` Theodore Ts'o
2015-08-31 19:19   ` Austin S Hemmelgarn [this message]
2015-08-31 21:09     ` Theodore Ts'o
2015-09-01  0:19   ` Chandan Rajendra
2015-09-01  0:38     ` Chandan Rajendra
2015-09-01  2:15     ` Theodore Ts'o
2015-09-01  2:33       ` Chandan Rajendra
2015-09-11  1:38         ` Qu Wenruo
2015-09-11  1:38           ` Qu Wenruo
2015-09-22  5:18           ` Chandan Rajendra

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=55E4A8BA.2050908@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=chandan@mykolab.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.