SUMMARY: disksuite question
- From: Dave Martini <martini1@xxxxxxxx>
- Date: Fri, 06 Mar 2009 10:50:02 -0800
Thank you everyone that replied.
Here is the answer to my question:
They need to be on their own unmounted partition. They are treated like
a raw partition. The databases need to be on their own slices so that
the disksuite drivers handle the device.
Here is my original question:
Do the state database replicas that get created in Solstice Disksuite
with the metadb command need to be on their own slices
or can they be for instance on an existing slice like /var/ or /export/home?
I have them on their own slice 7 now that is 20mb in size but would
like to delete them from there and make slice 7 bigger to create another
file system on it for this Solaris 9 machine and create the state
database replica's on an existing slice as mentioned. I have room at the
end of the disk to do this but will need to move the existing state
database replica.
Part Tag Flag Cylinders Size Blocks
0 root wm 1418 - 6380 6.84GB (4963/0/0) 14338107
1 var wm 6381 - 8507 2.93GB (2127/0/0) 6144903
2 backup wm 0 - 24619 33.92GB (24620/0/0) 71127180
3 unassigned wm 8508 - 10105 2.20GB (1598/0/0) 4616622
4 unassigned wm 10106 - 11703 2.20GB (1598/0/0) 4616622
5 swap wu 0 - 1417 1.95GB (1418/0/0) 4096602
6 unassigned wm 11704 - 22592 15.00GB (10889/0/0) 31458321
7 unassigned wm 22593 - 22605 18.34MB (13/0/0) 37557
Thanks much.
Dave Martini
LLNL
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Prev by Date: ZFS ACL's and Samba problems
- Next by Date: ALOM powercycle ignoring poweron command
- Previous by thread: ZFS ACL's and Samba problems
- Next by thread: ALOM powercycle ignoring poweron command
- Index(es):
Relevant Pages
|