fsck always errors out during boot with gjournal

[Gary Jennejohn]

I'm running 9-CURRENT AMD64.

I decided to use gjournal on /home.

I successfully did newfs -J to enable journaling anf gjournal -label
to get a ada0s1f.journal device.

The problem is that, unless I set fs_passno in /etc/fstab to 0, fsck
always complains that it can't find the superblock and booting fails.

But I always see messages that the journal is OK when booting:
GEOM_JOURNAL: Journal 4260374310: ada0s1f contains data.
GEOM_JOURNAL: Journal 4260374310: ada0s1f contains journal.
GEOM_JOURNAL: Journal ada0s1f clean.

So, is this normal behavior?  Seems rather peculiar to me.

---
Gary Jennejohn