From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <esandeen@redhat.com>
Cc: Jan Schmidt <list.btrfs@jan-o-sch.net>,
Eric Sandeen <sandeen@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: btrfs/276 - stop all fsstress before exiting
Date: Fri, 3 May 2013 08:06:26 -0500 [thread overview]
Message-ID: <5183B652.8020300@sgi.com> (raw)
In-Reply-To: <7DC41D7F-396D-4769-B573-816E80372456@redhat.com>
On 04/26/2013 08:10 AM, Eric Sandeen wrote:
> On Apr 26, 2013, at 3:35 AM, Jan Schmidt <list.btrfs@jan-o-sch.net> wrote:
>
>> On Fri, April 26, 2013 at 07:29 (+0200), Eric Sandeen wrote:
>>> Tests after 276 were failing because the background fsstress
>>> hadn't quit prior to exit, devices couldn't be unmounted, etc.
>>
>> I don't see how that would happen. Any further insight?
>>
> Yes, sorry for not including it. The parent process was killed, but the fsstress processes just got reparented to init.
>
> I tried for a while to use pkill to knock them of first but this seems simpler, actually.
>
> Eric
>
Jan, with Eric's explanation, may I put your Reviewed-by: on this patch?
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <esandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Jan Schmidt <list.btrfs@jan-o-sch.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: btrfs/276 - stop all fsstress before exiting
Date: Fri, 3 May 2013 08:06:26 -0500 [thread overview]
Message-ID: <5183B652.8020300@sgi.com> (raw)
In-Reply-To: <7DC41D7F-396D-4769-B573-816E80372456@redhat.com>
On 04/26/2013 08:10 AM, Eric Sandeen wrote:
> On Apr 26, 2013, at 3:35 AM, Jan Schmidt <list.btrfs@jan-o-sch.net> wrote:
>
>> On Fri, April 26, 2013 at 07:29 (+0200), Eric Sandeen wrote:
>>> Tests after 276 were failing because the background fsstress
>>> hadn't quit prior to exit, devices couldn't be unmounted, etc.
>>
>> I don't see how that would happen. Any further insight?
>>
> Yes, sorry for not including it. The parent process was killed, but the fsstress processes just got reparented to init.
>
> I tried for a while to use pkill to knock them of first but this seems simpler, actually.
>
> Eric
>
Jan, with Eric's explanation, may I put your Reviewed-by: on this patch?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-03 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 5:29 [PATCH] xfstests: btrfs/276 - stop all fsstress before exiting Eric Sandeen
2013-04-26 5:29 ` Eric Sandeen
2013-04-26 8:35 ` Jan Schmidt
2013-04-26 8:35 ` Jan Schmidt
2013-04-26 13:10 ` Eric Sandeen
2013-04-26 13:10 ` Eric Sandeen
2013-05-03 13:06 ` Rich Johnston [this message]
2013-05-03 13:06 ` Rich Johnston
2013-05-03 14:41 ` Jan Schmidt
2013-05-03 15:03 ` Rich Johnston
2013-05-03 15:03 ` Rich Johnston
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=5183B652.8020300@sgi.com \
--to=rjohnston@sgi.com \
--cc=esandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=sandeen@redhat.com \
--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.