linux-ext4 - Re: resize2fs hang at read function

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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 7 Mar 2018 08:45:53 +0100
From:   Lukas Czerner <lczerner@...hat.com>
To:     rong zhao <zhaorbox@...il.com>
Cc:     linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: resize2fs hang at read function

On Wed, Mar 07, 2018 at 09:59:35AM +0800, rong zhao wrote:
> Hi,
> 
> I met a problem on resize2fs ext4 filesystem.
> 
> # Environment
> OS: Redhat 7.4 64bit, Kernel: 3.10.0-693.11.6.el7.x86_64
> 
> Storage: connected 3PAR storage with multipath, create LVM on LUNs
> Filesystem: ext4
> 
> # Problem Description
> 1. create new filesystem, format ext4
> 2. I tried extend LVM, and resize2fs online, it worked indeed
> 3. I copied 27T data to the new filesystem
> 4. Then, I try to extend LVM and resize2fs online again, resize2fs
> hang at read function, the strace records are below:
> ----there are more lines above, do not paste here -------
> lseek(3, 38465727102976, SEEK_SET)      = 38465727102976
> read(3, "\1\0\300/\21\0\300/!\0\300/_\177\200\0\0\0\5\0\0\0\0\0\0\0\0\0\200\0\330\326"...,
> 4096) = 4096
> lseek(3, 38474317037568, SEEK_SET)      = 38474317037568
> read(3, "\1\0\340/\21\0\340/!\0\340/_\177\200\0\0\0\5\0\0\0\0\0\0\0\0\0\200\0000\214"...,
> 4096) = 4096
> 
> --- hang here

Hi,

thanks for report. Could you please fill a bug at bugzilla.redhat.com
and cc me ?

Thanks!
-Lukas

> 
> 5. the filesystem state is clean:
> dumpe2fs /dev/billdb_new/billdb_new | grep state
> dumpe2fs 1.42.9 (28-Dec-2013)
> Filesystem state:         clean
> 
> 6. e2fsck show the filesystem is healthy.
> 
> # Other Information
> 1. I had old filesystem with same issue, to solve this problem, I
> requested new LUNs from storage and create new filesystem
> 2. Copy data from old filesystem to new filesystem
> 3. The old fiesystem and new filesyste can be read/written without problem
> 
> 
> Please give me some suggestions, have googled long time..
> 
> Thanks.