lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-216981-13602@https.bugzilla.kernel.org/>
Date:   Tue, 31 Jan 2023 15:23:32 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 216981] New: Online resize of ext3 file system stuck

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@...nel-bugs.osdl.org
          Reporter: barhatesw09@...il.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