From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 3/3] mkfs.f2fs: don't need to limit MIN_VOLUME SIZE
Date: Mon, 10 Aug 2015 18:23:48 -0700 [thread overview]
Message-ID: <1439256228-8982-3-git-send-email-jaegeuk@kernel.org> (raw)
In-Reply-To: <1439256228-8982-1-git-send-email-jaegeuk@kernel.org>
The minimum volume size is determined while preparing superblock.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
include/f2fs_fs.h | 1 -
lib/libf2fs.c | 7 -------
2 files changed, 8 deletions(-)
diff --git a/include/f2fs_fs.h b/include/f2fs_fs.h
index 59cc0d1..38a774c 100644
--- a/include/f2fs_fs.h
+++ b/include/f2fs_fs.h
@@ -209,7 +209,6 @@ static inline uint64_t bswap_64(uint64_t val)
#define CHECKSUM_OFFSET 4092
/* for mkfs */
-#define F2FS_MIN_VOLUME_SIZE 104857600
#define F2FS_NUMBER_OF_CHECKPOINT_PACK 2
#define DEFAULT_SECTOR_SIZE 512
#define DEFAULT_SECTORS_PER_BLOCK 8
diff --git a/lib/libf2fs.c b/lib/libf2fs.c
index e8f4d47..83d1296 100644
--- a/lib/libf2fs.c
+++ b/lib/libf2fs.c
@@ -499,13 +499,6 @@ int f2fs_get_device_info(struct f2fs_configuration *c)
MSG(0, "Info: sector size = %u\n", c->sector_size);
MSG(0, "Info: total sectors = %"PRIu64" (%"PRIu64" MB)\n",
c->total_sectors, c->total_sectors >> 11);
- if (c->total_sectors <
- (F2FS_MIN_VOLUME_SIZE / c->sector_size)) {
- MSG(0, "Error: Min volume size supported is %d\n",
- F2FS_MIN_VOLUME_SIZE);
- return -1;
- }
-
return 0;
}
--
2.1.1
------------------------------------------------------------------------------
prev parent reply other threads:[~2015-08-11 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 1:23 [PATCH 1/3] mkfs.f2fs: fix wrong documentation Jaegeuk Kim
2015-08-11 1:23 ` [PATCH 2/3] mkfs.f2fs: set overprovision size more precisely Jaegeuk Kim
2015-08-11 1:23 ` Jaegeuk Kim [this message]
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=1439256228-8982-3-git-send-email-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).