cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] gfs2: use log_error before LM_OUT_ERROR
Date: Wed, 28 Mar 2007 17:13:32 +0100	[thread overview]
Message-ID: <1175098412.1636.75.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20070328160804.GE22230@redhat.com>

Hi,

Now in the -nmw git tree. Thanks,

Steve.

On Wed, 2007-03-28 at 11:08 -0500, David Teigland wrote:
> We always want to see the details of the error returned to gfs, but
> log_debug is often turned off, so use log_error (printk).
> 
> Signed-off-by: David Teigland <teigland@redhat.com>
> 
> Index: linux-2.6.20-git2-quilt/fs/gfs2/locking/dlm/lock.c
> ===================================================================
> --- linux-2.6.20-git2-quilt.orig/fs/gfs2/locking/dlm/lock.c	2007-02-04 12:44:54.000000000 -0600
> +++ linux-2.6.20-git2-quilt/fs/gfs2/locking/dlm/lock.c	2007-03-28 11:02:00.000000000 -0500
> @@ -268,7 +268,7 @@
>  	}
>  
>  	if (error) {
> -		log_debug("%s: gdlm_lock %x,%llx err=%d cur=%d req=%d lkf=%x "
> +		log_error("%s: gdlm_lock %x,%llx err=%d cur=%d req=%d lkf=%x "
>  			  "flags=%lx", ls->fsname, lp->lockname.ln_type,
>  			  (unsigned long long)lp->lockname.ln_number, error,
>  			  lp->cur, lp->req, lp->lkf, lp->flags);
> @@ -296,7 +296,7 @@
>  	error = dlm_unlock(ls->dlm_lockspace, lp->lksb.sb_lkid, lkf, NULL, lp);
>  
>  	if (error) {
> -		log_debug("%s: gdlm_unlock %x,%llx err=%d cur=%d req=%d lkf=%x "
> +		log_error("%s: gdlm_unlock %x,%llx err=%d cur=%d req=%d lkf=%x "
>  			  "flags=%lx", ls->fsname, lp->lockname.ln_type,
>  			  (unsigned long long)lp->lockname.ln_number, error,
>  			  lp->cur, lp->req, lp->lkf, lp->flags);



      reply	other threads:[~2007-03-28 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28 16:08 [Cluster-devel] [PATCH] gfs2: use log_error before LM_OUT_ERROR David Teigland
2007-03-28 16:13 ` Steven Whitehouse [this message]

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=1175098412.1636.75.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).