ESIZE2FS_PROG="$(type -P resize2fs)"
> -export F2FS_IO_PROG="$(type -P f2fs_io)"
> export FIO_PROG="$(type -P fio)"
> export FILEFRAG_PROG="$(type -P filefrag)"
> export E4DEFRAG_PROG="$(type -P e
Hi Chao Yu,
On Wed, 30 Apr 2025 10:47:31 +0800, Chao Yu wrote:
> This is a regression testcase to check whether we will handle database
> inode dirty status correctly:
> 1. make sure disk quota is enabled
> 2. create a regular file, and write data into the file
> 3. start transaction on the file
Thanks for submitting the new test. It looks good aside from a few minor
things below...
On Thu, 6 Mar 2025 16:18:09 +0800, Chao Yu wrote:
> This is a regression test to check whether fsck can handle corrupted
> nlinks correctly, it uses inject.f2fs to inject nlinks w/ wrong value,
> and expects
e -P dump.f2fs)
> export F2FS_IO_PROG=$(type -P f2fs_io)
> +export F2FS_INJECT_PROG=$(type -P inject.f2fs)
> export BTRFS_UTIL_PROG=$(type -P btrfs)
> export BTRFS_SHOW_SUPER_PROG=$(type -P btrfs-show-super)
> export BTRFS_CONVERT_PROG=$(type -P btrfs-convert)
Reviewed-by: David Diss
> *)
> local dev=$SCRATCH_DEV
> local fstyp=$FSTYP
Reviewed-by: David Disseldorp
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
omic
> file"), database file may become corrupted after atomic write while
> there is concurrent dirty inode flush in background.
>
> Cc: Jaegeuk Kim
> Cc: Daeho Jeong
> Signed-off-by: Chao Yu
Looks good.
Reviewed-by: David Disseldorp
_
On Thu, 14 Feb 2019 22:59:47 -0800, Omar Sandoval wrote:
> On Fri, Feb 15, 2019 at 11:16:57AM +1100, Dave Chinner wrote:
> > On Thu, Feb 14, 2019 at 03:14:29PM -0800, Omar Sandoval wrote:
> > > On Fri, Feb 15, 2019 at 09:06:26AM +1100, Dave Chinner wrote:
...
> > > > Inode create time is foren