All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/042: add sleep before shutdown
Date: Tue, 2 Jul 2019 23:34:29 -0400	[thread overview]
Message-ID: <20190703033429.GA19593@mit.edu> (raw)
In-Reply-To: <1562117471-2376-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>

On Wed, Jul 03, 2019 at 09:31:11AM +0800, Yang Xu wrote:
> On some server machines, the memory was so big that we
> don't have enough time to submit file.  After umoumt,
> hexdump will report no such file or directory on ext4.

Um, so this is passing for me using ext4.  The file system is getting
shutdown via "./src/godown -f $mnt".  The -f causes the shutdown file
system to be called with the LOGFLUSH flag set.  This causes a forced
journal commit before the file system is shut down, so how much memory
the system might have should be irrelvant.

The only thing I can think of is if the journal was not enabled, but
generic/042 calls _require_metadata_journalling, and so the test will
be skipped if the file system was created without a journal or if the
noload mount option is passed as part of the test config.

Can you say a little bit more about your test configuration and test
environment?  This test really shouldn't be needing your patch;
sleeping for ten seconds should *not* be making a difference as to
whether or not the file exists for hexdump to test.  And to the extent
that the test is trying to find race conditions, adding a sleep 10
defeats the purpose of the test.

				- Ted

  reply	other threads:[~2019-07-03  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  1:31 [PATCH] generic/042: add sleep before shutdown Yang Xu
2019-07-03  3:34 ` Theodore Ts'o [this message]
2019-07-03  8:15   ` Yang Xu
  -- strict thread matches above, loose matches on Subject: below --
2019-06-26 23:51 Yang Xu

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=20190703033429.GA19593@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=xuyang2018.jy@cn.fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.