Sponsored Content
Operating Systems Solaris Using liveupgrade on single ZFS pool Post 302726811 by sylvain on Monday 5th of November 2012 08:46:49 AM
Old 11-05-2012
Hi,

No lucreate can generate a clone of your actual boot environement on the same zpool (rpool by befault).
 

9 More Discussions You Might Find Interesting

1. Solaris

ZFS Pool Mix-up

Hi all I plan to install Solaris 10U6 on some SPARC server using ZFS as root pool, whereas I would like to keep the current setup done by VxVM: - 2 internal disks: c0t0d0 and c0t1d0 - bootable root-volume (mirrored, both disks) - 1 non-mirrored swap slice - 1 non-mirrored slices for Live... (1 Reply)
Discussion started by: blicki
1 Replies

2. Solaris

unable to import zfs pool

# zpool import pool: emcpool1 id: 5596268873059055768 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: Sun Message ID: ZFS-8000-3C config: emcpool1 ... (7 Replies)
Discussion started by: fugitive
7 Replies

3. Infrastructure Monitoring

zfs - migrate from pool to pool

Here are the details. cnjr-opennms>root$ zfs list NAME USED AVAIL REFER MOUNTPOINT openpool 20.6G 46.3G 35.5K /openpool openpool/ROOT 15.4G 46.3G 18K legacy openpool/ROOT/rds 15.4G 46.3G 15.3G / openpool/ROOT/rds/var 102M ... (3 Replies)
Discussion started by: pupp
3 Replies

4. Solaris

ZFS pool question

I created a pool the other day. I created a 10 gig files just for a test, then deleted it. I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool. When I ls -al the pool I just... (6 Replies)
Discussion started by: mrlayance
6 Replies

5. Solaris

zfs pool migration

I need to migrate an existing raidz pool to a new raidz pool with larger disks. I need the mount points and attributes to migrate as well. What is the best procedure to accomplish this. The current pool is 6x36GB disks 202GB capacity and I am migrating to 5x 72GB disks 340GB capacity. (2 Replies)
Discussion started by: jac
2 Replies

6. Solaris

Best way to rename a ZFS Pool?

Other than export/import, is there a cleaner way to rename a pool without unmounting de FS? Something like, say "zpool rename a b"? Thanks. (2 Replies)
Discussion started by: verdepollo
2 Replies

7. Solaris

ZFS - overfilled pool

installed Solaris 11 Express on my server machine a while ago. I created a Z2 RAID over five HDDs and created a few ZFS filesystems on it. Once I (unintentionally) managed to fill the pool completely with data and (to my surprise) the filesystems stopped working - I could not read/delete any... (3 Replies)
Discussion started by: RychnD
3 Replies

8. Solaris

ZFS - Dataset / pool name are the same...cannot destroy

I messed up my pool by doing zfs send...recive So I got the following : zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT rpool 928G 17.3G 911G 1% 1.00x ONLINE - tank1 928G 35.8G 892G 3% 1.00x ONLINE - So I have "tank1" pool. zfs get all... (8 Replies)
Discussion started by: eladgrs
8 Replies

9. UNIX for Beginners Questions & Answers

Opening up ZFS pool as writable

I have installed FreeBSD onto a raw image file using QEMU Emulator successfully. I have formatted the image file using the ZFS file system (ZFS POOL). Using the following commands below I have successfully mounted the image file ready to be opened by zpool sudo losetup /dev/loop0 .img sudo... (1 Reply)
Discussion started by: alphatron150
1 Replies
ludesc(1M)																ludesc(1M)

NAME
ludesc - display or set boot environment description SYNOPSIS
/usr/sbin/ludesc -A BE_description | -f {filename | -} [-l error_log] [-o outfile] [-X] /usr/sbin/ludesc -n BE_name [-f filename | -] [-l error_log] [-o outfile] [-X] /usr/sbin/ludesc -n BE_name [-l error_log] [-o outfile] [-X] BE_description DESCRIPTION
The ludesc command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The ludesc command allows you to manipulate boot environment (BE) descriptions. A BE description is an optional attribute of a BE. It can be text or binary data. For example, it might be a string such as "S9 beta test BE" or it be a file that contains 8-bit multi-byte charac- ters. The ludesc command in general and the options to manipulate binary-format descriptions in particular are suitable for use in pro- grams. You create a BE description using ludesc or lucreate(1M). Only ludesc allows you to change a BE description or add a description following BE creation. While a BE description is associated with a BE name, it is not interchangeable with that name. No Live Upgrade command allows you to spec- ify a BE description instead of a BE name when performing an operation on a BE. A shell might restrict what you enter for a BE description (in both ludesc and lucreate(1M)). In entering a description, use the following guidelines: o Always enclose a description in single quotes ('), unless the description includes a single quote. o If your description includes a single quote, enclose the description in double quotes ("). You then must use an escape sequence (usu- ally a backslash []) to enter a character that is special to the shell. See sh(1) for a list of special characters and a description of the escape sequence mechanism. Descriptions that include many special characters might be more conveniently inserted in a file (-f option) than entered on a command line (-A option). When ludesc outputs a BE description, it does so exactly as the description was entered. Because of this feature, a description that is a text string does not have a concluding newline, which means the system prompt immediately follows the last character of the description. The ludesc command requires root privileges. OPTIONS
The ludesc command has the following options: -A BE_description Displays the BE name associated with BE_description. -f {filename | -} Specify the BE description contained in filename or read from stdin. When used without -n, displays the BE name associated with the specified BE description. Used with -n, changes the description for the specified BE to the description specified with -f. -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -n BE_name With no other arguments, displays the BE description for the specified BE. With the -f option or the BE_description operand, changes the description for the specified BE to that specified with -f or BE_description. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. OPERANDS
BE_description Used only with the -n option. BE_description replaces the current BE description for the specified BE. EXAMPLES
The following are examples of the use of ludesc. Example 1: Basic Use The first command, below, assigns a description to a BE. The second command returns the name of the BE associated with the specified description. The last command returns the description associated with a specified BE. # ludesc -n first_disk 'Test disk' Setting description for boot environment <first_disk>. Propagating the change of BE description to all BEs. # ludesc -A 'Test disk' first_disk # # ludesc -n first_disk Test disk# As seen above and noted in the DESCRIPTION, ludesc does not append a newline to the display of BE description that is a text string. Example 2: Using Binary Files The following commands are analogs of the preceding examples, substituting a binary file-here, a file containing a description in Russian, using the Cyrillic alphabet--for a text string. In the third command, note the use of a file to capture output. Sending output of a binary file to the console can produce erratic results. # ludesc -n first_disk -f arrayBE.ru Setting description for boot environment <first_disk>. Propagating the change of BE description to all BEs. # ludesc -f arrayBE.ru first_disk # ludesc -n first_disk > /tmp/arrayBE.out EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), ludelete(1M), lufslist(1M), lumake(1M), lumount(1M), lurename(1M), lus- tatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 ludesc(1M)
All times are GMT -4. The time now is 05:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy