All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] to make files of ocfs2 under sysfs canonical
Date: Wed Dec 12 14:54:33 2007	[thread overview]
Message-ID: <20071212225250.GD28607@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20071212222857.GF16474@kroah.com>

On Wed, Dec 12, 2007 at 02:28:57PM -0800, Greg KH wrote:
> > The sysfs entries of ocfs2 are under /sys/oc2b, but I think they
> > generally should be under /sys/fs/oc2b, aren't they?
> 
> Yes, they should be, it looks like someone messed up putting them in the
> sysfs root directory.

'o2cb' refers to the stuff in ocfs2_nodemanager, so we wanted to keep it out
of the fs namespace (think more "cluster" than "file system").

We felt at the time (and still do) that it was better than polluting
/sys/fs/ with non file system related things.

Also, I feel that for perspective, I should mention that this layout isn't
anything new - we've been doing this for a while.


> > But as Joel said, this change will break ocfs2-tools, so the decision
> > was not made.
> 
> It should be pretty simple to change the tools to work for both places,
> right?

Changing a path (or just testing two of them) isn't a big deal, the problem
is that existing versions of ocfs2-tools will break very badly. That's
clearly unnaceptable for a production file system.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

  reply	other threads:[~2007-12-12 14:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 20:20 [Ocfs2-devel] [RFC] to make files of ocfs2 under sysfs canonical Denis Cheng
2007-12-06 21:12 ` Joel Becker
2007-12-06 23:21   ` rae l
2007-12-07  0:54     ` Mark Fasheh
2007-12-07  1:28     ` Joel Becker
2007-12-11 19:23     ` Greg KH
2007-12-11 17:02       ` rae l
2007-12-12 22:30         ` Greg KH
2007-12-12 14:54           ` Mark Fasheh [this message]
2007-12-13  0:07             ` Greg KH

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=20071212225250.GD28607@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.