public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] logprint: Fix printing of AGF buffers
Date: Fri, 18 Jul 2014 10:29:31 +1000	[thread overview]
Message-ID: <20140718002931.GI4453@dastard> (raw)
In-Reply-To: <20140717083905.GB1649@quack.suse.cz>

On Thu, Jul 17, 2014 at 10:39:05AM +0200, Jan Kara wrote:
> On Thu 17-07-14 09:17:25, Dave Chinner wrote:
> > IOWs, we've played whack-a-mole on this again while ignoring the
> > fundamental issues ithat still remain:
> > 
> > 	- that logprint has a lot of assumptions that simply aren't
> > 	  true; and
> > 	- that logprint simply does not handle split region
> > 	  continuations like the kernel recovery code does.
> > 
> > Both of these things lead to having to handle these strange "out of
> > space" cases in multiple places, and simply not handling them in
> > places that actually need to.
> > 
> > These are just more reasons why logprint - as it says itself in a
> > couple of comments - needs a complete rewrite.
>   Yeah, I've noticed that logprint definitely doesn't handle all possible
> cases and the code is ... well, organic :).

That's a very polite way of putting it ;)

> OTOH it worked for me (except
> for this bug) when I needed so for a debug tool like that it seemed good
> enough. I don't feel like rewriting it from scratch (at least in near
> future) but if someone can find time for that, it would be surely welcome.

Right, that's effectively been the state of play for some time. It's
a useful tool that could do with some work to make it better, but
nobody has had the time to do that work because most of the time it
works fine...

If only there were some minions around looking to learn about XFS
log recovery....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2014-07-18  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 14:45 [PATCH] logprint: Fix printing of AGF buffers Jan Kara
2014-07-15 10:19 ` Christoph Hellwig
2014-07-15 14:09   ` Jan Kara
2014-07-15 15:39     ` Christoph Hellwig
2014-07-16  0:38       ` Dave Chinner
2014-07-16  8:11         ` Christoph Hellwig
2014-07-16 20:33           ` Jan Kara
2014-07-16 23:17           ` Dave Chinner
2014-07-17  8:39             ` Jan Kara
2014-07-18  0:29               ` Dave Chinner [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=20140718002931.GI4453@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --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