06-08-2009
Just to inform those having the same issue or some kind of.
ZFS is not a volume but only an advanced disk manager. Therefore, setup like those mentioned in my first post, are not directly possible.
To realize this post, it is required to lower the ammount of space used by the zfs root during installation of Solaris (possible by Solaris 10 U6 at least). This makes Solaris to use the ammount as slice 7 of the disk and keeps the rest free.
So after the installation, the rest of the disk can be splitted into 5 more slices, as usual by using 'format' and therefore realise, what I planed to have.
Greez, Blicki
10 More Discussions You Might Find Interesting
1. Solaris
# 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
2. Infrastructure Monitoring
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
3. Solaris
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
4. Solaris
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
5. Solaris
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
6. Solaris
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
7. Solaris
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
8. Solaris
I accidently added a disk in different zpool instead of pool, where I want.
root@prtdrd21:/# zpool status cvfdb2_app_pool
pool: cvfdb2_app_pool
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
cvfdb2_app_pool ONLINE 0 0 0... (1 Reply)
Discussion started by: solaris_1977
1 Replies
9. Solaris
I have a newly created zpool, and I have set compression on, for the whole pool:
# zfs set compression=on newPool
Now I have zfs send | zfs receive lot of snapshots to my newPool, but the compression is gone. I was hoping that I would be able to send snapshots to the new pool (which is... (0 Replies)
Discussion started by: kebabbert
0 Replies
10. UNIX for Beginners Questions & Answers
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
LEARN ABOUT HPUX
vxbootsetup
vxbootsetup(1M) vxbootsetup(1M)
NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk
SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ]
DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a
disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must
be contiguous with only one subdisk.
The -g option may be used to specify the boot disk group.
If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to
be bootable.
If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable.
vxbootsetup requires that:
o The root volume must be named rootvol and must have a usage type of root.
o The swap volume must be named swapvol and must have a usage type of swap.
o The volumes containing /usr and /var (if any) must be named usr and var, respectively.
See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the
system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically.
If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the
disk bootable.
ARGUMENTS
medianame
Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable.
SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M),
vxrootmir(1M)
Veritas Volume Manager Troubleshooting Guide
VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)