Top
PRIMECLUSTER Global File Services Configuration and Administration Guide 4.5
FUJITSU Software

F.2.1 Incompatibilities from 4.1A20

There are some incompatibilities with the following functions compared to 4.1A20:

Table F.1 Incompatibilities from 4.1A20

Number

Item

1

Changes operation of truncate(2), ftruncate(2), creat(2), and open(2) specified with O_TRUNC from the other node to the file where mmap(2) is being executed

2

Changes port numbers reserved by GFS

3

Changes the type of a special file specified for the GFS command argument

4

Change in error message of sfcdf(8)

5

Change in error message of sfcfsck(8)

6

Check strengthening of parameter specified for -o specific_options option of sfcmkfs(8)

7

Changes allocated reserved area size by writing operations

8

Add the upper limit of concurrently open files

9

Addition of the i-node's cache memory release function at the time of accessing many files

10

Omitted value of the communication timeout between nodes

11

Deletion of the sfcfrmd information message

12

Change in operation at the time of specifying the mount option atime

13

Cannot create sockets

14

Cannot create named pipes

GFS : Global File Services

F.2.1.1 Changes operation of truncate(2), ftruncate(2), creat(2), and open(2) specified with O_TRUNC from the other node to the file where mmap(2) is being executed

Incompatibility description

When the following system calls are issued on another node for a file within mmap(2) on the GFS Shared File System, action of them is changed.

Before change: Normal exit

After change: Abnormal exit (return code: -1, errno: EBUSY)

Corrective action

None.

F.2.1.2 Changes port numbers reserved by GFS

Incompatibility description

Port numbers reserved by GFS in the /etc/services file have been changed.

Before change: 9200 - 9300

After change: 9200 - 9263, 9300

Corrective action

No corrective action is required.

F.2.1.3 Changes the type of a special file specified for the GFS command argument

Incompatibility description

The type of special files has been changed in the following commands:

Before change: Specify a character special file

After change: Specify a block special file. A character special file cannot be specified.

Corrective action

If a special file is specified for the argument of the above command, specify a block special file. If a character special file is specified, the commands will output error messages and abnormal exit.

F.2.1.4 Change in error message of sfcdf(8)

Incompatibility description

In the sfcdf(8) command, the error message output at the following conditions has been changed.

1) -m option is specified. And,

2-1) A special file name which does not exist is specified for the argument. Or,

2-2) A special file name other than the GFS Shared File System is specified for the argument.

Before change:

For 2-1)

sfcdf: ERROR: cannot open special: errmsg

For 2-2)

sfcdf: ERROR: invalid device: special

After change:

sfcdf: ERROR: special is not a sfcfs file system

Corrective action

None.

F.2.1.5 Change in error message of sfcfsck(8)

Incompatibility description

In the sfcfsck(8) command, the error message output at the following conditions has been changed.

A special file name other than the GFS Shared File System is specified for the argument.

Before change:

device-name is not for sfcfs

After change:

Can't check device-name

Corrective action

None.

F.2.1.6 Check strengthening of parameter specified for -o specific_options option of sfcmkfs(8)

Incompatibility description

The operation of sfcmkfs(8) for the following conditions was changed.

1) Any of the following -o specific_options options is specified.

free=n
logsz=n
maxnode=n
metasz=n
mfree=n
nbpi=n
nblkpext=n

2) The first character of n is a digit. And,

3) When characters other than the figure are included since the second character of n.

Before change:

The string only of a digit consecutive from the first character in n is recognized as a parameter.

Example) "-o free=9a0" is considered to be "-o free=9".

After change:

The following error messages are output, and it terminates abnormally.

sfcmkfs:ERROR: Illegal option : value

Corrective action

Please specify the string only of the digit for the parameter.

F.2.1.7 Changes allocated reserved area size by writing operations

Incompatibility description

When executing write processing for a file on the GFS Shared File System, reserve area size by a node basis was increased. Within this change, used data area that is obtained by df(1), sfcdf(8), or statfs(2) is increased, after executing write processing.

As the example, an output result of df(1) is shown below in case an 1 kilobyte file is created on a GFS Shared File System just after making.

Before change:

Filesystem              1K-blocks      Used Available Use% Mounted on
/dev/sfdsk/c1/dsk/vol1   56569128      5200  50907016   1% /mnt/gfs1

