mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Joe Perches <joe@perches.com>, Joel Becker <jlbec@evilplan.org>,
	ocfs2-devel@oss.oracle.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH next] ocfs2: Reduce object size of mlog uses
Date: Thu, 23 Apr 2015 16:19:23 -0700	[thread overview]
Message-ID: <20150423161923.be61ea8cd9e64a9e30a23eca@linux-foundation.org> (raw)
In-Reply-To: <20150423230418.GR17170@wotan.suse.de>

On Thu, 23 Apr 2015 16:04:18 -0700 Mark Fasheh <mfasheh@suse.de> wrote:

> > This code needs some pretty serious rework and rethink, perhaps
> > involving a change to the emitted info.  I was hoping one of the ocfs2
> > developers would take the bait, but they're all in hiding.
> 
> If it functions the same and doesn't have a major performance change, I'm
> pretty sure it'll be fine. We sometimes ask customers to enable some of the
> debugging if they are having an issue. I would ask that it be tested
> on a live system - a local fs, no cluster or cluster config required.

Is there a simpleton's guide to testing ocfs2 on a local disk?  One
which assumes a starting point of "knows how to type".

A few paragraphs in Documentation/filesystems/ocfs2.txt would be great
- then we can point non-ocfs2 people at it when they muck with stuff.

  reply	other threads:[~2015-04-23 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  7:17 Joe Perches
2015-04-22 22:46 ` Andrew Morton
2015-04-23  2:34   ` Joe Perches
2015-04-23  7:25   ` [PATCH V2 -next] " Joe Perches
2015-04-23 23:04   ` [PATCH next] " Mark Fasheh
2015-04-23 23:19     ` Andrew Morton [this message]
2015-04-23 23:37       ` Richard Weinberger
2015-04-24 20:31         ` [Ocfs2-devel] " Mark Fasheh
2015-04-23 23:35     ` Joe Perches
2015-04-28 18:30       ` [Ocfs2-devel] " Mark Fasheh
2015-04-30  5:05         ` Joe Perches

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=20150423161923.be61ea8cd9e64a9e30a23eca@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jlbec@evilplan.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.de \
    --cc=ocfs2-devel@oss.oracle.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

all inboxes | Powered by JetHome®