From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] block-count in mkfs.ocfs2
Date: Fri Jan 25 10:25:11 2008 [thread overview]
Message-ID: <479A295C.4020401@oracle.com> (raw)
In-Reply-To: <20080123095822.GB18317@baloo.nue.novell.com>
No reason other than mke2fs does the same. Using similar params makes
it easier for everyone. Also, we hardly expect anyone to limit the fs
to smaller than the volume size. AFAIK, it's mainly used in testing
(on/off)line fs resize. :)
It's 8k blocks... meaning 32M, for a 4K blocksize. That is fine if all
the user is doing is hosting datafiles as the db rarely grows the
datafiles... meaning no need for journaling.
Goldwyn Rodrigues wrote:
> Hi,
>
> While making changes to mkfs, I noticed blocks-count is taken as a positional argument (value determined by the position in the command line) instead of an optional argument (parsed by getopts such as --block-count). Is there a particular reason for this?
>
> Moreover, you might have to check on the default values of the mkfs_default_profile. Only the journal size in case of "datafiles" filesystem type seem to be having a default value of 8k.
>
> Regards,
>
>
prev parent reply other threads:[~2008-01-25 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 1:58 [Ocfs2-devel] block-count in mkfs.ocfs2 Goldwyn Rodrigues
2008-01-25 10:25 ` Sunil Mushran [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=479A295C.4020401@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.