HP StorageWorks 9100 Extreme Data Storage System release notes V1.0.2 (AN540-96015, June 2009)

DescriptionIssue

The green status/activity LEDs on certain drives may not be lit correctly to show the drive state, and

may intermittently revert to an unlit state .

In certain situations the green status/activity LEDs may not be lit correctly to show the drive state,

and may intermittently revert to an unlit state although the drive is configured and part of a provisioned

LUN.

Workaround: This issue does not affect the drive functionality, nor does it affect the amber fault LED

indicator.

25243

Filesystems are created by the ExDS CLI with a persistent mount on all servers.

When filesystems are created by the ExDS CLI create filesystem command, by default they

are created with a persistent mount on all servers which means that if any servers reboot they will

mount all filesystems after the reboot. Therefore, if you wish to create a non-default mount configuration

whereby filesystems are mounted on only a subset of servers then you should ensure that the

persistence is removed from the other servers. Otherwise, on reboot, all servers mount all filesystems.

Example: Assume a system with 16 servers called exdsdemo [1-16] and 8 filesystems (fs1 through

fs8 created on devices psv2 through psv9 and mounted at /mnt/fs1 through /mnt/fs8). After

the initial filesystem creation, all 8 filesystems are mounted persistent on all 16 servers.

Suppose that we wish to mount the filesystems as follows:

To do this for the fs1 filesystem we would issue the following commands:

• mx fs unmount --persistent –-active psv2 ALL_SERVERS

• mx fs mount --persist -—activate --path /mnt/fs1 psv2 exdsdemo1

exdsdemo2

• mx fs unmount --persistent –-active psv2 exdsdemo3 exdsdemo4 exdsdemo5

exdsdemo6 exdsdemo7 exdsdemo8 exdsdemo9 exdsdemo10 exdsdemo11

exdsdemo12 exdsdemo13 exdsdemo14 exdsdemo15 exdsdemo16

The corresponding commands would be issued for each of the remaining filesystems.

25336