mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moving ext3 journal file
Date: Fri, 23 Nov 2001 21:25:57 -0700	[thread overview]
Message-ID: <20011123212557.U1308@lynx.no> (raw)
In-Reply-To: <E167Fuw-00001K-00@DervishD> <20011123155901.C1308@lynx.no> <9tmocg$jfn$1@cesium.transmeta.com> <20011123174120.Q1308@lynx.no> <9tmr83$jo2$1@cesium.transmeta.com>
In-Reply-To: <9tmr83$jo2$1@cesium.transmeta.com>; from hpa@zytor.com on Fri, Nov 23, 2001 at 04:56:35PM -0800

On Nov 23, 2001  16:56 -0800, H. Peter Anvin wrote:
> By author:    Andreas Dilger <adilger@turbolabs.com>
> > I really don't see it as being a problem (other than a purely cosmetic
> > one) to have a .journal file in your root fs.  I lived with these for a
> > couple of years OK...
> 
> It's either a cosmetic problem or a really problematic one, depending
> on how closely controlled that particular part of the namespace is.
> The .journal file could potentially try to be copied, backed up, you
> name it.

Actually, unless users are actively trying to shoot themselves in the
foot, none of this really matters.  However, now that ext3 is in the
mainline, the number of users playing with guns has increased a large
amount, it seems, by the number of such reports on ext3-users.

Because .journal is created as immutable, even if it was backed up and
tried to be restored, it would be impossible to write to.  For the
"accursed" ext2 dump, it recognizes the "nodump" flag, but also knows
enough not to back up the journal file.  Sadly, neither cpio or tar
know about ext2 attributes.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-11-24  4:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 12:58 RaúlNúñez de Arenas Coronado
2001-11-23 18:20 ` Andreas Dilger
2001-11-24  1:02 ` David Gómez 
2001-11-23 22:59   ` Andreas Dilger
2001-11-24  0:07     ` H. Peter Anvin
2001-11-24  0:41       ` Andreas Dilger
2001-11-24  0:56         ` H. Peter Anvin
2001-11-24  4:25           ` Andreas Dilger [this message]
2001-11-24  5:05             ` H. Peter Anvin
2001-11-24 11:37               ` Michael Zimmermann
2001-11-25 10:33                 ` Mike Fedyk
2001-11-25 11:14                   ` Mike Castle
2001-11-25 22:55                     ` Mike Fedyk
2001-11-25 23:55                       ` Mike Fedyk
2001-11-24 17:26               ` Jamie Lokier
2001-11-24 17:49               ` Thorsten Glaser
2001-11-24 10:54       ` Marcel J.E. Mol
2001-11-24 21:19         ` Mike Castle
2001-11-24 22:49           ` Andreas Dilger
2001-11-25  3:34             ` Mike Castle

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=20011123212557.U1308@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=hpa@zytor.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®