On Fri, May 11, 2012 at 03:57:24PM -0400, Berke Durak wrote: > There seems to be a 256 MiB lower limit on device size : mkfs.btrfs > refuses to create a filesystem > on a device that is smaller than that. I was experimenting with the mkfs and sizes, and I found that: * mkfs crashes for sizes < 4M * mkfs sizes 4-10M is ok, mount passes, but the fs is unwritable and reports 'no space left', this is due to some hardcoded numbers in the allocator paths * mkfs 11M+ ok, mount ok, fs is writable and an exhaustive write filled the fs to SIZE-4M of data > What are the structural reasons for this limit? Could I reduce this > limit easily with a couple small code changes > or would it take a major effort? It should be possible to push the limit downwards, to like 2MB (current allocation 'cluster' size), or even to 1.44 so btrfs can support floppy disks as well. It's not a major work, but one has to make sure not to break assumptions made on various levels through the allocator(s). david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
