[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHWVdUWQXDf0fDTg=43ySNEbTEqPh1ue6ZujsBX-wTsmLQGz3A@mail.gmail.com>
Date: Wed, 15 May 2019 10:07:14 -0500
From: Vijay Chidambaram <vijay@...utexas.edu>
To: Filipe Manana <fdmanana@...nel.org>
Cc: fstests <fstests@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz>,
Filipe Manana <fdmanana@...e.com>
Subject: Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
On Wed, May 15, 2019 at 10:02 AM <fdmanana@...nel.org> wrote:
>
> From: Filipe Manana <fdmanana@...e.com>
>
> Run fsstress, fsync every file and directory, simulate a power failure and
> then verify the all files and directories exist, with the same data and
> metadata they had before the power failure.
I'm happy to see this sort of crash testing be merged into the Linux
kernel! I think something like this being run after every
merge/nightly build will make file systems significantly more robust
to crash-recovery bugs.
Powered by blists - more mailing lists