[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kern/124973: [gjournal] [patch] boot order affects geom_journal consumers selection
- To: freebsd-geom_(_at_)_FreeBSD_(_dot_)_org
- Subject: Re: kern/124973: [gjournal] [patch] boot order affects geom_journal consumers selection
- From: Aragon Gouveia <aragon_(_at_)_phat_(_dot_)_za_(_dot_)_net>
- Date: Sat, 25 Oct 2008 18:00:09 GMT
- Cc:
- Reply-to: Aragon Gouveia <aragon_(_at_)_phat_(_dot_)_za_(_dot_)_net>
The following reply was made to PR kern/124973; it has been noted by GNATS.
From: Aragon Gouveia <aragon_(_at_)_phat_(_dot_)_za_(_dot_)_net>
To: bug-followup_(_at_)_FreeBSD_(_dot_)_org, Alexei_(_dot_)_Volkov_(_at_)_softlynx_(_dot_)_ru
Cc:
Subject: Re: kern/124973: [gjournal] [patch] boot order affects geom_journal consumers selection
Date: Sat, 25 Oct 2008 19:33:29 +0200
Hi there,
I just hit my head against this tonight on 7.1-BETA2. My filesystems were
using ad0s1a, etc. before enabling gjournal. After creating a provider and
enabling gjournal in loader.conf, all the filesystem device nodes got
renamed to ad0a, etc.
I'm not sure if this has been fixed since Alexei filed it or if what I'm
describing is that fix, but all I did to fix things for me was to recreate
my gjournal provider with the '-h' argument:
gjournal label -h /dev/ad0s1g
And now everything behaves when gjournal is enabled in loader.conf. :)
Regards,
Aragon
_______________________________________________
freebsd-geom_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-geom
To unsubscribe, send any mail to "freebsd-geom-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org