From: Shen Feng <shen@cn.fujitsu.com>
To: Lee Trager <lt73@cs.drexel.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m
Date: Wed, 31 Dec 2008 17:20:14 +0800 [thread overview]
Message-ID: <495B394E.8070406@cn.fujitsu.com> (raw)
In-Reply-To: <495B2217.3030403@cs.drexel.edu>
My test shows that at least 100M is needed for a btrfs partition.
on 12/31/2008 03:41 PM, Lee Trager wrote:
> 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.
>
> Thanks,
>
> Lee
>
> Shen Feng wrote:
>> According to btrfs_prepare_device, btrfs file sysstem size
>> should be bigger then 256m.
>>
>> If mkfs.btrfs specifies the file system size samaller then
>> that, mkfs.btrfs should report error.
>>
>> Signed-off-by: Shen Feng <shen@cn.fujitsu.com>
>> ---
>> mkfs.c | 4 ++++
>> 1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/mkfs.c b/mkfs.c
>> index be93aaa..447e8d7 100644
>> --- a/mkfs.c
>> +++ b/mkfs.c
>> @@ -377,6 +377,10 @@ int main(int ac, char **av)
>> break;
>> case 'b':
>> block_count = parse_size(optarg);
>> + if (block_count < 256*1024*1024) {
>> + fprintf(stderr, "File system size is too small\n");
>> + exit(1);
>> + }
>> zero_end = 0;
>> break;
>> default:
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Best Regards,
--------------------------------------------------
Shen Feng
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
PHONE: +86-25-86630566-950
COINS: 79955-950
FAX: +86-25-83317685
MAIL: shen@cn.fujitsu.com
-------------------------------------------------
This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited. If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed.
next prev parent reply other threads:[~2008-12-31 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 6:12 [PATCH] Btrfs-progs: btrfs file system size should be bigger then 256m Shen Feng
2008-12-31 7:41 ` Lee Trager
2008-12-31 9:20 ` Shen Feng [this message]
2008-12-31 17:49 ` Zach Brown
2009-01-05 1:23 ` Shen Feng
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 14:44 Tomasz Chmielewski
[not found] ` <49622525.80001@schleiser.de>
2009-01-05 15:49 ` Tomasz Chmielewski
2009-01-05 16:39 ` Chris Mason
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=495B394E.8070406@cn.fujitsu.com \
--to=shen@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
/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