From: Gao Xiang <xiang@kernel.org>
To: Sandeep Dhavale <dhavale@google.com>
Cc: hsiangkao@linux.alibaba.com, kernel-team@android.com,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v3] erofs-utils: dump: print filesystem blocksize
Date: Thu, 18 Apr 2024 12:49:23 +0800 [thread overview]
Message-ID: <ZiCmU7NQikGbnuag@debian> (raw)
In-Reply-To: <20240418000054.2769023-1-dhavale@google.com>
On Wed, Apr 17, 2024 at 05:00:54PM -0700, Sandeep Dhavale wrote:
> mkfs.erofs supports creating filesystem images with different
> blocksizes. Add filesystem blocksize in super block dump so
> its easier to inspect the filesystem.
>
> The field is added after FS magic, so the output now looks like:
>
> Filesystem magic number: 0xE0F5E1E2
> Filesystem blocksize: 65536
> Filesystem blocks: 21
> Filesystem inode metadata start block: 0
> Filesystem shared xattr metadata start block: 0
> Filesystem root nid: 36
> Filesystem lz4_max_distance: 65535
> Filesystem sb_extslots: 0
> Filesystem inode count: 10
> Filesystem created: Wed Apr 17 16:53:10 2024
> Filesystem features: sb_csum mtime 0padding
> Filesystem UUID: e66f6dd1-6882-48c3-9770-fee7c4841a93
>
> Signed-off-by: Sandeep Dhavale <dhavale@google.com>
Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Thanks,
Gao Xiang
prev parent reply other threads:[~2024-04-18 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 0:00 [PATCH v3] erofs-utils: dump: print filesystem blocksize Sandeep Dhavale via Linux-erofs
2024-04-18 4:49 ` Gao Xiang [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=ZiCmU7NQikGbnuag@debian \
--to=xiang@kernel.org \
--cc=dhavale@google.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=kernel-team@android.com \
--cc=linux-erofs@lists.ozlabs.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 read-only IMAP folder(s) and NNTP newsgroup(s).