After change:

Filesystem              1K-blocks      Used Available Use% Mounted on
/dev/sfdsk/c1/dsk/vol1   56569128     20480  50891736   1% /mnt/gfs1

Reserve area is increased because it is interpreted as used date area (column of "Used"), and available data area (column of "Available") is decreased.

Corrective action

None.

F.2.1.8 Add the upper limit of concurrently open files

Incompatibility description

When 5000 different files are being concurrently opened on a GFS Shared File System, it was changed that operation of open(2) or creat(2)'s execution for 5001th file.

Before change: Normal exit

After change: Abnormal exit (return code: -1, errno: ENFILE)

Corrective action

Please check the following message in /var/log/messages.

kernel: VFS: file-max limit number reached

If this message is not output, 5000 different files are already being opened on the GFS Shared File System where the file tried to open exists.

Please execute close(2) to files that are being opened and can be closed (have already been transacted).

If you need to open 5000 and over files on the GFS Shared File System, please disperse the target files to multiple GFS Shared File Systems.

F.2.1.9 Addition of the i-node's cache memory release function at the time of accessing many files

Incompatibility description

When the amount of i-node's cache memory used by MDS exceeded 30000, processing that decreases the amount of i-node's cache memory from 30000 to 22000 was added.

Before change:

The function of releasing i-node's cache memory used by MDS doesn't work.

After change:

  1. When the amount of i-node's cache memory used by MDS exceeds 30000, the following message is output and release processing of i-node's cache memory will be started.

    NOTICE: sfcfs_mds:3020: mountpoint: The total number of vnodes used reached the upper bound. vnodes used=totalnum: upper bound=30000: lower bound=22000
  2. When the i-node's cache memory used by MDS has been released until 22000, release processing will stop with the following indication.

    NOTICE: sfcfs_mds:3021: mountpoint: The total number of vnodes used(=totalnum) is the lower bound(=22000).

Corrective action

None.
But the i-node's cache memory release is in progress in the period of between the two message indications, "NOTICE : sfcfs_mds:3020" and "NOTICE : sfcfs_mds:3021". During release processing, file accessibility on the file system will be affected. Please minimize file access.

F.2.1.10 Communication timeout value between nodes

Incompatible contents

In the monitoring of the node by communication, the default of timeout value is changed after a communicative response is lost until it estimates a partner node to be an abnormal state.

Before change: 60 seconds

After change: 180 seconds

Corrective action

No corrective action is required

Information

You do not have to change the communication timeout between nodes. The value can be changed.

See

Please refer to "14.1.2 Communication timeout value", "10.1.2 Change (in file system attributes)" and "11.1.2 Change (in file system attributes)" about the change method of the communication timeout value between nodes.

F.2.1.11 Deletion of information message of sfcfrmd daemon

Incompatibility description

The information message output at the time of starting sfcfrmd is deleted.

Before change: The following messages are output.

sfcfrmd[pid]: INFO: sfcfrmd:0001: set number of threads 16
sfcfrmd[pid]: INFO: sfcfrmd:0002: set service port number 9300
sfcfrmd[pid]: INFO: sfcfrmd:0003: set connection timeout value 30 [sec]

After change: The above message is not output.

Corrective action

No corrective action is required.

F.2.1.12 Change in operation at the time of specifying the mount option atime

Incompatibility description

Operation at the time of specifying the mount option atime has been changed.

Before change:

The last access time of a file is updated for each file access.

After change:

The last access time of a file is updated when the previous last access time is the same as or older than the last modify time or the last change time. Also, when the previous last access time of a file is old for over a day, it is updated.

Corrective action

To execute the operation performed before change, change the mount option which is described in /etc/fstab from atime to strictatime.

F.2.1.13 Cannot create sockets

Incompatibility description

Operation when creating sockets on the GFS Shared File System by specifying S_IFSOCK in the second argument of mknod(2) has been changed.

Before change: Normal exit

After change: Abnormal exit (return code: -1, errno: EPERM)

Corrective action

None.

F.2.1.14 Cannot create named pipes

Incompatibility description

Operation when creating named pipes on the GFS Shared File System by specifying S_IFIFO in the second argument of mknod(2) has been changed.

Before change: Normal exit

After change: Abnormal exit (return code: -1, errno: EPERM)

Corrective action

None.