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 OPENSOLARIS
root_archive
root_archive(1M) System Administration Commands root_archive(1M)
NAME
root_archive - manage bootable miniroot archives
SYNOPSIS
/boot/solaris/bin/root_archive pack archive root
/boot/solaris/bin/root_archive unpack archive root
/boot/solaris/bin/root_archive packmedia solaris_image root
/boot/solaris/bin/root_archive unpackmedia solaris_image root
DESCRIPTION
The root_archive utility is used to manage bootable miniroot archives and is currently only available on x86 platforms. The utility can
pack and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives.
root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or unmount file systems
and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands.
SUBCOMMANDS
The root_archive command has the following subcommands:
pack archive root Pack from the image found under the root directory to the archive.
unpack archive root
Unpack from the archive to an unpacked image under the root directory.
packmedia solaris_image root
Pack the solaris image to the root directory.
unpackmedia solaris_image root
Unpack the solaris image from the root directory.
For packmedia and unpackmedia, other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi-
cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used in the
running and hence pruned to conserve memory.
EXAMPLES
Example 1 Unpacking the Solaris x86 install image
The following command unpacks the current Solaris image from the root directory:
# root_archive unpackmedia
/export/nv/solarisdvd.nvx_dvd/latest /export/Boot
Where /export/nv/solarisdvd.nvx_dvd/latest represents a path to a Solaris x86 install image and /export/Boot is a directory that will be
purged or created, as necessary.
Example 2 Packing the Solaris x86 install image
The following command packs the current Solaris image to the root directory:
# root_archive packmedia
/export/nv/solarisdvd.nvx_dvd/latest /export/Boot
EXIT STATUS
The following exit values are returned:
0 The command completed successfully.
1 The command exited due to an error.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D)
SunOS 5.11 26 Sep 2005 root_archive(1M)