Hi,
On 06/25, Didier Spaier wrote:
> Hello list,
>
> this email is a follow-up of:
> https://www.mail-archive.com/linux-f2fs-devel@lists.sourceforge.net/msg14390.html
>
> I will number the questions Q1, Q2 etc.
>
> To summarize the context and goal: I want that the Slint installer
> format the
Hello list,
this email is a follow-up of:
https://www.mail-archive.com/linux-f2fs-devel@lists.sourceforge.net/msg14390.html
I will number the questions Q1, Q2 etc.
To summarize the context and goal: I want that the Slint installer
format the root partition with f2fs when appropriate, if possible
On 06/18, Chao Yu wrote:
> - Add to account and show per-log dirty_seg, full_seg and valid_blocks
> in debugfs.
> - reformat printed info.
>
> TYPEsegnosecno zoneno dirty_seg full_seg valid_blk
> - COLD data: 1523 1523 1523 1 0399
On 06/22, Chao Yu wrote:
> On 2020/6/22 0:38, Jaegeuk Kim wrote:
> > On 06/20, Chao Yu wrote:
> >> On 2020/6/20 6:47, Jaegeuk Kim wrote:
> >>> On 06/19, Chao Yu wrote:
> On 2020/6/19 13:49, Jaegeuk Kim wrote:
> > On 06/19, Chao Yu wrote:
> >> Hi Jaegeuk,
> >>
> >> On 2020/6/19
When f2fs_ioc_gc_range performs multiple segments gc ops, the return
value of f2fs_ioc_gc_range is determined by the last segment gc ops.
If its ops failed, the f2fs_ioc_gc_range will be considered to be failed
despite some of previous segments gc ops succeeded. Therefore, so we
fix: Redefine the r