From: Daeho Jeong
introduce the below 4 new sysfs node for atomic write statistics.
- current_atomic_write: the total current atomic write block count,
which is not committed yet.
- peak_atomic_write: the peak value of total current atomic write block
On Wed, Jul 13, 2022 at 4:15 AM Chao Yu wrote:
>
> On 2022/7/13 7:22, Matteo Croce wrote:
> > On Fri, 6 May 2022 09:33:06 +0800
> > Chao Yu wrote:
> >
> >> As Yanming reported in bugzilla:
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=215916
> >>
> >> The kernel message is shown below:
>
On Sat, Jul 16, 2022 at 8:22 PM Chao Yu wrote:
>
> On 2022/6/22 0:07, Jaegeuk Kim wrote:
> > Can we do like this which has no functional change but refactored
> > some functions?
> >
> > ---
> > fs/f2fs/compress.c | 208 -
> > fs/f2fs/data.c | 52
There is issue as follows when test f2fs atomic write:
F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (loop0): invalid crc_offset: 0
F2FS-fs (loop0): f2fs_check_nid_range: out-of-range nid=1, run fsck to fix.
F2FS-fs (loop0): f2fs_check_nid_range: out-of-range nid=2, ru
From: duguowei
If there are more than one f2fs sbi, there will be more
discard threads. But the comm is too long to show dev
minor. So, change the default prefix of thread from
"f2fs_discard" to "f2fs_dcd".
Before:
$ ps -e | grep f2fs
1628 ?00:00:00 f2fs_ckpt-7:10
1629 ?00:00:00
https://bugzilla.kernel.org/show_bug.cgi?id=216162
--- Comment #12 from [email protected] ---
Ah, I somehow completely missed that the dev branched was linked before in
comment 3, sorry.
That branch does indeed fix the issue, thanks for the hint.
Maybe the fix warrants a push to master and a n
