Hi Nirmal,

* Nirmal Agarwal ([email protected]) wrote:
> Hi all
> 
> I was trying to re-start the auto-installer service after it fails
> because of a known bug(CR 7060813). After I re-enable the service,
> it fails with the following message in the
> /system/volatile/install_log:
> 
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py",
> line 565, in execute_checkpoints
>     thread.start()
>   File "/usr/lib/python2.6/threading.py", line 477, in run
>     self.__target(*self.__args, **self.__kwargs)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py",
> line 816, in _execute_checkpoints
>     checkpoint.execute(dry_run)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/auto_install/checkpoints/target_selection.py",
> line 3293, in execute
>     self.select_targets(from_manifest, discovered)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/auto_install/checkpoints/target_selection.py",
> line 3188, in select_targets
>     new_target = self.__handle_target(from_manifest[0])
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/auto_install/checkpoints/target_selection.py",
> line 3014, in __handle_target
>     self.__validate_logical(new_desired_target)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/auto_install/checkpoints/target_selection.py",
> line 1234, in __validate_logical
>     "BE must be unique." % (child.name))
> SelectionError: BE 'solaris' already exists. BE must be unique.
> 
> 
> It appears that the filesystem and BE created earlier was not destroyed.
> 
> jack@auto-client:~# zfs list
> NAME                 USED  AVAIL  REFER  MOUNTPOINT
> rpool               1.47G  14.2G    31K  /rpool
> rpool/ROOT          98.5M  14.2G    31K  legacy
> rpool/ROOT/solaris  98.4M  14.2G  98.4M  /a
> rpool/dump           703M  14.2G   681M  -
> rpool/export          63K  14.2G    32K  /export
> rpool/export/home     31K  14.2G    31K  /export/home
> rpool/swap           703M  14.2G   681M  -
> jack@auto-client:~# zpool list
> NAME    SIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
> rpool  15.9G  1.43G  14.4G   8%  1.00x  ONLINE  -
> jack@auto-client:~# beadm list
> BE      Active Mountpoint Space  Policy Created
> --      ------ ---------- -----  ------ -------
> solaris -      /a         98.43M static 2011-07-08 13:31
> jack@auto-client:~#
> 
> Should restarting the service clear the filesystem ?

I'm by no means an expert on AI these days, but the install aborted (due
to the bug you mentioned) and so no cleanup would have taken place (if
there even is any in AI).  So, no, I wouldn't expect that just
restarting AI would clear the filesystem.  In fact I'm pretty sure we
wouldn't want to do that.  Something failed with the previous
installation attempt, destroying the filesystem explicitly upon restart
could wipe out any diagnostic data that may be available.

Cheers,

-- 
Glenn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to