Messages
This topic contains explanations for GPFS™ error messages.
Messages for IBM Spectrum Scale™ RAID in the ranges 6027-1850 – 6027-1899 and 6027-3000 – 6027-3099 are documented in IBM Spectrum Scale RAID: Administration.
- Message severity tags
GPFS has adopted a message severity tagging convention. This convention applies to some newer messages and to some messages that are being updated and adapted to be more usable by scripts or semi-automated management programs. - 6027-000
Attention: A disk being removed reduces the number of failure groups to nFailureGroups, which is below the number required for replication: nReplicas. - 6027-300 [N]
mmfsd ready - 6027-301
File fileName could not be run with err errno. - 6027-302 [E]
Could not execute script - 6027-303 [N]
script killed by signal signal - 6027-304 [W]
script ended abnormally - 6027-305 [N]
script failed with exit code code - 6027-306 [E]
Could not initialize inter-node communication - 6027-310 [I]
command initializing. {Version versionName: Built date time} - 6027-311 [N]
programName is shutting down. - 6027-312 [E]
Unknown trace class 'traceClass'. - 6027-313 [X]
Cannot open configuration file fileName. - 6027-314 [E]
command requires SuperuserName authority to execute. - 6027-315 [E]
Bad config file entry in fileName, line number. - 6027-316 [E]
Unknown config parameter "parameter" in fileName, line number. - 6027-317 [A]
Old server with PID pid still running. - 6027-318 [E]
Watchdog: Some process appears stuck; stopped the daemon process. - 6027-319
Could not create shared segment - 6027-320
Could not map shared segment - 6027-321
Shared segment mapped at wrong address (is value, should be value). - 6027-322
Could not map shared segment in kernel extension - 6027-323 [A]
Error unmapping shared segment. - 6027-324
Could not create message queue for main process - 6027-328 [W]
Value 'value' for 'parameter' is out of range in fileName. Valid values are value through value. value used. - 6027-329
Cannot pin the main shared segment: name - 6027-334 [E]
Error initializing internal communications. - 6027-335 [E]
Configuration error: check fileName. - 6027-336 [E]
Value 'value' for configuration parameter 'parameter' is not valid. Check fileName. - 6027-337 [N]
Waiting for resources to be reclaimed before exiting. - 6027-338 [N]
Waiting for number user(s) of shared segment to release it. - 6027-339 [E]
Nonnumeric trace value 'value' after class 'class'. - 6027-340
Child process file failed to start due to error rc: errStr. - 6027-341 [D]
Node nodeName is incompatible because its maximum compatible version (number) is less than the version of this node (number). [value/value] - 6027-342 [E]
Node nodeName is incompatible because its minimum compatible version is greater than the version of this node (number). [value/value] - 6027-343 [E]
Node nodeName is incompatible because its version (number) is less than the minimum compatible version of this node (number). [value/value] - 6027-344 [E]
Node nodeName is incompatible because its version is greater than the maximum compatible version of this node (number). [value/value] - 6027-345
Network error on ipAddress, check connectivity. - 6027-346 [E]
Incompatible daemon version. My version = number, repl.my_version = number - 6027-347 [E]
Remote host ipAddress refused connection because IP address ipAddress was not in the node list file - 6027-348 [E]
Bad "subnets" configuration: invalid subnet "ipAddress". - 6027-349 [E]
Bad "subnets" configuration: invalid cluster name pattern "clusterNamePattern". - 6027-350 [E]
Bad "subnets" configuration: primary IP address ipAddress is on a private subnet. Use a public IP address instead. - 6027-358
Communication with mmspsecserver through socket name failed, err value: errorString, msgType messageType. - 6027-359
The mmspsecserver process is shutting down. Reason: explanation. - 6027-360
Disk name must be removed from the /etc/filesystems stanza before it can be deleted. - 6027-361 [E]
Local access to disk failed with EIO, switching to access the disk remotely. - 6027-362
Attention: No disks were deleted, but some data was migrated. The file system may no longer be properly balanced. - 6027-363
I/O error writing disk descriptor for disk name. - 6027-364
Error processing disks. - 6027-365 [I]
Rediscovered local access to disk. - 6027-369
I/O error writing file system descriptor for disk name. - 6027-370
mmdeldisk completed. - 6027-371
Cannot delete all disks in the file system - 6027-372
Replacement disk must be in the same failure group as the disk being replaced. - 6027-373
Disk diskName is being replaced, so status of disk diskName must be replacement. - 6027-374
Disk name may not be replaced. - 6027-375
Disk name diskName already in file system. - 6027-376
Previous replace command must be completed before starting a new one. - 6027-377
Cannot replace a disk that is in use. - 6027-378 [I]
I/O still in progress near sector number on disk diskName. - 6027-379
Could not invalidate disk(s). - 6027-380
Disk name missing from disk descriptor list entry name. - 6027-382
Value value for the 'sector size' option for disk disk is not a multiple of value. - 6027-383
Disk name name appears more than once. - 6027-384
Disk name name already in file system. - 6027-385
Value value for the 'sector size' option for disk name is out of range. Valid values are number through number. - 6027-386
Value value for the 'sector size' option for disk name is invalid. - 6027-387
Value value for the 'failure group' option for disk name is out of range. Valid values are number through number. - 6027-388
Value value for the 'failure group' option for disk name is invalid. - 6027-389
Value value for the 'has metadata' option for disk name is out of range. Valid values are number through number. - 6027-390
Value value for the 'has metadata' option for disk name is invalid. - 6027-391
Value value for the 'has data' option for disk name is out of range. Valid values are number through number. - 6027-392
Value value for the 'has data' option for disk name is invalid. - 6027-393
Either the 'has data' option or the 'has metadata' option must be '1' for disk diskName. - 6027-394
Too many disks specified for file system. Maximum = number. - 6027-399
Not enough items in disk descriptor list entry, need fields. - 6027-416
Incompatible file system descriptor version or not formatted. - 6027-417
Bad file system descriptor. - 6027-418
Inconsistent file system quorum. readQuorum=value writeQuorum=value quorumSize=value. - 6027-419
Failed to read a file system descriptor. - 6027-420
Inode size must be greater than zero. - 6027-421
Inode size must be a multiple of logical sector size. - 6027-422
Inode size must be at least as large as the logical sector size. - 6027-423
Minimum fragment size must be a multiple of logical sector size. - 6027-424
Minimum fragment size must be greater than zero. - 6027-425
File system block size of blockSize is larger than maxblocksize parameter. - 6027-426
Warning: mount detected unavailable disks. Use mmlsdisk fileSystem to see details. - 6027-427
Indirect block size must be at least as large as the minimum fragment size. - 6027-428
Indirect block size must be a multiple of the minimum fragment size. - 6027-429
Indirect block size must be less than full data block size. - 6027-430
Default metadata replicas must be less than or equal to default maximum number of metadata replicas. - 6027-431
Default data replicas must be less than or equal to default maximum number of data replicas. - 6027-432
Default maximum metadata replicas must be less than or equal to value. - 6027-433
Default maximum data replicas must be less than or equal to value. - 6027-434
Indirect blocks must be at least as big as inodes. - 6027-435 [N]
The file system descriptor quorum has been overridden. - 6027-438
Duplicate disk name name. - 6027-439
Disk name sector size value does not match sector size value of other disk(s). - 6027-441
Unable to open disk 'name' on node nodeName. - 6027-445
Value for option '-m' cannot exceed the number of metadata failure groups. - 6027-446
Value for option '-r' cannot exceed the number of data failure groups. - 6027-451
No disks= list found in mount options. - 6027-452
No disks found in disks= list. - 6027-453
No disk name found in a clause of the list. - 6027-461
Unable to find name device. - 6027-462
name must be a char or block special device. - 6027-463
SubblocksPerFullBlock was not 32. - 6027-465
The average file size must be at least as large as the minimum fragment size. - 6027-468
Disk name listed in fileName or local mmsdrfs file, not found in device name. Run: mmcommon recoverfs name. - 6027-469
File system name does not match descriptor. - 6027-470
Disk name may still belong to file system filesystem. Created on IPandTime. - 6027-471
Disk diskName: Incompatible file system descriptor version or not formatted. - 6027-472 [E]
File system format version versionString is not supported. - 6027-473 [X]
File System fileSystem unmounted by the system with return code value reason code value - 6027-474 [X]
Recovery Log I/O failed, unmounting file system fileSystem - 6027-475
The option '--inode-limit' is not enabled. Use option '-V' to enable most recent features. - 6027-476
Restricted mount using only available file system descriptor. - 6027-477
The option -z is not enabled. Use the -V option to enable most recent features. - 6027-478
The option -z could not be changed. fileSystem is still in use. - 6027-479 [N]
Mount of fsName was blocked by fileName - 6027-480
Cannot enable DMAPI in a file system with existing snapshots. - 6027-481 [E]
Remount failed for mountid id: errnoDescription - 6027-482 [E]
Remount failed for device name: errnoDescription - 6027-483 [N]
Remounted name - 6027-484
Remount failed for device after daemon restart. - 6027-485
Perform mmchdisk for any disk failures and re-mount. - 6027-486
No local device specified for fileSystemName in clusterName. - 6027-487
Failed to write the file system descriptor to disk diskName. - 6027-488
Error opening the exclusion disk file fileName. - 6027-489
Attention: The desired replication factor exceeds the number of available dataOrMetadata failure groups. This is allowed, but the files will not be replicated and will therefore be at risk. - 6027-490 [N]
The descriptor replica on disk diskName has been excluded. - 6027-491
Incompatible file system format. Only file systems formatted with GPFS 3.2 or later can be mounted on this platform. - 6027-492
The file system is already at file system version number - 6027-493
File system version number is not supported on nodeName nodes in the cluster. - 6027-494
File system version number is not supported on the following nodeName remote nodes mounting the file system: - 6027-495
You have requested that the file system be upgraded to version number. This will enable new functionality but will prevent you from using the file system with earlier releases of GPFS. Do you want to continue? - 6027-496
You have requested that the file system version for local access be upgraded to version number. This will enable some new functionality but will prevent local nodes from using the file system with earlier releases of GPFS. Remote nodes are not affected by this change. Do you want to continue? - 6027-497
The file system has already been upgraded to number using -V full. It is not possible to revert back. - 6027-498
Incompatible file system format. Only file systems formatted with GPFS 3.2.1.5 or later can be mounted on this platform. - 6027-499 [X]
An unexpected Device Mapper path dmDevice (nsdId) has been detected. The new path does not have a Persistent Reserve set up. File system fileSystem will be internally unmounted. - 6027-500
name loaded and configured. - 6027-501
name:module moduleName unloaded. - 6027-502
Incorrect parameter: name. - 6027-504
Not enough memory to allocate internal data structure. - 6027-505
Internal error, aborting. - 6027-506
program: loadFile is already loaded at address. - 6027-507
program: loadFile is not loaded. - 6027-510
Cannot mount fileSystem on mountPoint: errorString - 6027-511
Cannot unmount fileSystem: errorDescription - 6027-512
name not listed in /etc/vfs - 6027-514
Cannot mount fileSystem on mountPoint: Already mounted. - 6027-515
Cannot mount fileSystem on mountPoint - 6027-516
Cannot mount fileSystem - 6027-517
Cannot mount fileSystem: errorString - 6027-518
Cannot mount fileSystem: Already mounted. - 6027-519
Cannot mount fileSystem on mountPoint: File system table full. - 6027-520
Cannot mount fileSystem: File system table full. - 6027-530
Mount of name failed: cannot mount restorable file system for read/write. - 6027-531
The following disks of name will be formatted on node nodeName: list. - 6027-532 [E]
The quota record recordNumber in file fileName is not valid. - 6027-533 [W]
Inode space inodeSpace in file system fileSystem is approaching the limit for the maximum number of inodes. - 6027-534
Cannot create a snapshot in a DMAPI-enabled file system, rc=returnCode. - 6027-535
Disks up to size size can be added to storage pool pool. - 6027-536
Insufficient system memory to run GPFS daemon. Reduce page pool memory size with the mmchconfig command or add additional RAM to system. - 6027-537
Disks up to size size can be added to this file system. - 6027-538
Error accessing disks. - 6027-539
Unable to clear descriptor areas for fileSystem. - 6027-540
Formatting file system. - 6027-541
Error formatting file system. - 6027-542 [N]
Fileset in file system fileSystem:filesetName (id filesetId) has been incompletely deleted. - 6027-543
Error writing file system descriptor for fileSystem. - 6027-544
Could not invalidate disk of fileSystem. - 6027-545
Error processing fileset metadata file. - 6027-546
Error processing allocation map for storage pool poolName. - 6027-547
Fileset filesetName was unlinked. - 6027-548
Fileset filesetName unlinked from filesetName. - 6027-549 [E]
Failed to open name. - 6027-550 [X]
Allocation manager for fileSystem failed to revoke ownership from node nodeName. - 6027-551
fileSystem is still in use. - 6027-552
Scan completed successfully. - 6027-553
Scan failed on number user or system files. - 6027-554
Scan failed on number out of number user or system files. - 6027-555
The desired replication factor exceeds the number of available failure groups. - 6027-556
Not enough space for the desired number of replicas. - 6027-557
Not enough space or available disks to properly balance the file. - 6027-558
Some data are unavailable. - 6027-559
Some data could not be read or written. - 6027-560
File system is already suspended. - 6027-561
Error migrating log. - 6027-562
Error processing inodes. - 6027-563
File system is already running. - 6027-564
Error processing inode allocation map. - 6027-565
Scanning user file metadata ... - 6027-566
Error processing user file metadata. - 6027-567
Waiting for pending file system scan to finish ... - 6027-568
Waiting for number pending file system scans to finish ... - 6027-569
Incompatible parameters. Unable to allocate space for file system metadata. Change one or more of the following as suggested and try again: - 6027-570
Incompatible parameters. Unable to create file system. Change one or more of the following as suggested and try again: - 6027-571
Logical sector size value must be the same as disk sector size. - 6027-572
Completed creation of file system fileSystem. - 6027-573
All data on the following disks of fileSystem will be destroyed: - 6027-574
Completed deletion of file system fileSystem. - 6027-575
Unable to complete low level format for fileSystem. Failed with error errorCode - 6027-576
Storage pools have not been enabled for file system fileSystem. - 6027-577
Attention: number user or system files are not properly replicated. - 6027-578
Attention: number out of number user or system files are not properly replicated: - 6027-579
Some unreplicated file system metadata has been lost. File system usable only in restricted mode. - 6027-580
Unable to access vital system metadata. Too many disks are unavailable. - 6027-581
Unable to access vital system metadata, file system corrupted. - 6027-582
Some data has been lost. - 6027-584
Incompatible parameters. Unable to allocate space for root directory. Change one or more of the following as suggested and try again: - 6027-585
Incompatible parameters. Unable to allocate space for ACL data. Change one or more of the following as suggested and try again: - 6027-586
Quota server initialization failed. - 6027-587
Unable to initialize quota client because there is no quota server. Please check error log on the file system manager node. The mmcheckquota command must be run with the file system unmounted before retrying the command. - 6027-588
No more than number nodes can mount a file system. - 6027-589
Scanning file system metadata, phase number ... - 6027-590 [W]
GPFS is experiencing a shortage of pagepool. This message will not be repeated for at least one hour. - 6027-591
Unable to allocate sufficient inodes for file system metadata. Increase the value for option and try again. - 6027-592
Mount of fileSystem is waiting for the mount disposition to be set by some data management application. - 6027-593 [E]
The root quota entry is not found in its assigned record - 6027-594
Disk diskName cannot be added to storage pool poolName. Allocation map cannot accommodate disks larger than size MB. - 6027-595 [E]
While creating quota files, file fileName, with no valid quota information was found in the root directory. Remove files with reserved quota file names (for example, user.quota) without valid quota information from the root directory by: - mounting the file system without quotas, - removing the files, and - remounting the file system with quotas to recreate new quota files. To use quota file names other than the reserved names, use the mmcheckquota command. - 6027-596 [I]
While creating quota files, file fileName containing quota information was found in the root directory. This file will be used as quotaType quota file. - 6027-597 [E]
The quota command was requested to process quotas for a type (user, group, or fileset), which is not enabled. - 6027-598 [E]
The supplied file does not contain quota information. - 6027-599 [E]
File supplied to the command does not exist in the root directory. - 6027-600
On node nodeName an earlier error may have caused some file system data to be inaccessible at this time. Check error log for additional information. After correcting the problem, the file system can be mounted again to restore normal data access. - 6027-601
Error changing pool size. - 6027-602
ERROR: file system not mounted. Mount file system fileSystem and retry command. - 6027-603
Current pool size: valueK = valueM, max block size: valueK = valueM. - 6027-604 [E]
Parameter incompatibility. File system block size is larger than maxblocksize parameter. - 6027-605 [N]
File system has been renamed. - 6027-606 [E]
The node number nodeNumber is not defined in the node list - 6027-607
mmcommon getEFOptions fileSystem failed. Return code value. - 6027-608 [E]
File system manager takeover failed. - 6027-609
File system fileSystem unmounted because it does not have a manager. - 6027-610
Cannot mount file system fileSystem because it does not have a manager. - 6027-611 [I]
Recovery: fileSystem, delay number sec. for safe recovery. - 6027-612
Unable to run command while the file system is suspended. - 6027-613 [N]
Expel node request from node. Expelling: node - 6027-614
Value value for option name is out of range. Valid values are number through number. - 6027-615
mmcommon getContactNodes clusterName failed. Return code value. - 6027-616 [X]
Duplicate address ipAddress in node list - 6027-617 [I]
Recovered number nodes for cluster clusterName. - 6027-618 [X]
Local host not found in node list (local ip interfaces: interfaceList) - 6027-619
Negative grace times are not allowed. - 6027-620
Hard quota limit must not be less than soft limit. - 6027-621
Negative quota limits are not allowed. - 6027-622 [E]
Failed to join remote cluster clusterName - 6027-623
All disks up and ready - 6027-624
No disks - 6027-625
File system manager takeover already pending. - 6027-626
Migrate to node nodeName already pending. - 6027-627
Node nodeName is already manager for fileSystem. - 6027-628
Sending migrate request to current manager node nodeName. - 6027-629 [N]
Node nodeName resigned as manager for fileSystem. - 6027-630 [N]
Node nodeName appointed as manager for fileSystem. - 6027-631
Failed to appoint node nodeName as manager for fileSystem. - 6027-632
Failed to appoint new manager for fileSystem. - 6027-633
The best choice node nodeName is already the manager for fileSystem. - 6027-634
Node name or number node is not valid. - 6027-635 [E]
The current file system manager failed and no new manager will be appointed. - 6027-636 [E]
Disk marked as stopped or offline. - 6027-637 [E]
RVSD is not active. - 6027-638 [E]
File system fileSystem unmounted by node nodeName - 6027-639 [E]
File system cannot be mounted in restricted mode and ro or rw concurrently - 6027-640 [E]
File system is mounted - 6027-641 [E]
Unable to access vital system metadata. Too many disks are unavailable or the file system is corrupted. - 6027-642 [N]
File system has been deleted. - 6027-643 [I]
Node nodeName completed take over for fileSystem. - 6027-644
The previous error was detected on node nodeName. - 6027-645
Attention: mmcommon getEFOptions fileSystem failed. Checking fileName. - 6027-646 [E]
File system unmounted due to loss of cluster membership. - 6027-647 [E]
File fileName could not be run with err errno. - 6027-648
EDITOR environment variable must be full pathname. - 6027-649
Error reading the mmpmon command file. - 6027-650 [X]
The mmfs daemon is shutting down abnormally. - 6027-660
Error displaying message from mmfsd. - 6027-661
mmfsd waiting for primary node nodeName. - 6027-662
mmfsd timed out waiting for primary node nodeName. - 6027-663
Lost connection to file system daemon. - 6027-664
Unexpected message from file system daemon. - 6027-665
Failed to connect to file system daemon: errorString - 6027-666
Failed to determine file system manager. - 6027-667
Could not set up socket - 6027-668
Could not send message to file system daemon - 6027-669
Could not connect to file system daemon. - 6027-670
Value for 'option' is not valid. Valid values are list. - 6027-671
Keyword missing or incorrect. - 6027-672
Too few arguments specified. - 6027-673
Too many arguments specified. - 6027-674
Too many values specified for option name. - 6027-675
Required value for option is missing. - 6027-676
Option option specified more than once. - 6027-677
Option option is incorrect. - 6027-678
Misplaced or incorrect parameter name. - 6027-679
Device name is not valid. - 6027-680 [E]
Disk failure. Volume name. rc = value. Physical volume name. - 6027-681
Required option name was not specified. - 6027-682
Device argument is missing. - 6027-683
Disk name is invalid. - 6027-684
Value value for option is incorrect. - 6027-685
Value value for option option is out of range. Valid values are number through number. - 6027-686
option (value) exceeds option (value). - 6027-687
Disk name is specified more than once. - 6027-688
Failed to read file system descriptor. - 6027-689
Failed to update file system descriptor. - 6027-690
Failed to allocate I/O buffer. - 6027-691
Failed to send message to node nodeName. - 6027-692
Value for option is not valid. Valid values are yes, no. - 6027-693
Cannot open disk name. - 6027-694
Disk not started; disk name has a bad volume label. - 6027-695 [E]
File system is read-only. - 6027-696 [E]
Too many disks are unavailable. - 6027-697 [E]
No log available. - 6027-698 [E]
Not enough memory to allocate internal data structure. - 6027-699 [E]
Inconsistency in file system metadata. - 6027-700 [E]
Log recovery failed. - 6027-701 [X]
Some file system data are inaccessible at this time. - 6027-702 [X]
Some file system data are inaccessible at this time. Check error log for additional information. After correcting the problem, the file system must be unmounted and then mounted to restore normal data access. - 6027-703 [X]
Some file system data are inaccessible at this time. Check error log for additional information. - 6027-704
Attention: Due to an earlier error normal access to this file system has been disabled. Check error log for additional information. After correcting the problem, the file system must be unmounted and then mounted again to restore normal data access. - 6027-705
Error code value. - 6027-706
The device name has no corresponding entry in fileName or has an incomplete entry. - 6027-707
Unable to open file fileName. - 6027-708
Keyword name is incorrect. Valid values are list. - 6027-709
Incorrect response. Valid responses are "yes", "no", or "noall" - 6027-710
Attention: - 6027-711 [E]
Specified entity, such as a disk or file system, does not exist. - 6027-712 [E]
Error in communications between mmfsd daemon and client program. - 6027-713
Unable to start because conflicting program name is running. Waiting until it completes. - 6027-714
Terminating because conflicting program name is running. - 6027-715
command is finished waiting. Starting execution now. - 6027-716 [E]
Some file system data or metadata has been lost. - 6027-717 [E]
Must execute mmfsck before mount. - 6027-718
The mmfsd daemon is not ready to handle commands yet. - 6027-719 [E]
Device type not supported. - 6027-720 [E]
Actual sector size does not match given sector size. - 6027-721 [E]
Host 'name' in fileName is not valid. - 6027-722
Attention: Due to an earlier error normal access to this file system has been disabled. Check error log for additional information. The file system must be mounted again to restore normal data access. - 6027-723
Attention: Due to an earlier error normal access to this file system has been disabled. Check error log for additional information. After correcting the problem, the file system must be mounted again to restore normal data access. - 6027-724 [E]
Incompatible file system format. - 6027-725
The mmfsd daemon is not ready to handle commands yet. Waiting for quorum. - 6027-726 [E]
Quota initialization/start-up failed. - 6027-727
Specified driver type type does not match disk name driver type type. - 6027-728
Specified sector size value does not match disk name sector size value. - 6027-729
Attention: No changes for disk name were specified. - 6027-730
command on fileSystem. - 6027-731
Error number while performing command for name quota on fileSystem - 6027-732
Error while performing command on fileSystem. - 6027-733
Edit quota: Incorrect format! - 6027-734 [W]
Quota check for 'fileSystem' ended prematurely. - 6027-735
Error editing string from mmfsd. - 6027-736
Attention: Due to an earlier error normal access to this file system has been disabled. Check error log for additional information. The file system must be unmounted and then mounted again to restore normal data access. - 6027-737
Attention: No metadata disks remain. - 6027-738
Attention: No data disks remain. - 6027-739
Attention: Due to an earlier configuration change the file system is no longer properly balanced. - 6027-740
Attention: Due to an earlier configuration change the file system is no longer properly replicated. - 6027-741
Attention: Due to an earlier configuration change the file system may contain data that is at risk of being lost. - 6027-742
Error occurred while executing a command for fileSystem. - 6027-743
Initial disk state was updated successfully, but another error may have changed the state again. - 6027-744
Unable to run command while the file system is mounted in restricted mode. - 6027-745
fileSystem: no quotaType quota management enabled. - 6027-746
Editing quota limits for this user or group not permitted. - 6027-747 [E]
Too many nodes in cluster (max number) or file system (max number). - 6027-748
fileSystem: no quota management enabled - 6027-749
Pool size changed to number K = number M. - 6027-750 [E]
The node address ipAddress is not defined in the node list - 6027-751 [E]
Error code value - 6027-752 [E]
Lost membership in cluster clusterName. Unmounting file systems. - 6027-753 [E]
Could not run command command - 6027-754
Error reading string for mmfsd. - 6027-755 [I]
Waiting for challenge challengeValue (node nodeNumber, sequence sequenceNumber) to be responded during disk election - 6027-756 [E]
Configuration invalid or inconsistent between different nodes. - 6027-757
name is not an excluded disk. - 6027-758
Disk(s) not started; disk name has a bad volume label. - 6027-759
fileSystem is still in use. - 6027-760 [E]
Unable to perform i/o to the disk. This node is either fenced from accessing the disk or this node's disk lease has expired. - 6027-761 [W]
Attention: excessive timer drift between node and node (number over number sec). - 6027-762
No quota enabled file system found. - 6027-763
uidInvalidate: Incorrect option option. - 6027-764
Error invalidating UID remapping cache for domain. - 6027-765 [W]
Tick value hasn't changed for nearly number seconds - 6027-766 [N]
This node will be expelled from cluster cluster due to expel msg from node - 6027-767 [N]
Request sent to node to expel node from cluster cluster - 6027-768
Wrong number of operands for mmpmon command 'command'. - 6027-769
Malformed mmpmon command 'command'. - 6027-770
Error writing user.quota file. - 6027-771
Error writing group.quota file. - 6027-772
Error writing fileset.quota file. - 6027-773
fileSystem: quota check may be incomplete because of SANergy activity on number files. - 6027-774
fileSystem: quota management is not enabled, or one or more quota clients are not available. - 6027-775
During mmcheckquota processing, number node(s) failed. It is recommended that mmcheckquota be repeated. - 6027-776
fileSystem: There was not enough space for the report. Please repeat quota check! - 6027-777 [I]
Recovering nodes: nodeList - 6027-778 [I]
Recovering nodes in cluster cluster: nodeList - 6027-779
Incorrect fileset name filesetName. - 6027-780
Incorrect path to fileset junction junctionName. - 6027-781
Storage pools have not been enabled for file system fileSystem. - 6027-784 [E]
Device not ready. - 6027-785 [E]
Cannot establish connection. - 6027-786 [E]
Message failed because the destination node refused the connection. - 6027-787 [E]
Security configuration data is inconsistent or unavailable. - 6027-788 [E]
Failed to load or initialize security library. - 6027-789
Unable to read offsets offset to offset for inode inode snap snap, from disk diskName, sector sector. - 6027-790
Specified storage pool poolName does not match disk diskName storage pool poolName. Use mmdeldisk and mmadddisk to change a disk's storage pool. - 6027-792
Policies have not been enabled for file system fileSystem. - 6027-793
No policy file was installed for file system fileSystem. - 6027-794
Failed to read policy file for file system fileSystem. - 6027-795
Failed to open fileName: errorCode. - 6027-796
Failed to read fileName: errorCode. - 6027-797
Failed to stat fileName: errorCode. - 6027-798
Policy files are limited to number bytes. - 6027-799
Policy `policyName' installed and broadcast to all nodes. - 6027-850
Unable to issue this command from a non-root user. - 6027-851
Unable to process interrupt received. - 6027-852
interval and count must be positive integers. - 6027-853
interval must be less than 1024. - 6027-854
count must be less than 1024. - 6027-855
Unable to connect to server, mmfsd is not started. - 6027-856
No information to report. - 6027-857
Error retrieving values. - 6027-858
File system not mounted. - 6027-859
Set DIRECTIO failed - 6027-860
-d is not appropriate for an NFSv4 ACL - 6027-861
Set afm ctl failed - 6027-862
Incorrect storage pool name poolName. - 6027-863
File cannot be assigned to storage pool 'poolName'. - 6027-864
Set storage pool failed. - 6027-865
Restripe file data failed. - 6027-866 [E]
Storage pools have not been enabled for this file system. - 6027-867
Change storage pool is not permitted. - 6027-868
mmchattr failed. - 6027-869
File replication exceeds number of failure groups in destination storage pool. - 6027-870 [E]
Error on getcwd(): errorString. Try an absolute path instead of just pathName - 6027-871 [E]
Error on gpfs_get_pathname_from_ fssnaphandle(pathName): errorString. - 6027-872 [E]
pathName is not within a mounted GPFS file system. - 6027-873 [W]
Error on gpfs_stat_inode([pathName/fileName],inodeNumber.genNumber): errorString - 6027-874 [E]
Error: incorrect Date@Time (YYYY-MM-DD@HH:MM:SS) specification: specification - 6027-875 [E]
Error on gpfs_stat(pathName): errorString - 6027-876 [E]
Error starting directory scan(pathName): errorString - 6027-877 [E]
Error opening pathName: errorString - 6027-878 [E]
Error on gpfs_fcntl(pathName): errorString (offset=offset) - 6027-879 [E]
Error deleting pathName: errorString - 6027-880
Error on gpfs_seek_inode(inodeNumber): errorString - 6027-881 [E]
Error on gpfs_iopen([rootPath/pathName],inodeNumber): errorString - 6027-882 [E]
Error on gpfs_ireaddir(rootPath/pathName): errorString - 6027-883
Error on gpfs_next_inode(maxInodeNumber): errorString - 6027-884 [E:nnn]
Error during directory scan - 6027-885 [E:nnn]
Error during inode scan: errorString - 6027-886 [E:nnn]
Error during policy decisions scan - 6027-887 [W]
Error on gpfs_igetstoragepool(dataPoolId): errorString - 6027-888 [W]
Error on gpfs_igetfilesetname(filesetId): errorString - 6027-889 [E]
Error on gpfs_get_fssnaphandle(rootPath): errorString. - 6027-890 [E]
Error on gpfs_open_inodescan(rootPath): errorString - 6027-891 [X]
WEIGHT(thresholdValue) UNKNOWN pathName - 6027-892 [E]
Error on pthread_create: where #threadNumber_or_portNumber_or_ socketNumber: errorString - 6027-893 [X]
Error on pthread_mutex_init: errorString - 6027-894 [X]
Error on pthread_mutex_lock: errorString - 6027-895 [X]
Error on pthread_mutex_unlock: errorString - 6027-896 [X]
Error on pthread_cond_init: errorString - 6027-897 [X]
Error on pthread_cond_signal: errorString - 6027-898 [X]
Error on pthread_cond_broadcast: errorString - 6027-899 [X]
Error on pthread_cond_wait: errorString - 6027-900 [E]
Error opening work file fileName: errorString - 6027-901 [E]
Error writing to work file fileName: errorString - 6027-902 [E]
Error parsing work file fileName. Service index: number - 6027-903 [E:nnn]
Error while loading policy rules. - 6027-904 [E]
Error returnCode from PD writer for inode=inodeNumber pathname=pathName - 6027-905 [E]
Error: Out of memory. Service index: number - 6027-906 [E:nnn]
Error on system(command) - 6027-907 [E:nnn]
Error from sort_file(inodeListname, sortCommand,sortInodeOptions,tempDir) - 6027-908 [W]
Attention: In RULE 'ruleName' (ruleNumber), the pool named by "poolName 'poolType'" is not defined in the file system. - 6027-909 [E]
Error on pthread_join: where #threadNumber: errorString - 6027-910 [E:nnn]
Error during policy execution - 6027-911 [E]
Error on changeSpecification change for pathName. errorString - 6027-912 [E]
Error on restriping of pathName. errorString - 6027-913
Desired replication exceeds number of failure groups. - 6027-914
Insufficient space in one of the replica failure groups. - 6027-915
Insufficient space to properly balance file. - 6027-916
Too many disks unavailable to properly balance file. - 6027-917
All replicas of a data block were previously deleted. - 6027-918
Cannot make this change to a nonzero length file. - 6027-919
Replication parameter range error (value, value). - 6027-920 [E]
Error on pthread_detach(self): where: errorString - 6027-921 [E]
Error on socket socketName(hostName): errorString - 6027-922 [X]
Error in Mtconx - p_accepts should not be empty - 6027-923 [W]
Error - command client is an incompatible version: hostName protocolVersion - 6027-924 [X]
Error - unrecognized client response from hostName: clientResponse - 6027-925
Directory cannot be assigned to storage pool 'poolName'. - 6027-926
Symbolic link cannot be assigned to storage pool 'poolName'. - 6027-927
System file cannot be assigned to storage pool 'poolName'. - 6027-928 [E]
Error: filesystem/device fileSystem has no snapshot with name snapshotName. - 6027-929 [W]
Attention: In RULE 'ruleName' (ruleNumber), both pools 'poolName' and 'poolName' are EXTERNAL. This is not a supported migration. - 6027-930 [W]
Attention: In RULE 'ruleName' LIST name 'listName' appears, but there is no corresponding EXTERNAL LIST 'listName' EXEC ... OPTS ... rule to specify a program to process the matching files. - 6027-931 [E]
Error - The policy evaluation phase did not complete. - 6027-932 [E]
Error - The policy execution phase did not complete. - 6027-933 [W]
EXEC 'wouldbeScriptPathname' of EXTERNAL POOL or LIST 'PoolOrListName' fails TEST with code scriptReturnCode on this node. - 6027-934 [W]
Attention: Specified snapshot: 'SnapshotName' will be ignored because the path specified: 'PathName' is not within that snapshot. - 6027-935 [W]
Attention: In RULE 'ruleName' (ruleNumber) LIMIT or REPLICATE clauses are ignored; not supported for migration to EXTERNAL pool 'storagePoolName'. - 6027-936 [W]
Error - command master is an incompatible version. - 6027-937 [E]
Error creating shared temporary sub-directory subDirName: subDirPath - 6027-938 [E]
Error closing work file fileName: errorString - 6027-939 [E]
Error on gpfs_quotactl(pathName,commandCode, resourceId): errorString - 6027-940
Open failed. - 6027-941
Set replication failed. - 6027-943
-M and -R are only valid for zero length files. - 6027-944
-m value exceeds number of failure groups for metadata. - 6027-945
-r value exceeds number of failure groups for data. - 6027-946
Not a regular file or directory. - 6027-947
Stat failed: A file or directory in the path name does not exist. - 6027-948 [E:nnn]
fileName: get clone attributes failed: errorString - 6027-949 [E]
fileName: invalid clone attributes. - 6027-950 [E:nnn]
File cloning requires the 'fastea' feature to be enabled. - 6027-951 [E]
Error on operationName to work file fileName: errorString - 6027-953
Failed to get a handle for fileset filesetName, snapshot snapshotName in file system fileSystem. errorMessage. - 6027-954
Failed to get the maximum inode number in the active file system. errorMessage. - 6027-955
Failed to set the maximum allowed memory for the specified fileSystem command. - 6027-956
Cannot allocate enough buffer to record different items. - 6027-957
Failed to get the root directory inode of fileset filesetName - 6027-959
'fileName' is not a regular file. - 6027-960
cannot access 'fileName': errorString. - 6027-961
Cannot execute command. - 6027-962
Failed to list fileset filesetName. - 6027-963
EDITOR environment variable not set - 6027-964
EDITOR environment variable must be an absolute path name - 6027-965
Cannot create temporary file - 6027-966
Cannot access fileName - 6027-967
Should the modified ACL be applied? (yes) or (no) - 6027-971
Cannot find fileName - 6027-972
name is not a directory (-d not valid). - 6027-973
Cannot allocate number byte buffer for ACL. - 6027-974
Failure reading ACL (rc=number). - 6027-976
Failure writing ACL (rc=number). - 6027-977
Authorization failure - 6027-978
Incorrect, duplicate, or missing access control entry detected. - 6027-979
Incorrect ACL entry: entry. - 6027-980
name is not a valid user name. - 6027-981
name is not a valid group name. - 6027-982
name is not a valid ACL entry type. - 6027-983
name is not a valid permission set. - 6027-985
An error was encountered while deleting the ACL (rc=value). - 6027-986
Cannot open fileName. - 6027-987
name is not a valid special name. - 6027-988
type is not a valid NFS V4 type. - 6027-989
name is not a valid NFS V4 flag. - 6027-990
Missing permissions (value found, value are required). - 6027-991
Combining FileInherit and DirInherit makes the mask ambiguous. - 6027-992
Subdirectory name already exists. Unable to create snapshot. - 6027-993
Keyword aclType is incorrect. Valid values are: 'posix', 'nfs4', 'native'. - 6027-994
ACL permissions cannot be denied to the file owner. - 6027-995
This command will run on a remote node, nodeName. - 6027-996 [E:nnn]
Error reading policy text from: fileName - 6027-997 [W]
Attention: RULE 'ruleName' attempts to redefine EXTERNAL POOLorLISTliteral 'poolName', ignored. - 6027-998 [E]
Error in FLR/PDR serving for client clientHostNameAndPortNumber: FLRs=numOfFileListRecords PDRs=numOfPolicyDecisionResponses pdrs=numOfPolicyDecisionResponseRecords - 6027-999 [E]
Authentication failed: myNumericNetworkAddress with partnersNumericNetworkAddress (code=codeIndicatingProtocolStepSequence rc=errnoStyleErrorCode) - 6027-1004
Incorrect [nodelist] format in file: nodeListLine - 6027-1005
Common is not sole item on [] line number. - 6027-1006
Incorrect custom [ ] line number. - 6027-1007
attribute found in common multiple times: attribute. - 6027-1008
Attribute found in custom multiple times: attribute. - 6027-1022
Missing mandatory arguments on command line. - 6027-1023
invalid maxBlockSize parameter: value - 6027-1028
Incorrect value for -name flag. - 6027-1029
Incorrect characters in integer field for -name option. - 6027-1030
Value below minimum for -optionLetter option. Valid range is from value to value - 6027-1031
Value above maximum for option -optionLetter. Valid range is from value to value. - 6027-1032
Incorrect option optionName. - 6027-1033
Option optionName specified twice. - 6027-1034
Missing argument after optionName option. - 6027-1035
Option -optionName is mandatory. - 6027-1036
Option expected at string. - 6027-1038
IndirectSize must be <= BlockSize and must be a multiple of LogicalSectorSize (512). - 6027-1039
InodeSize must be a multiple of LocalSectorSize (512). - 6027-1040
InodeSize must be less than or equal to Blocksize. - 6027-1042
DefaultMetadataReplicas must be less than or equal to MaxMetadataReplicas. - 6027-1043
DefaultDataReplicas must be less than or equal MaxDataReplicas. - 6027-1055
LogicalSectorSize must be a multiple of 512 - 6027-1056
Blocksize must be a multiple of LogicalSectorSize × 32 - 6027-1057
InodeSize must be less than or equal to Blocksize. - 6027-1059
Mode must be M or S: mode - 6027-1084
The specified block size (valueK) exceeds the maximum allowed block size currently in effect (valueK). Either specify a smaller value for the -B parameter, or increase the maximum block size by issuing: mmchconfig maxblocksize=valueK and restart the GPFS daemon. - 6027-1113
Incorrect option: option. - 6027-1119
Obsolete option: option. - 6027-1120
Interrupt received: No changes made. - 6027-1123
Disk name must be specified in disk descriptor. - 6027-1124
Disk usage must be dataOnly, metadataOnly, descOnly, or dataAndMetadata. - 6027-1132
Interrupt received: changes not propagated. - 6027-1133
Interrupt received. Only a subset of the parameters were changed. - 6027-1135
Restriping may not have finished. - 6027-1136
option option specified twice. - 6027-1137
option value must be yes or no. - 6027-1138
Incorrect extra argument: argument - 6027-1140
Incorrect integer for option: number. - 6027-1141
No disk descriptor file specified. - 6027-1142
File fileName already exists. - 6027-1143
Cannot open fileName. - 6027-1144
Incompatible cluster types. You cannot move file systems that were created by GPFS cluster type sourceCluster into GPFS cluster type targetCluster. - 6027-1145
parameter must be greater than 0: value - 6027-1147
Error converting diskName into an NSD. - 6027-1148
File system fileSystem already exists in the cluster. Use mmchfs -W to assign a new device name for the existing file system. - 6027-1149
fileSystem is defined to have mount point mountpoint. There is already such a mount point in the cluster. Use mmchfs -T to assign a new mount point to the existing file system. - 6027-1150
Error encountered while importing disk diskName. - 6027-1151
Disk diskName already exists in the cluster. - 6027-1152
Block size must be 64K, 128K, 256K, 512K, 1M, 2M, 4M, 8M or 16M. - 6027-1153
At least one node in the cluster must be defined as a quorum node. - 6027-1154
Incorrect node node specified for command. - 6027-1155
The NSD servers for the following disks from file system fileSystem were reset or not defined: diskList - 6027-1156
The NSD servers for the following free disks were reset or not defined: diskList - 6027-1157
Use the mmchnsd command to assign NSD servers as needed. - 6027-1159
The following file systems were not imported: fileSystemList - 6027-1160
The drive letters for the following file systems have been reset: fileSystemList. - 6027-1161
Use the dash character (-) to separate multiple node designations. - 6027-1162
Use the semicolon character (;) to separate the disk names. - 6027-1163
GPFS is still active on nodeName. - 6027-1164
Use mmchfs -t to assign drive letters as needed. - 6027-1165
The PR attributes for the following disks from file system fileSystem were reset or not yet established: diskList - 6027-1166
The PR attributes for the following free disks were reset or not yet established: diskList - 6027-1167
Use mmchconfig to enable Persistent Reserve in the cluster as needed. - 6027-1168
Inode size must be 512, 1K or 4K. - 6027-1169
attribute must be value. - 6027-1178
parameter must be from value to value: valueSpecified - 6027-1188
Duplicate disk specified: disk - 6027-1189
You cannot delete all the disks. - 6027-1197
parameter must be greater than value: value. - 6027-1200
tscrfs failed. Cannot create device - 6027-1201
Disk diskName does not belong to file system fileSystem. - 6027-1202
Active disks are missing from the GPFS configuration data. - 6027-1203
Attention: File system fileSystem may have some disks that are in a non-ready state. Issue the command: mmcommon recoverfs fileSystem - 6027-1204
command failed. - 6027-1205
Failed to connect to remote cluster clusterName. - 6027-1206
File system fileSystem belongs to cluster clusterName. Command is not allowed for remote file systems. - 6027-1207
There is already an existing file system using value. - 6027-1208
File system fileSystem not found in cluster clusterName. - 6027-1209
GPFS is down on this node. - 6027-1210
GPFS is not ready to handle commands yet. - 6027-1211
fileSystem refers to file system fileSystem in cluster clusterName. - 6027-1212
File system fileSystem does not belong to cluster clusterName. - 6027-1213
command failed. Error code errorCode. - 6027-1214
Unable to enable Persistent Reserve on the following disks: diskList - 6027-1215
Unable to reset the Persistent Reserve attributes on one or more disks on the following nodes: nodeList - 6027-1216
File fileName contains additional error information. - 6027-1217
A disk descriptor contains an incorrect separator character. - 6027-1218
Node nodeName does not have a GPFS server license designation. - 6027-1219
NSD discovery on node nodeName failed with return code value. - 6027-1220
Node nodeName cannot be used as an NSD server for Persistent Reserve disk diskName because it is not an AIX node. - 6027-1221
The number of NSD servers exceeds the maximum (value) allowed. - 6027-1222
Cannot assign a minor number for file system fileSystem (major number deviceMajorNumber). - 6027-1223
ipAddress cannot be used for NFS serving; it is used by the GPFS daemon. - 6027-1224
There is no file system with drive letter driveLetter. - 6027-1225
Explicit drive letters are supported only in a Windows environment. Specify a mount point or allow the default settings to take effect. - 6027-1226
Explicit mount points are not supported in a Windows environment. Specify a drive letter or allow the default settings to take effect. - 6027-1227
The main GPFS cluster configuration file is locked. Retrying … - 6027-1228
Lock creation successful. - 6027-1229
Timed out waiting for lock. Try again later. - 6027-1230
diskName is a tiebreaker disk and cannot be deleted. - 6027-1231
GPFS detected more than eight quorum nodes while node quorum with tiebreaker disks is in use. - 6027-1232
GPFS failed to initialize the tiebreaker disks. - 6027-1233
Incorrect keyword: value. - 6027-1234
Adding node node to the cluster will exceed the quorum node limit. - 6027-1235
The fileName kernel extension does not exist. Use the mmbuildgpl command to create the needed kernel extension for your kernel or copy the binaries from another node with the identical environment. - 6027-1236
Unable to verify kernel/module configuration. - 6027-1237
The GPFS daemon is still running; use the mmshutdown command. - 6027-1238
Module fileName is still in use. Unmount all GPFS file systems and issue the command: mmfsadm cleanup - 6027-1239
Error unloading module moduleName. - 6027-1240
Module fileName is already loaded. - 6027-1241
diskName was not found in /proc/partitions. - 6027-1242
GPFS is waiting for requiredCondition - 6027-1243
command: Processing user configuration file fileName - 6027-1244
configParameter is set by the mmcrcluster processing. Line in error: configLine. The line will be ignored; processing continues. - 6027-1245
configParameter must be set with the command command. Line in error: configLine. The line is ignored; processing continues. - 6027-1246
configParameter is an obsolete parameter. Line in error: configLine. The line is ignored; processing continues. - 6027-1247
configParameter cannot appear in a node-override section. Line in error: configLine. The line is ignored; processing continues. - 6027-1248
Mount point can not be a relative path name: path - 6027-1249
operand can not be a relative path name: path. - 6027-1250
Key file is not valid. - 6027-1251
Key file mismatch. - 6027-1252
Node nodeName already belongs to the GPFS cluster. - 6027-1253
Incorrect value for option option. - 6027-1254
Warning: Not all nodes have proper GPFS license designations. Use the mmchlicense command to designate licenses as needed. - 6027-1255
There is nothing to commit. You must first run: command. - 6027-1256
The current authentication files are already committed. - 6027-1257
There are uncommitted authentication files. You must first run: command. - 6027-1258
You must establish a cipher list first. Run: command. - 6027-1259
command not found. Ensure the OpenSSL code is properly installed. - 6027-1260
File fileName does not contain any typeOfStanza stanzas. - 6027-1261
descriptorField must be specified in descriptorType descriptor. - 6027-1262
Unable to obtain the GPFS configuration file lock. Retrying ... - 6027-1263
Unable to obtain the GPFS configuration file lock. - 6027-1268
Missing arguments. - 6027-1269
The device name device starts with a slash, but not /dev/. - 6027-1270
The device name device contains a slash, but not as its first character. - 6027-1271
Unexpected error from command. Return code: value - 6027-1272
Unknown user name userName. - 6027-1273
Unknown group name groupName. - 6027-1274
Unexpected error obtaining the lockName lock. - 6027-1275
Daemon node adapter Node was not found on admin node Node. - 6027-1276
Command failed for disks: diskList. - 6027-1277
No contact nodes were provided for cluster clusterName. - 6027-1278
None of the contact nodes in cluster clusterName can be reached. - 6027-1287
Node nodeName returned ENODEV for disk diskName. - 6027-1288
Remote cluster clusterName was not found. - 6027-1289
Name name is not allowed. It contains the following invalid special character: char - 6027-1290
GPFS configuration data for file system fileSystem may not be in agreement with the on-disk data for the file system. Issue the command: mmcommon recoverfs fileSystem - 6027-1291
Options name and name cannot be specified at the same time. - 6027-1292
The -N option cannot be used with attribute name. - 6027-1293
There are no remote file systems. - 6027-1294
Remote file system fileSystem is not defined. - 6027-1295
The GPFS configuration information is incorrect or not available. - 6027-1296
Device name cannot be 'all'. - 6027-1297
Each device specifies metadataOnly for disk usage. This file system could not store data. - 6027-1298
Each device specifies dataOnly for disk usage. This file system could not store metadata. - 6027-1299
Incorrect value value specified for failure group. - 6027-1300
No file systems were found. - 6027-1301
The NSD servers specified in the disk descriptor do not match the NSD servers currently in effect. - 6027-1302
clusterName is the name of the local cluster. - 6027-1303
This function is not available in the GPFS Express Edition. - 6027-1304
Missing argument after option option. - 6027-1305
Prerequisite libraries not found or correct version not installed. Ensure productName is properly installed. - 6027-1306
Command command failed with return code value. - 6027-1307
Disk disk on node nodeName already has a volume group vgName that does not appear to have been created by this program in a prior invocation. Correct the descriptor file or remove the volume group and retry. - 6027-1308
feature is not available in the GPFS Express Edition. - 6027-1309
Storage pools are not available in the GPFS Express Edition. - 6027-1332
Cannot find disk with command. - 6027-1333
The following nodes could not be restored: nodeList. Correct the problems and use the mmsdrrestore command to recover these nodes. - 6027-1334
Incorrect value for option option. Valid values are: validValues. - 6027-1335
Command completed: Not all required changes were made. - 6027-1338
Command is not allowed for remote file systems. - 6027-1339
Disk usage value is incompatible with storage pool name. - 6027-1340
File fileName not found. Recover the file or run mmauth genkey. - 6027-1341
Starting force unmount of GPFS file systems - 6027-1342
Unmount not finished after value seconds. Waiting value more seconds. - 6027-1343
Unmount not finished after value seconds. - 6027-1344
Shutting down GPFS daemons - 6027-1345
Finished - 6027-1347
Disk with NSD volume id NSD volume id no longer exists in the GPFS cluster configuration data but the NSD volume id was not erased from the disk. To remove the NSD volume id, issue: mmdelnsd -p NSD volume id - 6027-1348
Disk with NSD volume id NSD volume id no longer exists in the GPFS cluster configuration data but the NSD volume id was not erased from the disk. To remove the NSD volume id, issue: mmdelnsd -p NSD volume id -N nodeNameList - 6027-1352
fileSystem is not a remote file system known to GPFS. - 6027-1357
An internode connection between GPFS nodes was disrupted. - 6027-1358
No clusters are authorized to access this cluster. - 6027-1359
Cluster clusterName is not authorized to access this cluster. - 6027-1361
Attention: There are no available valid VFS type values for mmfs in /etc/vfs. - 6027-1362
There are no remote cluster definitions. - 6027-1363
Remote cluster clusterName is not defined. - 6027-1364
No disks specified - 6027-1365
Disk diskName already belongs to file system fileSystem. - 6027-1366
File system fileSystem has some disks that are in a non-ready state. - 6027-1367
Attention: Not all disks were marked as available. - 6027-1368
This GPFS cluster contains declarations for remote file systems and clusters. You cannot delete the last node. First use the delete option of the mmremotecluster and mmremotefs commands. - 6027-1370
The following nodes could not be reached: - 6027-1371
Propagating the cluster configuration data to all affected nodes. This is an asynchronous process. - 6027-1373
There is no file system information in input file fileName. - 6027-1374
File system fileSystem was not found in input file fileName. - 6027-1375
The following file systems were not imported: fileSystem. - 6027-1377
Attention: Unknown attribute specified: name. Press the ENTER key to continue. - 6027-1378
Incorrect record found in the mmsdrfs file (code value): - 6027-1379
There is no file system with mount point mountpoint. - 6027-1380
File system fileSystem is already mounted at mountpoint. - 6027-1381
Mount point cannot be specified when mounting all file systems. - 6027-1382
This node does not belong to a GPFS cluster. - 6027-1383
There is no record for this node in file fileName. Either the node is not part of the cluster, the file is for a different cluster, or not all of the node's adapter interfaces have been activated yet. - 6027-1386
Unexpected value for Gpfs object: value. - 6027-1388
File system fileSystem is not known to the GPFS cluster. - 6027-1390
Node node does not belong to the GPFS cluster, or was specified as input multiple times. - 6027-1393
Incorrect node designation specified: type. - 6027-1394
Operation not allowed for the local cluster. - 6027-1450
Could not allocate storage. - 6027-1500 [E]
Open devicetype device failed with error: - 6027-1501 [X]
Volume label of disk name is name, should be uid. - 6027-1502 [X]
Volume label of disk diskName is corrupt. - 6027-1503
Completed adding disks to file system fileSystem. - 6027-1504
File name could not be run with err error. - 6027-1505
Could not get minor number for name. - 6027-1507
READ_KEYS ioctl failed with errno=returnCode, tried timesTried times. Related values are scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-1508
Registration failed with errno=returnCode, tried timesTried times. Related values are scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-1509
READRES ioctl failed with errno=returnCode, tried timesTried times. Related values are scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-1510 [E]
Error mounting file system stripeGroup on mountPoint; errorQualifier (gpfsErrno) - 6027-1511 [E]
Error unmounting file system stripeGroup; errorQualifier (gpfsErrno) - 6027-1512 [E]
WMI query for queryType failed; errorQualifier (gpfsErrno) - 6027-1513
DiskName is not an sg device, or sg driver is older than sg3 - 6027-1514
ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1515
READ KEY ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1516
REGISTER ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1517
READ RESERVE ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1518
RESERVE ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1519
INQUIRY ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1520
PREEMPT ABORT ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1521
Can not find register key registerKeyValue at device diskName. - 6027-1522
CLEAR ioctl failed with rc=returnCode. Related values are SCSI status=scsiStatusValue, host_status=hostStatusValue, driver_status=driverStatsValue. - 6027-1523
Disk name longer than value is not allowed. - 6027-1524
The READ_KEYS ioctl data does not contain the key that was passed as input. - 6027-1525
Invalid minReleaseLevel parameter: value - 6027-1530
Attention: parameter is set to value. - 6027-1531
parameter value - 6027-1532
Attention: parameter (value) is not valid in conjunction with parameter (value). - 6027-1533
parameter cannot be set dynamically. - 6027-1534
parameter must have a value. - 6027-1535
Unknown config name: parameter - 6027-1536
parameter must be set using the tschpool command. - 6027-1537 [E]
Connect failed to ipAddress: reason - 6027-1538 [I]
Connect in progress to ipAddress - 6027-1539 [E]
Connect progress select failed to ipAddress: reason - 6027-1540 [A]
Try and buy license has expired! - 6027-1541 [N]
Try and buy license expires in number days. - 6027-1542 [A]
Old shared memory exists but it is not valid nor cleanable. - 6027-1543
error propagating parameter. - 6027-1544 [W]
Sum of prefetchthreads(value), worker1threads(value) and nsdMaxWorkerThreads (value) exceeds value. Reducing them to value, value and value. - 6027-1545 [A]
The GPFS product that you are attempting to run is not a fully functioning version. This probably means that this is an update version and not the full product version. Install the GPFS full product version first, then apply any applicable update version before attempting to start GPFS. - 6027-1546 [W]
Attention: parameter size of value is too small. New value is value. - 6027-1547 [A]
Error initializing daemon: performing shutdown - 6027-1548 [A]
Error: daemon and kernel extension do not match. - 6027-1549 [A]
Attention: custom-built kernel extension; the daemon and kernel extension do not match. - 6027-1550 [W]
Error: Unable to establish a session with an Active Directory server. ID remapping via Microsoft Identity Management for Unix will be unavailable. - 6027-1555
Mount point and device name cannot be equal: name - 6027-1556
Interrupt received. - 6027-1557
You must first generate an authentication key file. Run: mmauth genkey new. - 6027-1559
The -i option failed. Changes will take effect after GPFS is restarted. - 6027-1560
This GPFS cluster contains file systems. You cannot delete the last node. - 6027-1561
Attention: Failed to remove node-specific changes. - 6027-1562
command command cannot be executed. Either none of the nodes in the cluster are reachable, or GPFS is down on all of the nodes. - 6027-1563
Attention: The file system may no longer be properly balanced. - 6027-1564
To change the authentication key for the local cluster, run: mmauth genkey. - 6027-1565
disk not found in file system fileSystem. - 6027-1566
Remote cluster clusterName is already defined. - 6027-1567
fileSystem from cluster clusterName is already defined. - 6027-1568
command command failed. Only parameterList changed. - 6027-1570
virtual shared disk support is not installed. - 6027-1571
commandName does not exist or failed; automount mounting may not work. - 6027-1572
The command must run on a node that is part of the cluster. - 6027-1573
Command completed: No changes made. - 6027-1574
Permission failure. The command requires root authority to execute. - 6027-1578
File fileName does not contain node names. - 6027-1579
File fileName does not contain data. - 6027-1587
Unable to determine the local device name for disk nsdName on node nodeName. - 6027-1588
Unknown GPFS execution environment: value - 6027-1590
nodeName cannot be reached. - 6027-1591
Attention: Unable to retrieve GPFS cluster files from node nodeName - 6027-1592
Unable to retrieve GPFS cluster files from node nodeName - 6027-1594
Run the command command until successful. - 6027-1595
No nodes were found that matched the input specification. - 6027-1596
The same node was specified for both the primary and the secondary server. - 6027-1597
Node node is specified more than once. - 6027-1598
Node nodeName was not added to the cluster. The node appears to already belong to a GPFS cluster. - 6027-1599
The level of GPFS on node nodeName does not support the requested action. - 6027-1600
Make sure that the following nodes are available: nodeList - 6027-1602
nodeName is not a member of this cluster. - 6027-1603
The following nodes could not be added to the GPFS cluster: nodeList. Correct the problems and use the mmaddnode command to add these nodes to the cluster. - 6027-1604
Information cannot be displayed. Either none of the nodes in the cluster are reachable, or GPFS is down on all of the nodes. - 6027-1610
Disk diskName is the only disk in file system fileSystem. You cannot replace a disk when it is the only remaining disk in the file system. - 6027-1613
WCOLL (working collective) environment variable not set. - 6027-1614
Cannot open file fileName. Error string was: errorString. - 6027-1615
nodeName remote shell process had return code value. - 6027-1616
Caught SIG signal - terminating the child processes. - 6027-1617
There are no available nodes on which to run the command. - 6027-1618
Unable to pipe. Error string was: errorString. - 6027-1619
Unable to redirect outputStream. Error string was: string. - 6027-1623
command: Mounting file systems ... - 6027-1625
option cannot be used with attribute name. - 6027-1626
Command is not supported in the type environment. - 6027-1627
The following nodes are not aware of the configuration server change: nodeList. Do not start GPFS on the above nodes until the problem is resolved. - 6027-1628
Cannot determine basic environment information. Not enough nodes are available. - 6027-1629
Error found while checking node descriptor descriptor - 6027-1630
The GPFS cluster data on nodeName is back level. - 6027-1631
The commit process failed. - 6027-1632
The GPFS cluster configuration data on nodeName is different than the data on nodeName. - 6027-1633
Failed to create a backup copy of the GPFS cluster data on nodeName. - 6027-1634
The GPFS cluster configuration server node nodeName cannot be removed. - 6027-1636
Error found while checking disk descriptor descriptor - 6027-1637
command quitting. None of the specified nodes are valid. - 6027-1638
Command: There are no unassigned nodes in the cluster. - 6027-1639
Command failed. Examine previous error messages to determine cause. - 6027-1642
command: Starting GPFS ... - 6027-1643
The number of quorum nodes exceeds the maximum (number) allowed. - 6027-1644
Attention: The number of quorum nodes exceeds the suggested maximum (number). - 6027-1645
Node nodeName is fenced out from disk diskName. - 6027-1647
Unable to find disk with NSD volume id NSD volume id. - 6027-1648
GPFS was unable to obtain a lock from node nodeName. - 6027-1661
Failed while processing disk descriptor descriptor on node nodeName. - 6027-1662
Disk device deviceName refers to an existing NSD name - 6027-1663
Disk descriptor descriptor should refer to an existing NSD. Use mmcrnsd to create the NSD. - 6027-1664
command: Processing node nodeName - 6027-1665
Issue the command from a node that remains in the cluster. - 6027-1666 [I]
No disks were found. - 6027-1670
Incorrect or missing remote shell command: name - 6027-1671
Incorrect or missing remote file copy command: name - 6027-1672
option value parameter must be an absolute path name. - 6027-1674
command: Unmounting file systems ... - 6027-1677
Disk diskName is of an unknown type. - 6027-1680
Disk name diskName is already registered for use by GPFS. - 6027-1681
Node nodeName is being used as an NSD server. - 6027-1685
Processing continues without lock protection. - 6027-1688
Command was unable to obtain the lock for the GPFS system data. Unable to reach the holder of the lock nodeName. Check the preceding messages, if any. Follow the procedure outlined in the GPFS: Problem Determination Guide. - 6027-1689
vpath disk diskName is not recognized as an IBM SDD device. - 6027-1699
Remount failed for file system fileSystem. Error code errorCode. - 6027-1700
Failed to load LAPI library. functionName not found. Changing communication protocol to TCP. - 6027-1701
mmfsd waiting to connect to mmspsecserver. Setting up to retry every number seconds for number minutes. - 6027-1702
Process pid failed at functionName call, socket socketName, errno value - 6027-1703
The processName process encountered error: errorString. - 6027-1704
mmspsecserver (pid number) ready for service. - 6027-1705
command: incorrect number of connections (number), exiting... - 6027-1706
mmspsecserver: parent program is not "mmfsd", exiting... - 6027-1707
mmfsd connected to mmspsecserver - 6027-1708
The mmfsd daemon failed to fork mmspsecserver. Failure reason explanation - 6027-1709 [I]
Accepted and connected to ipAddress - 6027-1710 [N]
Connecting to ipAddress - 6027-1711 [I]
Connected to ipAddress - 6027-1712
Unexpected zero bytes received from name. Continuing. - 6027-1715
EINVAL trap from connect call to ipAddress (socket name) - 6027-1716 [N]
Close connection to ipAddress - 6027-1717 [E]
Error initializing the configuration server, err value - 6027-1718 [E]
Could not run command name, err value - 6027-1724 [E]
The key used by the cluster named clusterName has changed. Contact the administrator to obtain the new key and register it using "mmremotecluster update". - 6027-1725 [E]
[E] The key used by the contact node named contactNodeName has changed. Contact the administrator to obtain the new key and register it using mmauth update. - 6027-1726 [E]
The administrator of the cluster named clusterName requires authentication. Contact the administrator to obtain the clusters key and register the key using "mmremotecluster update". - 6027-1727 [E]
The administrator of the cluster named clusterName does not require authentication. Unregister the clusters key using "mmremotecluster update". - 6027-1728 [E]
Remote mounts are not enabled within the cluster named clusterName. Contact the administrator and request that they enable remote mounts. - 6027-1729 [E]
The cluster named clusterName has not authorized this cluster to mount file systems. Contact the cluster administrator and request access. - 6027-1730 [E]
Unsupported cipherList cipherList requested. - 6027-1731 [E]
Unsupported cipherList cipherList requested. - 6027-1732 [X]
Remote mounts are not enabled within this cluster. - 6027-1733
OpenSSL dynamic lock support could not be loaded. - 6027-1734 [E]
OpenSSL engine support could not be loaded. - 6027-1735 [E]
Close connection to ipAddress. Attempting reconnect. - 6027-1736 [N]
Reconnected to ipAddress - 6027-1737 [N]
Close connection to ipAddress (errorString). - 6027-1738 [E]
Close connection to ipAddress (errorString). Attempting reconnect. - 6027-1739 [X]
Accept socket connection failed: err value. - 6027-1740 [E]
Timed out waiting for a reply from node ipAddress. - 6027-1741 [E]
Error code value received from node ipAddress. - 6027-1742 [E]
Message ID value was lost by node ipAddress. - 6027-1743 [W]
Failed to load GSKit library path: (dlerror) errorMessage - 6027-1744 [I]
GSKit library loaded and initialized. - 6027-1745 [E]
Unable to resolve symbol for routine: functionName (dlerror) errorMessage - 6027-1746 [E]
Failed to load or initialize GSKit library: error value - 6027-1747 [W]
The TLS handshake with node ipAddress failed with error value (handshakeType). - 6027-1748 [W]
A secure receive from node ipAddress failed with error value. - 6027-1749 [W]
A secure send to node ipAddress failed with error value. - 6027-1750 [N]
The handshakeType TLS handshake with node ipAddress was cancelled: connection reset by peer (return code value). - 6027-1751 [N]
A secure send to node ipAddress was cancelled: connection reset by peer (return code value). - 6027-1752 [N]
A secure receive to node ipAddress was cancelled: connection reset by peer (return code value). - 6027-1753 [E]
The crypto library with FIPS support is not available for this architecture. Disable FIPS mode and reattempt the operation. - 6027-1754 [E]
Failed to initialize the crypto library in FIPS mode. Ensure that the crypto library package was correctly installed. - 6027-1755 [W]
The certificate for 'canonicalName' is expired. Validity period is from begDate to endDate. - 6027-1756 [E]
The TCP connection to IP address ipAddress (socket socketNum) state is unexpected: ca_state=caStateValue unacked=unackedCount rto=rtoValue. - 6027-1803 [E]
Global NSD disk, name, not found. - 6027-1804 [E]
I/O to NSD disk, name, fails. No such NSD locally found. - 6027-1805 [N]
Rediscovered nsd server access to name. - 6027-1806 [X]
A Persistent Reserve could not be established on device name (deviceName): errorLine. - 6027-1807 [E]
NSD nsdName is using Persistent Reserve, this will require an NSD server on an osName node. - 6027-1808 [A]
Unable to reserve space for NSD buffers. Increase pagepool size to at least requiredPagePoolSize MB. Refer to the IBM Spectrum Scale: Administration Guide for more information on selecting an appropriate pagepool size. - 6027-1809 [E]
The defined server serverName for NSD NsdName couldn't be resolved. - 6027-1810 [I]
Vdisk server recovery: delay number sec. for safe recovery. - 6027-1811 [I]
Vdisk server recovery: delay complete. - 6027-1812 [E]
Rediscovery failed for name. - 6027-1813 [A]
Error reading volume identifier (for objectName name) from configuration file. - 6027-1814 [E]
Vdisk vdiskName cannot be associated with its recovery group recoveryGroupName. This vdisk will be ignored. - 6027-1815 [A]
Error reading volume identifier (for NSD name) from configuration file. - 6027-1816 [E]
The defined server serverName for recovery group recoveryGroupName could not be resolved. - 6027-1817 [E]
Vdisks are defined, but no recovery groups are defined. - 6027-1818 [I]
Relinquished recovery group recoveryGroupName (err errorCode). - 6027-1819
Disk descriptor for name refers to an existing pdisk. - 6027-1820
Disk descriptor for name refers to an existing NSD. - 6027-1821
Error errno writing disk descriptor on name. - 6027-1822
Error errno reading disk descriptor on name. - 6027-1823
Path error, name and name are the same disk. - 6027-1824 [X]
An unexpected Device Mapper path dmDevice (nsdId) has been detected. The new path does not have a Persistent Reserve set up. Server disk diskName will be put offline - 6027-1825 [A]
Unrecoverable NSD checksum error on I/O to NSD disk nsdName, using server serverName. Exceeds retry limit number. - 6027-1826 [W]
The host name of the server serverName that is defined for NSD local cache NsdName could not be resolved. - 6027-1900
Failed to stat pathName. - 6027-1901
pathName is not a GPFS file system object. - 6027-1902
The policy file cannot be determined. - 6027-1903
path must be an absolute path name. - 6027-1904
Device with major/minor numbers number and number already exists. - 6027-1905
name was not created by GPFS or could not be refreshed. - 6027-1906
There is no file system with drive letter driveLetter. - 6027-1908
The option option is not allowed for remote file systems. - 6027-1909
There are no available free disks. Disks must be prepared prior to invoking command. Define the disks using the command command. - 6027-1910
Node nodeName is not a quorum node. - 6027-1911
File system fileSystem belongs to cluster clusterName. The option option is not allowed for remote file systems. - 6027-1922
IP aliasing is not supported (node). Specify the main device. - 6027-1927
The requested disks are not known to GPFS. - 6027-1929
cipherlist is not a valid cipher list. - 6027-1930
Disk diskName belongs to file system fileSystem. - 6027-1931
The following disks are not known to GPFS: diskNames. - 6027-1932
No disks were specified that could be deleted. - 6027-1933
Disk diskName has been removed from the GPFS cluster configuration data but the NSD volume id was not erased from the disk. To remove the NSD volume id, issue mmdelnsd -p NSDvolumeid. - 6027-1934
Disk diskName has been removed from the GPFS cluster configuration data but the NSD volume id was not erased from the disk. To remove the NSD volume id, issue: mmdelnsd -p NSDvolumeid -N nodeList. - 6027-1936
Node nodeName cannot support Persistent Reserve on disk diskName because it is not an AIX node. The disk will be used as a non-PR disk. - 6027-1937
A node was specified more than once as an NSD server in disk descriptor descriptor. - 6027-1938
configParameter is an incorrect parameter. Line in error: configLine. The line is ignored; processing continues. - 6027-1939
Line in error: line. - 6027-1940
Unable to set reserve policy policy on disk diskName on node nodeName. - 6027-1941
Cannot handle multiple interfaces for host hostName. - 6027-1942
Unexpected output from the 'host -t a name' command: - 6027-1943
Host name not found. - 6027-1945
Disk name diskName is not allowed. Names beginning with gpfs are reserved for use by GPFS. - 6027-1947
Use mmauth genkey to recover the file fileName, or to generate and commit a new key. - 6027-1948
Disk diskName is too large. - 6027-1949
Propagating the cluster configuration data to all affected nodes. - 6027-1950
Local update lock is busy. - 6027-1951
Failed to obtain the local environment update lock. - 6027-1962
Permission denied for disk diskName - 6027-1963
Disk diskName was not found. - 6027-1964
I/O error on diskName - 6027-1967
Disk diskName belongs to back-level file system fileSystem or the state of the disk is not ready. Use mmchfs -V to convert the file system to the latest format. Use mmchdisk to change the state of a disk. - 6027-1968
Failed while processing disk diskName. - 6027-1969
Device device already exists on node nodeName - 6027-1970
Disk diskName has no space for the quorum data structures. Specify a different disk as tiebreaker disk. - 6027-1974
None of the quorum nodes can be reached. - 6027-1975
The descriptor file contains more than one descriptor. - 6027-1976
The descriptor file contains no descriptor. - 6027-1977
Failed validating disk diskName. Error code errorCode. - 6027-1984
Name name is not allowed. It is longer than the maximum allowable length (length). - 6027-1985
mmfskxload: The format of the GPFS kernel extension is not correct for this version of AIX. - 6027-1986
junctionName does not resolve to a directory in deviceName. The junction must be within the specified file system. - 6027-1987
Name name is not allowed. - 6027-1988
File system fileSystem is not mounted. - 6027-1993
File fileName either does not exist or has an incorrect format. - 6027-1994
Did not find any match with the input disk address. - 6027-1995
Device deviceName is not mounted on node nodeName. - 6027-1996
Command was unable to determine whether file system fileSystem is mounted. - 6027-1998
Line lineNumber of file fileName is incorrect: - 6027-1999
Syntax error. The correct syntax is: string. - 6027-2000
Could not clear fencing for disk physicalDiskName. - 6027-2002
Disk physicalDiskName of type diskType is not supported for fencing. - 6027-2004
None of the specified nodes belong to this GPFS cluster. - 6027-2007
Unable to display fencing for disk physicalDiskName. - 6027-2008
For the logical volume specification -l lvName to be valid lvName must be the only logical volume in the volume group. However, volume group vgName contains logical volumes. - 6027-2009
logicalVolume is not a valid logical volume. - 6027-2010
vgName is not a valid volume group name. - 6027-2011
For the hdisk specification -h physicalDiskName to be valid physicalDiskName must be the only disk in the volume group. However, volume group vgName contains disks. - 6027-2012
physicalDiskName is not a valid physical volume name. - 6027-2013
pvid is not a valid physical volume id. - 6027-2014
Node node does not have access to disk physicalDiskName. - 6027-2015
Node node does not hold a reservation for disk physicalDiskName. - 6027-2016
SSA fencing support is not present on this node. - 6027-2017
Node ID nodeId is not a valid SSA node ID. SSA node IDs must be a number in the range of 1 to 128. - 6027-2018
The SSA node id is not set. - 6027-2019
Unable to retrieve the SSA node id. - 6027-2020
Unable to set fencing for disk physicalDiskName. - 6027-2021
Unable to clear PR reservations for disk physicalDiskNam. - 6027-2022
Could not open disk physicalDiskName, errno value. - 6027-2023
retVal = value, errno = value for key value. - 6027-2024
ioctl failed with rc=returnCode, errno=errnoValue. Related values are scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-2025
READ_KEYS ioctl failed with errno=returnCode, tried timesTried times. Related values are scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-2026
READRES ioctl failed with errno=returnCode, tried timesTried times. Related values are: scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-2027
READRES ioctl failed with errno=returnCode, tried timesTried times. Related values are: scsi_status=scsiStatusValue, sense_key=senseKeyValue, scsi_asc=scsiAscValue, scsi_ascq=scsiAscqValue. - 6027-2028
could not open disk device diskDeviceName - 6027-2029
could not close disk device diskDeviceName - 6027-2030
ioctl failed with DSB=value and result=value reason: explanation - 6027-2031
ioctl failed with non-zero return code - 6027-2049 [X]
Cannot pin a page pool of size value bytes. - 6027-2050 [E]
Pagepool has size actualValue bytes instead of the requested requestedValue bytes. - 6027-2100
Incorrect range value-value specified. - 6027-2101
Insufficient free space in fileSystem (storage minimum required). - 6027-2102
Node nodeName is not mmremotefs to run the command. - 6027-2103
Directory dirName does not exist - 6027-2104
The GPFS release level could not be determined on nodes: nodeList. - 6027-2105
The following nodes must be upgraded to GPFS release productVersion or higher: nodeList - 6027-2106
Ensure the nodes are available and run: command. - 6027-2107
Upgrade the lower release level nodes and run: command. - 6027-2108
Error found while processing stanza - 6027-2109
Failed while processing disk stanza on node nodeName. - 6027-2110
Missing required parameter parameter - 6027-2111
The following disks were not deleted: diskList - 6027-2112
Permission failure. Option option requires root authority to run. - 6027-2113
Not able to associate diskName on node nodeName with any known GPFS disk. - 6027-2114
The subsystem subsystem is already active. - 6027-2115
Unable to resolve address range for disk diskName on node nodeName. - 6027-2116 [E]
The GPFS daemon must be active on the recovery group server nodes. - 6027-2117 [E]
object name already exists. - 6027-2118 [E]
The parameter is invalid or missing in the pdisk descriptor. - 6027-2119 [E]
Recovery group name not found. - 6027-2120 [E]
Unable to delete recovery group name on nodes nodeNames. - 6027-2121 [I]
Recovery group name deleted on node nodeName. - 6027-2122 [E]
The number of spares (numberOfSpares) must be less than the number of pdisks (numberOfpdisks) being created. - 6027-2123 [E]
The GPFS daemon is down on the vdiskName servers. - 6027-2124 [E]
Vdisk vdiskName is still NSD nsdName. Use the mmdelnsd command. - 6027-2125 [E]
nsdName is a vdisk-based NSD and cannot be used as a tiebreaker disk. - 6027-2126 [I]
No recovery groups were found. - 6027-2127 [E]
Disk descriptor descriptor refers to an existing pdisk. - 6027-2128 [E]
The attribute attribute must be configured to use hostname as a recovery group server. - 6027-2129 [E]
Vdisk block size (blockSize) must match the file system block size (blockSize). - 6027-2130 [E]
Could not find an active server for recovery group name. - 6027-2131 [E]
Cannot create an NSD on a log vdisk. - 6027-2132 [E]
Log vdisk vdiskName cannot be deleted while there are other vdisks in recovery group name. - 6027-2133 [E]
Unable to delete recovery group name; vdisks are still defined. - 6027-2134
Node nodeName cannot be used as an NSD server for Persistent Reserve disk diskName because it is not a Linux node. - 6027-2135
All nodes in the cluster must be running AIX to enable Persistent Reserve for SAN attached disk diskName. - 6027-2136
All NSD server nodes must be running AIX to enable Persistent Reserve for disk diskName. - 6027-2137
An attempt to clear the Persistent Reserve reservations on disk diskName failed. - 6027-2138
The cluster must be running either all AIX or all Linux nodes to change Persistent Reserve disk diskName to a SAN-attached disk. - 6027-2139
NSD server nodes must be running either all AIX or all Linux to enable Persistent Reserve for disk diskName. - 6027-2140
All NSD server nodes must be running AIX or all running Linux to enable Persistent Reserve for disk diskName. - 6027-2141
Disk diskName is not configured as a regular hdisk. - 6027-2142
Disk diskName is not configured as a regular generic disk. - 6027-2143
Mount point mountPoint can not be part of automount directory automountDir. - 6027-2144 [E]
The lockName lock for file system fileSystem is busy. - 6027-2145 [E]
Internal remote command 'mmremote command' no longer supported. - 6027-2147 [E]
BlockSize must be specified in disk descriptor. - 6027-2148 [E]
nodeName is not a valid recovery group server for recoveryGroupName. - 6027-2149 [E]
Could not get recovery group information from an active server. - 6027-2150
The archive system client backupProgram could not be found or is not executable. - 6027-2151
The path directoryPath is not contained in the snapshot snapshotName. - 6027-2152
The path directoryPath containing image archives was not found. - 6027-2153
The archiving system backupProgram exited with status return code. Image backup files have been preserved in globalWorkDir - 6027-2154
Unable to create a policy file for image backup in policyFilePath. - 6027-2155
File system fileSystem must be mounted read only for restore. - 6027-2156
The image archive index ImagePath could not be found. - 6027-2157
The image archive index ImagePath is corrupt or incomplete. - 6027-2158
Disk usage must be dataOnly, metadataOnly, descOnly, dataAndMetadata, vdiskLog, vdiskLogTip, vdiskLogTipBackup, or vdiskLogReserved. - 6027-2159 [E]
parameter is not valid or missing in the vdisk descriptor. - 6027-2160 [E]
Vdisk vdiskName is already mapped to NSD nsdName. - 6027-2161 [E]
NAS servers cannot be specified when creating an NSD on a vdisk. - 6027-2162 [E]
Cannot set nsdRAIDTracks to zero; nodeName is a recovery group server. - 6027-2163 [E]
Vdisk name not found in the daemon. Recovery may be occurring. The disk will not be deleted. - 6027-2164 [E]
Disk descriptor for name refers to an existing pdisk. - 6027-2165 [E]
Node nodeName cannot be used as a server of both vdisks and non-vdisk NSDs. - 6027-2166 [E]
IBM Spectrum Scale RAID is not configured. - 6027-2167 [E]
Device deviceName does not exist or is not active on this node. - 6027-2168 [E]
The GPFS cluster must be shut down before downloading firmware to port cards. - 6027-2169
Unable to disable Persistent Reserve on the following disks: diskList - 6027-2170 [E]
Recovery group recoveryGroupName does not exist or is not active. - 6027-2171 [E]
objectType objectName already exists in the cluster. - 6027-2172 [E]
Errors encountered while importing IBM Spectrum Scale RAID objects. - 6027-2173 [I]
Use mmchrecoverygroup to assign and activate servers for the following recovery groups (automatically assigns NSD servers as well): recoveryGroupList - 6027-2174
Option option can be specified only in conjunction with option. - 6027-2175 [E]
Exported path exportPath does not exist - 6027-2176 [E]
mmchattr for fileName failed. - 6027-2177 [E]
Cannot create file fileName. - 6027-2178
File fileName does not contain any NSD descriptors or stanzas. - 6027-2181 [E]
Failover is allowed only for single-writer, independent-writer filesets. - 6027-2182 [E]
Resync is allowed only for single-writer filesets. - 6027-2183 [E]
Peer snapshots using mmpsnap are allowed only for single-writer or primary filesets. - 6027-2184 [E]
If the recovery group is damaged, issue mmdelrecoverygroup name -p. - 6027-2185 [E]
There are no pdisk stanzas in the input file fileName. - 6027-2186 [E]
There were no valid vdisk stanzas in the input file fileName. - 6027-2187 [E]
Could not get pdisk information for the following recovery groups: recoveryGroupList - 6027-2188
Unable to determine the local node identity. - 6027-2189 [E]
Action action is allowed only for read-only filesets. - 6027-2190 [E]
Cannot prefetch file fileName. The file does not belong to fileset fileset. - 6027-2191 [E]
Vdisk vdiskName not found in recovery group recoveryGroupName. - 6027-2193 [E]
Recovery group recoveryGroupName must be active on the primary server serverName. - 6027-2194 [E]
The state of fileset filesetName is Expired; prefetch cannot be performed. - 6027-2195 [E]
Error getting snapshot ID for snapshotName. - 6027-2196 [E]
Resync is allowed only when the fileset queue is in active state. - 6027-2197 [E]
Empty file encountered when running the mmafmctl flushPending command. - 6027-2198 [E]
Cannot run the mmafmctl flushPending command on directory dirName. - 6027-2199 [E]
No enclosures were found. - 6027-2200 [E]
Cannot have multiple nodes updating firmware for the same enclosure. Enclosure serialNumber is already being updated by node nodeName. - 6027-2201 [E]
The mmafmctl flushPending command completed with errors. - 6027-2202 [E]
There is a SCSI-3 PR reservation on disk diskname. mmcrnsd cannot format the disk because the cluster is not configured as PR enabled. - 6027-2203
Node nodeName is not a gateway node. - 6027-2204
AFM target map mapName is already defined. - 6027-2205
There are no AFM target map definitions. - 6027-2206
AFM target map mapName is not defined. - 6027-2207
Node nodeName is being used as a gateway node for the AFM cluster clusterName. - 6027-2208 [E]
commandName is already running in the cluster. - 6027-2209 [E]
Unable to list objectName on node nodeName. - 6027-2210 [E]
Unable to build a storage enclosure inventory file on node nodeName. - 6027-2211 [E]
Error collecting firmware information on node nodeName. - 6027-2212 [E]
Firmware update file updateFile was not found. - 6027-2213 [E]
Pdisk path redundancy was lost while updating enclosure firmware. - 6027-2214 [E]
Timeout waiting for firmware to load. - 6027-2215 [E]
Storage enclosure serialNumber not found. - 6027-2216
Quota management is disabled for file system fileSystem. - 6027-2217 [E]
Error errno updating firmware for drives driveList. - 6027-2218 [E]
Storage enclosure serialNumber component componentType component ID componentId not found. - 6027-2219 [E]
Storage enclosure serialNumber component componentType component ID componentId did not fail. Service is not required. - 6027-2220 [E]
Recovery group name has pdisks with missing paths. Consider using the -v no option of the mmchrecoverygroup command. - 6027-2221 [E]
Error determining redundancy of enclosure serialNumber ESM esmName. - 6027-2222 [E]
Storage enclosure serialNumber already has a newer firmware version: firmwareLevel. - 6027-2223 [E]
Storage enclosure serialNumber is not redundant. Shutdown GPFS in the cluster and retry the mmchfirmware command. - 6027-2224 [E]
Peer snapshot creation failed. Error code errorCode. - 6027-2225 [E]
Peer snapshot successfully deleted at cache. The delete snapshot operation failed at home. Error code errorCode. - 6027-2226 [E]
Invalid firmware update file. - 6027-2227 [E]
Failback is allowed only for independent-writer filesets. - 6027-2228 [E]
The daemon version (daemonVersion) on node nodeName is lower than the daemon version (daemonVersion) on node nodeName. - 6027-2229 [E]
Cache Eviction/Prefetch is not allowed for Primary and Secondary mode filesets. - 6027-2230 [E]
afmTarget=newTargetString is not allowed. To change the AFM target, use mmafmctl failover with the --target-only option. For primary filesets, use mmafmctl changeSecondary. - 6027-2231 [E]
The specified block size blockSize is smaller than the system page size pageSize. - 6027-2232 [E]
Peer snapshots are allowed only for targets using the NFS protocol. - 6027-2233 [E]
Fileset filesetName in file system filesystemName does not contain peer snapshot snapshotName. The delete snapshot operation failed at cache. Error code errorCode. - 6027-2234 [E]
Use the mmafmctl converttoprimary command for converting to primary fileset. - 6027-2235 [E]
Only independent filesets can be converted to secondary filesets. - 6027-2236 [E]
The CPU architecture on this node does not support tracing in traceMode mode. Switching to traceMode mode. - 6027-2237 [W]
An image backup made from the live file system may not be usable for image restore. Specify a valid global snapshot for image backup. - 6027-2238 [E]
Use the mmafmctl convertToSecondary command for converting to secondary. - 6027-2239 [E]
Drive serialNumber serialNumber is being managed by server nodeName. Reissue the mmchfirmware command for server nodeName. - 6027-2240 [E]
Option is not supported for a secondary fileset. - 6027-2241 [E]
Node nodeName is not a CES node. - 6027-2242 [E]
Error in configuration file. - 6027-2245 [E]
To change the AFM target, use mmafmctl changeSecondary for the primary. - 6027-2246 [E]
Timeout executing function: functionName (return code=returnCode). - 6027-2247 [E]
Creation of exchangeDir failed. - 6027-2248 [E]
CCR command failed: command - 6027-2249 [E]
Error getting next nextName from CCR. - 6027-2250 [E]
Error putting next nextName to CCR, new ID: newExpid version: version - 6027-2251 [E]
Error retrieving configuration file: configFile - 6027-2252 [E]
Error reading export configuration file (return code: returnCode). - 6027-2253 [E]
Error creating the internal export data objects (return code returnCode). - 6027-2254 [E]
Error creating single export output, export exportPath not found (return code returnCode). - 6027-2255 [E]
Error creating export output (return code: returnCode). - 6027-2256 [E]
Error creating the internal export output file string array (return code: returnCode). - 6027-2257 [E]
Error deleting export, export exportPath not found (return code: returnCode). - 6027-2258 [E]
Error writing export configuration file to CCR (return code: returnCode). - 6027-2259 [E]
The path exportPath to create the export does not exist (return code:returnCode). - 6027-2260 [E]
The path exportPath to create the export is invalid (return code: returnCode). - 6027-2261 [E]
Error creating new export object, invalid data entered (return code: returnCode). - 6027-2262 [E]
Error creating new export object; getting new export ID (return code: returnCode). - 6027-2263 [E]
Error adding export; new export path exportPath already exists. - 6027-2264 [E]
The --servers option is only used to provide names for primary and backup server configurations. Provide a maximum of two server names. - 6027-2265 [E]
Cannot convert fileset to secondary fileset. - 6027-2266 [E]
The snapshot names that start with psnap-rpo or psnap0-rpo are reserved for RPO. - 6027-2267 [I]
Fileset filesetName in file system fileSystem is either unlinked or being deleted. Home delete-snapshot operation was not queued. - 6027-2268 [E]
This is already a secondary fileset. - 6027-2269 [E]
Adapter adapterIdentifier was not found. - 6027-2270 [E]
Error errno updating firmware for adapter adapterIdentifier. - 6027-2271 [E]
Error locating the reference client in inputStringContainingClient (return code: returnCode). - 6027-2272 [E]
Error removing the requested client in inputStringContainingClient from a client declaration, return code: returnCode - 6027-2273 [E]
Error adding the requested client in inputStringContainingClient to a client declaration, return code: returnCode - 6027-2274 [E]
Error locating the reference client in inputStringContainingClient (return code: returnCode). - 6027-2275 [E]
Unable to determine the status of DASD device dasdDevice - 6027-2276 [E]
The specified DASD device dasdDevice is not properly formatted. It is not an ECKD-type device, or it has a format other then CDL or LDL, or it has a block size other then 4096. - 6027-2277 [E]
Unable to determine if DASD device dasdDevice is partitioned. - 6027-2278 [E]
Cannot partition DASD device dasdDevice; it is already partitioned. - 6027-2279 [E]
Unable to partition DASD device dasdDevice - 6027-2280 [E]
The DASD device with bus ID busID cannot be found or it is in use. - 6027-2281 [E]
Error errno updating firmware for enclosure enclosureIdentifier. - 6027-2282 [E]
Action action is not allowed for secondary filesets. - 6027-2283 [E]
Node nodeName is already a CES node. - 6027-2284 [E]
The fileset afmshowhomesnapshot value is 'yes'. The fileset mode cannot be changed. - 6027-2285 [E]
Deletion of initial snapshot snapshotName of fileset filesetName in file system fileSystem failed. The delete fileset operation failed at cache. Error code errorCode. - 6027-2286 [E]
RPO peer snapshots using mmpsnap are allowed only for primary filesets. - 6027-2287
The fileset needs to be linked to change afmShowHomeSnapshot to 'no'. - 6027-2288 [E]
Option optionName is not supported for AFM filesets. - 6027-2289 [E]
Peer snapshot creation failed while running subCommand. Error code errorCode - 6027-2290 [E]
The comment string should be less than 50 characters long. - 6027-2291 [E]
Peer snapshot creation failed while generating snapshot name. Error code errorCode - 6027-2292 [E]
The initial snapshot psnap0Name does not exist. The peer snapshot creation failed. Error code errorCode - 6027-2293 [E]
The peer snapshot creation failed because fileset filesetName is in filesetState state. - 6027-2294 [E]
Removing older peer snapshots failed while obtaining snap IDs. Error code errorCode - 6027-2295 [E]
Removing older peer snapshots failed while obtaining old snap IDs. Error code errorCode - 6027-2296 [E]
Need a target to convert to the primary fileset. - 6027-2297 [E]
The check-metadata and nocheck-metadata options are not supported for a non-AFM fileset. - 6027-2298 [E]
Only independent filesets can be converted to primary or secondary. - 6027-2299 [E]
Issue the mmafmctl getstate command to check fileset state and if required issue mmafmctl convertToPrimary. - 6027-2300 [E]
The check-metadata and nocheck-metadata options are not supported for the primary fileset. - 6027-2301 [E]
The inband option is not supported for the primary fileset. - 6027-2302 [E]
AFM target cannot be changed for the primary fileset. - 6027-2303 [E]
The inband option is not supported for an AFM fileset. - 6027-2304 [E]
Target cannot be changed for an AFM fileset. - 6027-2305 [E]
The mmafmctl convertToPrimary command is not allowed for this primary fileset. - 6027-2306 [E]
Failed to check for cached files while doing primary conversion from filesetMode mode. - 6027-2307 [E]
Uncached files present, run prefetch first. - 6027-2308 [E]
Uncached files present, run prefetch first using policy output: nodeDirFileOut. - 6027-2309 [E]
Conversion to primary not allowed for filesetMode mode. - 6027-2310 [E]
This option is available only for a primary fileset. - 6027-2311 [E]
The target-only option is not allowed for a promoted primary without a target. - 6027-2312 [E]
Need a target to setup the new secondary. - 6027-2313 [E]
The target-only and inband options are not allowed together. - 6027-2314 [E]
Could not run commandName. Verify that the Object protocol was installed. - 6027-2315 [E]
Could not determine CCR file for service serviceName - 6027-2316 [E]
Unable to retrieve file fileName from CCR using command command. Verify that the Object protocol is correctly installed. - 6027-2317 [E]
Unable to parse version number of file fileName from mmccr output - 6027-2318 [E]
Could not put localFilePath into the CCR as ccrName - 6027-2319 [I]
Version mismatch during upload of fileName (version). Retrying. - 6027-2320
directoryName does not resolve to a directory in deviceName. The directory must be within the specified file system. - 6027-2321 [E]
AFM primary or secondary filesets cannot be created for file system fileSystem because version is less than supportedVersion. - 6027-2322 [E]
The OBJ service cannot be enabled because it is not installed. The file fileName was not found. - 6027-2323 [E]
The OBJ service cannot be enabled because the number of CES IPs below the minimum of minValue expected. - 6027-2324 [E]
The object store for serviceName is either not a GPFS type or mountPoint does not exist. - 6027-2325 [E]
File fileName does not exist in CCR. Verify that the Object protocol is correctly installed. - 6027-2326 [E]
The OBJ service cannot be enabled because attribute attributeName for a CES IP has not been defined. Verify that the Object protocol is correctly installed. - 6027-2327
The snapshot snapshotName is the wrong scope for use in targetType backup - 6027-2329 [E]
The fileset attributes cannot be set for the primary fileset with caching disabled. - 6027-2330 [E]
The outband option is not supported for AFM filesets. - 6027-2331 [E]
CCR value ccrValue not defined. The OBJ service cannot be enabled if identity authentication is not configured. - 6027-2332 [E]
Only regular independent filesets are converted to secondary filesets. - 6027-2333 [E]
Failed to disable serviceName service. Ensure authType authentication is removed. - 6027-2334 [E]
Fileset indFileset cannot be changed because it has a dependent fileset depFileset - 6027-2335 [E]
Failed to convert fileset, because the policy to detect special files is failing. - 6027-2336 [E]
Immutable/append-only files or clones copied from a snapshot are present, hence conversion is disallowed - 6027-2337 [E]
Conversion to primary is not allowed at this time. Retry the command later. - 6027-2338 [E]
Conversion to primary is not allowed because the state of the fileset is filesetState. - 6027-2339 [E]
Orphans are present, run prefetch first. - 6027-2340 [E]
Fileset was left in PrimInitFail state. Take the necessary actions. - 6027-2341 [E]
This operation can be done only on a primary fileset - 6027-2342 [E]
Failover/resync is currently running so conversion is not allowed - 6027-2343 [E]
DR Setup cannot be done on a fileset with mode filesetMode. - 6027-2344 [E]
The GPFS daemon must be active on the node from which the mmcmd is executed with option --inode-criteria or -o. - 6027-2345 [E]
The provided snapshot name must be unique to list filesets in a specific snapshot - 6027-2346 [E]
The local node is not a CES node. - 6027-2347 [E]
Error changing export, export exportPath not found. - 6027-2348 [E]
A device for directoryName does not exist or is not active on this node. - 6027-2349 [E]
The fileset for junctionName does not exist in the targetType specified. - 6027-2350 [E]
The fileset for junctionName is not linked in the targetType specified. - 6027-2351 [E]
One or more unlinked filesets (filesetNames) exist in the targetType specified. Check your filesets and try again. - 6027-2352
The snapshot snapshotName could not be found for use by commandName - 6027-2353 [E]
The snapshot name cannot be generated. - 6027-2354
Node nodeName must be disabled as a CES node before trying to remove it from the GPFS cluster. - 6027-2355 [E]
Unable to reload moduleName. Node hostname should be rebooted. - 6027-2356 [E]
Node nodeName is being used as a recovery group server. - 6027-2357 [E]
Root fileset cannot be converted to primary fileset. - 6027-2358 [E]
Root fileset cannot be converted to secondary fileset. - 6027-2359 [I]
Attention: command is now enabled. This attribute can no longer be modified. - 6027-2360 [E]
The current value of command is attrName. This value cannot be changed. - 6027-2361 [E]
command is enabled. File systems cannot be deleted. - 6027-2362 [E]
The current value of command is attrName. No changes made. - 6027-2363 [E]
Operation is not permitted as state of the fileset is filesetState. - 6027-2364 [E]
Fileset name is missing. - 6027-2365 [E]
Firmware loader filename not executable. - 6027-2366
Node nodeName is being used as an NSD server. This may include Local Read Only Cache (LROC) storage. Review these details and determine the NSD type by running the mmlsnsd command. For standard NSDs, you must either delete the disk or define another node as its server. For nodes that include LROC NSDs (local cache) must have all the LROC NSDs removed before the node can be deleted. Fully review the mmdelnsd command documentation before making any changes. - 6027-2367 [E]
Fileset having iammode mode cannot be converted to primary fileset. - 6027-2368 [E]
Unable to find information for Hypervisor. - 6027-2369 [E]
Unable to list DASD devices - 6027-2370 [E]
Unable to flush buffer for DASD device name1 - 6027-2371 [E]
Unable to read the partition table for DASD device dasdDevice. - 6027-2372 [E]
Unable to find information to DASD device dasdDevice. - 6027-2373
feature is only available in the IBM Spectrum Scale Advanced Edition. - 6027-2374 [E]
Unable to delete recovery group name; as the associated VDisk sets are still defined. - 6027-2376 [E]
Node class nodeclass cannot be action. It is marked for use by Transparent Cloud Tiering. To remove this node class, first disable all the nodes with mmchnode --cloud-gateway-disable. - 6027-2377 [E]
Node nodeclass cannot be deleted. It is marked for use by Transparent Cloud Tiering. To remove this node, first disable it with mmchnode --cloud-gateway-disable. - 6027-2378 [E]
To enable Transparent Cloud Tiering nodes, you must first enable the Transparent\n\ Cloud Tiering feature. This feature provides a new level of storage tiering capability to the IBM Spectrum Scale customer. Please contact your IBM Client Technical Specialist (or send an email to scale@us.ibm.com) to review your use case of the Transparent Cloud Tiering feature and to obtain the instructions to enable the feature in your environment. - 6027-2379 [E]
The FBA-type DASD device dasdDevice is not a partition. - 6027-2380 [E]
Support for FBA-type DASD device is not enabled. Run mmchconfig release=LATEST to activate the new function. - 6027-2381 [E]
Missing argument missingArg - 6027-2382 [E]
Conversion is not allowed for filesets with active clone files. - 6027-2383 [E]
Conversion to secondary fileset has failed. - 6027-2384 [E]
No object storage policy found. - 6027-2385 [E]
Failed to create soft link between directories: directoryName1, directoryName2. - 6027-2386 [E]
Provided fileset path filesetPath is already enabled for objectization. - 6027-2387 [E]
Provided container containerName is already enabled for objectization. - 6027-2388 [E]
Given fileset: filesetName is not part of object file system: fileSystemName. - 6027-2389 [E]
Fileset path is already used by object protocol. It cannot be selected for objectization. - 6027-2390 [E]
SELinux needs to be in either disabled or permissive mode. - 6027-2391 [E]
The configuration of SED based encryption for the drive 'name1' is failed. - 6027-2392 [E]
Found pdisk serialNumber in recovery group recoverygroupName has pdiskName paths. - 6027-2393 [E]
Use the -N parameter to specify the nodes that have access to the hardware to be updated. - 6027-2500
mmsanrepairfs already in progress for "name" - 6027-2501
Could not allocate storage. - 6027-2503
"name" is not SANergy enabled. - 6027-2504
Waiting number seconds for SANergy data structure cleanup. - 6027-2576 [E]
Error: Daemon value kernel value PAGE_SIZE mismatch. - 6027-2600
Cannot create a new snapshot until an existing one is deleted. File system fileSystem has a limit of number online snapshots. - 6027-2601
Snapshot name dirName already exists. - 6027-2602
Unable to delete snapshot snapshotName from file system fileSystem. rc=returnCode. - 6027-2603
Unable to get permission to create snapshot, rc=returnCode. - 6027-2604
Unable to quiesce all nodes, rc=returnCode. - 6027-2605
Unable to resume all nodes, rc=returnCode. - 6027-2606
Unable to sync all nodes, rc=returnCode. - 6027-2607
Cannot create new snapshot until an existing one is deleted. Fileset filesetName has a limit of number snapshots. - 6027-2608
Cannot create new snapshot: state of fileset filesetName is inconsistent (badState). - 6027-2609
Fileset named filesetName does not exist. - 6027-2610
File system fileSystem does not contain snapshot snapshotName err = number. - 6027-2611
Cannot delete snapshot snapshotName which is in state snapshotState. - 6027-2612
Snapshot named snapshotName does not exist. - 6027-2613
Cannot restore snapshot. fileSystem is mounted on number node(s) and in use on number node(s). - 6027-2614
File system fileSystem does not contain snapshot snapshotName err = number. - 6027-2615
Cannot restore snapshot snapshotName which is snapshotState, err = number. - 6027-2616
Restoring snapshot snapshotName requires quotaTypes quotas to be enabled. - 6027-2617
You must run: mmchfs fileSystem -Q yes. - 6027-2618 [N]
Restoring snapshot snapshotName in file system fileSystem requires quotaTypes quotas to be enabled. - 6027-2619
Restoring snapshot snapshotName requires quotaTypes quotas to be disabled. - 6027-2620
You must run: mmchfs fileSystem -Q no. - 6027-2621 [N]
Restoring snapshot snapshotName in file system fileSystem requires quotaTypes quotas to be disabled. - 6027-2623 [E]
Error deleting snapshot snapshotName in file system fileSystem err number - 6027-2624
Previous snapshot snapshotName is not valid and must be deleted before a new snapshot may be created. - 6027-2625
Previous snapshot snapshotName must be restored before a new snapshot may be created. - 6027-2626
Previous snapshot snapshotName is not valid and must be deleted before another snapshot may be deleted. - 6027-2627
Previous snapshot snapshotName is not valid and must be deleted before another snapshot may be restored. - 6027-2628
More than one snapshot is marked for restore. - 6027-2629
Offline snapshot being restored. - 6027-2630
Program failed, error number. - 6027-2631
Attention: Snapshot snapshotName was being restored to fileSystem. - 6027-2633
Attention: Disk configuration for fileSystem has changed while tsdf was running. - 6027-2634
Attention: number of number regions in fileSystem were unavailable for free space. - 6027-2635
The free space data is not available. Reissue the command without the -q option to collect it. - 6027-2636
Disks in storage pool storagePool must have disk usage type dataOnly. - 6027-2637
The file system must contain at least one disk for metadata. - 6027-2638
Maximum of number storage pools allowed. - 6027-2639
Incorrect fileset name filesetName. - 6027-2640
Incorrect path to fileset junction filesetJunction. - 6027-2641
Incorrect fileset junction name filesetJunction. - 6027-2642
Specify one and only one of FilesetName or -J JunctionPath. - 6027-2643
Cannot create a new fileset until an existing one is deleted. File system fileSystem has a limit of maxNumber filesets. - 6027-2644
Comment exceeds maximum length of maxNumber characters. - 6027-2645
Fileset filesetName already exists. - 6027-2646
Unable to sync all nodes while quiesced, rc=returnCode - 6027-2647
Fileset filesetName must be unlinked to be deleted. - 6027-2648
Filesets have not been enabled for file system fileSystem. - 6027-2649
Fileset filesetName contains user files and cannot be deleted unless the -f option is specified. - 6027-2650
Fileset information is not available. - 6027-2651
Fileset filesetName cannot be unlinked. - 6027-2652
Fileset at junctionPath cannot be unlinked. - 6027-2653
Failed to unlink fileset filesetName from filesetName. - 6027-2654
Fileset filesetName cannot be deleted while other filesets are linked to it. - 6027-2655
Fileset filesetName cannot be deleted. - 6027-2656
Unable to quiesce fileset at all nodes. - 6027-2657
Fileset filesetName has open files. Specify -f to force unlink. - 6027-2658
Fileset filesetName cannot be linked into a snapshot at pathName. - 6027-2659
Fileset filesetName is already linked. - 6027-2660
Fileset filesetName cannot be linked. - 6027-2661
Fileset junction pathName already exists. - 6027-2662
Directory pathName for junction has too many links. - 6027-2663
Fileset filesetName cannot be changed. - 6027-2664
Fileset at pathName cannot be changed. - 6027-2665
mmfileid already in progress for name. - 6027-2666
mmfileid can only handle a maximum of diskAddresses disk addresses. - 6027-2667 [I]
Allowing block allocation for file system fileSystem that makes a file ill-replicated due to insufficient resource and puts data at risk. - 6027-2670
Fileset name filesetName not found. - 6027-2671
Fileset command on fileSystem failed; snapshot snapshotName must be restored first. - 6027-2672
Junction parent directory inode number inodeNumber is not valid. - 6027-2673 [X]
Duplicate owners of an allocation region (index indexNumber, region regionNumber, pool poolNumber) were detected for file system fileSystem: nodes nodeName and nodeName. - 6027-2674 [X]
The owner of an allocation region (index indexNumber, region regionNumber, pool poolNumber) that was detected for file system fileSystem: node nodeName is not valid. - 6027-2675
Only file systems with NFSv4 ACL semantics enabled can be mounted on this platform. - 6027-2676
Only file systems with NFSv4 locking semantics enabled can be mounted on this platform. - 6027-2677
Fileset filesetName has pending changes that need to be synced. - 6027-2678
File system fileSystem is mounted on nodes nodes or fileset filesetName is not unlinked. - 6027-2679
Mount of fileSystem failed because mount event not handled by any data management application. - 6027-2680
AFM filesets cannot be created for file system fileSystem. - 6027-2681
Snapshot snapshotName has linked independent filesets - 6027-2682 [E]
Set quota file attribute error (reasonCode)explanation - 6027-2683
Fileset filesetName in file system fileSystem does not contain snapshot snapshotName, err = number - 6027-2684
File system fileSystem does not contain global snapshot snapshotName, err = number - 6027-2685
Total file system capacity allows minMaxInodes inodes in fileSystem. Currently the total inode limits used by all the inode spaces in inodeSpace is inodeSpaceLimit. There must be at least number inodes available to create a new inode space. Use the mmlsfileset -L command to show the maximum inode limits of each fileset. Try reducing the maximum inode limits for some of the inode spaces in fileSystem. - 6027-2688
Only independent filesets can be configured as AFM filesets. The --inode-space=new option is required. - 6027-2689
The value for --block-size must be the keyword auto or the value must be of the form [n]K, [n]M, [n]G or [n]T, where n is an optional integer in the range 1 to 1023. - 6027-2690
Fileset filesetName can only be linked within its own inode space. - 6027-2691
The fastea feature needs to be enabled for file system fileSystem before creating AFM filesets. - 6027-2692
Error encountered while processing the input file. - 6027-2693
Fileset junction name junctionName conflicts with the current setting of mmsnapdir. - 6027-2694 [I]
The requested maximum number of inodes is already at number. - 6027-2695 [E]
The number of inodes to preallocate cannot be higher than the maximum number of inodes. - 6027-2696 [E]
The number of inodes to preallocate cannot be lower than the number inodes already allocated. - 6027-2697
Fileset at junctionPath has pending changes that need to be synced. - 6027-2698
File system fileSystem is mounted on nodes nodes or fileset at junctionPath is not unlinked. - 6027-2699
Cannot create a new independent fileset until an existing one is deleted. File system fileSystem has a limit of maxNumber independent filesets. - 6027-2700 [E]
A node join was rejected. This could be due to incompatible daemon versions, failure to find the node in the configuration database, or no configuration manager found. - 6027-2701
The mmpmon command file is empty. - 6027-2702
Unexpected mmpmon response from file system daemon. - 6027-2703
Unknown mmpmon command command. - 6027-2704
Permission failure. The command requires root authority to execute. - 6027-2705
Could not establish connection to file system daemon. - 6027-2706 [I]
Recovered number nodes. - 6027-2707 [I]
Node join protocol waiting value seconds for node recovery - 6027-2708 [E]
Rejected node join protocol. Phase two of node failure recovery appears to still be in progress. - 6027-2709
Configuration manager node nodeName not found in the node list. - 6027-2710 [E]
Node nodeName is being expelled due to expired lease. - 6027-2711 [E]
File system table full. - 6027-2712
Option 'optionName' has been deprecated. - 6027-2713
Permission failure. The command requires SuperuserName authority to execute. - 6027-2714
Could not appoint node nodeName as cluster manager. errorString - 6027-2715
Could not appoint a new cluster manager. errorString - 6027-2716 [I]
Challenge response received; canceling disk election. - 6027-2717
Node nodeName is already a cluster manager or another node is taking over as the cluster manager. - 6027-2718
Incorrect port range: GPFSCMDPORTRANGE='range'. Using default. - 6027-2719
The files provided do not contain valid quota entries. - 6027-2722 [E]
Node limit of number has been reached. Ignoring nodeName. - 6027-2723 [N]
This node (nodeName) is now Cluster Manager for clusterName. - 6027-2724 [I]
reasonString. Probing cluster clusterName - 6027-2725 [N]
Node nodeName lease renewal is overdue. Pinging to check if it is alive - 6027-2726 [I]
Recovered number nodes for file system fileSystem. - 6027-2727
fileSystem: quota manager is not available. - 6027-2728 [N]
Connection from node rejected because it does not support IPv6 - 6027-2729
Value value for option optionName is out of range. Valid values are value through value. - 6027-2730 [E]
Node nodeName failed to take over as cluster manager. - 6027-2731
Failed to locate a working cluster manager. - 6027-2732
Attention: No data disks remain in the system pool. Use mmapplypolicy to migrate all data left in the system pool to other storage pool. - 6027-2733
The file system name (fsname) is longer than the maximum allowable length (maxLength). - 6027-2734 [E]
Disk failure from node nodeName Volume name. Physical volume name. - 6027-2735 [E]
Not a manager - 6027-2736
The value for --block-size must be the keyword auto or the value must be of the form nK, nM, nG or nT, where n is an optional integer in the range 1 to 1023. - 6027-2737
Editing quota limits for root fileset is not permitted. - 6027-2738
Editing quota limits for the root user is not permitted - 6027-2739
Editing quota limits for groupName group not permitted. - 6027-2740 [I]
Starting new election as previous clmgr is expelled - 6027-2741 [W]
This node can not continue to be cluster manager - 6027-2742 [I]
CallExitScript: exit script exitScript on event eventName returned code returnCode, quorumloss. - 6027-2743
Permission denied. - 6027-2744 [D]
Invoking tiebreaker callback script - 6027-2745 [E]
File system is not mounted. - 6027-2746 [E]
Too many disks unavailable for this server to continue serving a RecoveryGroup. - 6027-2747 [E]
Inconsistency detected between the local node number retrieved from 'mmsdrfs' (nodeNumber) and the node number retrieved from 'mmfs.cfg' (nodeNumber). - 6027-2748
Terminating because a conflicting program on the same inode space inodeSpace is running. - 6027-2749
Specified locality group 'number' does not match disk 'name' locality group 'number'. To change locality groups in an SNC environment, please use the mmdeldisk and mmadddisk commands. - 6027-2750 [I]
Node NodeName is now the Group Leader. - 6027-2751 [I]
Starting new election: Last elected: NodeNumber Sequence: SequenceNumber - 6027-2752 [I]
This node got elected. Sequence: SequenceNumber - 6027-2753 [N]
Responding to disk challenge: response: ResponseValue. Error code: ErrorCode. - 6027-2754 [X]
Challenge thread did not respond to challenge in time: took TimeIntervalSecs seconds. - 6027-2755 [N]
Another node committed disk election with sequence CommittedSequenceNumber (our sequence was OurSequenceNumber). - 6027-2756
Attention: In file system FileSystemName, FileSetName (Default) QuotaLimitType(QuotaLimit) for QuotaTypeUserName/GroupName/FilesetName is too small. Suggest setting it higher than minQuotaLimit. - 6027-2757 [E]
The peer snapshot is in progress. Queue cannot be flushed now. - 6027-2758 [E]
The AFM target does not support this operation. Run mmafmconfig on the AFM target cluster. - 6027-2759 [N]
Disk lease period expired in cluster ClusterName. Attempting to reacquire lease. - 6027-2760 [N]
Disk lease reacquired in cluster ClusterName. - 6027-2761
Unable to run command on 'fileSystem' while the file system is mounted in restricted mode. - 6027-2762
Unable to run command on 'fileSystem' while the file system is suspended. - 6027-2763
Unable to start command on 'fileSystem' because conflicting program name is running. Waiting until it completes. - 6027-2764
Terminating command on fileSystem because a conflicting program name is running. - 6027-2765
command on 'fileSystem' is finished waiting. Processing continues ... name - 6027-2766 [I]
User script has chosen to expel node nodeName instead of node nodeName. - 6027-2767 [E]
Error errorNumber while accessing tiebreaker devices. - 6027-2770
Disk diskName belongs to a write-affinity enabled storage pool. Its failure group cannot be changed. - 6027-2771
fileSystem: Default per-fileset quotas are disabled for quotaType. - 6027-2772
Cannot close disk name. - 6027-2773
fileSystem:filesetName: default quota for quotaType is disabled. - 6027-2774
fileSystem: Per-fileset quotas are not enabled. - 6027-2775
Storage pool named poolName does not exist. - 6027-2776
Attention: A disk being stopped reduces the degree of system metadata replication (value) or data replication (value) to lower than tolerable. - 6027-2777 [E]
Node nodeName is being expelled because of an expired lease. Pings sent: pingsSent. Replies received: pingRepliesReceived. - 6027-2778 [I]
Node nodeName: ping timed out. Pings sent: pingsSent. Replies received: pingRepliesReceived. - 6027-2779 [E]
Challenge thread stopped. - 6027-2780 [E]
Not enough quorum nodes reachable: reachableNodes. - 6027-2781 [E]
Lease expired for numSecs seconds (shutdownOnLeaseExpiry). - 6027-2782 [E]
This node is being expelled from the cluster. - 6027-2783 [E]
New leader elected with a higher ballot number. - 6027-2784 [E]
No longer a cluster manager or lost quorum while running a group protocol. - 6027-2785 [X]
A severe error was encountered during cluster probe. - 6027-2786 [E]
Unable to contact any quorum nodes during cluster probe. - 6027-2787 [E]
Unable to contact enough other quorum nodes during cluster probe. - 6027-2788 [E]
Attempt to run leader election failed with error errorNumber. - 6027-2789 [E]
Tiebreaker script returned a non-zero value. - 6027-2790
Attention: Disk parameters were changed. Use the mmrestripefs command with the -r option to relocate data and metadata. - 6027-2791
Disk diskName does not belong to file system deviceName. - 6027-2792
The current file system version does not support default per-fileset quotas. - 6027-2793 [E]
Contents of local fileName file are invalid. Node may be unable to be elected group leader. - 6027-2794 [E]
Invalid content of disk paxos sector for disk diskName. - 6027-2795
An error occurred while executing command for fileSystem. - 6027-2796 [W]
Callback event eventName is not supported on this node; processing continues ... - 6027-2797 [I]
Node nodeName: lease request received late. Pings sent: pingsSent. Maximum pings missed: maxPingsMissed. - 6027-2798 [E]
The node nodeName does not have a valid Extended License to run the requested command. - 6027-2799
Option 'option' is incompatible with option 'option'. - 6027-2800
Available memory exceeded on request to allocate number bytes. Trace point sourceFile-tracePoint. - 6027-2801
Policy set syntax version versionString not supported. - 6027-2802
Object name 'poolName_or_filesetName' is not valid. - 6027-2803
Policy set must start with VERSION. - 6027-2804
Unexpected SQL result code - sqlResultCode. - 6027-2805 [I]
Loaded policy 'policyFileName or filesystemName': summaryOfPolicyRules - 6027-2806 [E]
Error while validating policy 'policyFileName or filesystemName': rc=errorCode: errorDetailsString - 6027-2807 [W]
Error in evaluation of placement policy for file fileName: errorDetailsString - 6027-2808
In rule 'ruleName' (ruleNumber), 'wouldBePoolName' is not a valid pool name. - 6027-2809
Validated policy 'policyFileName or filesystemName': summaryOfPolicyRules - 6027-2810 [W]
There are numberOfPools storage pools but the policy file is missing or empty. - 6027-2811
Policy has no storage pool placement rules! - 6027-2812
Keyword 'keywordValue' begins a second clauseName clause - only one is allowed. - 6027-2813
This 'ruleName' rule is missing a clauseType required clause. - 6027-2814
This 'ruleName' rule is of unknown type or not supported. - 6027-2815
The value 'value' is not supported in a 'clauseType' clause. - 6027-2816
Policy rules employ features that would require a file system upgrade. - 6027-2817
Error on popen/pclose (command_string): rc=return_code_from_popen_or_pclose - 6027-2818
A problem occurred during m4 processing of policy rules. rc = return_code_from_popen_pclose_or_m4 - 6027-2819
Error opening temp file temp_file_name: errorString - 6027-2820
Error reading temp file temp_file_name: errorString - 6027-2821
Rule 'ruleName' (ruleNumber) specifies a THRESHOLD for EXTERNAL POOL 'externalPoolName'. This is not supported. - 6027-2822
This file system does not support fast extended attributes, which are needed for encryption. - 6027-2823 [E]
Encryption activated in the file system, but node not enabled for encryption. - 6027-2824
This file system version does not support encryption rules. - 6027-2825
Duplicate encryption set name 'setName'. - 6027-2826
The encryption set 'setName' requested by rule 'rule' could not be found. - 6027-2827 [E]
Error in evaluation of encryption policy for file fileName: %s - 6027-2828 [E]
Encryption not supported on Windows. Encrypted file systems are not allowed when Windows nodes are present in the cluster. - 6027-2950 [E]
Trace value 'value' after class 'class' must be from 0 to 14. - 6027-2951 [W]
Value value for worker1Threads must be <= than the original setting value - 6027-2952 [E]
Unknown assert class 'assertClass'. - 6027-2953 [E]
Non-numeric assert value 'value' after class 'class'. - 6027-2954 [E]
Assert value 'value' after class 'class' must be from 0 to 127. - 6027-2955 [W]
Time-of-day may have jumped back. Late by delaySeconds seconds to wake certain threads. - 6027-2956 [E]
Invalid crypto engine type (encryptionCryptoEngineType): cryptoEngineType. - 6027-2957 [E]
Invalid cluster manager selection choice (clusterManagerSelection): clusterManagerSelection. - 6027-2958 [E]
Invalid NIST compliance type (nistCompliance): nistComplianceValue. - 6027-2959 [E]
The CPU architecture on this node does not support tracing in traceMode mode. Switching to traceMode mode. - 6027-2960 [W]
Unable to establish a session with Active Directory server for the domain 'domainServer'. ID mapping through Microsoft Identity Management for Unix will be unavailable. - 6027-2961 [I]
Established a session with Active Directory server for the domain 'domainServer'. - 6027-3101
Pdisk rotation rate invalid in option 'option'. - 6027-3102
Pdisk FRU number too long in option 'option', maximum length length. - 6027-3103
Pdisk location too long in option 'option', maximum length length. - 6027-3104
Pdisk failure domains too long in option 'name1name2', maximum length name3. - 6027-3105
Pdisk nPathActive invalid in option 'option'. - 6027-3106
Pdisk nPathTotal invalid in option 'option'. - 6027-3107
Pdisk nsdFormatVersion invalid in option 'name1name2'. - 6027-3108
Declustered array name name1 appears more than once in the declustered array stanzas. - 6027-3200
AFM ERROR: command pCacheCmd fileset filesetName fileids [parentId.childId.tParentId.targetId,ReqCmd] original error oerr application error aerr remote error remoteError - 6027-3201
AFM ERROR DETAILS: type: remoteCmdType snapshot name snapshotName snapshot ID snapshotId - 6027-3204
AFM: Failed to set xattr on inode inodeNum error err, ignoring. - 6027-3205
AFM: Failed to get xattrs for inode inodeNum, ignoring. - 6027-3209
Home NFS mount of host:path failed with error err - 6027-3210
Cannot find AFM control file for fileset filesetName in the exported file system at home. ACLs and extended attributes will not be synchronized. Sparse files will have zeros written for holes. - 6027-3211
Change in home export detected. Caching will be disabled. - 6027-3212
AFM ERROR: Cannot enable AFM for fileset filesetName (error err) - 6027-3213
Cannot find snapshot link directory name for exported file system at home for fileset filesetName. Snapshot directory at home will be cached. - 6027-3214 [E]
AFM: Unexpiration of fileset filesetName failed with error err. Use mmafmctl to manually unexpire the fileset. - 6027-3215 [W]
AFM: Peer snapshot delayed due to long running execution of operation to remote cluster for fileset filesetName. Peer snapshot continuing to wait. - 6027-3216
Fileset filesetName encountered an error synchronizing with the remote cluster. Cannot synchronize with the remote cluster until AFM recovery is executed. - 6027-3217
AFM ERROR Unable to unmount NFS export for fileset filesetName - 6027-3220
AFM: Home NFS mount of host:path failed with error err for file system fileSystem fileset id filesetName. Caching will be disabled and the mount will be tried again after mountRetryTime seconds, on next request to gateway - 6027-3221
AFM: Home NFS mount of host:path succeeded for file system fileSystem fileset filesetName. Caching is enabled. - 6027-3224 [I]
AFM: Failed to set extended attributes on file system fileSystem inode inodeNum error err, ignoring. - 6027-3225 [I]
AFM: Failed to get extended attributes for file system fileSystem inode inodeNum, ignoring. - 6027-3226 [I]
AFM: Cannot find control file for file system fileSystem fileset filesetName in the exported file system at home. ACLs and extended attributes will not be synchronized. Sparse files will have zeros written for holes. - 6027-3227 [E]
AFM: Cannot enable AFM for file system fileSystem fileset filesetName (error err) - 6027-3228 [E]
AFM: Unable to unmount NFS export for file system fileSystem fileset filesetName - 6027-3229 [E]
AFM: File system fileSystem fileset filesetName encountered an error synchronizing with the remote cluster. Cannot synchronize with the remote cluster until AFM recovery is executed. - 6027-3230 [I]
AFM: Cannot find snapshot link directory name for exported file system at home for file system fileSystem fileset filesetName. Snapshot directory at home will be cached. - 6027-3232
type AFM: pCacheCmd file system fileSystem fileset filesetName file IDs [parentId.childId.tParentId.targetId,flag] name sourceName origin error err - 6027-3233 [I]
AFM: Previous error repeated repeatNum times. - 6027-3234 [E]
AFM: Unable to start thread to unexpire filesets. - 6027-3235 [I]
AFM: Stopping recovery for the file system fileSystem fileset filesetName - 6027-3236 [E]
AFM: Recovery on file system fileSystem fileset filesetName failed with error err. Recovery will be retried on next access after recovery retry interval (timeout seconds) or manually resolve known problems and recover the fileset. - 6027-3239 [E]
AFM: Remote command remoteCmdType on file system fileSystem snapshot snapshotName snapshot ID snapshotId failed. - 6027-3240 [E]
AFM: pCacheCmd file system fileSystem fileset filesetName file IDs [parentId.childId.tParentId.targetId,flag] error err - 6027-3241 [I]
AFM: GW queue transfer started for file system fileSystem fileset filesetName. Transferring to nodeAddress. - 6027-3242 [I]
AFM: GW queue transfer started for file system fileSystem fileset filesetName. Receiving from nodeAddress. - 6027-3243 [I]
AFM: GW queue transfer completed for file system fileSystem fileset filesetName. error error - 6027-3244 [I]
AFM: Home mount of afmTarget succeeded for file system fileSystem fileset filesetName. Caching is enabled. - 6027-3245 [E]
AFM: Home mount of afmTarget failed with error error for file system fileSystem fileset ID filesetName. Caching will be disabled and the mount will be tried again after mountRetryTime seconds, on the next request to the gateway. - 6027-3246 [I]
AFM: Prefetch recovery started for the file system fileSystem fileset filesetName. - 6027-3247 [I]
AFM: Prefetch recovery completed for the file system fileSystem fileset filesetName. error error - 6027-3248 [E]
AFM: Cannot find the control file for fileset filesetName in the exported file system at home. This file is required to operate in primary mode. The fileset will be disabled. - 6027-3249 [E]
AFM: Target for fileset filesetName is not a secondary-mode fileset or file system. This is required to operate in primary mode. The fileset will be disabled. - 6027-3250 [E]
AFM: Refresh intervals cannot be set for fileset. - 6027-3252 [I]
AFM: Home has been restored for cache filesetName. Synchronization with home will be resumed. - 6027-3253 [E]
AFM: Change in home is detected for cache filesetName. Synchronization with home is suspended until the problem is resolved. - 6027-3254 [W]
AFM: Home is taking longer than expected to respond for cache filesetName. Synchronization with home is temporarily suspended. - 6027-3255 [E]
AFM: Target for fileset filesetName is a secondary-mode fileset or file system. Only a primary-mode, read-only or local-update mode fileset can operate on a secondary-mode fileset. The fileset will be disabled. - 6027-3256 [I]
AFM: The RPO peer snapshot was missed for file system fileSystem fileset filesetName. - 6027-3257 [E]
AFM: Unable to start thread to verify primary filesets for RPO. - 6027-3300
Attribute afmShowHomeSnapshot cannot be changed for a single-writer fileset. - 6027-3301
Unable to quiesce all nodes; some processes are busy or holding required resources. - 6027-3302
Attribute afmShowHomeSnapshot cannot be changed for a afmMode fileset. - 6027-3303
Cannot restore snapshot; quota management is active for fileSystem. - 6027-3304
Attention: Disk space reclaim on number of number regions in fileSystem returned errors. - 6027-3305
AFM Fileset filesetName cannot be changed as it is in beingDeleted state - 6027-3306
Fileset cannot be changed because it is unlinked. - 6027-3307
Fileset cannot be changed. - 6027-3308
This AFM option cannot be set for a secondary fileset. - 6027-3309
The AFM attribute specified cannot be set for a primary fileset. - 6027-3310
A secondary fileset cannot be changed. - 6027-3311
A primary fileset cannot be changed. - 6027-3312
No inode was found matching the criteria. - 6027-3313
File system scan RESTARTED due to resume of all disks being emptied. - 6027-3314
File system scan RESTARTED due to new disks to be emptied. - 6027-3315
File system scan CANCELLED due to new disks to be emptied or resume of all disks being emptied. - 6027-3316
Unable to create file system because there is not enough space for the log files. Number of log files: numberOfLogFiles. Log file size: logFileSize. Change one or more of the following as suggested and try again: - 6027-3317
Warning: file system is not 4K aligned due to small reasonString. Native 4K sector disks cannot be added to this file system unless the disk that is used is dataOnly and the data block size is at least 128K. - 6027-3318
Fileset filesetName cannot be deleted as it is in compliant mode and it contains user files. - 6027-3319
The AFM attribute optionName cannot be set for a primary fileset. - 6027-3320
commandName: indefiniteRetentionProtection is enabled. File system cannot be deleted. - 6027-3321
Snapshot snapshotName is an internal pcache recovery snapshot and cannot be deleted by user. - 6027-3400
Attention: The file system is at risk. The specified replication factor does not tolerate unavailable metadata disks. - 6027-3401
Failure group value for disk diskName is not valid. - 6027-3402 [X]
An unexpected device mapper path dmDevice (nsdId) was detected. The new path does not have Persistent Reserve enabled. The local access to disk diskName will be marked as down. - 6027-3404 [E]
The current file system version does not support write caching. - 6027-3405 [E]
Cannot change the rapid repair, \"fileSystemName\" is mounted on number node(s). - 6027-3406
Error: Cannot add 4K native dataOnly disk diskName to non-4K aligned file system unless the file system version is at least 4.1.1.4. - 6027-3407 [E]
Disk failure. Volume name. rc = value, and physical volume name. - 6027-3450
Error errorNumber when purging key (file system fileSystem). Key name format possibly incorrect. - 6027-3451
Error errorNumber when emptying cache (file system fileSystem). - 6027-3452 [E]
Unable to create encrypted file fileName (inode inodeNumber, fileset filesetNumber, file system fileSystem). - 6027-3453 [E]
Unable to open encrypted file: inode inodeNumber, fileset filesetNumber, file system fileSystem. - 6027-3457 [E]
Unable to rewrap key with name Keyname (inode inodeNumber, fileset filesetNumber, file system fileSystem). - 6027-3458 [E]
Invalid length for the Keyname string. - 6027-3459 [E]
Not enough memory. - 6027-3460 [E]
Incorrect format for the Keyname string. - 6027-3461 [E]
Error code: errorNumber. - 6027-3462 [E]
Unable to rewrap key: original key name: originalKeyname, new key name: newKeyname (inode inodeNumber, fileset filesetNumber, file system fileSystem). - 6027-3463 [E]
Rewrap error. - 6027-3464 [E]
New key is already in use. - 6027-3465 [E]
Cannot retrieve original key. - 6027-3466 [E]
Cannot retrieve new key. - 6027-3468 [E]
Rewrap error code errorNumber. - 6027-3469 [E]
Encryption is enabled but the crypto module could not be initialized. Error code: number. Ensure that the GPFS crypto package was installed. - 6027-3470 [E]
Cannot create file fileName: extended attribute is too large: numBytesRequired bytes (numBytesAvailable available) (fileset filesetNumber, file system fileSystem). - 6027-3471 [E]
At least one key must be specified. - 6027-3472 [E]
Could not combine the keys. - 6027-3473 [E]
Could not locate the RKM.conf file. - 6027-3474 [E]
Could not open fileType file ('fileName' was specified). - 6027-3475 [E]
Could not read file 'fileName'. - 6027-3476 [E]
Could not seek through file 'fileName'. - 6027-3477 [E]
Could not wrap the FEK. - 6027-3478 [E]
Insufficient memory. - 6027-3479 [E]
Missing combine parameter string. - 6027-3480 [E]
Missing encryption parameter string. - 6027-3481 [E]
Missing wrapping parameter string. - 6027-3482 [E]
'combineParameter' could not be parsed as a valid combine parameter string. - 6027-3483 [E]
'encryptionParameter' could not be parsed as a valid encryption parameter string. - 6027-3484 [E]
'wrappingParameter' could not be parsed as a valid wrapping parameter string. - 6027-3485 [E]
The Keyname string cannot be longer than number characters. - 6027-3486 [E]
The KMIP library could not be initialized. - 6027-3487 [E]
The RKM ID cannot be longer than number characters. - 6027-3488 [E]
The length of the key ID cannot be zero. - 6027-3489 [E]
The length of the RKM ID cannot be zero. - 6027-3490 [E]
The maximum size of the RKM.conf file currently supported is number bytes. - 6027-3491 [E]
The string 'Keyname' could not be parsed as a valid key name. - 6027-3493 [E]
numKeys keys were specified but a maximum of numKeysMax is supported. - 6027-3494 [E]
Unrecognized cipher mode. - 6027-3495 [E]
Unrecognized cipher. - 6027-3496 [E]
Unrecognized combine mode. - 6027-3497 [E]
Unrecognized encryption mode. - 6027-3498 [E]
Invalid key length. - 6027-3499 [E]
Unrecognized wrapping mode. - 6027-3500 [E]
Duplicate Keyname string 'keyIdentifier'. - 6027-3501 [E]
Unrecognized combine mode ('combineMode'). - 6027-3502 [E]
Unrecognized cipher mode ('cipherMode'). - 6027-3503 [E]
Unrecognized cipher ('cipher'). - 6027-3504 [E]
Unrecognized encryption mode ('mode'). - 6027-3505 [E]
Invalid key length ('keyLength'). - 6027-3506 [E]
Mode 'mode1' is not compatible with mode 'mode2', aborting. - 6027-3509 [E]
Key 'keyID:RKMID' could not be fetched (RKM reported error errorNumber). - 6027-3510 [E]
Could not bind symbol symbolName (errorDescription). - 6027-3512 [E]
The specified type 'type' for backend 'backend' is invalid. - 6027-3513 [E]
Duplicate backend 'backend'. - 6027-3517 [E]
Could not open library (libName). - 6027-3518 [E]
The length of the RKM ID string is invalid (must be between 0 and length characters). - 6027-3519 [E]
'numAttempts' is not a valid number of connection attempts. - 6027-3520 [E]
'sleepInterval' is not a valid sleep interval. - 6027-3521 [E]
'timeout' is not a valid connection timeout. - 6027-3522 [E]
'url' is not a valid URL. - 6027-3524 [E]
'tenantName' is not a valid tenantName. - 6027-3527 [E]
Backend 'backend' could not be initialized (error errorNumber). - 6027-3528 [E]
Unrecognized wrapping mode ('wrapMode'). - 6027-3529 [E]
An error was encountered while processing file 'fileName': - 6027-3530 [E]
Unable to open encrypted file: key retrieval not initialized (inode inodeNumber, fileset filesetNumber, file system fileSystem). - 6027-3533 [E]
Invalid encryption key derivation function. - 6027-3534 [E]
Unrecognized encryption key derivation function ('keyDerivation'). - 6027-3535 [E]
Incorrect client certificate label 'clientCertLabel' for backend 'backend'. - 6027-3537 [E]
Setting default encryption parameters requires empty combine and wrapping parameter strings. - 6027-3540 [E]
The specified RKM backend type (rkmType) is invalid. - 6027-3541 [E]
Encryption is not supported on Windows. - 6027-3543 [E]
The integrity of the file encrypting key could not be verified after unwrapping; the operation was cancelled. - 6027-3545 [E]
Encryption is enabled but there is no valid license. Ensure that the GPFS crypto package was installed properly. - 6027-3546 [E]
Key 'keyID:rkmID' could not be fetched. The specified RKM ID does not exist; check the RKM.conf settings. - 6027-3547 [E]
Key 'keyID:rkmID' could not be fetched. The connection was reset by the peer while performing the TLS handshake. - 6027-3548 [E]
Key 'keyID:rkmID' could not be fetched. The IP address of the RKM could not be resolved. - 6027-3549 [E]
Key 'keyID:rkmID' could not be fetched. The TCP connection with the RKM could not be established. - 6027-3550
Error when retrieving encryption attribute: errorDescription. - 6027-3551
Error flushing work file fileName: errorString - 6027-3552
Failed to fork a new process to operationString file system. - 6027-3553
Failed to sync fileset filesetName. - 6027-3554
The restore command encountered an out-of-memory error. - 6027-3555
name must be combined with FileInherit, DirInherit or both. - 6027-3556
cmdName error: insufficient memory. - 6027-3557
cmdName error: could not create a temporary file. - 6027-3558
cmdName error: could not initialize the key management subsystem (error returnCode). - 6027-3559
cmdName error: could not create the key database (error returnCode). - 6027-3560
cmdName error: could not create the new self-signed certificate (error returnCode). - 6027-3561
cmdName error: could not extract the key item (error returnCode). - 6027-3562
cmdName error: base64 conversion failed (error returnCode). - 6027-3563
cmdName error: could not extract the private key (error returnCode). - 6027-3564
cmdName error: could not initialize the ICC subsystem (error returnCode returnCode). - 6027-3565
cmdName error: I/O error. - 6027-3566
cmdName error: could not open file 'fileName'. - 6027-3567
cmdName error: could not convert the private key. - 6027-3568
cmdName error: could not extract the private key information structure. - 6027-3569
cmdName error: could not convert the private key information to DER format. - 6027-3570
cmdName error: could not encrypt the private key information structure (error returnCode). - 6027-3571
cmdName error: could not insert the key in the keystore, check your system's clock (error returnCode). - 6027-3572
cmdName error: could not insert the key in the keystore (error returnCode). - 6027-3573
cmdName error: could not insert the certificate in the keystore (error returnCode). - 6027-3574
cmdName error: could not initialize the digest algorithm. - 6027-3575
cmdName error: error while computing the digest. - 6027-3576
cmdName error: could not initialize the SSL environment (error returnCode). - 6027-3577
Failed to sync fileset filesetName. errString. - 6027-3578 [E]
pathName is not a valid argument for this command. You must specify a path name within a single GPFS snapshot. - 6027-3579
cmdName error: the cryptographic library could not be initialized in FIPS mode. - 6027-3580
Failed to sync file system: fileSystem Error: errString. - 6027-3581
Failed to create the operation list file. - 6027-3582 [E]
Compression is not supported for clone or clone-parent files. - 6027-3583 [E]
Compression is not supported for snapshot files. - 6027-3584 [E]
Current file system version does not support compression. - 6027-3585 [E]
Compression is not supported for AFM cached files. - 6027-3586 [E]
Compression/uncompression failed. - 6027-3587 [E]
Aborting compression as the file is opened in hyper allocation mode. - 6027-3588 [E]
Aborting compression as the file is currently memory mapped, opened in direct I/O mode, or stored in a horizontal storage pool. - 6027-3589
cmdName error: Cannot set the password twice. - 6027-3590
cmdName error: Could not access file fileName (error errorCode). - 6027-3591
cmdName error: The password specified in file fileName exceeds the maximum length of length characters. - 6027-3592
cmdName error: Could not read the password from file fileName. - 6027-3593 [E]
Compression is supported only for regular files. - 6027-3594 [E]
[E] Failed to synchronize the being restored fileset:filesetName. [I] Please stop the activities in the fileset and rerun the command. - 6027-3595 [E]
[E] Failed to synchronize the being restored file system:fileSystem. [I] Please stop the activities in the file system and rerun the command. - 6027-3596
cmdName error: could not read/write file from/to directory 'pathName'. This path does not exist. - 6027-3700 [E]
Key 'keyID' was not found on RKM ID 'rkmID'. - 6027-3701 [E]
Key 'keyID:rkmID' could not be fetched. The authentication with the RKM was not successful. - 6027-3702 [E]
Key 'keyID:rkmID' could not be fetched. Permission denied. - 6027-3703 [E]
I/O error while accessing the keystore file 'keystoreFileName'. - 6027-3704 [E]
The keystore file 'keystoreFileName' has an invalid format. - 6027-3705 [E]
Incorrect FEK length after unwrapping; the operation was cancelled. - 6027-3706 [E]
The crypto library with FIPS support is not available for this architecture. Disable FIPS mode and reattempt the operation. - 6027-3707 [E]
The crypto library could not be initialized in FIPS mode. Ensure that the crypto library package was correctly installed. - 6027-3708 [E]
Incorrect passphrase for backend 'backend'. - 6027-3709 [E]
Error encountered when parsing line lineNumber: expected a new RKM backend stanza. - 6027-3710 [E]
Error encountered when parsing line lineNumber: invalid key 'keyIdentifier'. - 6027-3711 [E]
Error encountered when parsing line lineNumber: invalid key-value pair. - 6027-3712 [E]
Error encountered when parsing line lineNumber: incomplete RKM backend stanza 'backend'. - 6027-3713 [E]
An error was encountered when parsing line lineNumber: duplicate key 'key'. - 6027-3714 [E]
Incorrect permissions for the /var/mmfs/etc/RKM.conf configuration file on node nodeName: the file must be owned by the root user and be in the root group, must be a regular file and be readable and writable by the owner only. - 6027-3715 [E]
Error encountered when parsing line lineNumber: RKM ID 'RKMID' is too long, it cannot exceed length characters. - 6027-3716 [E]
Key 'keyID:rkmID' could not be fetched. The TLS handshake could not be completed successfully. - 6027-3717 [E]
Key 'keyID:rkmID' could not be fetched. The RKM is in quarantine after experiencing a fatal error. - 6027-3718 [E]
Key 'keyID:rkmID' could not be fetched. Invalid request. - 6027-3719 [W]
Wrapping parameter string 'oldWrappingParameter' is not safe and will be replaced with 'newWrappingParameter'. - 6027-3720 [E]
binaryName error: Invalid command type 'command'. - 6027-3721 [E]
binaryName error: Invalid arguments. - 6027-3722 [E]
An error was encountered while processing file 'fileName': errorString - 6027-3723 [E]
Incorrect permissions for the configuration file fileName on node nodeName. - 6027-3726 [E]
Key 'keyID:rkmID' could not be fetched. Bad certificate. - 6027-3727 [E]
Key 'keyID:rkmID' could not be fetched. Invalid tenantName. - 6027-3728 [E]
The keyStore permissions are incorrect for fileName. Access should be only granted to root, and no execute permission is allowed for the file. - 6027-3729 [E]
Key 'keyID:rkmID' could not be fetched. The SSL connection cannot be initialized. - 6027-3900
Invalid flag 'flagName' in the criteria file. - 6027-3901
Failed to receive inode list: listName. - 6027-3902
Check file 'fileName' on fileSystem for inodes that were found matching the criteria. - 6027-3903 [W]
quotaType quota is disabled or quota file is invalid. - 6027-3904 [W]
quotaType quota file is not a metadata file. File was not copied. - 6027-3905 [E]
Specified directory does not exist or is invalid. - 6027-3906 [W]
backupQuotaFile already exists. - 6027-3907 [E]
No other quorum node found during cluster probe. - 6027-3908
Check file 'fileName' on fileSystem for inodes with broken disk addresses or failures. - 6027-3909
The file (backupQuotaFile) is a quota file in fileSystem already. - 6027-3910 [I]
Delay number seconds for safe recovery. - 6027-3911
Error reading message from the file system daemon: errorString : The system ran out of memory buffers or memory to expand the memory buffer pool. - 6027-3912 [E]
File fileName cannot run with error errorCode: errorString. - 6027-3913
Attention: disk diskName is a 4K native dataOnly disk and it is used in a non-4K aligned file system. Its usage is not allowed to change from dataOnly. - 6027-3914 [E]
Current file system version does not support compression. - 6027-3915
Invalid file system name provided: 'FileSystemName'. - 6027-3916 [E]
fileSystemName is a clone of fileSystemName, which is mounted already. - 6027-3917 [E]
The file fileName does not exist in the root directory of fileSystemName. - 6027-3918 [N]
Disk lease period expired number seconds ago in cluster clusterName. Attempting to reacquire the lease. - 6027-3919 [E]
No attribute found. - 6027-3920 [E]
Cannot find an available quorum node that would be able to successfully run Expel command. - 6027-4000 [I]
descriptorType descriptor on this NSD can be updated by running the following command from the node physically connected to NSD nsdName: - 6027-4001 [I]
'mmfsadm writeDesc <device> descriptorType descriptorId:descriptorId nsdFormatVersion pdiskStatus', where device is the device name of that NSD. - 6027-4002 [I]
Before running this command, check both NSDs. You might have to delete one of the NSDs. - 6027-4003 [E]
The on-disk descriptorType descriptor of nsdName descriptorIdName descriptorId:descriptorId is not valid because of bad corruptionType: - 6027-4004 [D]
On-disk NSD descriptor: nsdId nsdId nsdMagic nsdMagic nsdFormatVersion nsdFormatVersion on disk nsdChecksum nsdChecksum calculated checksum calculatedChecksum nsdDescSize nsdDescSize firstPaxosSector firstPaxosSector nPaxosSectors nPaxosSectors nsdIsPdisk nsdIsPdisk - 6027-4005 [D]
Local copy of NSD descriptor: nsdId nsdId nsdMagic nsdMagic formatVersion formatVersion nsdDescSize nsdDescSize firstPaxosSector firstPaxosSector nPaxosSectors nPaxosSectors - 6027-4006 [I]
Writing NSD descriptor of nsdName with local copy: nsdId nsdId nsdFormatVersion formatVersion firstPaxosSector firstPaxosSector nPaxosSectors nPaxosSectors nsdDescSize nsdDescSize nsdIsPdisk nsdIsPdisk nsdChecksum nsdChecksum - 6027-4007
errorType descriptor on descriptorType nsdId nsdId:nsdId error error - 6027-4008 [E]
On-disk descriptorType descriptor of nsdName is valid but has a different UID: uid descriptorId:descriptorId on-disk uid descriptorId:descriptorId nsdId nsdId:nsdId - 6027-4009 [E]
On-disk NSD descriptor of nsdName is valid but has a different ID. ID in cache is cachedId and ID on-disk is ondiskId - 6027-4010 [I]
This corruption can happen if the device is reused by another NSD with the -v option and a file system is created with that reused NSD. - 6027-4011 [D]
On-disk disk descriptor: uid descriptorID:descriptorID magic descMagic formatVersion formatVersion descSize descSize checksum on disk diskChecksum calculated checksum calculatedChecksum firstSGDescSector firstSGDescSector nSGDescSectors nSGDescSectors lastUpdateTime lastUpdateTime - 6027-4012 [D]
Local copy of disk descriptor: uid descriptorID:descriptorID firstSGDescSector firstSGDescSector nSGDescSectors nSGDescSectors - 6027-4013 [I]
Writing disk descriptor of nsdName with local copy: uid descriptorID:descriptorID, magic magic, formatVersion formatVersion firstSGDescSector firstSGDescSector nSGDescSectors nSGDescSectors descSize descSize - 6027-4014 [D]
Local copy of StripeGroup descriptor: uid descriptorID:descriptorID curFmtVersion curFmtVersion configVersion configVersion - 6027-4015 [D]
On-disk StripeGroup descriptor: uid sgUid:sgUid magic magic curFmtVersion curFmtVersion descSize descSize on-disk checksum diskChecksum calculated checksum calculatedChecksum configVersion configVersion lastUpdateTime lastUpdateTime - 6027-4016 [E]
Data buffer checksum mismatch during write. File system fileSystem tag tag1 tag2 nBytes nBytes diskAddresses - 6027-4017 [E]
Current file system version does not support the initial disk status BeingAddedByGNR. - 6027-4018 [E]
Disk diskName is not an existing vdisk, but initial status BeingAddedByGNR is specified
Parent topic: References