7 known issues and workarounds, 1 server reboot, 2 errors from install2 – HP StorageWorks Scalable File Share User Manual

Page 61: 3 application file locking, 4 mds is unresponsive, Errors, Changing group_upcall

Advertising
background image

7 Known Issues and Workarounds

The following items are known issues and workarounds.

7.1 Server Reboot

After the server reboots, it checks the file system and reboots again.

/boot: check forced

You can ignore this message.

7.2 Errors from install2

You might receive the following errors when running install2.

error: package cpq_cciss is not installed
error: package bnx2 is not installed
error: package nx_nic is not installed
error: package nx_lsa is not installed
error: package hponcfg is not installed

You can ignore these errors.

7.3 Application File Locking

Applications using fcntl for file locking will fail unless HP SFS is mounted on the clients with
the flock option. See

“Installation Instructions” (page 40)

for an example of how to use the

flock

option.

7.4 MDS Is Unresponsive

When processes on multiple client nodes are simultaneously changing directory entries on the
same directory, the MDS can appear to be hung. Watchdog timeout messages appear in /var/
log/messages

on the MDS. The workaround is to reboot the MDS node.

7.5 Changing group_upcall Value to Disable Group Validation

By default the HP SFS G3.2-0 group_upcall value on the MDS server is set to /usr/sbin/
l_getgroups

. This causes all user and group IDs to be validated on the HP SFS server. Therefore,

the server must have complete information about all user accounts using /etc/passwd and
/etc/group

or some other equivalent mechanism. Users who are unknown to the server will

not have access to the Lustre file systems.

This function can be disabled by setting group_upcall to NONE using the following procedure:

1.

All clients must umount the HP SFS file system.

2.

All HP SFS servers must umount the HP SFS file system.

IMPORTANT:

All clients and servers must not have HP SFS mounted. Otherwise, the file

system configuration data is corrupted.

3.

Perform the following two steps on the MDS node only:
a.

tunefs.lustre --dryrun --erase-params --param="mdt.group_upcall=NONE" --writeconf /dev/mapper/mpath?

Capture all param settings from the output of dryrun. These must be replaced because
the --erase-params option removes them.

7.1 Server Reboot

61

Advertising