[Bug 216981] New: Online resize of ext3 file system stuck

[Bug 216981] New: Online resize of ext3 file system stuck

[bugzilla-daemon]

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.

[Bug 216981] Online file system resize stuck for ext3

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=216981

Sunil Barhate (barhatesw09@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |trivial
                 CC|                            |barhatesw09@gmail.com
            Summary|Online resize of ext3 file  |Online file system resize
                   |system stuck                |stuck for ext3
           Severity|blocking                    |high

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 216981] Online file system resize stuck for ext3

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=216981

Theodore Tso (tytso@mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
               Tree|Mainline                    |Fedora
                 CC|                            |tytso@mit.edu
         Resolution|---                         |INVALID

--- Comment #1 from Theodore Tso (tytso@mit.edu) ---
This is a bug report for a Red Hat kernel, not mainstream.  It's also as a
result, an absolutely antique, antedeluvian kernel from an upstream kernel. 
Please report this problem to Red Hat, and they will provide support --- not
upstream maintainers.

Alternatively, please try to see if the problem can be replicated on the latest
upstream kernel.  If it can be, feel free to open a new bug and specify an
upstream kernel version in the bug report.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.