From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216981] New: Online resize of ext3 file system stuck
Date: Tue, 31 Jan 2023 15:23:32 +0000 [thread overview]
Message-ID: <bug-216981-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216981
Bug ID: 216981
Summary: Online resize of ext3 file system stuck
Product: File System
Version: 2.5
Kernel Version: 4.18.0-372.9.1.el8.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: ext3
Assignee: fs_ext3@kernel-bugs.osdl.org
Reporter: barhatesw09@gmail.com
Regression: No
Trying out kubernetes online volume resize feature with ext4 and ext3 file
system.
While the application using the volume tried to resize the volume.
For ext4 file system it worked. But it stuck with ext3 file system.
block level the device got resized.
nvme1n1 259:0 0 642.6G 0 disk
/var/lib/kubelet/pods/6a184d50-341e-4412-9ffb-22574055d8a8/volumes/kubernetes.io~csi/pvc-c200984e-959a-424a-90cf-84a8498a61f0/
But, in dmesg can see these logs, It stuck resizing fs between block 168460288
to 168460800.
[Tue Jan 31 06:40:21 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:40:21 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
[Tue Jan 31 06:42:23 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:42:23 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
[Tue Jan 31 06:44:25 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:44:25 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
[Tue Jan 31 06:46:27 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:46:27 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
[Tue Jan 31 06:48:29 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:48:29 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
[Tue Jan 31 06:50:31 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460800 blocks
[Tue Jan 31 06:50:31 2023] EXT4-fs (nvme1n1): resizing filesystem from
168460288 to 168460288 blocks
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-01-31 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 15:23 bugzilla-daemon [this message]
2023-01-31 15:27 ` [Bug 216981] Online file system resize stuck for ext3 bugzilla-daemon
2023-01-31 16:01 ` bugzilla-daemon
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=bug-216981-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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).