gjournal is not automounted any more

[M. Warner Losh]

In message: <440945C2-252E-489A-902E-A499753A5EF8 at mac.com>
            Marcel Moolenaar <xcllnt at mac.com> writes:
: 
: On Jan 2, 2009, at 10:14 PM, M. Warner Losh wrote:
: 
: > In message: <20090103033543.GB77475 at dragon.NUXI.org>
: >            "David O'Brien" <obrien at freebsd.org> writes:
: > : On Fri, Jan 02, 2009 at 11:47:57AM -0700, M. Warner Losh wrote:
: > : > In message: <20090102091334.GA41230 at dragon.NUXI.org>
: > : >             "David O'Brien" <obrien at freebsd.org> writes:
: > : > : Before 'fsck' would read the lable for the FS type.  That has  
: > changed and
: > : > : thus you cannot just 'fsck /dev/ad1s1d' anymore.  So the FS  
: > type in fstab
: > : > : must be accurate.
: > : >
: > : > Why did that change?  I routinely have disks that aren't in my
: > : > /etc/fstab that I mount and this is a pain in the backside.
: > :
: > : Due to r186240 which:
: > :     Make gpart the default partitioning class on all platforms.
: > :
: > : Seems GEOM_PART_BSD does not like labels that GEOM_BSD did.
: >
: > Then why the change?  Shouldn't we make it like them for  
: > compatibility?
: 
: David's statement is incorrect. They like the same labels
: for all practical purposes. The problem at hand here is
: that fsck(8) & newfs(8) ask of GEOM_BSD what the partition
: type is. This means 2 things:
: 1.  Any platform that doesn't use the BSD disklabel by
:      default needs to have a proper /etc/fstab and is not
:      behaving the same as i386.
: 2.  Switching to GPT as the default partitioning scheme
:      yields the same problem.
: 
: As I said in an email to arch@, it's good to query the
: partition type to determine what to do when more specific
: information is missing (running fsck(8) vs fsck_ffs(8)).
: But it wasn't something that was there at the switchover
: point.

But my problems are with a platform that has BSD labels, and not GPT
labels, with a proper BSD label on the device.  mount works properly
without extra args, but fsck doesn't and this is a new behavior
introduced recently...  I know this because I'd been messing with this
disk in an enclosure several weeks ago and also playing with cardbus
fixes, some of which hung my machine (which means that the disk wasn't
cleanly unmounted, so I was doing a lot of fsck).

% disklabel da0s1
# /dev/da0s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a: 976767986       16    4.2BSD     2048 16384 28520 
  c: 976768002        0    unused        0     0         # "raw" part, don't edit

I'll have to go read things on arch at .

Warner