Rodrigo Barbosa wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, Jun 11, 2005 at 09:06:26PM -0400, Mark Weaver wrote: > >>Peter Farrow wrote: >> >>>If you use ghost, you need to edit fstab to make it look for ext 2 file >>>systems as ghost doesn't copy the journal inode of ext 3. >>> >>>then use tune2fs -j /dev/....... to add it back in and edit the fstab >>>back to ext3 on the new drive... >> >>well shucks! someone should've told me that before I ghosted my web >>server's hard drive, three hard drives of client machines and all the >>countless other "ext3" file systems that my boss has done in recent past >>using ghost. Darn, if we've known its not supposed to work then we may >>not have been able to do what we've already done. ;) >> >>in short, yes it does and no you don't have to do anything special with >>fstab to make ghost work which is why I made the comment I did about it >>just working. > > > Actually, both of you are right :) > > Under normal condition, you can just ignore the journal metadata. > However, if you are cloning right after a crash, you might want to > be careful, since the filesystem might be inconsistent. > > []s > > - -- > Rodrigo Barbosa <rodrigob at suespammers.org> > "Quid quid Latine dictum sit, altum viditur" > "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) you've got a point there because I have run into a few where there were definite filesystem problems that I couldn't get around. Which is why in another post I asked if you'd layout your process that you've mentioned. I'm really curious about how you're doing it. Anything Linux I can learn is always a good thing. -- Mark ----------------------------------------------------------- Paid for by Penguins against modern appliances(R) Linux User Since 1996 Powered by Mandrake Linux 8.2, 10.0 & RHEL 4