public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: A L <mail@lechevalier.se>
To: Bill Dietrich <bill@billdietrich.me>, linux-btrfs@vger.kernel.org
Subject: Re: Minimum size of Btrfs volume ?
Date: Sun, 23 Aug 2020 17:08:17 +0200 (GMT+02:00)	[thread overview]
Message-ID: <19d8936.867cd4c.1741bdced46@lechevalier.se> (raw)
In-Reply-To: <1de8d385-4f63-cf84-2a60-9519e55035bc@billdietrich.me>



---- From: Bill Dietrich <bill@billdietrich.me> -- Sent: 2020-08-23 - 15:26 ----

> [Noob here, sorry if I'm doing anything wrong.]
> 
> What is the minimum size of a simple single-disk Btrfs volume,
> and where is it documented ?  I can't find that info.
> 
> I'm told the minimum size is about 109 MB (114294784 bytes).
> True ?  Is there any way to get around that, at mkfs-time ?
> I'd like to use Btrfs inside a VeraCrypt container, and that's
> a fairly big minimum size for that use.
> 
> I'm using Btrfs on Ubuntu GNOME 20.04 desktop.
> 
> Thanks,
> 
> Bill Dietrich
> bill@billdietrich.me
> 
> 
> 
> -- Email domain proudly hosted at https://migadu.com

I'm not sure what minium limit is, but you can try using mkfs.btrfs --mixed. This worked with a 50MiB fs on btrfs-progs 5.7:

# btrfs fi us /mnt/loop
Overall:
    Device size:		  50.00MiB
    Device allocated:		   9.00MiB
    Device unallocated:		  41.00MiB
    Device missing:		     0.00B
    Used:			  32.00KiB
    Free (estimated):		  45.16MiB	(min: 45.16MiB)
    Data ratio:			      1.00
    Metadata ratio:		      1.00
    Global reserve:		 832.00KiB	(used: 0.00B)
    Multiple profiles:		        no

Data+Metadata,single: Size:5.00MiB, Used:28.00KiB (0.55%)
   /dev/loop0	   5.00MiB

System,single: Size:4.00MiB, Used:4.00KiB (0.10%)
   /dev/loop0	   4.00MiB

Unallocated:
   /dev/loop0	  41.00MiB



  reply	other threads:[~2020-08-23 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 13:26 Minimum size of Btrfs volume ? Bill Dietrich
2020-08-23 15:08 ` A L [this message]
2020-08-23 15:13   ` A L
2020-08-24  2:10 ` Chris Murphy

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=19d8936.867cd4c.1741bdced46@lechevalier.se \
    --to=mail@lechevalier.se \
    --cc=bill@billdietrich.me \
    --cc=linux-btrfs@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