[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [linux-lvm] EXT2 to EXT3 LVM volume on Redhat



Yup exactly.
For example I have;
/dev/system/home /home ext3 data=journal 1 2

Its the bomb. I have a hell of a lot of dynamic data
in that /home so in event of a crash there was a big
chance of corruption. Not Any More!!!!!
8-)


> [mailto:linux-lvm-admin sistina com] On Behalf Of Aslak 
> Sommerfelt Skretting
> 
> This journal=data you talk about, is this an option to be 
> used with the 'mount' command?
> 
> ----- Original Message -----
> From: "Steve Wray" <steve wray paradise net nz>
> To: <linux-lvm sistina com>
> Sent: Tuesday, June 04, 2002 11:15 PM
> Subject: RE: [linux-lvm] EXT2 to EXT3 LVM volume on Redhat
> 
> 
> > > From: linux-lvm-admin sistina com 
> > > [mailto:linux-lvm-admin sistina com] On Behalf Of Aslak
> > >
> > > Hi again, and thanks for your quick reply!
> > >
> > > >----- Original Message -----
> > > >From: "Ben Lutgens" <blutgens sistina com>
> > [big snip]
> > > >Don't presume that because it's EXT3 that fscks are no longer 
> > > >necessary. Only thing the journal guarantees is that 
> your metadata 
> > > >won't become corrupt (i think journal=data mount option 
> fixes this
> > but
> > > >will affect performance and not neccessarily badly). If your
> > filesystem
> > > >has been shutdown cleanly many many times you could 
> still has some 
> > > >loss. A fsck should take care of that.
> >
> > Yup journal=data is fantastic; I wouldn't be without it
> > on the volume that holds the home directories!
> > I tend to allocate filesystems based on functionality;
> > tmp gets ext2 cos its fast,
> > places like /var/spool get XFS cos it can be grown
> > in a pinch.






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]