From: Alexander Tsvetkov <alexander.tsvetkov@oracle.com>
To: linux-ext4@vger.kernel.org
Subject: bigalloc cluster size
Date: Tue, 21 Apr 2015 16:31:20 +0300 [thread overview]
Message-ID: <55365128.206@oracle.com> (raw)
Hello,
I've noted that valid cluster size is not limited by 256M according to
"mke2fs" manual:
"-C cluster-size
Specify the size of cluster in bytes for filesystems using the bigalloc
feature. Valid cluster-size values are from 2048 to 256M bytes per
cluster."
but actually it's limited by 512M:
"[root@fedora ~]# mkfs.ext4 -O bigalloc -C 512m /dev/sdb
mke2fs 1.43-WIP (29-Mar-2015)
/dev/sdb contains a ext4 file system
created on Tue Apr 21 15:30:27 2015
Proceed anyway? (y,n) yes
Warning: the bigalloc feature is still under development
See https://ext4.wiki.kernel.org/index.php/Bigalloc for more information
Creating filesystem with 2097152 4k blocks and 16 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
[root@fedora ~]# mkfs.ext4 -O bigalloc -C 1024m /dev/sdb
mkfs.ext4: invalid cluster size - 1024m"
(running on vbox Fedora x86_64, latest e2fsprogs, kernel 4.0.0-rc5)
Is it documentation issue?
Thanks,
Alexander Tsvetkov
reply other threads:[~2015-04-21 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55365128.206@oracle.com \
--to=alexander.tsvetkov@oracle.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).