From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: David T Hollis <dhollis@davehollis.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext2 -> ext3 on the fly?
Date: Fri, 29 Aug 2003 10:27:22 -0400 [thread overview]
Message-ID: <20030829142722.GB12564@rdlg.net> (raw)
In-Reply-To: <3F4F6233.5050809@davehollis.com>
[-- Attachment #1: Type: text/plain, Size: 2848 bytes --]
Thus spake David T Hollis (dhollis@davehollis.com):
> Robert L. Harris wrote:
>
> >I have a number of servers which are currently mounting /usr as ext2. I
> >have a means of doing an tune2fs -j on all of them remotely en mass but
> >I'd rather not reboot them all to enable journaling on machines that are
> >up and not having issues. I've tried to do a:
> >
> >mount -t ext3 -o remount /usr
> >
> >as well as just a mount -o remount after changing the fstab.
> >
> >on a test box but it just blows out a usage message. Is there a way to
> >do this remount without a complete reboot that'll be transparant to
> >users?
> >
> >
> >If not, is it dangerous to tune2fs the filesystems, change the fstab and
> >then leave the box up for 2-6 months and let them reboot through
> >atrrition, upgrades, etc?
> >
> >Current kernel is 2.4.21-ac3, getting outages and upgrades is a rather
> >long process involving regression testing, etc.
> >
> >Robert
> >
> >:wq!
> >---------------------------------------------------------------------------
> >Robert L. Harris | GPG Key ID: E344DA3B
> > @ x-hkp://pgp.mit.edu
> >DISCLAIMER:
> > These are MY OPINIONS ALONE. I speak for no-one else.
> >
> >Life is not a destination, it's a journey.
> > Microsoft produces 15 car pileups on the highway.
> > Don't stop traffic to stand and gawk at the tragedy.
> >
> >
> I would be inclined to say it's not safe not from a code perspective but
> an administration perspective. If you make a change as significant as
> the file system format but don't test it until you reboot the box six
> months from now (when you aren't thinking about how you changed it six
> months ago) problems are likely to happen. Could be a simple typo or
> something else, but it can definitely come back to bite you in the
> backside. Granted, if you forgot to change your fstab to ext3, you'd
> still boot and be fine running as ext2, you just never can tell what
> could happen. Murphy always likes to visit on those occasions.
My thoughts exactly, just wanted someone else to say it so I can give it
to management. Unfortunately I know their response will be that our
package management system will ensure this won't happen which
technically it shouldn't but I can think of a couple ways ti still
could.
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-29 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 14:16 Robert L. Harris
2003-08-29 14:24 ` David T Hollis
2003-08-29 14:27 ` Robert L. Harris [this message]
2003-08-29 15:25 ` Valdis.Kletnieks
2003-08-29 14:27 ` Matti Aarnio
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=20030829142722.GB12564@rdlg.net \
--to=robert.l.harris@rdlg.net \
--cc=dhollis@davehollis.com \
--cc=linux-kernel@vger.kernel.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 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®