Celerra Default disks

id 1-6 are OS disks, everything else is user LUNs. I just know but the size that the first 6 as OS.

Dynamox,

11GB - 2 no.s

2GB- 3no.s

30GB-1 no.

Could you please elaborate purpose of each LUNs? those six LUNs mapped to both blades or mapped to only active mover server_2?

i don't know the purpose of each individual LUN, i just know that's where DART operating system resides. See the "servers" column (1,2). That means those devices are presented to both datamovers, active on only one a time.

It is 2x 11GB , 3x 2GB and 32 GB in your case.

Control LUNs 0-4 (id 1-5 ) will have this fixed size and the sixth LUN will have different size (32 GB, 64 GB etc..) depending on the celerra model.

LUN 0 (id=1 in NAS) will have NASDB files and LUN 1 will have its backup.

I will have to have a look into the old notes to see what the other LUNs are for .

Vipin,

any update on 3*2GB LUNs?

They are all system volumes.  As a matter of fact, the entirety of Target 0 is reserved for system LUNs.  This means that any LUN ID below 16 (10h) is reserved as a Celerra system LUN.

If you do a df -h, you can see the disks and their purpose:

# df -lhP

Filesystem     Size Used Avail Use% Mounted on

/dev/hda3      2.0G 877M 1.1G 46% / ( Linux root partition 2GB)

/dev/hda1      122M 4.0M 112M 4% /boot  (Linux boot partition LUN 2 128MB)

none           1010M 0 1010M 0% /dev/shm  (Linux shared memory partition)

/dev/nde1      1.8G 683M 1003M 41% /nbsnas  (LUN 4 2GB)

/dev/hda5      2.0G 570M 1.4G 30% /nas  2GB (Linux partition LUN 2)

/dev/mapper/emc_vg_pri_ide-emc_lv_home 591M 27M 535M 5% /home ( Linux partition LUN 2 600MB)

/dev/mapper/emc_vg_pri_ide-emc_lv_celerra_backup 827M 64M 722M 9% /celerra/backup  (Linux partition LUN 2 840MB)

/dev/mapper/emc_vg_pri_ide-emc_lv_celerra_backendmonitor 7.8M 1.2M 6.3M 16% /celerra/backendmonitor  (LUN 2 8MB)

/dev/mapper/emc_vg_lun_0-emc_lv_nbsnas_jserver 1.4G 45M 1.3G 4% /nbsnas/jserver  (LUN 0 root_disk 1.38GB)

/dev/mapper/emc_vg_pri_ide-emc_lv_nas_jserver 1.4G 45M 1.3G 4% /nas/jserver ( Linux partition LUN 2 1.38GB)

/dev/mapper/emc_vg_lun_5-emc_lv_nas_var 97M 5.6M 87M 7% /nbsnas/var  (LUN 5 100MB)

/dev/mapper/emc_vg_lun_0-emc_lv_nas_var_dump 1.7G 35M 1.6G 3% /nbsnas/var/dump  (LUN 0 root_disk 1.65GB)

/dev/mapper/emc_vg_lun_0-emc_lv_nas_var_auditing 117M 5.6M 105M 6% /nbsnas/var/auditing ( LUN 0 root_disk 120MB)

/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_backup 827M 65M 720M 9% /nbsnas/var/backup ( LUN 5 840MB)

/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_emcsupport 552M 17M 507M 4% /nbsnas/var/emcsupport  (LUN 5 560MB)

/dev/mapper/emc_vg_lun_5-emc_lv_nas_var_log 206M 5.8M 189M 3% /nbsnas/var/log  (LUN 5 212MB)

/dev/nda1      134M 50M 84M 38% /nbsnas/dos  (LUN 0 root_disk 134MB)

Hi Bill,

I guess your "df -h" output belongs to control station's local HDD partition layout.

Hi,

The output is produced on the Control Station. The devices, however, come from two places:

- the hard drive of the Control Station (/dev/hd), and

- the back end LUNs, LUN 0 through 5 (/dev/sd). Those LUNs are served up by the Data Movers using NBS (network block services) and become available as SCSI disks.

The df output just makes it easy to see what they are used for and where they are mounted on the CS.

Sent from my iPad