I see you creating a few "stub" luns to create some sort of logical separation and maybe give Windows more IO queue to drive its request through but from capacity perspective i would create them as small as you can.
With recent M$ OS you can "mount" a device on a mountpoint (just like you already do with any unix). But you need a device (\\.\physicaldrive2 mounted as X: ) that contain directories (X:\home1 X:\home2 X:\private ...) You later mount \\.\physicaldrive3 on X:\home1, \\.\physicaldrive4 on X:\home2 ..
Now the question is .. how big is X: (\\.\physicaldrive2) ??
Ok, let's say 100 megabytes stub. Have you used this number successfully? We have up to 6 or 8 LUNS mounted on a stub LUN (four were 1TB each), but for my new application I will have 3. Two of the LUNS will be 1TB, and the third about 800GB. Using 1 GB, as previously done, seemed wasteful of storage space. But I am unsure of what the stub LUN does, other than what we know - use a drive letter and allow the other LUNS to be "mounted" as a folder under the drive letter. We don't plan on putting any files at the drive root, so file space is not an issue. I just don't want to make a small LUN and map it to a drive, but find out later that it's not big enough when I attach the real LUNs (BTW, Is this Microsft's answer to a problem of only having 21 possible "drives" available to attach storage?)
dynamox
9 Legend
•
20.4K Posts
0
February 26th, 2009 07:00
http://support.microsoft.com/kb/280297
I see you creating a few "stub" luns to create some sort of logical separation and maybe give Windows more IO queue to drive its request through but from capacity perspective i would create them as small as you can.
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 14:00
Btw ..Welcome to EMC Forums
thanks
dynamox
9 Legend
•
20.4K Posts
0
February 25th, 2009 14:00
xe2sdc
4 Operator
•
2.8K Posts
1
February 25th, 2009 14:00
You later mount \\.\physicaldrive3 on X:\home1, \\.\physicaldrive4 on X:\home2 ..
Now the question is .. how big is X: (\\.\physicaldrive2) ??
xe2sdc
4 Operator
•
2.8K Posts
0
February 26th, 2009 00:00
rickr1
2 Posts
0
February 26th, 2009 06:00
We have up to 6 or 8 LUNS mounted on a stub LUN (four were 1TB each), but for my new application I will have 3. Two of the LUNS will be 1TB, and the third about 800GB.
Using 1 GB, as previously done, seemed wasteful of storage space. But I am unsure of what the stub LUN does, other than what we know - use a drive letter and allow the other LUNS to be "mounted" as a folder under the drive letter. We don't plan on putting any files at the drive root, so file space is not an issue. I just don't want to make a small LUN and map it to a drive, but find out later that it's not big enough when I attach the real LUNs
(BTW, Is this Microsft's answer to a problem of only having 21 possible "drives" available to attach storage?)