Sponsored Content
Full Discussion: Create Pool
Operating Systems Solaris Create Pool Post 302996114 by ygemici on Wednesday 19th of April 2017 06:26:49 AM
Old 04-19-2017
* HP Proliant is a good choice Smilie

Now , I assume it's a server with 8 discs.
Best practice ,
* first 2-disk "Raid1" structure will suffice as you would think for the system ( of course we will monitor the warning LEDs and ILOM Smilie )
* for the other 6 disks , the most suitable raid config is "Raid 5" ( if your database was production enviroment then maybe 1 disk spare can be considered but not needed for develop )

* and your hp tools ( smart storage admin / smart array ) forwards to you for creating raid pools and and advices for some details ( stripe size , raid conf and some defaults... )

good luck
regards
ygemici
This User Gave Thanks to ygemici For This Post:
 

10 More Discussions You Might Find Interesting

1. IP Networking

connection pool

Hi; Can someone please explain how do connections differ from threads? or a link to a good site about connection pooling and how threads are utilized by the OS. Thanks (1 Reply)
Discussion started by: suntan
1 Replies

2. Solaris

project vs pool vs use

hi, i am looking for a tool to see how many CPUs, controlled by FSS inside a pool, a project used over some time.... i have a 20k with several zones inside some pools. the cpu-sets/pools are configured with FSS and the zones with different shares. Inside the zones, i use projects with FSS... (2 Replies)
Discussion started by: pressy
2 Replies

3. Infrastructure Monitoring

zfs - migrate from pool to pool

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

4. Solaris

ZFS pool question

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

5. Solaris

zfs pool migration

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

6. Solaris

not able to use pool

i have this pool1 on my sun4u sparc machine bash-3.00# zpool get all pool1 NAME PROPERTY VALUE SOURCE pool1 size 292G - pool1 used 76.5K - pool1 available 292G - pool1 capacity 0% -... (1 Reply)
Discussion started by: Sojourner
1 Replies

7. Solaris

Do I need a pool before I can mirror my disks?

Hi! I would also like to know if I need first to create a pool before I can mirror my disks inside that pool. My first disk is c7t0d0s0 and my second disk is c7t2d0s0 as seen in the figure below. I would create a pool named rpool1 for this 2 disks. # zpool create rpool1 c7t0d0p0 c7t2d0p0 ... (18 Replies)
Discussion started by: CarlosP
18 Replies

8. BSD

Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset

I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error: # zpool create zfspool /dev/da0s1a cannot create 'zfspool': no such pool or dataset # zpool create zfspool /dev/da0 cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies

9. Solaris

Zpool with 3 2-way mirrors in a pool

I have a single zpool with 3 2-way mirrors ( 3 x 2 way vdevs) it has a degraded disk in mirror-2, I know I can suffer a single drive failure, but looking at this how many drive failures can this suffer before it is no good? On the face of it, I thought that I could lose a further 2 drives in each... (4 Replies)
Discussion started by: fishface
4 Replies

10. Solaris

Beadm create -p on another pool - making sense of it

Hi all, I am trying out Solaris 11.3 Realize the option of -p when using beadm that i can actually create another boot environment on another pool. root@Unicorn6:~# beadm create -p mypool solaris-1 root@Unicorn6:~# beadm list -a BE/Dataset/Snapshot Flags... (1 Reply)
Discussion started by: javanoob
1 Replies
UDISKS(1)							      udisks								 UDISKS(1)

NAME
udisks - udisks command line tool SYNOPSIS
udisks [OPTIONS] DESCRIPTION
udisks is a simple command line client for the udisks(7) system bus service. OPTIONS
--dump Dump all information about all devices. Please include this when filing bugs. --enumerate Lists all object paths of devices know to the daemon. --enumerate-device-files Lists all device files of devices know to the daemon. --monitor Connect to the daemon and print a line every time an event happens. --monitor-detail Like --monitor but prints the full details of the device whenever an event happens. --show-info device_file Shows information about device_file. --inhibit-polling device_file [-- program arg ...] Inhibits polling on device_file. If no program is given, polling is inhibited until Ctrl+C is pressed. Otherwise the program is spawned and the polling is only inhibited until the program terminates. --poll-for-media device_file Polls device_file to perform media detection. --inhibit-all-polling [-- program arg ...] Inhibits polling on all devices. If no program is given, polling is inhibited until Ctrl+C is pressed. Otherwise the program is spawned and the polling is only inhibited until the program terminates. --mount device_file [--mount-fstype fstype] [--mount-options options] Mounts the device represented by device_file using the file system fstype and a comma-separated list of options. --unmount device_file [--unmount-options options] Unmounts the device represented by device_file using a comma-separated list of options. --detach device_file [--detach-options options] Detaches (e.g. powering down the physical port the device is connected to) the device represented by device_file using a comma-separated list of options. --ata-smart-refresh device_file [--ata-smart-wakeup] Refreshes ATA SMART data for device_file. If the disk is sleeping it will not be woken up unless --ata-smart-wakeup is passed. will be used. --ata-smart-refresh device_file --ata-smart-simulate blob Read ATA SMART data from blob for device_file. This can only be done by the super user and is typically used for testing that clients relying on the ATA SMART data provided by udisks behave correctly. The libatasmart git repository at http://git.0pointer.de/?p=libatasmart.git;a=summary contains a collection of blobs from failing disks. --inhibit [-- program arg ...] Inhibits clients from invoking methods on the daemon that require authorization (all methods will return the org.freedesktop.UDisks.Error.Inhibited error) if the caller is not the super user. This is typically used by OS installers and other programs that expects full control of the system, specifically to avoid automounting devices. Only the super user can do this. If no program is given, the daemon is inhibited until Ctrl+C is pressed. Otherwise the program is spawned and the daemon is only inhibited until the program terminates. --set-spindown device_file --spindown-timeout seconds [-- program arg ...] Configures disk spindown timeout on device_file to seconds. See the section called "SPINNING DOWN DISKS" for important information before using this option. If no program is given, the spindown time will be used until Ctrl+C is pressed. Otherwise the program is spawned and the the spindown timeout will only be used until the program terminates. --set-spindown-all --spindown-timeout seconds [-- program arg ...] Configures disk spindown timeout on all disks that can be spun down to seconds. See the section called "SPINNING DOWN DISKS" for important information before using this option. If no program is given, the spindown time will be used until Ctrl+C is pressed. Otherwise the program is spawned and the the spindown timeout will only be used until the program terminates. --help Show help options. SPINNING DOWN DISKS
Caution should be exercised when configuring disk spin down timeouts. Note that every time a disk is spun down, the "start-stop-count" ATA SMART attribute will increase by 1 and most disks are only good for a limited number (typically 50,000 but it varies by manufacturer and model). In addition, the drive may take as long as 30 seconds to respond to subsequent disk access - most drives are typically faster, see the "spin-up-time" ATA SMART attribute. On the other hand, cautious use (e.g. using conservative timeouts) of the ability to spin down disks, can be a good way to trade power consumption (typically 8 vs 1 Watts for 3.5" drives) and heat emission for a slightly higher latency. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udisks-daemon(8), udisks(7), udisks April 2008 UDISKS(1)
All times are GMT -4. The time now is 01:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy