Messages in this thread | | | Date | Fri, 23 Nov 2001 21:25:57 -0700 | From | Andreas Dilger <> | Subject | Re: Moving ext3 journal file |
| |
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/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |