From: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mount -o remount problems with ext3 and journal= options in /etc/fstab
Date: Sat, 29 Nov 2008 00:06:01 -0500 [thread overview]
Message-ID: <20081129050601.GE3372@mit.edu> (raw)
In-Reply-To: <200811281703.12669.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
On Fri, Nov 28, 2008 at 05:03:10PM -0500, Mike Frysinger wrote:
> well, i guess the first question to ask is, does it make sense to have these
> journal options in /etc/fstab ?
No, not really. The original intent for journal=update was to update
from a V1 journal superblock to the V2 journal superblock. This
transition happened in around 2001. It was intended to be used to ask
the kernel to do a one-time conversion of the superblock version.
There's no real reason to have this in the kernel; it's the sort of
thing that is much better done in the userspace tools anyway. p
We should probably remove it from the kernel, actually. There might
be some really ancient 2.4 systems that still have journals with V1
superblocks, but they are few and far between.
In any case, if this was going to be in the kernel, it makes
absolutely zero sense for it to be in /etc/fstab. It should only be
something that the user manually specifies when first mounting the
filesystem, and for that reason it's actually better done in a
userspace tool.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-29 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200811271447.44837.vapier@gentoo.org>
[not found] ` <20081127230227.GR2961@nb.net.home>
[not found] ` <20081127230227.GR2961-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-11-28 22:03 ` mount -o remount problems with ext3 and journal= options in /etc/fstab Mike Frysinger
[not found] ` <200811281703.12669.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2008-11-29 5:06 ` Theodore Tso [this message]
2008-11-29 6:16 ` Mike Frysinger
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=20081129050601.GE3372@mit.edu \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
/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.