From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] tune2fs: Update overhead when toggling journal feature
Date: Tue, 6 Jul 2021 22:28:38 -0400 [thread overview]
Message-ID: <YOURVgGENH0O+avb@mit.edu> (raw)
In-Reply-To: <20210614212830.20207-1-jack@suse.cz>
On Mon, Jun 14, 2021 at 11:28:30PM +0200, Jan Kara wrote:
> When adding or removing journal from a filesystem, we also need to add /
> remove journal blocks from overhead stored in the superblock. Otherwise
> total number of blocks in the filesystem as reported by statfs(2) need
> not match reality and could lead to odd results like negative number of
> used blocks reported by df(1).
>
> Signed-off-by: Jan Kara <jack@suse.cz>
Applied thanks.
- Ted
prev parent reply other threads:[~2021-07-07 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:28 [PATCH] tune2fs: Update overhead when toggling journal feature Jan Kara
2021-06-14 21:38 ` Andreas Dilger
2021-06-15 7:52 ` Jan Kara
2021-07-07 2:28 ` Theodore Ts'o [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=YOURVgGENH0O+avb@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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 NNTP newsgroup(s).