Skip to contentSkip to conversation

Btrfs-progs: btrfs file system size should be bigger then 256m

PATCH Tomasz Chmielewski 2 participants 3 messages Jan 5, 2009 1 message not in the archive Btrfs file system

lore
Share & tools
lore
#0 lore raw
Quoted 1 line

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?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 7 lines · Kaspar Schleiser

Hey,

Quoted 3 lines · Tomasz Chmielewski
Quoted 1 line

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?

Just 2 MB is enough for mkfs.ext4 to create a valid filesystem.

Also, the patch seems to be incomplete - i.e. what will happen if we try to btrfs-convert a 50MB ext3 filesystem into btrfs?

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#3 lore raw
Quoted 20 lines · Tomasz Chmielewski
Quoted 11 lines · Kaspar Schleiser

Hey,

Quoted 7 lines · Tomasz Chmielewski
Quoted 4 lines

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.

Quoted 7 lines

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