Problem in SVM after live upgrade Post: 302716945

Sponsored Content

Operating Systems Solaris Problem in SVM after live upgrade Post 302716945 by amity on Wednesday 17th of October 2012 10:43:16 AM

10-17-2012

Registered User

Please find the output

Code:

bash-3.2# uname -a
SunOS sunvm 5.10 Generic_147441-01 i86pc i386 i86pc
bash-3.2#
bash-3.2# df /
/                  (/dev/dsk/c0d1s0   ): 1875718 blocks   545592 files
bash-3.2# df -h
Filesystem             size   used  avail capacity  Mounted on
/dev/dsk/c0d1s0        5.8G   4.9G   857M    86%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   569M   992K   568M     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
                       5.8G   4.9G   857M    86%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   568M    40K   568M     1%    /tmp
swap                   568M    32K   568M     1%    /var/run
bash-3.2#
bash-3.2#
bash-3.2# metastat -c
d30              m  5.4GB d31
    d31          s  5.4GB c0d0s7
d20              m  517MB d21
    d21          s  517MB c0d0s1
d10              m  5.9GB d11
    d11          s  5.9GB c0d0s0
bash-3.2#
bash-3.2# metadb
^[[A    flags           first blk       block count
     a m  pc luo        16              8192            /dev/dsk/c0d0s5
     a    pc luo        8208            8192            /dev/dsk/c0d0s5
     a    pc luo        16400           8192            /dev/dsk/c0d0s5
bash-3.2#

Last edited by Scott; 10-17-2012 at 12:49 PM.. Reason: Code tags...

amity

View Public Profile for amity

Find all posts by amity

9 More Discussions You Might Find Interesting

1. Solaris

Live upgrade Issue

Hi, I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7

2. Solaris

Problem with live upgrade creation: Telling me metadevices do not exist

Hi I am having a problem creating my live upgrade environment. Here is the error I get: root@server:/# lucreate -c SOL10_18May -n SOL10_19May -z /lu_excludelist -m /:dev/md/dsk/d0:ufs -m /var:/dev/md/dsk/d4:ufs -m /export/home:/dev/md/dsk/d6:ufs -m -:/dev/md/dsk/d3:swap -C...

3. Solaris

Live upgrade question

I want to basically update an ABE that someone created a few months back. I'm sure stuff has changed since it was made, and I was going to delete it and create a new one. But from what I'm looking at, the lumake appears like it would be a faster approach. I want to use live upgrade to...

4. Solaris

Live Upgrade Issue

I tried a live upgrade for one my solaris 10u8 server which didnt go sucessfull and after that i now have following mounts in memory. df: cannot statvfs /.alt.sol10u8_2/var: No such file or directory df: cannot statvfs /.alt.sol10u8_2/var/run: No such file or directory df: cannot statvfs...

5. Emergency UNIX and Linux Support

Live Upgrade Query

I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade. OS DVD is mounted on /mnt Boot environments are Solaris9old (Active now)...

6. Solaris

Live upgrade query

Hi All, Is it possible to use external san disk for creating alternate boot environment and boot from it.My root disk is about 70 gb and i want to use external san disk for 272gb to create alternate boot environment.If this is possible can you please redirect me some good documents, i had...

7. Solaris

Live upgrade first steps

Hello Guys, I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me. The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade? 1. before creating the new boot environment? or 2. after creating...

8. Solaris

Powerpath upgrade with SVM disksets

Hi all I am running the following hardware: 2 SUN Solaris 10 machines They are connected to EMC clarion LUNs We are running a Sun Cluster 3.2 managing both nodes We are using Solaris Volume Manager to handle the shared storage for the cluster. It is using a number of named disk sets that is...

9. Solaris

Patching using live upgrade - with non-globalzone

Hi all, I would like to ask what will be the best practice for the following setup / - c0t0d0s0 - current BE (named First) / - c0t0d1s0 - alternate BE (name Second) i have a non-global zone with zonepath in /zones/myzone /mnt/opt - c0t0d2s6 (shared between the 2 BE)...

LEARN ABOUT CENTOS

redhat-upgrade-tool

REDHAT-UPGRADE-TOOL(8)					  redhat-upgrade-tool User Manual				    REDHAT-UPGRADE-TOOL(8)

NAME

       redhat-upgrade-tool - Red Hat Upgrade tool

SYNOPSIS

       redhat-upgrade-tool [OPTIONS] SOURCE

DESCRIPTION

       redhat-upgrade-tool is the Red Hat Upgrade tool.

       The redhat-upgrade-tool client runs on the system to be upgraded. It determines what packages are needed for upgrade and gathers them from
       the source(s) given. It also fetches and sets up the boot images needed to run the upgrade and sets up the system to perform the upgrade at
       next boot.

       The actual upgrade takes place when the system is rebooted, using the boot images set up by redhat-upgrade-tool. The upgrade initrd starts
       the existing system (mostly) as normal, lets it mount all the local filesystems, then starts the upgrade.

       When the upgrade finishes, it reboots the system into the newly-upgraded OS.

OPTIONS

   Optional arguments
       -h, --help
	   Show a help message and exit.

       -v, --verbose
	   Print more info.

       -d, --debug
	   Print lots of debugging info.

       --debuglog DEBUGLOG
	   Write debugging output to the given file. Defaults to /var/log/redhat-upgrade-tool.log.

       --reboot
	   Automatically reboot to start the upgrade when ready.

   SOURCE
       These options tell redhat-upgrade-tool where to look for the packages and boot images needed to run the upgrade. At least one of these
       options is required.

       --device [DEV]
	   Device or mountpoint of mounted install media. If DEV is omitted, redhat-upgrade-tool will scan all currently-mounted removable devices
	   (USB disks, optical media, etc.)

       --iso ISO
	   Installation image file.

       --network VERSION
	   Online repos matching VERSION (a number or "rawhide")

       Multiple sources may be used, if desired.

   Additional options for --network
       --enablerepo REPOID
	   Enable one or more repos (wildcards allowed).

       --disablerepo REPOID
	   Disable one or more repos (wildcards allowed).

       --addrepo REPOID=[@]URL
	   Add the repo at URL. Prefix URL with @ to indicate that the URL is a mirrorlist.

       --instrepo REPOID
	   Get upgrader boot images from the repo named REPOID. The repo must contain a valid .treeinfo file which points to the location of
	   usable kernel and upgrade images.

   Cleanup commands
       --resetbootloader
	   Remove any modifications made to bootloader configuration.

       --clean
	   Clean up everything written by redhat-upgrade-tool.

EXAMPLES

       redhat-upgrade-tool --network 7.0 --instrepo <repo URL>

       Upgrade to RHEL 7.0 by downloading all needed packages and data from the specified repository.

       redhat-upgrade-tool --device --network 7.0

       Upgrade to RHEL 7.0 using install media mounted somewhere on the system, fetching updates from the network if needed.

EXIT STATUS

       0
	   Success.

       1
	   Cancelled by user, failure writing files to disk, or other unknown error

       2
	   Failed to download/copy files from the given SOURCE

       3
	   RPM upgrade transaction test failed

BUGS

       The --iso image must be on a filesystem listed in /etc/fstab.

AUTHORS

       Will Woods <wwoods@redhat.com>

redhat-upgrade-tool						    11/08/2013						    REDHAT-UPGRADE-TOOL(8)