On 08/20/09 02:36, Vano Beridze wrote:
Glenn Lagasse wrote:
Hi Vano,
* Vano Beridze ([email protected]) wrote:
Hello
I have one 80gb hdd and 2 identical 320 hdd-s. All of them are sata drives.
I'm going to install OpenSolaris 2009.06 on 80gb HDD and create
mirrored pool using 2 320 hdd drives to store my data.
I have the following questions:
1. Is it good drive layout? Can I have mirrored root pool using only
2 320 hdd-s?
It's one option. As long as you don't mind having no parity for your
root pool on the 80G disk. And yes, you can create a mirrored root
pool using only the 320G disks.
That's great that I can do mirrored pool using only 2 320 disks, So I
will save 80gb disk for something else.
If I create mirrored root pool using only 2 320 disks will I be able to
recover easily in case of one disk failure?
Yes. I have experienced that with 2x500GB disk drives, back in the S10
11/06 or 8/07 time frame. I was UFS boot, and I don't remember which
drive failed. However, the 400GB of data I had on it in a ZFS pool was
still there, and re-silvered when I received the replacement drive.
I mean it will like:
1. remove failed hdd from the pool.
If it if isn't already marked a such.
2. remove it physically
3. install new one physically
4. add new disk into the pool
I think replace is the option/sub-command I used.
and everything will be rebuilt and my root mirrored pool will be ready?
2. Will I be able create pool at the install time or I should do it
afterwards?
You have to do that afterwards. Installer only allow you to create a
root pool.
Personally, and it is just me, in your configuration I would consider
installing the rpool on the 80 GB drive, in maybe a 70+ GB slice, and
leave another slice handy. Then I would create the data pool on the pair
of 320GB drives, mirrored.
Solaris does not boot off of EFI labeled disks, so the boot disk needs
an SMI label. That means the write cache is turned off. Thus you are
leaving a little behind in terms of write performance, which may not
make a different--it doesn't in most of my cases. By having the data be
on separate, non-boot, it can be EFI.
However, you could also use that other slice on the 80GB disk as an
intent log. Your OS slice should not get a lot of major traffic to it,
so splitting the intent log from the data spindles may do well for some
writes, especially NFS writes, without a lot of contention to the intent
log.
Just a thought, since there will be a risk that if the 80GB drive goes,
you are down until it is fixed.
Alternatively, it is a good place to put backups, if you boot off of the
320GB disks.
Steffen
The installer will create the root pool for you on whatever disk you
choose. You will have to setup the mirror after installation. See the
ZFS documentation on how to do that.
Ok I will look at it.
3. My motherboard Asus P5B Deluxe has 2 controllers. Should I
connect 320 hdd-s to separate sata port of the each controller to
achieve better safety/performance?
IIRC sata doesn't have this sort of guideline like old IDE interfaces
did. In IDE land, you wanted to seperate out the controllers you used
so that you weren't blocked when making requests to drives on the same
controller. Sata did away with this limitation.
I undesrtand, but will it be faster or slower to use two separate
controllers?
Cheers,
------------------------------------------------------------------------
_______________________________________________
opensolaris-discuss mailing list
[email protected]
_______________________________________________
opensolaris-discuss mailing list
[email protected]
