Thanks everyone. Your inputs helped me a lot.
The 'rpool/ROOT' mountpoint is set to 'legacy' as I don't see any reason to
mount it. But I am not certain if that can cause any issue in the future, or
that's a right thing to do. Any suggestions ?
Thanks
Arjun
__
Hello,
Trying to understand how to backup mirrored zfs boot pool 'rpool' to tape,
and restore it back if in case the disks are lost.
Backup would be done with an enterprise tool like tsm, legato etc.
As an example, here is the layout:
# zfs list
NAME USED AVAIL
ion is to create a mirrored root pool and then use the
> zpool split option to create an identical root pool (that is then
> imported with a new name, like rpool2), but this identical root pool
> won't be bootable either. You would then need to mount rpool2's file
> systems
Hi,
Let me add another query.
I would assume it would be perfectly ok to choose any name for root
pool, instead of 'rpool', during the OS install. Please suggest
otherwise.
Thanks
Arjun
On 4/8/11, Arjun YK wrote:
> Hello,
>
> I have a situation where a host, which is bo
Hello,
I have a situation where a host, which is booted off its 'rpool', need
to temporarily import the 'rpool' of another host, edit some files in
it, and export the pool back retaining its original name 'rpool'. Can
this be done ?
Here is what I am trying to do:
# zpool import -R /a rpool temp
Hello,
I am trying to update files on LDOM boot disk from Control Domain, but I
can't get it working fully.
I have a setup that allows to quickly deploy LDOM guest domains. The Golden
OS Image of guest domain boot disk is on a ZFS Volume. This ZFS Volume has
been Snapshot and Cloned for the quick
Hi,
I am trying to use ZFS for boot, and kind of confused about how the boot
paritions like /var to be layed out.
With old UFS, we create /var as sepearate filesystem to avoid various logs
filling up the / filesystem
With ZFS, during the OS install it gives the option to "Put /var on a
separate
