From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 38A44C433F5 for ; Tue, 15 Mar 2022 00:31:03 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nTv5b-00046z-Ap; Tue, 15 Mar 2022 00:31:01 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nTv5a-00046f-FY for linux-f2fs-devel@lists.sourceforge.net; Tue, 15 Mar 2022 00:31:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=SwXyqJgfjqYv89yjQWaX/2aHbMe4gu8hPHA69oG/PWY=; b=kHBVC8QlWUw5+JE18gyWfOGwk1 /78Wnpl0rMpVGsGnv+QBh/LtZv18LLTJBvDy9ujFiX3pyzEweRzgcXQNDAgqSjn/ugfUfBbVXF2/F RX1VEL+EwZh9C7qRWThAyHVQZ5rvtFl5mS0C3x7cE/sEY7G/0Il3/554OiBHLSe6s0gM=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To :From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=SwXyqJgfjqYv89yjQWaX/2aHbMe4gu8hPHA69oG/PWY=; b=IlCGBl54zL/hsAraMVqze8vLt6 31c/xw4a+5BMQ6E5LtJSIa8dePSIzRl1cYLYzhMwr3Z+3O/IlZr+2AljQuStB58lLA+TIbvh2ZME+ Bt1M3aSI7pdxNOQwcl+4mlh+EpemHLNv+t1tAlCyQnLuxi4xfmh460a1Tt6GBmtae8MM=; Received: from dfw.source.kernel.org ([139.178.84.217]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.94.2) id 1nTv5X-0006YY-07 for linux-f2fs-devel@lists.sourceforge.net; Tue, 15 Mar 2022 00:31:00 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8699261514; Tue, 15 Mar 2022 00:30:45 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DB93FC340E9; Tue, 15 Mar 2022 00:30:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1647304245; bh=bLe/QVFp8radYLp9AdKDfy4+4qML8MrMtuLOt+CAuO0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ot9TTECR6aYWpF4uWO+D4wa0+GWnsvET718fhszAsM780hSUkl5XiEs5HCp8d22rZ Zd5FsPXQw1GlHy2fSysa4TCfWR14Ie6d2yr5QLHj9vwpwLRNBCbEqQbgsHPy71tfjk +iYP8aBFLrL0gdzoihGv+xrXUH+8Zq2ExdliChbfP863Le0CTN4Fg1l9DaorDImrXW +oB+sXBlm93YiNPkTanNGFITJFyx3SuBJnXBXhF4uuBkvUGFGuZ1dalswkJz6mxlri UnRgYhMRpnANEs3N+tYR640Pl5y7DAH2zZic5Xdwqtfz3g6Jk61ZwFaWhedOJxnJ1I k1kk1E7zlOYow== Date: Mon, 14 Mar 2022 17:30:43 -0700 From: Jaegeuk Kim To: Juhyung Park Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Headers-End: 1nTv5X-0006YY-07 Subject: Re: [f2fs-dev] EIO returned when reading files from R/O, compressed f2fs image X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net Juhyung, On 03/14, Juhyung Park wrote: > Hi. > > We have a production server storing some Android firmwares over a ZFS > file-system, and we noticed some issues when extracting firmware files > that use f2fs for Android system partitions. > > This is a proprietary environment, so I cannot disclose every detail, > so I hope you understand. I'll try to elaborate as much as I can. > > The server is running Ubuntu 20.04 with Linux v5.15 (recently upgraded > from v5.13 after noticing RO feature added on v5.14 being required). > We have a set of scripts extracting Android firmware files. The input > is typically the OTA zip file and after going through the script, it > extracts every file and binary image from a given file. > > So that includes extracting super (dynamic partition), ext4 system > partitions with dedup enabled, and now, f2fs system partitions with RO > and compression enabled. > > Our script never had to deal with f2fs before as we only started > seeing f2fs system partitions with recently released devices. > > This is the f2fs mount flag after mounting with `mount -o ro > system.raw /some/dir`: > ro,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=2,alloc_mode=reuse,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,discard_unit=block > > There are *a lot* of files in Android firmware these days, so we try > to parallelize parts when we can. > > This is a snippet of the script: > ``` > #!/bin/bash > <...> > RSYNC="rsync -ahAXx --inplace --numeric-ids" > <...> > for val in system vendor product odm; do > if ! ls images/$val.raw > /dev/null 2>&1; then continue; fi > > mkdir -p fs > cd fs > > mkdir -p $val.mount tmp_$val > mount -o ro ../images/$val.raw $val.mount > > $RSYNC $val.mount/ "$DEST_PWD/fs/$val/" & > echo $! > $val.pid > disown > > cd $val.mount > find . -type d -exec mkdir -p "$DEST_PWD/strings/$val/"{} \; > find . -type d -exec mkdir -p "../tmp_$val/"{} \; > > while read file; do strings "$file" > "$DEST_PWD/strings/$val/$file" > & done < <(find . -type f | grep -v '\.apk\|\.jar\|\.zip') > wait > > <...> > > cd ../ > rm -rf tmp_$val > cd ../ > done > > wait > <...> > for val in system vendor product odm; do > if ! ls images/$val.raw > /dev/null 2>&1; then continue; fi > tail --pid=$(cat fs/$val.pid) -f /dev/null > umount fs/$val.mount > rmdir fs/$val.mount > rm -f images/$val.img images/$val.raw 2>/dev/null > done > ``` > > The offending part is: > ``` > $RSYNC $val.mount/ "$DEST_PWD/fs/$val/" & > find . -type d -exec mkdir -p "$DEST_PWD/strings/$val/"{} \; > find . -type d -exec mkdir -p "../tmp_$val/"{} \; > while read file; do strings "$file" > "$DEST_PWD/strings/$val/$file" > & done < <(find . -type f | grep -v '\.apk\|\.jar\|\.zip') > wait > ``` > > When that part is reached, the script forks thousands of new processes > and starts reading from f2fs. (We simply decided to rely on Linux's > task scheduler and didn't bother to limit the number of > sub-processes.) > > I am able to reliably cause f2fs to return EIO on some files: > cp: error reading './system/priv-app/some_apk_1/some_apk_1.apk': > Input/output error > cp: error reading './system/priv-app/some_apk_2/some_apk_2.apk': > Input/output error > cp: error reading './system/priv-app/some_apk_3/some_apk_3.apk': > Input/output error > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_1/some_apk_1.apk": > Input/output error (5) > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_2/some_apk_2.apk": > Input/output error (5) > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_3/some_apk_3.apk": > Input/output error (5) > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_1/some_apk_1.apk": > Input/output error (5) > ERROR: system/priv-app/some_apk_1/some_apk_1.apk failed verification > -- update retained. > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_2/some_apk_2.apk": > Input/output error (5) > ERROR: system/priv-app/some_apk_2/some_apk_2.apk failed verification > -- update retained. > rsync: [sender] read errors mapping > "/ssd/some_firmware.zip/fs/system.mount/system/priv-app/some_apk_3/some_apk_3.apk": > Input/output error (5) > ERROR: system/priv-app/some_apk_3/some_apk_3.apk failed verification > -- update retained. > rsync error: some files/attrs were not transferred (see previous > errors) (code 23) at main.c(1333) [sender=v3.2.3-45-ga28c4558] > > The dmesg remains silent. Hmm, could you share fsck.f2fs result with the image? > > When I modify the script a little bit and force it to run in a > single-thread (by removing &), it runs well. > > I was able to confirm that it isn't a memory issue. The server has > 50G+ of free memory, and the issue is still reliably reproducible when > I defragment the memory by dropping caches and doing `echo 1 > > /proc/sys/vm/compact_memory`. > > I wasn't able to test any recent kernels (v5.16 or v5.17) as it's > unsupported by ZFS. And it being a production server, I am somewhat > limited in dabbling around the kernel. > > I am planning to test a new kernel with v5.15 + > f2fs-stable/linux-5.15.y merged. Meanwhile, if this is a new report or > fixed with newer commits, I'd appreciate a tip. > > Thanks. > > > _______________________________________________ > Linux-f2fs-devel mailing list > Linux-f2fs-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel