public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Chandra Seetharaman <sekharan@us.ibm.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: Notify via syslog when godown is shutting down fs
Date: Mon, 21 Feb 2011 17:30:00 -0600	[thread overview]
Message-ID: <1298331000.2169.4.camel@doink> (raw)
In-Reply-To: <4D5C554D.8080004@sandeen.net>

On Wed, 2011-02-16 at 16:53 -0600, Eric Sandeen wrote:
> Just a hint for those perusing logs that the ensuing shutdown is
> intentional...

Good idea.

Signed-off-by: Alex Elder <aelder@sgi.com>

> Feb 16 17:06:17 hostname godown: xfstests-induced forced shutdown of /mnt/scratch
> Feb 16 17:06:17 hostname kernel: Filesystem "sdb3": xfs_log_force: error 5 returned.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-02-21 23:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 19:41 xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-15 22:30 ` Dave Chinner
2011-02-16 20:00   ` Chandra Seetharaman
2011-02-16 22:14     ` Dave Chinner
2011-02-16 22:53       ` [PATCH] xfstests: Notify via syslog when godown is shutting down fs Eric Sandeen
2011-02-17 17:33         ` Chandra Seetharaman
2011-02-21 23:30         ` Alex Elder [this message]
2011-02-16 23:42       ` xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-17  3:00         ` Eric Sandeen
2011-02-17 18:49           ` Chandra Seetharaman
2011-02-17 22:52             ` Dave Chinner
2011-02-18  2:09               ` Chandra Seetharaman
2011-02-18  3:30                 ` Dave Chinner
2011-02-18 19:57                   ` Chandra Seetharaman

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=1298331000.2169.4.camel@doink \
    --to=aelder@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=sekharan@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox