Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-16 Thread Philippe De Muyter
; if (nat_get_blkaddr(ne) == NULL_ADDR) add_free_nid(sbi, nid, false); } Best Regards Philippe On Thu, Sep 15, 2022 at 03:10:04PM +0800, Wu Bo wrote: > On 2022/9/14 16:08, Philippe De Muyter wrote: > > > Hello Wu Bo, > > > >

Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-14 Thread Philippe De Muyter
Hello Wu Bo, On Wed, Sep 14, 2022 at 12:04:23PM +0800, Wu Bo wrote: > As Philippe De Muyter reported: > https://lore.kernel.org/linux-f2fs-devel/20220913224908.GA25100@172.21.0.10/T/#u > > The warning log showed that when finding a new space for nat the journal > space turned

[f2fs-dev] concern about f2fs and fsck.f2fs

2022-09-13 Thread Philippe De Muyter
Hello, I use the f2fs version from linux 4.1.15 for the root partition of our product. At that time, fsck.f2fs did nothing. But now I feel the need to run fsck.f2fs in a initramfs at startup. I have cloned f2fs-tools and compiled version 1.14 of f2fs.fsck, and used it to check and fix automatica

Re: [f2fs-dev] f2fs_bug_on in init_dirty_segmap

2017-03-12 Thread Philippe De Muyter
On Sat, Mar 11, 2017 at 01:01:11PM -0800, Jaegeuk Kim wrote: > On 03/10, Philippe De Muyter wrote: > > On Fri, Mar 10, 2017 at 10:20:34AM -0800, Jaegeuk Kim wrote: > > > On 03/10, Philippe De Muyter wrote: > > > ... > > > > > > It is actually

Re: [f2fs-dev] f2fs_bug_on in init_dirty_segmap

2017-03-10 Thread Philippe De Muyter
On Fri, Mar 10, 2017 at 10:20:34AM -0800, Jaegeuk Kim wrote: > On 03/10, Philippe De Muyter wrote: > ... > > > > It is actually a Freescale (now NXP) provided kernel tagged > > > > rel_imx_4.1.15_1.2.0_ga > > > > available at git://git.freescale.com

Re: [f2fs-dev] f2fs_bug_on in init_dirty_segmap

2017-03-10 Thread Philippe De Muyter
On Thu, Mar 09, 2017 at 03:11:46PM -0800, Jaegeuk Kim wrote: > On 03/09, Philippe De Muyter wrote: > > Hi, > > > > thanks for your quick answer > > > > On Wed, Mar 08, 2017 at 01:52:03PM -0800, Jaegeuk Kim wrote: > > > Hi, > > > > &

Re: [f2fs-dev] f2fs_bug_on in init_dirty_segmap

2017-03-09 Thread Philippe De Muyter
Hi, thanks for your quick answer On Wed, Mar 08, 2017 at 01:52:03PM -0800, Jaegeuk Kim wrote: > Hi, > > On 03/08, Philippe De Muyter wrote: > > Hi f2fs developpers, > > > > Please excuse my maybe dumb question. > > > > I recently encountered a kernel p

[f2fs-dev] f2fs_bug_on in init_dirty_segmap

2017-03-08 Thread Philippe De Muyter
> sbi->blocks_per_seg) { f2fs_bug_on(sbi, 1); <<<<<<<<<<<<<<<<<<<< continue; } Is that really a condition requiring a kernel panic, or could a read-only mount be allowe