Yes, I agree with you,
If you have plenty of huge disks, you can even use the RAW LV mode.
Just create your LV with AIX and add them to ADSM like raw volumes.
You do not need to format them so adding new volume to ADSM is immediate.
The draqback is that you can not use the jsflog. If your disks stg are
copied
everyday to tapes, you can take the risk, personnaly I do. Performance
are
better when writing to raw lv because AIX does has nothing to do with
JFSLOG.
Here is how I did, it work fine, my SSA disks are 18Gb each.
Herve
# df
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/adsm_db11_lv 7766016 6824 100% 19 1% /adsm/db/db11
/dev/adsm_db12_lv 7766016 6824 100% 19 1% /adsm/db/db12
/dev/adsm_db21_lv 7766016 6824 100% 19 1% /adsm/db/db21
/dev/adsm_db22_lv 7766016 6824 100% 19 1%
/adsm/db/db22
/dev/adsm_log11_lv 1015808 5968 100% 18 1%
/adsm/log/log11
/dev/adsm_log12_lv 1015808 5968 100% 18 1%
/adsm/log/log12
/dev/adsm_log21_lv 1015808 5968 100% 18 1%
/adsm/log/log21
/dev/adsm_log22_lv 1015808 5968 100% 18 1%
/adsm/log/log22
# lsvg -l poolvg
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
pool11_lv jfs 136 136 1 open/syncd N/A
pool12_lv jfs 135 135 1 open/syncd N/A
pool21_lv jfs 136 136 1 open/syncd N/A
pool31_lv jfs 68 68 1 open/syncd N/A
pool32_lv jfs 34 34 1 open/syncd N/A
pool41_lv jfs 67 67 1 open/syncd N/A
pool42_lv jfs 204 204 1 open/syncd N/A
pool51_lv jfs 136 136 1 open/syncd N/A
pool52_lv jfs 135 135 1 open/syncd N/A
pool61_lv jfs 136 136 1 open/syncd N/A
pool62_lv jfs 135 135 1 open/syncd N/A
pool22_lv jfs 135 135 1 open/syncd N/A
pool33_lv jfs 16 16 1 open/syncd N/A
VOLUME_NAME STGPOOL_NAME DEVCLASS_NAME
EST_CAPACITY_MB USED RECL STATUS
------------------ ------------------ ------------------
-------------------- ------ ------ ------------------
-------------------- ------ ------ ------------------
/dev/rpool11_lv TBF_DSK
/dev/rpool11_lv TBF_DSK
DISK 8704.0 14.0
ONLINE
/dev/rpool12_lv SWIFT_DSK
DISK 8640.0 1.6
ONLINE
/dev/rpool21_lv ORACLE_DB_DSK
DISK 8704.0 0.0
ONLINE
/dev/rpool22_lv NT_DB_DSK
DISK 8640.0 25.2
ONLINE
/dev/rpool31_lv SQLSERVER_DB_DSK
DISK 4352.0 3.1
ONLINE
/dev/rpool32_lv NOTES_DSK
DISK 2176.0 0.0
ONLINE
/dev/rpool33_lv VMS_DSK
DISK 1024.0 16.1
ONLINE
/dev/rpool41_lv UNIX_ESP_BQE_DSK
DISK 4288.0 2.7
ONLINE
/dev/rpool42_lv NT_DATA_USER_DSK
DISK 13056.0 38.5
ONLINE
/dev/rpool51_lv NT_DEFAULT_DSK
DISK 8704.0 28.2
ONLINE
/dev/rpool52_lv UNIX_DEFAULT_DSK
DISK 8640.0 3.3
ONLINE
/dev/rpool61_lv UNIX_DEFAULT_DSK
DISK 8704.0 3.5
ONLINE
/dev/rpool62_lv UNIX_DEFAULT_DSK
DISK 8640.0 2.4 ONLINE
cookde AT BP DOT COM on 09/02/2000 01:24:00
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Herve Chibois/FR/ABNAMRO/NL)
Subject: Re: Disk pool layout, pls help!
NO don't stripe the data... if you really watch ADSM you will note that is
spreads its activity across logical volumes assigned to it
When we striped it slowed us down...
Just define 50 9 GB files, one per physical device (and I'd make about 10
file systems with 5 vols per file sys)
We don't mirror our diskpool, yes periodically we might have a small
amount
of data loss but the actual production machine is still running and if it
has any problem with a loss of a backup it can just push another one (our
main backups are large data base archives)
what I've done and things work fine... at first I worked really hard at
positioning DB vols & LOG vols as the first devices our of an SSA loop and
made stgvols all the disks in the middle but anymore I just make sure
DB's &
logs and DBcopies & log copies are across different drawers on different
SSA
cards if possible
later,
DWight
> ----------
> From: Way Milk[SMTP:loudway AT YAHOO DOT COM]
> Reply To: ADSM: Dist Stor Manager
> Sent: Tuesday, February 08, 2000 4:16 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Disk pool layout, pls help!
>
> Hi, *SM Gurus:
>
> I really need you guys help on this one:
> I need to create a disk pool around 450G (50 9G disks)
> . My basic layout would be: create 10 logical volume,
> each lv spans on 5 disks. When creating the LVs, There
> is three policies I can use 1) RANGE of physical
> volumes set to minimum, which mean use them
> sequetially, 2) RANGE of physical volumes set to MAX,
> which means use soft-stripping with stripping block
> size=PP size (16Mb) 3) use striping, set the blksize
> to 4,8,16,32,56,128k.
>
> What is the efficent way to layout on disk pool setup?
> Should I use striping or not? If striping is
> prefrered, what should be the striping block size, 4k
> ,16k or 56k?
>
> What is you guys current setting, if you also have a
> huge diskpool?
>
> Thanks a lot
>
> Ming
>
> AIX system specialist
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
|