Yes, and the fix is in the last codereview I sent out. Hopefully
someone from the team can review it and it will make build 48. In the
meantime, 'zfs mount -a' after importing the pool will get you around
this problem. Sorry bout that.
- Eric
On Sat, Aug 26, 2006 at 08:46:50PM -0500, Mike Gerd
On 8/26/06, Mike Gerdts <[EMAIL PROTECTED]> wrote:
FWIW, I saw the same backtrace on build 46 doing some wierd stuff
documented at http://mgerdts.blogspot.com/. At the time I was booted
from cdrom media importing a pool that I had previously exported.
I got thinking... how can I outdo the "ME
On 8/26/06, James Dickens <[EMAIL PROTECTED]> wrote:
bash-3.00# pstack core.zpool.import
core 'core.zpool.import' of 644:zpool import -f pool
ff348adc zfs_prop_get (0, d, ffbfaef0, 400, 0, 0) + 14
ff34ed88 dataset_compare (c3f90, c3f9c, ffbfa2f0, 472a4, 14, ff396000) + 30
ff12f798 qsor
Hi
This weekend I upgraded my blade 1500 to b46 from b39, when importing
my pools, one raidz and another a single slice with -f because I
forgot to export the drives as usual, zpool dropped a core, file
somewhere after the pools were imported and before the filessysttems
were mounted. I ran zfs
