Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
From: "Theodore Ts'o" <tytso@xxxxxxx>
Date: Thu, 16 May 2019 12:59:21 -0400
Cc: fstests <fstests@xxxxxxxxxxxxxxx>, linux-btrfs <linux-btrfs@xxxxxxxxxxxxxxx>, linux-ext4 <linux-ext4@xxxxxxxxxxxxxxx>, Jan Kara <jack@xxxxxxx>, Filipe Manana <fdmanana@xxxxxxxx>
In-reply-to: <CAL3q7H7q5Xphhax3qPdt1fnjaWrekMgMKzKfDyOLm+bbgsw6Aw@mail.gmail.com>
References: <20190515150221.16647-1-fdmanana@kernel.org> <20190516092848.GA6975@mit.edu> <CAL3q7H7q5Xphhax3qPdt1fnjaWrekMgMKzKfDyOLm+bbgsw6Aw@mail.gmail.com>
User-agent: Mutt/1.10.1 (2018-07-13)

On Thu, May 16, 2019 at 10:54:57AM +0100, Filipe Manana wrote:
> 
> Haven't tried ext4 with 1 process only (instead of 4), but I can try
> to see if it happens without concurrency as well.

How many CPU's and how much memory were you using?  And I assume this
was using KVM/QEMU?  How was it configured?

Thanks,

					- Ted

Follow-Ups:
- Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
  - From: Filipe Manana

References:
- [PATCH] fstests: generic, fsync fuzz tester with fsstress
  - From: fdmanana
- Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
  - From: Theodore Ts'o
- Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
  - From: Filipe Manana

Prev by Date: Re: storm-of-soft-lockups: spinlocks running on all cores, preventing forward progress (4.14- to 5.0+)
Next by Date: Re: Used disk size of a received subvolume?
Previous by thread: Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
Next by thread: Re: [PATCH] fstests: generic, fsync fuzz tester with fsstress
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]