From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 04/15] lib/tst_test: Add .all_filesystems flag
Date: Wed, 11 Oct 2017 07:17:11 -0400 (EDT) [thread overview]
Message-ID: <1439328594.28383859.1507720631224.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20171011111101.GB3527@rei>
----- Original Message -----
> Hi!
> > > > 3) fs_fill test is still quite verbose
> > > >
> > > > # ./fs_fill > log2 2>&1
> > > > # du -h log2
> > > > 688K log2
> > > >
> > > > # grep Got log2
> > > > fs_fill.c:96: PASS: Got 5713 ENOSPC
> > > > fs_fill.c:96: PASS: Got 9 ENOSPC
> > > > fs_fill.c:96: PASS: Got 1709 ENOSPC
> > > >
> > > > I'm running this on single CPU KVM guest, which is (presumably due to
> > > > caching
> > > > and host SSD) able to trigger ENOSPC many times in those 2 seconds.
> > > >
> > > > I expect baremetal systems with many CPUs producing lot of output as
> > > > well,
> > > > because we start tst_fill_fs() in NR_CPU+2 threads.
> > >
> > > Okay. What about rewriting the main loop to sleep in short intervals and
> > > check the ENOSCP counter and exit if reasonably large number was found.
> >
> > There might be systems, where I/O is very slow and waiting for 100
> > ENOSPC might take too long. So, I think it should be both enospc_cnt
> > and total time as well. Whatever comes first, we exit. That should
> > limit max test output to ~10kB.
>
> Sure so what about exitting either at 100 ENOSPC or after 1s in a case
> that we got at least one ENOSPC?
Sounds good to me.
Regards,
Jan
next prev parent reply other threads:[~2017-10-11 11:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 12:31 [LTP] [PATCH v2 01/15] lib/tst_mkfs: Clear first 512k of the device Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 02/15] lib: Add interface to list supported filesystems Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 03/15] SAFE_MOUNT: Handle FUSE mounts as well Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 04/15] lib/tst_test: Add .all_filesystems flag Cyril Hrubis
2017-10-11 8:42 ` Jan Stancek
2017-10-11 9:54 ` Cyril Hrubis
2017-10-11 10:38 ` Jan Stancek
2017-10-11 11:11 ` Cyril Hrubis
2017-10-11 11:17 ` Jan Stancek [this message]
2017-10-10 12:31 ` [LTP] [PATCH v2 05/15] lib/tst_fs: Add tst_fill_fs() Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 06/15] syscalls/fallocate05: New test Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 07/15] syscalls/msync04: Run test for all filesystems Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 08/15] syscalls/fallocate04: Convert to the new library Cyril Hrubis
2017-10-10 12:31 ` [LTP] [PATCH v2 09/15] syscalls/fallocate04: Run test for all filesystems Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 10/15] syscalls/setxattr01: Convert to the new library Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 11/15] syscalls/setxattr01: Run test for all filesystems Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 12/15] syscallse/setxattr02: Convert to the new library Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 13/15] syscalls/fsync01: " Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 14/15] syscalls/fsync01: Run test for all filesystems Cyril Hrubis
2017-10-10 12:32 ` [LTP] [PATCH v2 15/15] fs/fs_fill: Add a test to fill a FS in a few threads Cyril Hrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439328594.28383859.1507720631224.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox