From: Steven Whitehouse <swhiteho@redhat.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [13/16]
Date: Mon, 27 Feb 2006 08:46:48 +0000 [thread overview]
Message-ID: <1141030008.6400.780.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20060222185059.GC2633@ucw.cz>
Hi,
On Wed, 2006-02-22 at 18:50 +0000, Pavel Machek wrote:
> Hi!
>
> > Documentation/filesystems/gfs2.txt | 44 +++++++++++++++++++++++++++++++++++
> > fs/Kconfig | 6 ++--
> > fs/Makefile | 2 +
> > fs/gfs2/Kconfig | 46 +++++++++++++++++++++++++++++++++++++
> > fs/gfs2/Makefile | 42 +++++++++++++++++++++++++++++++++
> > 5 files changed, 137 insertions(+), 3 deletions(-)
> >
> > --- a/fs/Kconfig
> > +++ b/fs/Kconfig
> > @@ -883,8 +884,6 @@ config CONFIGFS_FS
> > Both sysfs and configfs can and should exist together on the
> > same system. One is not a replacement for the other.
> >
> > - If unsure, say N.
> > -
>
> Why? Most users probably still want configfs_fs=N.
>
Yes, this one has crept in by mistake I think. I'll fix that right away.
> > @@ -1327,7 +1326,7 @@ config UFS_FS
> >
> > config UFS_FS_WRITE
> > bool "UFS file system write support (DANGEROUS)"
> > - depends on UFS_FS && EXPERIMENTAL
> > + depends on UFS_FS && EXPERIMENTAL && BROKEN
> > help
>
> Well, maybe, but I thought this is gfs2 patch...
>
Indeed. This even does not feature in any of the gfs2 patches in the git
tree. For some reason the command I used to create the diff has picked
up this change as well. I'm not entirely sure why as its in both the
gfs2 tree and the origin tree (Linus' tree).
>
> > +To use gfs as a local file system, no external clustering systems are
> > +needed, simply:
> > +
> > + $ mkfs -t gfs2 -p lock_nolock -j 1 /dev/block_device
> > + $ mount -t gfs2 /dev/block_device /dir
> > +
> > +GFS2 is not on-disk compatible with previous versions of GFS.
> > +
> > +The following man pages can be found at the URL above:
> > + gfs2_mkfs to make a filesystem
>
> I thought conventional name would be mkfs.gfs2 ... could you use that
> variant?
>
> Pavel
Yes, you can. I just always tend to run it through the mkfs front end
rather than directly. It installs itself under mkfs.gfs2 of course and
we need up update the man page (GFS1 used to call its mkfs gfs_mkfs but
I saw no reason not to make the change to a more conventional name).
Steve.
prev parent reply other threads:[~2006-02-27 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 15:05 Steven Whitehouse
2006-02-22 18:50 ` Pavel Machek
2006-02-24 22:30 ` Joel Becker
2006-02-27 8:58 ` Steven Whitehouse
2006-02-27 8:46 ` 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=1141030008.6400.780.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®