On 2022/6/7 11:40, Yufen Yu wrote:
Usage:
dump.f2fs -I [inode nid] /dev/sda
This feature can be useful for some bugs caused by system crash.
We not only need dump current valid node page, but alse the history
data in disk, which can give some clues for status change of the inode.
On 06/15, Yufen Yu via Linux-f2fs-devel wrote:
> gentry ping...
Thanks, merged.
>
> On 2022/6/7 11:40, Yufen Yu wrote:
> > Usage:
> > dump.f2fs -I [inode nid] /dev/sda
> >
> > This feature can be useful for some bugs caused by system crash.
> > We not only need dump current valid node
gentry ping...
On 2022/6/7 11:40, Yufen Yu wrote:
Usage:
dump.f2fs -I [inode nid] /dev/sda
This feature can be useful for some bugs caused by system crash.
We not only need dump current valid node page, but alse the history
data in disk, which can give some clues for status change of
v2:
add ASSERT(ret >= 0);
v3:
skip data segment when scan full disk
On 2022/6/7 11:40, Yufen Yu wrote:
Usage:
dump.f2fs -I [inode nid] /dev/sda
This feature can be useful for some bugs caused by system crash.
We not only need dump current valid node page, but alse the
Usage:
dump.f2fs -I [inode nid] /dev/sda
This feature can be useful for some bugs caused by system crash.
We not only need dump current valid node page, but alse the history
data in disk, which can give some clues for status change of the inode.
Signed-off-by: Yufen Yu
---
fsck/dump.c
