on 20/12/2012 00:14 Garrett Cooper said the following:
On Thu, Dec 13, 2012 at 2:56 PM, Freddie Cash fjwc...@gmail.com wrote:
...
You could at least point to the FreeBSD Forums version of that post. :)
https://forums.freebsd.org/showthread.php?t=31662
Andriy,
I figured out my
on 20/12/2012 00:34 Kimmo Paasiala said the following:
What is the status of the MFC process to 9-STABLE? I'm on 9-STABLE
r244407, should I be able to boot from this ZFS pool without
zpool.cache?
I haven't MFC-ed the change as of now.
After I eventually MFC it you should be able to boot from
On Thu, Dec 13, 2012 at 2:56 PM, Freddie Cash fjwc...@gmail.com wrote:
...
You could at least point to the FreeBSD Forums version of that post. :)
https://forums.freebsd.org/showthread.php?t=31662
Andriy,
I figured out my problem. It was really, really stupid PEBKAC (copied
a KERNCONF from
On Wed, Nov 28, 2012 at 8:35 PM, Andriy Gapon a...@freebsd.org wrote:
Recently some changes were made to how a root pool is opened for root
filesystem
mounting. Previously the root pool had to be present in zpool.cache. Now it
is
automatically discovered by probing available GEOM
on 07/12/2012 02:33 Garrett Cooper said the following:
On Thu, Dec 6, 2012 at 3:08 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please document the process to make this work in UPDATING (or at least
the fact that this behavior was changed).
I'm debugging moving from 9.1-RC2 to
on 07/12/2012 02:55 Garrett Cooper said the following:
If I try and let it import the pool at boot it claims the pool is in a
FAULTED state when I point mountroot to /dev/cd0 (one of gjb's
snapshot CDs -- thanks!), run service hostid onestart, etc. If I
export and try to reimport the pool it
On Thu, Dec 13, 2012 at 3:20 AM, Andriy Gapon a...@freebsd.org wrote:
...
One thing that I recommend to all ZFS users is to make use of boot
environments.
They are very easy, very convenient and may save a lot of trouble.
Use either any of the tool available in ports (e.g. sysutils/beadm)
On Thu, Dec 13, 2012 at 3:24 AM, Andriy Gapon a...@freebsd.org wrote:
...
This sounds messy, not sure if it has any informative value.
I think I've seen something like this after some reason ZFS import from
upsteam
when my kernel and userland were out of sync.
Do you do a full boot from
On Thu, Dec 13, 2012 at 2:49 PM, Garrett Cooper yaneg...@gmail.com wrote:
On Thu, Dec 13, 2012 at 3:20 AM, Andriy Gapon a...@freebsd.org wrote:
...
One thing that I recommend to all ZFS users is to make use of boot
environments.
They are very easy, very convenient and may save a lot of
On Mon, Dec 10, 2012 at 1:25 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Going back in time a until the start of November didn't help. This
zpool get version for both of the pools is quite interesting -- in
particular, why is the value unset (-)? I've provided the zdb -C
info as well
On Thu, Dec 6, 2012 at 4:55 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
(Removing bogus list)
If I try and let it import the pool at boot it claims the pool is in a
FAULTED state when I point mountroot to /dev/cd0 (one of gjb's
snapshot CDs -- thanks!), run service hostid onestart,
On Thu, Dec 6, 2012 at 3:08 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please document the process to make this work in UPDATING (or at least
the fact that this behavior was changed).
I'm debugging moving from 9.1-RC2 to CURRENT [as of Tuesday] as it
hasn't been as smooth as some of
On Thu, Dec 6, 2012 at 4:33 PM, Garrett Cooper yaneg...@gmail.com wrote:
On Thu, Dec 6, 2012 at 3:08 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please document the process to make this work in UPDATING (or at least
the fact that this behavior was changed).
I'm debugging moving from
On Fri, Nov 30, 2012 at 08:51:48AM +0200, Daniel Braniss wrote:
Recently some changes were made to how a root pool is opened for root
filesystem
mounting. Previously the root pool had to be present in zpool.cache. Now
it is
automatically discovered by probing available GEOM
on 01/12/2012 15:36 Pawel Jakub Dawidek said the following:
On Fri, Nov 30, 2012 at 08:51:48AM +0200, Daniel Braniss wrote:
GREATE in a diskless environment, /boot is read only, and the
zpool.cache issue has been bothering me ever since, there was no way (and
I tried) to re route it.
I
Recently some changes were made to how a root pool is opened for root
filesystem
mounting. Previously the root pool had to be present in zpool.cache. Now it
is
automatically discovered by probing available GEOM providers.
The new scheme is believed to be more flexible. For example, it
16 matches
Mail list logo
