10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am upgrading Veritas from 5.1 to 6.0.1/6.0.5 in a Solaris 10 u8 server with OS mirrored (rpool) in zfs/zpool configuration.
I need to split it to have a quick way to backout in case of failure (make splitted mirror side bootable for a quick revert, like booting from it). I remember... (3 Replies)
Discussion started by: feroccimx
3 Replies
2. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies
3. Solaris
Hi everyone,
I'm hoping someone can help me out here. I've googled lots and don't think I can find an easy answer to this.
We're in the process of upgrading Solaris from v10 5/08 to v10 9/10. The zpools for luns are currently at version 10, and I understand Solaris v10 9/10 has support for... (3 Replies)
Discussion started by: badoshi
3 Replies
4. Solaris
running VM server for Sparc on a Solaris 11 server. I have a Guest LDOm that had two seperate zpools running, one for the zones and one for the OS. The OS was corrupted and had to be replaced. The zones zfs file system is intact I think. I still have access to the disk and can still see it in... (3 Replies)
Discussion started by: os2mac
3 Replies
5. BSD
I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error:
# zpool create zfspool /dev/da0s1a
cannot create 'zfspool': no such pool or dataset
# zpool create zfspool /dev/da0
cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies
6. Solaris
i need how to use graphical user interface for zfs using web console ,
thanks (3 Replies)
Discussion started by: Amr
3 Replies
7. Solaris
Hi All,
I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties.
File seems to be in packed format.I am not sure how to unpack it.
But from opensolaris code base we can see that they have used libz for uncompromising this file, but... (0 Replies)
Discussion started by: shailesh_111
0 Replies
8. Solaris
I am using Solaris 10, and would like a web gui for mail or can replace the mail server if needed, it doesnt need to be anything elaborate, just something where i can view mail via a web browser rather than command line and hitting 'd' a 1000 times to delete all my cron job mails etc :p
I've... (8 Replies)
Discussion started by: ippy98
8 Replies
9. Solaris
All,
I am trying to get the Sun Web Console to work with ZFS and am not getting anywhere. When I first tried to get the web console https://server:6789/zfs it gave me a page can't be displayed (500 error). I've played around and performed the following and can now get it to log in and display... (7 Replies)
Discussion started by: darkoth
7 Replies
10. Solaris
Hi there,
I recently discovered the ZFS GUI and wanted to try it out. :)
The login page works and also the next page. But if I choose "ZFS Administration", the page stays blank and the browser reports an error:
Pictures:... (5 Replies)
Discussion started by: Ebbi
5 Replies
System Administration Commands beadm(1M)
NAME
beadm - utility for managing zfs boot environments
SYNOPSIS
/usr/sbin/beadm
beadm create [-a] [-d description]
[-e non-activeBeName | beName@snapshot]
[-o property=value] ... [-p zpool] beName
beadm create beName@snapshot
beadm destroy [-fF] beName | beName@snapshot
beadm list [-a | -ds] [-H] [beName]
beadm mount beName mountpoint
beadm unmount [-f] beName
beadm rename beName newBeName
beadm activate beName
DESCRIPTION
The beadm command is the user interface for managing zfs
Boot Environments (BEs). This utility is intended to be
used by System Administrators who want to manage multiple
Solaris Instances on a single system.
The beadm command will support the following operations:
- Create a new BE, based on the active BE.
- Create a new BE, based on an inactive BE.
- Create a snapshot of an existing BE.
- Create a new BE, based on an existing snapshot.
- Create a new BE, and copy it to a different zpool.
- Activate an existing, inactive BE.
- Mount a BE.
- Unmount a BE.
- Destroy a BE.
- Destroy a snapshot of a BE.
- Rename an existing, inactive BE.
- Display information about your snapshots and datasets.
SUBCOMMANDS
The beadm command has the subcommands and options listed
below. Also see EXAMPLES below.
beadm
Displays command usage.
beadm create [-a] [-d description]
[-e non-activeBeName | beName@snapshot]
[-o property=value] ... [-p zpool] beName
Creates a new boot environment named beName. If the
-e option is not provided, the new boot environment will
be created as a clone of the currently running boot
environment. If the -d option is provided then the
description is also used as the title for the BE's
entry in the GRUB menu for x86 systems or in the boot
menu for SPARC systems. If the -d option is not provided,
beName will be used as the title.
-a Activate the newly created BE
upon creation. The default is to
not activate the newly created
BE.
-d description Create a new BE with a desc-
ription associated with it.
-e non-activeBeName Create a new BE from an existing
inactive BE.
-e beName@snapshot Create a new BE from an existing
snapshot of the BE named beName.
-o property=value Create the datasets for new BE
with specific ZFS properties.
Multiple -o options can be
specified. See zfs(1M) for more
information on the -o option.
-p zpool Create the new BE in the
specified zpool. If this is not
provided, the default behavior is
to create the new BE in the same
pool as as the origin BE.
beadm create beName@snapshot
Creates a snapshot of the existing BE named beName.
beadm destroy [-fF] beName | beName@snapshot
Destroys the boot environment named beName or destroys
an existing snapshot of the boot environment named
beName@snapshot. Destroying a boot environment will also
destroy all snapshots of that boot environment. Use
this command with caution.
-f Forcefully unmount the boot environment
if it is currently mounted.
-F Force the action without prompting to
verify the destruction of the boot
environment.
beadm list [-a | -ds] [-H] [beName]
Lists information about the existing boot environment
named beName, or lists information for all boot
environments if beName is not provided. The 'Active'
field indicates whether the boot environment is active
now, represented by 'N'; active on reboot, represented
by 'R'; or both, represented by 'NR'.
Each line in the machine parasable output has the boot
environment name as the first field. The 'Space' field
is displayed in bytes and the 'Created' field is
displayed in UTC format. The -H option used with no
other options gives the boot environment's uuid in the
second field. This field will be blank if the boot
environment does not have a uuid. See the EXAMPLES
section.
-a Lists all available information about
the boot environment. This includes
subordinate file systems and snapshots.
-d Lists information about all subordinate
file systems belonging to the boot
environment.
-s Lists information about the snapshots
of the boot environment.
-H Do not list header information. Each
field in the list information is
separated by a semicolon.
beadm mount beName mountpoint
Mounts a boot environment named beName at mountpoint.
mountpoint must be an already existing empty directory.
beadm unmount [-f] beName
Unmounts the boot environment named beName.
-f Forcefully unmount the boot environment
even if its currently busy.
beadm rename beName newBeName
Renames the boot environment named beName to newBeName.
beadm activate beName
Makes beName the active BE on next reboot.
EXAMPLES
Example 1: Create a new BE named BE1, by cloning the current
live BE.
# beadm create BE1
Example 2: Create a new BE named BE2, by cloning the existing
inactive BE named BE1.
# beadm create -e BE1 BE2
Example 3: Create a snapshot named now of the existing BE
named BE1.
# beadm create BE1@now
Example 4: Create a new BE named BE3, by cloning an existing
snapshot of BE1.
# beadm create -e BE1@now BE3
Example 5: Create a new BE named BE4 based on the currently
running BE. Create the new BE in rpool2.
# beadm create -p rpool2 BE4
Example 6: Create a new BE named BE5 based on the currently
running BE. Create the new BE in rpool2, and create
its datasets with compression turned on.
# beadm create -p rpool2 -o compression=on BE5
Example 7: Create a new BE named BE6 based on the currently
running BE and provide a description for it.
# beadm create -d "BE6 used as test environment" BE6
Example 8: Activate an existing, inactive BE named BE3.
# beadm activate BE3
Example 9: Mount the BE named BE3 at /mnt.
# beadm mount BE3 /mnt
Example 10: Unmount the mounted BE named BE3.
# beadm unmount BE3
Example 11: Destroy the BE named BE3 without verification.
# beadm destroy -f BE3
Example 12: Destroy the snapshot named now of BE1.
# beadm destroy BE1@now
Example 13: Rename the existing, inactive BE named BE1 to
BE3.
# beadm rename BE1 BE3
Example 14: List all existing boot environments.
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
BE2 - - 72.0K static 2008-05-21 12:26
BE3 - - 332.0K static 2008-08-26 10:28
BE4 - - 15.78M static 2008-09-05 18:20
BE5 NR / 7.25G static 2008-09-09 16:53
Example 14: List all existing boot environmets and list all
dataset and snapshot information about those boot
environments.
# beadm list -d -s
BE/Dataset/Snapshot Active Mountpoint Space Policy Created
------------------- ------ ---------- ----- ------ -------
BE2
p/ROOT/BE2 - - 36.0K static 2008-05-21 12:26
p/ROOT/BE2/opt - - 18.0K static 2008-05-21 16:26
p/ROOT/BE2/opt@now - - 0 static 2008-09-08 22:43
p/ROOT/BE2@now - - 0 static 2008-09-08 22:43
BE3
p/ROOT/BE3 - - 192.0K static 2008-08-26 10:28
p/ROOT/BE3/opt - - 86.0K static 2008-08-26 10:28
p/ROOT/BE3/opt/local - - 36.0K static 2008-08-28 10:58
BE4
p/ROOT/BE4 - - 15.78M static 2008-09-05 18:20
BE5
p/ROOT/BE5 NR / 6.10G static 2008-09-09 16:53
p/ROOT/BE5/opt - /opt 24.55M static 2008-09-09 16:53
p/ROOT/BE5/opt@bar - - 18.38M static 2008-09-10 00:59
p/ROOT/BE5/opt@foo - - 18.38M static 2008-06-10 16:37
p/ROOT/BE5@bar - - 139.44M static 2008-09-10 00:59
p/ROOT/BE5@foo - - 912.85M static 2008-06-10 16:37
Example 15: List all dataset and snapshot information about BE5
# beadm list -a BE5
BE/Dataset/Snapshot Active Mountpoint Space Policy Created
------------------- ------ ---------- ----- ------ -------
BE5
p/ROOT/BE5 NR / 6.10G static 2008-09-09 16:53
p/ROOT/BE5/opt - /opt 24.55M static 2008-09-09 16:53
p/ROOT/BE5/opt@bar - - 18.38M static 2008-09-10 00:59
p/ROOT/BE5/opt@foo - - 18.38M static 2008-06-10 16:37
p/ROOT/BE5@bar - - 139.44M static 2008-09-10 00:59
p/ROOT/BE5@foo - - 912.85M static 2008-06-10 16:37
Example 16: List machine parsable information about all boot
environments.
# beadm list -H
BE2;;;;55296;static;1211397974
BE3;;;;339968;static;1219771706
BE4;;;;16541696;static;1220664051
BE5;215b8387-4968-627c-d2d0-f4a011414bab;NR;/;7786206208;static;1221004384
EXIT STATUS
The following exit values are returned:
0 - Success
>0 - Failure
FILES
/var/log/beadm/<beName>/create.log.<yyyymmdd_hhmmss>
Log used for capturing beadm create output
yyyymmdd_hhmmss - 20071130_140558
yy - year; 2007
mm - month; 11
dd - day; 30
hh - hour; 14
mm - minute; 05
ss - second; 58
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWbeadm |
|_____________________________|_____________________________|
| Interface Stability | Uncommitted |
|_____________________________|_____________________________|
SEE ALSO
zfs(1M)
NOTES
Last change: 10 September 2008