From: Andreas Dilger <adilger@dilger.ca>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: misc/mke2fs.8.in: Update default inode size description
Date: Wed, 17 Apr 2024 17:07:58 -0600 [thread overview]
Message-ID: <DF4FF2DC-E1A1-4F65-9AED-DDDF177BA180@dilger.ca> (raw)
In-Reply-To: <E1rx4t4-00073d-1e@zenith>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Apr 17, 2024, at 5:48 AM, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:
>
> Since a23b50cd ("mke2fs: warn about missing y2038 support when
> formatting fresh ext4 fs"), the default inode size is 256 bytes
> for all filesystems, including small and floppy, except for the
> Hurd since it currently only supports 128-byte inodes.
>
> Signed-off-by: Pascal Hambourg <pascal@plouf.fr.eu.org>
Looks good.
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> ---
> misc/mke2fs.8.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
> index 30f97bb5..8122e7f7 100644
> --- a/misc/mke2fs.8.in
> +++ b/misc/mke2fs.8.in
> @@ -508,8 +508,8 @@ The default inode size is controlled by the
> file. In the
> .B mke2fs.conf
> file shipped with e2fsprogs, the default inode size is 256 bytes for
> -most file systems, except for small file systems where the inode size
> -will be 128 bytes.
> +all file systems, except for the GNU Hurd since it only supports
> +128-byte inodes.
> .TP
> .B \-j
> Create the file system with an ext3 journal. If the
> --
> 2.39.2
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2024-04-17 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:48 [PATCH] e2fsprogs: misc/mke2fs.8.in: Update default inode size description Pascal Hambourg
2024-04-17 23:07 ` Andreas Dilger [this message]
2024-04-18 14:52 ` Theodore Ts'o
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=DF4FF2DC-E1A1-4F65-9AED-DDDF177BA180@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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 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.