PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
Contents Index PreviousNext

Appendix A Kernel Messages> A.1 Diagnostics

A.1.4 NOTICE: sfxfs:0004: mount_point: too much fragment (extent)

[Explanation]

The meta-data area used to manage free data space is full in that file system indicated by mount_point, due to fragmentation of the free data space. Any data area that is subsequently released cannot be used as free data space for the file system and may be used as an active area. When a file is deleted, therefore, the space being used by the file system indicated by the df(1M) may not decrease. This message is displayed in the following cases:

[Action]

If a free data space that is handled as an active area is adjacent, it may be possible to manage it as free space by executing a full check with fsck_sfxfs(1M).

Execute a full check with fsck_sfxfs(1M) by first unmounting the file system and then specifying fsck -o nolog.

If the extent of the file system usage, as indicated by executing the df(1M), does not decrease after you execute a full check with fsck_sfxfs(1M), you can restore the free data space by first recreating and then restoring the file system after you reexamine the setup value of the following parameter in mkfs_sfxfs(1M) or sfxnewfs(1M) after backing up the files in the file system.

To prevent the output of this message while the extent of the free data space is the most discrete, the average number of blocks (nblkprext) that is managed in one extent must be used as the default (1).

Any free data space that is handled as active space cannot be restored as a free space data area through defragmentation of the file system, because it is not managed as free space.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004