From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 1/2] xfs: log unmount events on console
Date: Tue, 24 Feb 2015 23:51:20 +1100 [thread overview]
Message-ID: <20150224125120.GC4251@dastard> (raw)
In-Reply-To: <20150224115325.GA2356@laptop.bfoster>
On Tue, Feb 24, 2015 at 06:53:25AM -0500, Brian Foster wrote:
> On Mon, Feb 23, 2015 at 01:06:29PM -0800, Christoph Hellwig wrote:
> > On Mon, Feb 23, 2015 at 02:53:04PM -0600, Eric Sandeen wrote:
> > > On 2/23/15 2:49 PM, Christoph Hellwig wrote:
> > > > Oh well, even more spam during xfstest runs :)
> > >
> > > Heh, but no review...?
> > >
> > > I could be talked out of it, if people think it's not useful
> > > enough.
> >
> > I can't really get excited enough either way to give a review or nak..
> >
>
> Heh, what verbosity is xfs_notice()? Maybe using debug level would be
> better?
The context Eric and I wanted to see this was when triaging bugs on
production systems. e.g. to know if someone unmounted a shut down
filesystem and tried to repair it before rebooting the system...
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:[~2015-02-24 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 19:13 [PATCH 0/2] xfs: minor kernel logging updates Eric Sandeen
2015-02-23 19:15 ` [PATCH 1/2] xfs: log unmount events on console Eric Sandeen
2015-02-23 20:49 ` Christoph Hellwig
2015-02-23 20:53 ` Eric Sandeen
2015-02-23 21:06 ` Christoph Hellwig
2015-02-24 11:53 ` Brian Foster
2015-02-24 12:51 ` Dave Chinner [this message]
2015-02-24 13:03 ` Brian Foster
2015-02-23 19:19 ` [PATCH 2/2] xfs: clarify async write failure ratelimit message Eric Sandeen
2015-02-23 20:49 ` Christoph Hellwig
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=20150224125120.GC4251@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=hch@infradead.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--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