View Single Post
Old 10-19-06, 03:55 PM   #1
fhj52
Registered User
 
Join Date: Jan 2005
Posts: 135
Default What is the NVRAID stripe size?

Hi:

I searched here but found no answer. The NVRAID BIOS does not show detailed parameters about the RAID array.
Q1: What is the stripe size that Media Shield uses(i.e., for ''optimal'' ..., is it always 64k?)

I have looked for some document that explains the suggested method for setup to allow cross-platform usage(MS OS & Linux) as well as just basic steps but have not found such.
Q2: Is there such a doc from Nvidia?

I suppose the most outstanding issue of the Media Shield has been that it is oriented towards benefitting MS OS users because the utilities only run in MS OS.
Q3: Has anything been done to make them Linux friendly? ( i.e., get emails for failed disk and identify the failed disk.)

Thanks!


---------
[Edit]
That's it but I do have some more questions if Q2 answer is no. These are the (more) immediate ones.
For NVRAID:
is it possible to change the stripe size for setup of the array?

is it possible to migrate from 0+1 to another RAID or vice-versa? (Linux or MS OS)

I.e., I need input. ...looking for proper setup & formatting of disks.
E.g., ... is low-level format required if migrating from/to another type of RAID?
Do the raw/new disks need to be partitioned before NVRAID can use them?
Should the partitions be formatted before the RAID array is setup or is the NVRAID going to undo that anyway?

What filesystem, if any specific one, should be used to set the partition type and for formatting before NVRAID is used to set the RAID array type? I.e., does it need to be the same as what will be used on the array or does it matter?

I ask because I have some odd, ithink, output from fdisk and do not know if it is my config and/or setup or something else.
These are (4) 80GB SATA disks that were individually partitioned and formatted before using NVRAID 0+1 BIOS setup. Currently, after using dmraid and having active array, fdisk has some, apparently, unreal info.
fdisk -l -u:
Code:
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63   310006304   155003121   83  Linux

Disk /dev/sdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sde: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/sde doesn't contain a valid partition table

Disk /dev/sdf: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *          63   310006304   155003121   83  Linux
I don't know why it shows that sdd & sde don't have valid partitons but sdc and sdf do and that troubles me.
The NVRAID array is formatted with one partition as 158723.23MB( 310006305 sectors) and ~1324.28MB of ''free space''(unpartitioned) according to cfdisk. The fdisk -l does not list it at all.
... short version is that, at least, fdisk s/b saying none of the (4) devices have valid partition tables. Question is, is it fdisk or me/NVRAID-setup?

Then dmraid was used to find and activate the RAID. Currently:
#> dmraid -s -s -ccc
Code:
nvidia_bdagicca:312602880:128:raid10:ok:2:4:0
nvidia_bdagicca-0:312602880:128:stripe:ok:0:2:0
/dev/sdf:nvidia:nvidia_bdagicca-0:stripe:ok:156301486:0
/dev/sdd:nvidia:nvidia_bdagicca-0:stripe:ok:156301486:0
nvidia_bdagicca-1:312602880:128:stripe:ok:0:2:0
/dev/sdc:nvidia:nvidia_bdagicca-1:stripe:ok:156301486:0
/dev/sde:nvidia:nvidia_bdagicca-1:stripe:ok:156301486:0
I don't know why d-f and c-e are together rather than c-d and e-f or if makes any difference.

The /dev/mapper/nvidia_bdagicca was partitioned with cfdisk; rebooted and then formatted.
I have been running some filesystem tests so the filesystem has been changed a few times. Hence why I ask for proper procedures.

Although I don't have specific issues/problems at this time with data loss, etc., I surely do not want any later on when the fs is nearly full of data.

If Media Shield RAID utilities are still MS OS bound, what Linux methods are available to get similar functions?
__________________
When two people meet and exchange gifts, each has one object.
When two people meet and exchange ideas, each has two ideas.
... Open Source. Just do it.

---------------------------------
System: BFG GTX260^2 graphics but has ** TERRIBLE BLINKING OS **
SuperMicro H8DCi+AMI BIOS;dual Opt'285;8GB;LSI 320-2x w/ 6xU320 Fuji' MAXs in RAID 10; 4xSATAII on LSI 3041E for backup. Multi-boot Mandriva Linux, openSUSE, WinXPx64 & Win2k-AS; Creative Audigy2-Digital audio.
Gigabyte GA-2CEWH & NVRAID are GONE ... Finally!!

Last edited by fhj52; 10-22-06 at 06:30 AM.
fhj52 is offline   Reply With Quote