On 11/7/06, Richard Elling - PAE <[EMAIL PROTECTED]> wrote:
> d10 mirror of c0t2d0s0 and c0t3d0s0 swap (2+2GB, to match above)
Also a waste, use a swap file. Add a dumpdev if you care about
kernel dumps, no need to mirror a dumpdev.
How do you figure that allocating space to a swap file is less of a
waste than adding space to a swap device?
Simple /. Make it big enough to be useful. Keep its changes to a
minimum. Make more than one, so that you can use LiveUpgrade.
For consistency, you could make each disk look the same.
s0 / 10G
s6 zpool free
s7 metadb 100M
Since ZFS can get performance boosts from enabling the disk write
cache if it has the whole disk, you may want to consider something
more like the following for two of the disks (assumes mirroring rather
than raidz in the zpool):
s0 / 10G
s1 swap <pick your size>
s3 alt / 10G
s6 zpool free
s7 metadb 100M
The other pair of disks are given entirely to the zpool.
Use two disks for your BE, the other two for your ABE (assuming all are
bootable).
In any case, be sure that your root slices do not start at cylinder 0
(hmmm... maybe this is SPARC-specific advice...). One way to populate
an ABE is to mirror slices. However, you cannot mirror between a
device that starts at cylinder 0 and one that does not. Consider the
following mock-up (output may be a bit skewed):
Starting state...
# lustatus
slice0 - active mounted at d0
slice3 - may or may not exist, if it exists it is on d30
# metastat -p
d0 -m d1 d2 1
d1 1 1 c0t0d0s0
d2 1 1 c0t1d0s0
d30 -m d31 d32 1
d31 1 1 c0t0d0s3
d32 1 1 c0t1d0s3
Get rid of slice3 boot environment, make d31 available to recreate it.
# ludelete slice3
# metadetach d30 d31
# metaclear -r d30
Mirror d0 to d31. Wait for it to complete.
# metattach d0 d31
# while metastat -p | grep % ; do sleep 30 ; done
Detach d31 from d0, recreate d30 mirror
# metadetach d0 d31
# metainit d30 -m d31 1
# metainit d32 1 1 c0t1d0s3
# metattach d30 d32
Create boot environment named slice3:
# lucreate -n slice3 /:d30:ufs,preserve
Now you can manipulate the slice3 boot environment as needed.
Why go through all of this? My reasons have typically been:
1) Normally lucreate uses cpio, which doesn't cope with sparse files
well. /var/adm/lastlog is a sparse file that can be problematic if
you have users with large UID's
2) Lots of file systems mounted and little interest in creating very
complex command lines with many -x options.
Mike
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
