Re: gjournal and fstab

On Thu, Nov 02, 2006 at 02:18:42PM +0000, Ceri Davies wrote, and it was proclaimed:
> On Thu, Nov 02, 2006 at 02:58:54PM +0100, Pawel Jakub Dawidek wrote:
> > On Thu, Nov 02, 2006 at 01:54:04PM +0000, Coleman Kane wrote:
> > > On Thu, Nov 02, 2006 at 11:14:04AM +0000, Ceri Davies wrote, and it was proclaimed:
> > > > On Wed, Nov 01, 2006 at 08:09:05PM -0500, Coleman Kane wrote:
> > > > > Hi, nice job with the gjournal update.
> > > > > 
> > > > > I am testing it out and am curious if you can tell me how best to add
> > > > > entries for gjournal filesystems in /etc/fstab.
> > > > > 
> > > > > It seems that if I add (as a line in fstab):
> > > > > /dev/ad0s1f.journal /usr ffs noatime,async 2 2
> > > > > 
> > > > > 
> > > > > Also, fsck seems to not know how to identify the filesystem type by mount
> > > > > nor by devicename. I must run fsck_ffs explicitly. I must also mount them
> > > > > manually, explicitly.
> > > > 
> > > > I have:
> > > > 	/dev/ad0s1g.journal /usr/home ufs rw,nosuid 2 2
> > > > 
> > > > which works ok.
> > > > 
> > > > Do you have GEOM_JOURNAL in your kernel or are you loading it from
> > > > loader.conf?
> > > > 
> > > > Ceri
> > > > -- 
> > > > That must be wonderful!  I don't understand it at all.
> > > >                                                   -- Moliere
> > > 
> > > I am loading it from loader.conf. In addition, I added -DUFS_GJOURNAL
> > > to /usr/src/sys/modules/ufs/Makefile (the CFLAGS) to compile in support
> > > for GJOURNAL to the ufs.ko module.
> > > 
> > > I am loading the geom_journal.ko from the loader as well. Perhaps it
> > > is unhappy that I left out the "rw" flag mount option, I will try it
> > > again with that added.
> > 
> > BTW. I suggest using 'async', which is safe when used with gjournal.
> 
> What's the recommentdation re: softupdates?
> 
> Ceri
> -- 
> That must be wonderful!  I don't understand it at all.
>                                                   -- Moliere

I figured out the problem. I ommitted "rw" from the mount options, so the
fstab reader couldn't detect if it was swap or not? Not expected behavior
from mount, fsck, but I can live with it.

--
coleman kane