From: Masayoshi MIZUMA <m.mizuma@jp.fujitsu.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] xfstests: 277 new test to check freeze/unfreeze works well or not under heavy load.
Date: Mon, 12 Dec 2011 18:31:55 +0900 [thread overview]
Message-ID: <20111212183153.DF3F.61FB500B@jp.fujitsu.com> (raw)
In-Reply-To: <20111209071700.GD14273@dastard>
(2011/12/09 16:17), Dave Chinner wrote:
> On Fri, Dec 09, 2011 at 02:52:31PM +0900, Masayoshi MIZUMA wrote:
> > Hi,
> >
> > unfreeze function, thaw_super(), sometimes hangs up if flush kernel
> > thread does writeback to the same filesystem concurrently.
> > (the problem is reported at
> > http://marc.info/?l=linux-ext4&m=132339590004560&w=2)
> >
> > This test runs freeze/unfreeze under heavy load. If the problem is
> > reproduced, this test will hang up...
>
> This is effectively a duplicate of test 068, which is currently
> described as an XFS only test. It is actually generic now that
> xfs_freeze works on other filesytsems, so please update 068
> appropriately rather that introducing a new test.
OK, I will try to update 068 to reproduce the problem, thanks!
Masayoshi Mizuma
>
> Cheers,
>
> Dave
>
> --
> Dave Chinner
> david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Masayoshi MIZUMA <m.mizuma@jp.fujitsu.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: 277 new test to check freeze/unfreeze works well or not under heavy load.
Date: Mon, 12 Dec 2011 18:31:55 +0900 [thread overview]
Message-ID: <20111212183153.DF3F.61FB500B@jp.fujitsu.com> (raw)
In-Reply-To: <20111209071700.GD14273@dastard>
(2011/12/09 16:17), Dave Chinner wrote:
> On Fri, Dec 09, 2011 at 02:52:31PM +0900, Masayoshi MIZUMA wrote:
> > Hi,
> >
> > unfreeze function, thaw_super(), sometimes hangs up if flush kernel
> > thread does writeback to the same filesystem concurrently.
> > (the problem is reported at
> > http://marc.info/?l=linux-ext4&m=132339590004560&w=2)
> >
> > This test runs freeze/unfreeze under heavy load. If the problem is
> > reproduced, this test will hang up...
>
> This is effectively a duplicate of test 068, which is currently
> described as an XFS only test. It is actually generic now that
> xfs_freeze works on other filesytsems, so please update 068
> appropriately rather that introducing a new test.
OK, I will try to update 068 to reproduce the problem, thanks!
Masayoshi Mizuma
>
> Cheers,
>
> Dave
>
> --
> Dave Chinner
> david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-12 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 5:52 [PATCH] xfstests: 277 new test to check freeze/unfreeze works well or not under heavy load Masayoshi MIZUMA
2011-12-09 5:52 ` Masayoshi MIZUMA
2011-12-09 7:17 ` Dave Chinner
2011-12-09 7:17 ` Dave Chinner
2011-12-12 9:31 ` Masayoshi MIZUMA [this message]
2011-12-12 9:31 ` Masayoshi MIZUMA
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=20111212183153.DF3F.61FB500B@jp.fujitsu.com \
--to=m.mizuma@jp.fujitsu.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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.