From: Sandeep Dhavale via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: linux-erofs@lists.ozlabs.org
Cc: hsiangkao@linux.alibaba.com, kernel-team@android.com
Subject: [PATCH v3] erofs-utils: dump: print filesystem blocksize
Date: Wed, 17 Apr 2024 17:00:54 -0700 [thread overview]
Message-ID: <20240418000054.2769023-1-dhavale@google.com> (raw)
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>
---
Changes since v2:
- Use %u to print the FS blocksize as we don't expect it to be
very large as suggested by Gao
Changes since v1:
- Moved the field after FS magic as suggested by Gao
dump/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dump/main.c b/dump/main.c
index a89fc6b..dd2c620 100644
--- a/dump/main.c
+++ b/dump/main.c
@@ -633,6 +633,8 @@ static void erofsdump_show_superblock(void)
fprintf(stdout, "Filesystem magic number: 0x%04X\n",
EROFS_SUPER_MAGIC_V1);
+ fprintf(stdout, "Filesystem blocksize: %u\n",
+ erofs_blksiz(&sbi));
fprintf(stdout, "Filesystem blocks: %llu\n",
sbi.total_blocks | 0ULL);
fprintf(stdout, "Filesystem inode metadata start block: %u\n",
--
2.44.0.683.g7961c838ac-goog
next reply other threads:[~2024-04-18 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 0:00 Sandeep Dhavale via Linux-erofs [this message]
2024-04-18 4:49 ` [PATCH v3] erofs-utils: dump: print filesystem blocksize Gao Xiang
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=20240418000054.2769023-1-dhavale@google.com \
--to=linux-erofs@lists.ozlabs.org \
--cc=dhavale@google.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=kernel-team@android.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 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).