search for: btrfs_block_reserved_1m_for_sup

...: " /* * We don't want to overwrite 1M at the beginning of device, even though * there is our 1st superblock at 64k. Some possible reasons: * - the first 64k blank is useful for some boot loader/manager * - the first 1M could be scratched by buggy partitioner or somesuch */ #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) " 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I don't know exactly how Syslinux is handling this, but it should be using the whole available space (1MiB instead). -- Paulo Alcantara, C.E.S.A.R Speaking for myself only.

Here are 3 patches to avoid undesired aborts of mkfs.btrfs. These are based on top of Chris''s btrfs-progs.git: git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git Thanks, H.Seto Hidetoshi Seto (3): btrfs-progs: error if device for mkfs is too small btrfs-progs: error if device have no space to make primary chunks btrfs-progs: calculate available

...9;t want to overwrite 1M at the beginning of device, even though > * there is our 1st superblock at 64k. Some possible reasons: > * - the first 64k blank is useful for some boot loader/manager > * - the first 1M could be scratched by buggy partitioner or somesuch > */ > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > " > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > don't know exactly how Syslinux is handling this, but it should be using > the whole available space (1MiB instead). > I have tried to get a formal ruling on the use...

...at the beginning of device, even though > > * there is our 1st superblock at 64k. Some possible reasons: > > * - the first 64k blank is useful for some boot loader/manager > > * - the first 1M could be scratched by buggy partitioner or somesuch > > */ > > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > > " > > > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > > don't know exactly how Syslinux is handling this, but it should be using > > the whole available space (1MiB instead). > > > > I have...

...9;t want to overwrite 1M at the beginning of device, even though > * there is our 1st superblock at 64k. Some possible reasons: > * - the first 64k blank is useful for some boot loader/manager > * - the first 1M could be scratched by buggy partitioner or somesuch > */ > #define BTRFS_BLOCK_RESERVED_1M_FOR_SUPER ((u64)1024 * 1024) > " > > 1MiB seems to be a reasonable size to fit bootsector + LDLINUX.SYS in. I > don't know exactly how Syslinux is handling this, but it should be using > the whole available space (1MiB instead). > > -- > Paulo Alcantara, C.E.S.A.R > S...

On Tue, May 20, 2014 at 12:20 PM, Anatol Pomozov <anatol.pomozov at gmail.com> wrote: > Hi > > On Tue, May 20, 2014 at 9:18 AM, Anatol Pomozov > <anatol.pomozov at gmail.com> wrote: >> Hi >> >> On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On May 20, 2014 12:33 AM, "Anatol Pomozov"