Lori,
Thanks for taking the time to reply. Please see below.
Karl
Lori Alt wrote:> Karl Rossing wrote:
>> Currently running b93.
>>
>> I''d like to try out b101.
>>
>> I previously had b90 running on the system. I ran ludelete snv_90_zfs
>>
>> but I still see snv_90_zfs:
>> $ zfs list
>> NAME USED AVAIL REFER MOUNTPOINT
>> rpool 52.9G 6.11G 31K /rpool
>> rpool/ROOT 41.0G 6.11G 19K /rpool/ROOT
>> rpool/ROOT/snv_90_zfs 29.6G 6.11G 29.3G /.alt.tmp.b-Ugf.mnt/
>> rpool/ROOT/snv_90_zfs at snv_93 319M - 29.6G -
>> rpool/ROOT/snv_93 11.4G 6.11G 26.4G /
>> rpool/dump 3.95G 6.11G 3.95G -
>> rpool/swap 8.00G 13.1G 1.05G -
>>
>>
>> I also did some house cleaning and delete about 10GB of data but I
>> don''t see that reflected with zfs list or df -h.
>>
>> Should I be concerned before I do a lucreate/luupgrade?
>>
> Probably, because it looks like you might not
> have enough space.
>
do I need to zfs destroy rpool/ROOT/snv_90_zfs and
rpool/ROOT/snv_90_zfs at snv_93?
> Was there any output from ludelete?
I didn''t capture that :(> If you do a lustatus now, does the BE still show up?
>
> lori
lustatus:
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
snv_93 yes yes yes no -
The new be i''m calling snv_101
lucreate -c snv_93 -n snv_101
Checking GRUB menu...
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <snv_93> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <snv_101>.
Source boot environment is <snv_93>.
Creating boot environment <snv_101>.
Cloning file systems from boot environment <snv_93> to create boot
environment <snv_101>.
Creating snapshot for <rpool/ROOT/snv_93> on <rpool/ROOT/snv_93 at
snv_101>.
Creating clone for <rpool/ROOT/snv_93 at snv_101> on
<rpool/ROOT/snv_101>.
Setting canmount=noauto for </> in zone <global> on
<rpool/ROOT/snv_101>.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE
<snv_101> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <snv_101> in GRUB menu
Population of boot environment <snv_101> successful.
Creation of boot environment <snv_101> successful.
lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
snv_93 yes yes yes no -
snv_101 yes no no yes -
Then when I luupgrade -u -n snv_101 -s /export/Sol11_x86_b101 the server
freezes and reboots. I don''t see any error message on the console or
/var/adm/messages.
/var/crash/server_name has:
-rw-r--r-- 1 root root 1689799 Oct 28 15:04 unix.0
-rw-r--r-- 1 root root 2713427 Oct 28 15:20 unix.1
-rw-r--r-- 1 root root 2713427 Oct 28 15:39 unix.2
-rw-r--r-- 1 root root 1133973504 Oct 28 15:05 vmcore.0
-rw-r--r-- 1 root root 518361088 Oct 28 15:21 vmcore.1
-rw-r--r-- 1 root root 488185856 Oct 28 15:40 vmcore.2
CONFIDENTIALITY NOTICE: This communication (including all attachments) is
confidential and is intended for the use of the named addressee(s) only and
may contain information that is private, confidential, privileged, and
exempt from disclosure under law. All rights to privilege are expressly
claimed and reserved and are not waived. Any use, dissemination,
distribution, copying or disclosure of this message and any attachments, in
whole or in part, by anyone other than the intended recipient(s) is strictly
prohibited. If you have received this communication in error, please notify
the sender immediately, delete this communication from all data storage
devices and destroy all hard copies.