linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Wojcik, Artur" <artur.wojcik@intel.com>
Cc: Neil Brown <neilb@suse.de>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm PATCH 0/2] Improvement: new logging library for mdadm/mdmon
Date: Fri, 29 Jan 2010 15:23:35 -0700	[thread overview]
Message-ID: <4B635FE7.4040908@intel.com> (raw)
In-Reply-To: <1264781188.2788.99.camel@awojcik-linux>

Wojcik, Artur wrote:
> On Fri, 2010-01-29 at 09:52 +0000, Neil Brown wrote:
>> I'd probably need a lot of convincing to add something like this to mdadm.
>>
> 
> I did not expect this patch to be accepted without convincing you or at
> least without a lot of explanations :). What interest you the most?
> 
> The reason for this improvement/patch is:
> 
> 1) to unify the way mdadm and mdmon log messages,

Unification implies code reduction, this is currently just code movement.

> 2) to have logs from mdadm and mdmon applications at the same time
> 3) to be able to capture log messages when system is booting, 
> 4) to simplify the source code. 

The only one that would be interesting from a debug perspective is 3, 
but syslog is not available in the initramfs and I currently do not see 
how it would be much better than just redirecting the console to the 
serial port and logging it there.  The dprintf() calls in mdmon are 
sometimes useful, but I am skeptical of needing those on all the time.

Can you identify debug scenarios that require this level of logging 
sophistication (versus doing one-off build/configuration changes to dump 
some diagnostic info)?  As it stands this looks like a solution looking 
for a problem.

--
Dan


  parent reply	other threads:[~2010-01-29 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 16:04 [mdadm PATCH 0/2] Improvement: new logging library for mdadm/mdmon Artur Wojcik
2010-01-28 16:04 ` [mdadm PATCH 1/2] Improvement: new logging facility Artur Wojcik
2010-01-29  9:52 ` [mdadm PATCH 0/2] Improvement: new logging library for mdadm/mdmon Neil Brown
2010-01-29 16:06   ` Artur Wojcik
2010-01-29 16:38     ` Robin Hill
2010-01-29 22:23     ` Dan Williams [this message]
2010-01-30  7:19       ` Michael Evans

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=4B635FE7.4040908@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=artur.wojcik@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).