I finally had some time to revisit the zpool import issue I have been
having.  I wanted to pinpoint exactly when the problem was introduced.
After doing a physical binary search by downloading and creating USB keys,
I was able to determine that the problem was introduced with the SmartOS
20141113T164921Z release.   All versions before that (up to and including
20141030T164802Z) have no problems importing my zpool.  However,
versions 20141113T164921Z and later all produce the "WARNING: can't open
objset for zones" error I mentioned previously.  When doing a "zpool
upgrade" on 20141113T164921Z it shows that there are no upgrades available
to apply to my pool, so I don't think the issue has anything to do with the
newer version expecting newer zpool features or anything like that.

Does anyone know of any good dtrace scripts that I could use to track down
the problem?  I found some old postings on the web by Eric Schrock
mentioning a raidz dtrace script.  However, my pool consists of 3 sets of
mirrored vdevs so that doesn't sound like the right script for me.

Of course, the reason I'm eager to boot on the latest releases is so that I
can test LX branded zones.  I tried to use my existing 20141030T164802Z
image (the latest image I can successfully boot) to provision the new
Centos6 LX image, but it gives the errors such as:

Command failed: zone '501eb8e5-e5c7-4df8-b390-2bff3f2f5696': exec
/usr/lib/brand/lx/lx_boot 501eb8e5-e5c7-4df8-b390-2bff3f2f5696
/zones/501eb8e5-e5c7-4df8-b390-2bff3f2f5696 failed

zone '501eb8e5-e5c7-4df8-b390-2bff3f2f5696': error removing flows for net0

zoneadm: zone '501eb8e5-e5c7-4df8-b390-2bff3f2f5696': call to zoneadmd
failed

Any assistance would be greatly appreciated.

Sincerely,
Neal Lauver

On Sat, Feb 21, 2015 at 11:19 PM, Neal Lauver <[email protected]> wrote:

> I thought I should provide some more info.  Here's how the system looks
> when it successfully boots on the 20140724T221203Z image:
>
> [root@smartos ~]# uname -a
>
> SunOS 00-25-90-d4-16-48 5.11 joyent_20140724T221203Z i86pc i386 i86pc
>
> [root@smartos ~]# zpool list -v zones
>
> NAME                        SIZE  ALLOC   FREE   FRAG  EXPANDSZ    CAP
> DEDUP  HEALTH  ALTROOT
>
> zones                      2.72T  2.16T   574G    39%         -    79%
> 1.00x  ONLINE  -
>
>   mirror                    928G   736G   192G    39%         -
>
>     c0t50014EE25DEAD967d0      -      -      -      -         -
>
>     c0t50014EE0578BDE41d0      -      -      -      -         -
>
>   mirror                    928G   738G   190G    39%         -
>
>     c0t50014EE2B011E30Cd0      -      -      -      -         -
>
>     c0t50014EE25F75124Ad0      -      -      -      -         -
>
>   mirror                    928G   736G   192G    39%         -
>
>     c0t50014EE20A14CE3Fd0      -      -      -      -         -
>
>     c0t50014EE00236A48Cd0      -      -      -      -         -
>
> [root@smartos ~]# zpool status -v zones
>
>   pool: zones
>
>  state: ONLINE
>
>   scan: scrub repaired 0 in 27h58m with 0 errors on Wed Feb 18 15:15:26
> 2015
>
> config:
>
>
>         NAME                       STATE     READ WRITE CKSUM
>
>         zones                      ONLINE       0     0     0
>
>           mirror-0                 ONLINE       0     0     0
>
>             c0t50014EE25DEAD967d0  ONLINE       0     0     0
>
>             c0t50014EE0578BDE41d0  ONLINE       0     0     0
>
>           mirror-1                 ONLINE       0     0     0
>
>             c0t50014EE2B011E30Cd0  ONLINE       0     0     0
>
>             c0t50014EE25F75124Ad0  ONLINE       0     0     0
>
>           mirror-2                 ONLINE       0     0     0
>
>             c0t50014EE20A14CE3Fd0  ONLINE       0     0     0
>
>             c0t50014EE00236A48Cd0  ONLINE       0     0     0
>
>
> errors: No known data errors
>
> [root@smartos ~]# zpool get version zones
>
> NAME   PROPERTY  VALUE    SOURCE
>
> zones  version   -        default
>
>
> Thanks,
>
> Neal Lauver
>
> On Sat, Feb 21, 2015 at 11:04 PM, Neal Lauver <[email protected]>
> wrote:
>
>> Hello all,
>>
>> My apologies if this has been explained elsewhere, but I have been unable
>> to find any mention of it after searching.  I have been unable to use the
>> recent SmartOS USB images (specifically smartos-20150205T075858Z-USB.img
>> and smartos-20150219T102159Z-USB.img).  When I boot on them I get the
>> following errors:
>>
>> SunOS Release 5.11 Version joyent_20150219T102159Z 64-bit
>>
>> Copyright (c) 2010-2015, Joyent Inc. All rights reserved.
>>
>> WARNING: can't open objset for zones
>>
>> WARNING: can't open objset for zones
>>
>> WARNING: can't open objset for zones
>>
>> WARNING: can't open objset for zones
>>
>> cannot open 'zones': dataset does not exist
>>
>> cannot open 'zones': dataset does not exist
>>
>> /usr/bin/sysinfo: line 261: +  : syntax error: operand expected (error
>> token is
>>
>> "+  ")
>>
>> As you would imagine, once it fails to detect the existing "zones" pool
>> it launches the default initial configuration menu.
>>
>> I usually boot on image 20140724T221203Z which still has no problems
>> booting.  I haven't tried to upgrade to a newer version until just
>> recently, so I don't know when this problem might have been introduced over
>> the past several months.   I haven't done anything unusual with my
>> configuration that I can think of -- my pool has the default name of
>> "zones".
>>
>> Has anyone else seen this before?  Any words of wisdom?
>>
>> Your assistance is greatly appreciated.
>>
>> Thanks,
>>
>> Neal Lauver
>>
>
>



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to