From: "Rantala, Tommi T. (Nokia - FI/Espoo)" <tommi.t.rantala@nokia.com>
To: "jefflexu@linux.alibaba.com" <jefflexu@linux.alibaba.com>,
"enwlinux@gmail.com" <enwlinux@gmail.com>,
"hsiangkao@linux.alibaba.com" <hsiangkao@linux.alibaba.com>,
"tytso@mit.edu" <tytso@mit.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Inode 2885482 (000000008e814f64): i_reserved_data_blocks (2) not cleared!
Date: Thu, 14 Oct 2021 12:54:14 +0000 [thread overview]
Message-ID: <767ea5bb27e31cc58bea15cd2aec492946679bde.camel@nokia.com> (raw)
Hi,
I'm seeing these i_reserved_data_blocks not cleared! messages when using ext4
with nodelalloc, message added in:
commit 6fed83957f21eff11c8496e9f24253b03d2bc1dc
Author: Jeffle Xu <jefflexu@linux.alibaba.com>
Date: Mon Aug 23 14:13:58 2021 +0800
ext4: fix reserved space counter leakage
I can quickly reproduce in 5.15.0-rc5-00041-g348949d9a444 by doing some
filesystem I/O while toggling delalloc:
while true; do mount -o remount,nodelalloc /; sleep 1; mount -o remount,delalloc /; sleep 1; done &
git clone linux xxx; rm -rf xxx
[ 222.928341] EXT4-fs (vdb1): re-mounted. Opts: delalloc. Quota mode: disabled.
[ 223.932516] EXT4-fs (vdb1): re-mounted. Opts: nodelalloc. Quota mode: disabled.
[ 224.183741] EXT4-fs (vdb1): Inode 2885482 (000000008e814f64): i_reserved_data_blocks (2) not cleared!
[ 224.185064] EXT4-fs (vdb1): Inode 2885478 (00000000862b48ad): i_reserved_data_blocks (2) not cleared!
[ 224.186434] EXT4-fs (vdb1): Inode 2885474 (00000000a20bdd95): i_reserved_data_blocks (7) not cleared!
[ 224.187649] EXT4-fs (vdb1): Inode 2885476 (00000000028005e1): i_reserved_data_blocks (2) not cleared!
[ 224.189016] EXT4-fs (vdb1): Inode 2885475 (0000000025d9617d): i_reserved_data_blocks (2) not cleared!
[ 224.190370] EXT4-fs (vdb1): Inode 2885480 (00000000d0722d90): i_reserved_data_blocks (7) not cleared!
[ 224.191732] EXT4-fs (vdb1): Inode 2885481 (000000009b50d6cb): i_reserved_data_blocks (1) not cleared!
[ 224.193093] EXT4-fs (vdb1): Inode 2885472 (00000000fe907f54): i_reserved_data_blocks (1) not cleared!
[ 227.946984] EXT4-fs: 9213 callbacks suppressed
[ 227.946989] EXT4-fs (vdb1): re-mounted. Opts: nodelalloc. Quota mode: disabled.
-Tommi
next reply other threads:[~2021-10-14 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 12:54 Rantala, Tommi T. (Nokia - FI/Espoo) [this message]
2021-10-14 18:06 ` Inode 2885482 (000000008e814f64): i_reserved_data_blocks (2) not cleared! Gao Xiang
2021-10-14 21:57 ` Theodore Ts'o
2021-10-15 2:49 ` Gao Xiang
2021-10-18 3:54 ` JeffleXu
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=767ea5bb27e31cc58bea15cd2aec492946679bde.camel@nokia.com \
--to=tommi.t.rantala@nokia.com \
--cc=enwlinux@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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