From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaegeuk Kim Subject: Re: f2fs corruption due to f2fs_gc crash. Date: Fri, 20 Jan 2017 17:52:57 +0800 Message-ID: <20170120095257.GB43432@jaegeuk.local> References: <20170119234300.GB42028@jaegeuk.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1cUVsh-0006Rq-7M for linux-f2fs-devel@lists.sourceforge.net; Fri, 20 Jan 2017 09:53:15 +0000 Received: from mail.kernel.org ([198.145.29.136]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1cUVsg-00081F-E9 for linux-f2fs-devel@lists.sourceforge.net; Fri, 20 Jan 2017 09:53:15 +0000 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: KARBOWSKI Piotr Cc: linux-f2fs-devel@lists.sourceforge.net On 01/20, KARBOWSKI Piotr wrote: > Hi, > > On 01/20/2017 12:43 AM, Jaegeuk Kim wrote: > > If possible, could you share the fsck log whether it repaired something? > > That message is caused by wrong summary type, which is able to be fixed by > > fsck. > > Yes, of course. Please find the log below. Hi, > > + fsck.f2fs -a /dev/mapper/sd_stash > Info: Fix the reported corruption. > Info: Segments per section = 1 > Info: Sections per zone = 1 > Info: sector size = 512 > Info: total sectors = 384497664 (187743 MB) > Info: MKFS version > "Linux version 4.8.9-frontier1 (root@kurogane) (gcc version 5.4.0 (Gentoo > 5.4.0 p1.0, pie-0.6.5) ) #5 SMP Mon Dec 19 16:57:47 CET 2016" > Info: FSCK version > from "Linux version 4.9.4 (root@kurogane) (gcc version 5.4.0 (Gentoo > 5.4.0-r2 p1.2, pie-0.6.5) ) #1 SMP Wed Jan 18 23:38:00 CET 2017" > to "Linux version 4.9.4 (root@kurogane) (gcc version 5.4.0 (Gentoo > 5.4.0-r2 p1.2, pie-0.6.5) ) #1 SMP Wed Jan 18 23:38:00 CET 2017" > Info: superblock features = 0 : > Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000 > Info: total FS sectors = 384497664 (187743 MB) > Info: CKPT version = dac > Info: checkpoint state = 51 : fsck unmount So, it shows fsck, which means there were IO errors given by sd card. How about using the latest f2fs-tools/dev-test? http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/log/?h=dev-test Thanks, > > [FSCK] Unreachable nat entries [Ok..] [0x0] > [FSCK] SIT valid block bitmap checking [Ok..] > [FSCK] Hard link checking for regular file [Ok..] [0x7] > [FSCK] valid_block_count matching with CP [Ok..] [0x1f34b71] > [FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x9aef] > [FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x9aef] > [FSCK] valid_inode_count matched with CP [Ok..] [0x1260] > [FSCK] free segment_count matched with CP [Ok..] [0x73d3] > [FSCK] next block offset is free [Ok..] > [FSCK] fixing SIT types > [FSCK] other corrupted bugs [Ok..] > > Done. > + mount LABEL=sd_stash > > -- Piotr. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot