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 1065FC25B78 for ; Tue, 28 May 2024 15:31:59 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com) by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1sBynv-0002Wc-A5; Tue, 28 May 2024 15:31:59 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-2.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1sBynu-0002WK-2I for linux-f2fs-devel@lists.sourceforge.net; Tue, 28 May 2024 15:31:58 +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=Zo0qS+tMMuBwc0hgWTl13hwnQAyHCQzfOIUMgjQa1eA=; b=lvWSzJMdjhXzNNCvOGdXM7Jm8v /mwk5YXQRSEcubUl51AayTxhU6AgVFhUCMrE02jsSTRvICWpphgatWuwtnLhvT/iC30ULFQyGnlxL iTGjPxSb5dne9XAoH2YfGKo6LvI/pw4HnMD+BoQuHCnBvERn9DIFG9Xpq+EXUnlc7cIE=; 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=Zo0qS+tMMuBwc0hgWTl13hwnQAyHCQzfOIUMgjQa1eA=; b=goF+9h8riRwSEHaTr5h0881fCr dyFW+ahcKlCwzR2wMXmXsFJDkscA7rmz0X/XmK4vfL/ERfxUzlXJzlTi5pWNvzUW4ScvJeDHRp9VM M3mYKEi1E0iqPZve3I+TOB1YDOI1cmga2K3jrdUEs5+t1NfWY1gVvqoh/w7ikhnfVRrs=; Received: from sin.source.kernel.org ([145.40.73.55]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1sBynu-0000nl-Al for linux-f2fs-devel@lists.sourceforge.net; Tue, 28 May 2024 15:31:58 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id C6A98CE0EE2; Tue, 28 May 2024 01:24:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2608C2BBFC; Tue, 28 May 2024 01:24:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1716859444; bh=bh1toJKYzRYSq5Vs19qY+4H7xmdzT5pppXUEGALRUSE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uOch9BbZrmeVYGsEszzs5M73zW/+hDlQeVbQjZKRvlfpxzKQ6ztq194HldtKHxGRg FbaGMuESfWhJaTbGRpeS3WEDXfu56EBmaN0NlLYPk3VccwgKeT6F16Afrryee4xJaj NsH6+2hdKVTHIWHwfwvYmPZ885tBH2GepMrQKECL/Q5Kx3ExLoSR54nbR4SMaWkZvc UTQ9xIoU6vZAVi6nzetAlYldc5JBGRarp26qN0/y774TIOcoYb5/glehGnvMha1RIA YlD3rGqtQsBfIXPC0EqsW6khZmhBNsM7gMj2xN21I2beJXoWvbSFQP20owlQTLL9Mx jJDyXtBJADzMQ== Date: Tue, 28 May 2024 01:24:02 +0000 From: Jaegeuk Kim To: Gustavo Brondani Schenkel Message-ID: References: <2024052527-panama-playgroup-899a@gregkh> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Headers-End: 1sBynu-0000nl-Al Subject: Re: [f2fs-dev] Issue with f2fs on kernel 6.9.x 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-kernel@vger.kernel.org, stable@vger.kernel.org, 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 Hi, We're aware of this issue, and the potential fix [1] was merged in 6.9.3-rc1 in https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#t Could you please check that patch addresses your problem? [1] https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#mfd878849ed6dd660ca22aec9ca1a8eb31bc11f0c Thanks, On 05/27, Gustavo Brondani Schenkel wrote: > Hi, > since upgrade to Kernel 6.9 I am getting Issues when booting using f2fs. > If I am correct, I am receiving `fs error: invalid_blkaddr` in two distinct > drives, one nvme, and other sata. > Each reboot the fsck runs to correct this suppose error. > If I downgrade to Kernel 6.6.29, on the first boot, fsck runs just once, > than after reboot is normal. > I used 6.9.0, but in 6.9.1 it took my attention because I don't reboot > often. One 6.9.2 the Issue persist. > Since I didn't find nothing about issues on kernel messages I am trying > reach you. > > I use Slackware Linux 15.0-current, and debug flags are disabled by default, > but if you needed, > I can rebuilt the kernel with the flags you say are needed, to find what are > happening. > > PS: I didn't find any better way to report this issue, said that, sorry if > this is the wrong way to do so. > > -- > Gustavo B. Schenkel > System Analyst > B.Sc(IT), MBA(Banking) > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 85704BE40; Tue, 28 May 2024 01:24:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716859444; cv=none; b=PvP1H62Kds9X2nG+wi+eqATqHRfrYUIk0Y76W85fCwF00LL+HOnWQDa7X+kP7Y1we648E+WD5Iaa9pfnieZPeR4P6nJOHkNnhi5fzgxtisIniS4/RSz9B2dtDl9QhIk7sEmPnq+Pi6PdF12m1ajsVCXKMKOC4ejBTvwkMp18N0k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716859444; c=relaxed/simple; bh=bh1toJKYzRYSq5Vs19qY+4H7xmdzT5pppXUEGALRUSE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Ryd3LOy8edKcTrATdNPAuw5yo5Ipuim0e6rGpIhAF7UIVRApOa0i3ovo8pJKqd5pTiKY4SGzX+UL2qi8hfhP3uLLC88sGYAo+bqxvaLkGtTlE6YaESkzXdTIwUke1C84LKgGWB5m5CrarRJXyjU4xJMzT6BSE26y6edbvUbrZhM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=uOch9BbZ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="uOch9BbZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2608C2BBFC; Tue, 28 May 2024 01:24:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1716859444; bh=bh1toJKYzRYSq5Vs19qY+4H7xmdzT5pppXUEGALRUSE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uOch9BbZrmeVYGsEszzs5M73zW/+hDlQeVbQjZKRvlfpxzKQ6ztq194HldtKHxGRg FbaGMuESfWhJaTbGRpeS3WEDXfu56EBmaN0NlLYPk3VccwgKeT6F16Afrryee4xJaj NsH6+2hdKVTHIWHwfwvYmPZ885tBH2GepMrQKECL/Q5Kx3ExLoSR54nbR4SMaWkZvc UTQ9xIoU6vZAVi6nzetAlYldc5JBGRarp26qN0/y774TIOcoYb5/glehGnvMha1RIA YlD3rGqtQsBfIXPC0EqsW6khZmhBNsM7gMj2xN21I2beJXoWvbSFQP20owlQTLL9Mx jJDyXtBJADzMQ== Date: Tue, 28 May 2024 01:24:02 +0000 From: Jaegeuk Kim To: Gustavo Brondani Schenkel Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: Issue with f2fs on kernel 6.9.x Message-ID: References: <2024052527-panama-playgroup-899a@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi, We're aware of this issue, and the potential fix [1] was merged in 6.9.3-rc1 in https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#t Could you please check that patch addresses your problem? [1] https://lore.kernel.org/stable/ZlT506xwTYWg72Jj@duo.ucw.cz/T/#mfd878849ed6dd660ca22aec9ca1a8eb31bc11f0c Thanks, On 05/27, Gustavo Brondani Schenkel wrote: > Hi, > since upgrade to Kernel 6.9 I am getting Issues when booting using f2fs. > If I am correct, I am receiving `fs error: invalid_blkaddr` in two distinct > drives, one nvme, and other sata. > Each reboot the fsck runs to correct this suppose error. > If I downgrade to Kernel 6.6.29, on the first boot, fsck runs just once, > than after reboot is normal. > I used 6.9.0, but in 6.9.1 it took my attention because I don't reboot > often. One 6.9.2 the Issue persist. > Since I didn't find nothing about issues on kernel messages I am trying > reach you. > > I use Slackware Linux 15.0-current, and debug flags are disabled by default, > but if you needed, > I can rebuilt the kernel with the flags you say are needed, to find what are > happening. > > PS: I didn't find any better way to report this issue, said that, sorry if > this is the wrong way to do so. > > -- > Gustavo B. Schenkel > System Analyst > B.Sc(IT), MBA(Banking) >