/* Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved. */ / / ident "%Z%%M% %I% %E%" / / NAME / acfsus.msg / DESCRIPTION / Message file for ACFS commands / NOTES / # CHARACTER_SET_NAME=American_America.US7ASCII / / MODIFIED / averhuls 07/25/11 - XbranchMerge averhuls_install_from_load from / main / averhuls 07/22/11 - add 9399. / averhuls 07/21/11 - XbranchMerge averhuls_crs_modify_and_more from / main / certan 07/20/11 - Backport certan_acfsroot_odmdir_check from main / certan 07/18/11 - Add messages 9395 and 9396 / mlmiller 07/14/11 - Backport mlmiller_bug-12747467 from main / rkiyer 07/14/11 - Bug 12743981: Introduced message 10422 / mlmiller 07/13/11 - Add message 07256 to warn user that protection / bits were unexpected. / averhuls 07/11/11 - Modify 9427, 9337. Add 09164-7. / averhuls 06/30/11 - XbranchMerge averhuls_acfsroot_return_codes / from main / gsanders 06/30/11 - Backport gsanders_bug-12692110 from main / mkeller 06/28/11 - Add msg 3323 / gsanders 06/26/11 - Add 09394 / averhuls 06/22/11 - add 3514. / averhuls 06/22/11 - copy 3514 from 11.2.0.3. / jibeltz 06/20/11 - Backport jibeltz_bug-12620353 from main / averhuls 06/20/11 - Add reboot recommended messages. / jibeltz 06/08/11 - Added messages 5170 and 5171 / nagkumar 06/07/11 - Add messages 10935. / ethibaul 05/26/11 - Add messages 3450 and 3451 / tmark 05/12/11 - Backport tmark_bugs5-6_main from main / averhuls 05/06/11 - Minor edit of 9331. / tmark 05/05/11 - Bug 12430724: Added message 3178. / rkiyer 05/02/11 - Add message 10355 for Antivirus system realm. / rkiyer 05/02/11 - Updated messages 10408 and 10409 / rbreau 04/27/11 - Add message 7165 / averhuls 04/26/11 - XbranchMerge averhuls_persistent_log from main / averhuls 04/22/11 - Add persistent log messages. / mkeller 04/18/11 - Backport mkeller_rep from main / nagkumar 04/14/11 - Add msgs from 10901 - 10934. / sverhuls 03/24/11 - Backport sverhuls_bug-11804097 from main / rbreau 03/23/11 - Backport rbreau_bug-11807310 from main / anjiwaji 03/23/11 - Add verbose option messages for acfsload / 9159 and 9160. Also add a verbose flag to 9331 / and 9338. Add new usage messages 9161-9163. / mcarrell 03/21/11 - Backport mcarrell_bug-11874601 from main / hmishra 03/18/11 - Modified msg 10421 / qmcintos 03/16/11 - Backport qmcintos_bug-11848640 from main / averhuls 03/15/11 - Backport averhuls_bug-11849923 from main / rkiyer 03/15/11 - Update message 10659 / mkeller 03/14/11 - Backport mkeller_bug-11682127 from main / qmcintos 03/14/11 - Add 3177 / averhuls 03/11/11 - Add 9158. / ethibaul 03/10/11 - Backport ethibaul_bug-11820987 from main / ethibaul 03/10/11 - 11820987: Add 4058 / mkeller 03/07/11 - Add msgs 5730 + 5731. / ethibaul 03/03/11 - Backport ethibaul_bug-11742666 from main / tmark 02/25/11 - Backport tmark_bug-11691115 from main / ethibaul 02/25/11 - 11742666: Add new version message for repl / and tags / anjiwaji 02/23/11 - Add extra debugging messages for acfsload and / acfslib. / mkeller 02/23/11 - Backport mkeller_dr10 from main / mkeller 02/16/11 - Backport mkeller_acfsutilbugs from main / josmith 02/11/11 - Add error message when we cannot query the OCR / version information / mkeller 02/09/11 - Add tag message 03318 / mlmiller 02/09/11 - Backport mlmiller_bug-10426317 from main / ethibaul 02/09/11 - Backport ethibaul_second_vers_sol_aix from main / nagkumar 02/08/11 - Backport nagkumar_bug_10065857 from main / jzolla 02/02/11 - Add encryption message 10421 / nagkumar 01/31/11 - Add msgs 10351, 10352, 10353 and 10354. / josmith 01/12/11 - Add mountpoint length exceeded message for / replication / anjiwaji 01/11/11 - Add header message for acfsroot warning message / from dependency checks. / mlmiller 01/07/11 - XbranchMerge mlmiller_bug-10163596 from main / qmcintos 01/07/11 - Add message 00561,07013,07015,07918 and 07927 / tmark 01/05/11 - Modified 3174. / mlmiller 01/03/11 - Add 5801-5807 for free space threshold warning / in replication foreman, add 5092-5094 / josmith 12/29/10 - Add replication max interval error / raharris 12/13/10 - XbranchMerge / raharris_mkfs_dash_b_warnings_bug_10036078 from / main / josmith 12/09/10 - XbranchMerge josmith_bug-10049050 from main / ethibaul 12/09/10 - XbranchMerge ethibaul_repl_alert_msgs from main / hmishra 12/09/10 - Add 10777-10779 and 10594 message / mlmiller 12/08/10 - Translate 'acfsutil repl info' statues. / Added 00166-00170 & 05155 / josmith 11/30/10 - Add replication CRS Resource message / jzolla 11/22/10 - Added messages 10706 and 10707 / ethibaul 11/19/10 - add replication alert log message fragments / raharris 11/17/10 - Add mkfs ignoring invalid block size message / when a block size besides 4096 was specified, / and then force a 4096 value and keep on going. / ethibaul 11/10/10 - update action statement for 549 / gsanders 10/27/10 - add 09152, 09153, modify 09126 / gsanders 10/27/10 = add 09152, 09153, modify 09126 / averhuls 10/26/10 - Add 09388. / qmcintos 10/22/10 - Add msg 03317 for set tag failure. / ethibaul 10/22/10 - Add message fragments 100-103 / - Add messages 3315 and 3402 / mkeller 10/19/10 - Added 5700-5729 for acfsutuil repl compare / btsao 10/15/10 - Add 7757-7760 msgs;Change 7744, 7745 cause text / raharris 10/14/10 - Add new acfsutil size error messages that / specify that ADVM was the reason why a file / system could not be resized (03171, 03172, / 03173). / - Change 03008 so it is related to just ACFS / resize issues, and allow the 03171, 03172, / 03173 errors handle ADVM/ASM resize issues. / josmith 10/13/10 - Add replicated FS size too small message / jzolla 10/12/10 - Add message 10705 / hmishra 10/01/10 - Added msg 10799. / agraves 09/30/10 - Add new message for Ignoring mounts / nagkumar 09/14/10 - Added msg 10350. / averhuls 09/13/10 - Fix NT advmutil mount/dismount usage spacing to / pass tkvfinfo5. / josmith 09/08/10 - Add Replication Lag Time output / averhuls 09/07/10 - Fix acfsroot usage. / josmith 08/27/10 - Add empty stats range message for replication / gsanders 08/20/10 - Add messages 03165, 03166, 03167, 03168 / ethibaul 08/18/10 - add 2125 / mlmiller 08/10/10 - Add message 05522 for repl terminate when / disk is full / hmishra 08/04/10 - add message 10151 / nimunjal 08/03/10 - Add 10420 / josmith 08/03/10 - Add repl init primary error messages / rkiyer 07/28/10 - Change message 10348 (update 'realm management' / to 'ACFS Security administrator') / averhuls 07/28/10 - add 9091. / nimunjal 07/27/10 - Fix typos 10663-66, add 10702-04 / averhuls 07/23/10 - Update advmutil volinfo usage. / averhuls 07/21/10 - Add 9384. Obsolete 9110. / rkiyer 07/20/10 - Added message 10776 for invalid version / averhuls 07/19/10 - Add 9126. / nagkumar 07/19/10 - modified the msg 10408. / nagkumar 07/11/10 - Added message 10419. / ssprasad 07/11/10 - bug 9799212 fix. / rkiyer 07/09/10 - Change 10277 cause and action / hmishra 07/08/10 - Add messages 10663-10664 . / plancian 07/07/10 - Added message 09150 / jzolla 06/24/10 - Added message 10690 / rkiyer 06/24/10 - added messages 10796 and 10797 for encryption / init recovery / rbreau 06/21/10 - Add new messages for extent errors: / 07235, 07236, 07498, 07499, 07500, 07501, / 07502, 07503 / hmishra 06/21/10 - add message 10689 / mkeller 06/15/10 - Added repl exception number 6505 and reserved / 6500-6525 for exceptions. / nagkumar 06/09/10 - Added msgs 10298 and 10299 / nimunjal 06/07/10 - Add 10798 / hmishra 06/05/10 - add message 10795 / ethibaul 06/03/10 - Add 3314 / certan 06/02/10 - Add message 2119-2124, 4032-4037 / jinjche 06/02/10 - Add messages for acfsroot reregister & / unregister commands / jzolla 05/28/10 - Added security/encryption logging messages / 10728-10733, updated encryption/security log / file names in other messages, added encryption / log messages 10454-10462 / ssprasad 05/25/10 - bug fix 9714664 / rkiyer 05/21/10 - update few sec and encr messages with review / comments from Bill Manry / hmishra 05/24/10 - add message 10792-10794 / nagkumar 05/21/10 - Added 10588 - 10593 / ethibaul 05/20/10 - change %x to %d in 1085 / hmishra 05/17/10 - add message 10660 and 10661 / ethibaul 05/13/10 - Add 3310-3313 / qmcintos 05/09/10 - add message 05085 / btsao 05/07/10 - Add messages 7742-7756 for fsck. / agraves 05/05/10 - Remove the OneOff field for USM versions. / rkiyer 04/25/10 - Introduced messages for password prompts and / for password validation / gsanders 05/05/10 - Add message 9459 / mlmiller 05/04/10 - Add 5083 & 5084 for replication re-inits / averhuls 04/28/10 - Enhance several CAUSE/ACTIONs. / jinjche 04/28/10 - Change to reflect review comments / jinjche 04/27/10 - Add message 09366 / stomar 04/27/10 - Update message 10415 / ethibaul 04/26/10 - Replication message review / hsabbine 04/21/10 - Add Backup Operator Realm created message / tmark 04/20/10 - RW snaps project. / jzolla 04/20/10 - Added new encryption messages / agraves 04/20/10 - Add new feature, advmutil canonical message. / rkiyer 04/19/10 - Add messages 10773 and 10774 for wallet locks / agraves 04/19/10 - Change stale to offline in 9111. / rkiyer 04/19/10 - Modified msgs 10223 and 10224. Added new / message for new rule types 10262 and 10263 / ethibaul 04/15/10 - Add msg 5518 / agraves 04/14/10 - Fix message ordering / mlmiller 04/13/10 - Message for time differences between primary / and standby nodes, 5354. Also adjust / replication stats so that they print per / minute instead of hour, and format the output. / hmishra 04/12/10 - Add Message 10309 / agraves 04/10/10 - Change stale to offline. / agraves 04/08/10 - Add new unable to run acfsutil message for / resources. / jinjche 04/07/10 - Address Bill Manry's comments / rbreau 03/25/10 - Fix truncation problem for message 7155 / Bug # 9523398 / ethibaul 03/23/10 - Added Solaris mount usage messages:2114-2118 / sverhuls 03/23/10 - Add feature not supported on this platform / message. New message #620. / averhuls 03/19/10 - Add msg 9426. / certan 03/19/10 - ACFS-02098 was shared between Solaris and / AIX, but separate messages are now needed due / to different usage output. Added ACFS-02113 / to be used by AIX. / hmishra 03/18/10 - added message 10340,10341,10772 / averhuls 03/16/10 - convert the remaining 4 char codes to 5 chars / for consistency. / averhuls 03/16/10 - convert the remaining 4 char id codes to 5 / chars for consistency. / abakst 03/10/10 - Add warning for non-empty directory during / acfsroot uninstall / jeabraha 03/02/10 - Update Solaris mount usage for read-only / support / mlmiller 03/01/10 - New message 05010 / anjiwaji 03/01/10 - Add additional acfsinstall messages for error / handling / raharris 02/22/10 - Add ACFS-00619 This is a little/big endian / computer error message. / jzolla 02/19/10 - New messages for Security and Encryption / logging: 10725, 10726, 10727, 10414, 10658 / jinjche 02/18/10 - Add more messages for acfsroot / rkiyer 02/10/10 - New messages introduced for init checks and / modified some existing ones. / hsabbine 02/06/10 - Add ACFSSEC messages 10331, 10332, and 10333 / for reaching max limits / hmishra 02/04/10 - added message 10331-10338 / nagkumar 02/01/10 - Added/Changed the messages 10645, 10646, / 10650-53, 10675-77, 10687-88. / hsabbine 02/01/10 - Added new ACFSSEC message 10330 for description / mkeller 01/25/10 - Fix/improve 05507+08 05511+12. remove / duplicates 05509+10. / nagkumar 01/15/10 - ACFS security and encryption message updates / in the range 10500 - 10750 and 10322 - 10329 / ssprasad 01/10/10 - Added ACFSSEC message 10240 / nimunjal 12/28/09 - Added ACFSSEC message 10261 / ethibaul 12/22/09 - 2096 and 2097: use devices and nodevices / btsao 12/16/09 - Add message 3309. / ethibaul 12/09/09 - 9195035: Add 1150 / rramdath 12/07/09 - ACFS security and encryption message changes-II / nimunjal 12/01/09 - Added messages 10596-10599 and 10624 for acfssec / jzolla 11/24/09 - Added messages 10412 and 10413 for encryption / jinjche 11/19/09 - change a character in a debugging message / averhuls 11/05/09 - Add 9137. / jinjche 10/30/09 - Made changes to reflect Tony's code review / comments / jinjche 10/28/09 - Add more messages for acfsroot on AIX / abakst 09/28/09 - Add 09349, 09350 for acfsroot / averhuls 09/21/09 - Add 9115. / abakst 09/18/09 - Add messages for acfsroot / btsao 08/31/09 - Add new message 3308. / agraves 08/21/09 - Add message for advumtil to print out compat. / averhuls 08/12/09 - Add acfsinstall messages. / abakst 08/10/09 - Add 00608 for conflicting mount options / ethibaul 07/21/09 - Modify all message id's to be 5 digits / - Add messages for SOL mount / averhuls 07/16/09 - Add msg 9110. / bonelso 07/15/09 - Add 9038,9039 / abakst 07/13/09 - Add messages used by AIX mount / averhuls 07/07/09 - Add acfs*mount clean failure message (9275). / averhuls 07/02/09 - Add msg 136, 9290. / averhuls 07/02/09 - Add msg 9136, 9290. / jinjche 06/24/09 - Add more messages for ADVM configuration tools / rbreau 06/05/09 - Modify fsck messages to conform to Oracle / standards / ethibaul 06/01/09 - Add -o rootsuid,device,nodevice to mount usage / mkeller 05/26/09 - Bring over replication msgs from clsdus.msg, / modify some. / jibeltz 05/18/09 - fix variable name in msg 7107 / ethibaul 05/15/09 - Add -o norootsuid to mount usage / jinjche 05/13/09 - Add more messages for AIX configuration tools / rbreau 05/13/09 - Fix message 7390 - missing print option / agraves 05/11/09 - Add cause/action, change some currently there. / crusman 05/02/09 - AIX usage for fsck and mkfs / agraves 04/29/09 - Incorporate Bill Manry's review comments for / Tony Verhulst. / averhuls 04/30/09 - Add acfsdriverstate -orahome usage message. / rbreau 04/21/09 - Change "expected: %s" to ", but expected to / find: %s" in fsck messages and provide examples / to help translators. / averhuls 04/15/09 - Rename usminstall to acfsinstall. / jeabraha 04/15/09 - Update 7001 (syntax line for fsck) / qmcintos 04/10/09 - Replace %e with %u. / jinjche 04/09/09 - Add messages for AIX device configuration tools / averhuls 04/02/09 - Add "Operating system '%s' not supported". / raharris 04/02/09 - Add OfsFixGrowGBM() error messages. / - Add messages 7720, 7721, 7722, 7723, 7724, / 7725, 7726, 7727, 7728, 7729, 7740, 7741 / - Modify 3008 to include cause/action which / mentions that the user may be able to use ACFS / fixer to allow future expansion. / crusman 04/01/09 - Add 555, 556 / ethibaul 03/30/09 - Changes due to translation comments / averhuls 03/19/09 - Remove obsoleted acfsdbhome messages. / tmark 03/16/09 - Delete 7021, 7167, 7332, 7362, 7384, 7481, / and 7623. / Modify 7039, 7053, 7074, 7084, 7121, 7387, 7411, / 7465, 7599, 7617, and 7623. / Add 7030, 7048, 7052, 7069, 7355, 7356, 7362, / and 7904-7911. / jeabraha 03/16/09 - Add 7901 (%s Hash Bucket Header controlling_bkt / (%s) must be less than ...) / ethibaul 03/10/09 - Add 1095 and 1096 / amilicia 02/24/09 - Remove OFS_ATTRIB_NO_BUFFERING attribute. / averhuls 02/20/09 - Change usm_* to acfs* (usm_root -> acfsroot). / averhuls 02/11/09 - Add message for usm_mount. / jeabraha 02/10/09 - Add message 7900 (freeDataList blkNum is / invalid...) / averhuls 02/06/09 - Add new usm_root message 9343. / ethibaul 01/28/09 - Add 2092 / averhuls 01/21/09 - Change message 9317. / bonelso 01/20/09 - advmutil changes / ethibaul 01/13/09 - use Oracle Restart instead of SIHA / raharris 01/02/09 - Change wording of 7278 (Integrity check any / unprocessed files...) / - Change wording of 7283 (OfsCheckOrphanIntegrity: / fenum: %s offset: %s type: %s) / - Change wording of 7299 (\tUnprocessed file / integrity check complete.\n) / - Change wording of 7647 (fenum=%u: Local / extents: Table full.) / agraves 12/31/08 - Add new messages for registry key / initialization from ACFS control device. / mcarrell 12/30/08 - Add AIX to 7652. / averhuls 12/22/08 - Add usm install / runtime tools messages. / ethibaul 12/02/08 - Add 550, 1019, 1021, 1022 / azlotek 11/25/08 - Add message for resize partial failure case. / ethibaul 11/25/08 - Add 549 / sverhuls 11/20/08 - Remove 3133 / rbreau 11/10/08 - Add messages for FSCK / btsao 10/30/08 - Add ofsutil Tagging messages. / jeabraha 10/29/08 - Changes for fsck / ethibaul 10/24/08 - Apply review comments / sverhuls 10/22/08 - Change message 606 + add 3961 / averhuls 10/15/08 - Minor advmutil volinfo -l format change. / ethibaul 10/06/08 - Fix multi line messages / ethibaul 09/25/08 - Add new snap info msg ids / ethibaul 09/25/08 - fix snap dir reference / ethibaul 09/17/08 - Add ranges; Fix 7414255 / mkeller 09/15/08 - delete 3109 / bonelso 09/14/08 - Modify some advmutil messages / unmount --> dismount / ethibaul 08/19/08 - 618, 1094 / ethibaul 08/18/08 - ofs->acfs command name changes / crusman 08/18/08 - add 3147 to 3154 / ethibaul 08/12/08 - Add 3157, 3158 / mkeller 08/12/08 - 610 -> 617 / mkeller 07/31/08 - 3139 -> 3142 / averhuls 07/28/08 - add advmutil volinfo messages. / mkeller 07/11/08 - 3143 is now used for a different purpose / mkeller 06/11/08 - Many Oracle Registry message add/mods/deletes / bonelso 06/02/08 - Add new messages for advmutil / ethibaul 04/25/08 - Change OFS->ACFS, AVD->ADVM / mkeller 05/21/08 - fix 03143 / ethibaul 05/15/08 - Add 592 / mkeller 05/08/08 - Add and remove messages for acfsutil registry -i / averhuls 04/24/08 - Add advmutil messages. / sverhuls 04/15/08 - Fix 6896200 / ethibaul 04/04/08 - Add messages used by acfsmountvol and / acfsdismount / ethibaul 04/03/08 - Add messages used by acfsutil registry / ethibaul 03/26/08 - Add messages used by acfsutil / sverhuls 03/18/08 - Fix 6855426 / ethibaul 02/21/08 - Add messages used by acfsformat/mkfs.acfs / and mount.acfs / mlmiller 02/27/08 - Add replication messages / ethibaul 12/28/07 - Created / /////////////////////////////////////////////////////////// // ALL ERROR CODES MUST BE 5 CHARACTERS // /////////////////////////////////////////////////////////// / MSG GROUP ERROR CODE RANGE / --------- ---------------- / unused 00000-00099 / phrases, fragments 00100-00499 / generic 00500-00999 / mkfs.acfs/acfsformat 01000-01999 / mount.acfs/acfsmountvol 02000-02999 / acfsutil 03000-03999 / acfsdismount 04000-04999 / replication 05000-06999 / fsck.acfs/acfschkdsk 07000-08999 / advmutil 09000-09099 / usm install/runtime 09100-09499 / security 10000-10999 / device config tools 11000-11999 / / // / Phrases, message fragments 00100, 0, "ENABLED" 00101, 0, "DISABLED" 00102, 0, "primary" 00103, 0, "standby" 00104, 0, "Failed to open file %s." 00105, 0, "Failed to communicate with driver." 00106, 0, "File deletion failed." 00107, 0, "Failed to move file from %s to %s." 00108, 0, "Read failed." 00109, 0, "Unable to obtain the system time." 00110, 0, "Insufficient memory." 00111, 0, "File resize failed." 00112, 0, "UNUSED" 00113, 0, "Standby terminating normally." 00114, 0, "Relocating: The standby replication site cannot be configured." 00115, 0, "Terminating normally." 00116, 0, "Internal error." 00117, 0, "Failing over." 00118, 0, "Initialization error." 00119, 0, "Internal initialization error." 00120, 0, "Replication daemon cannot attach to the ASM instance." 00121, 0, "System call error." 00122, 0, "Shutdown: A volume could not be accessed. It may have been offlined. " 00123, 0, "UNUSED" 00124, 0, "UNUSED" 00125, 0, "Could not synchronize replication. No storage left on device." 00126, 0, "Failed to synchronize replication primary and standby file sytems." 00127, 0, "UNUSED" 00128, 0, "UNUSED" 00129, 0, "The replication %s daemon is running with insufficient privileges." 00130, 0, "Write failed." 00131, 0, "Apply process is already stopped." 00132, 0, "UNUSED" 00134, 0, "Could not register apply process with CRS. No storage left on device." 00135, 0, "Could not unregister apply process with CRS. No storage left on device." 00136, 0, "ACFS driver returned: No storage left on device." 00137, 0, "Normal shutdown: Process terminated." 00138, 0, "Could not apply the security credentials to a file. No storage left on device." 00139, 0, "Could not update file modification times. No storage left on device." 00140, 0, "UNUSED" 00141, 0, "Apply daemon running with insufficient privileges." 00160, 0, "UNUSED" 00161, 0, "Initialization error." 00162, 0, "Internal error: Failed to get the replication configuration." 00163, 0, "Initialization error: Failed to set standby replication site configuration." 00164, 0, "Cannot set the replication configuration." 00165, 0, "Failed to retrieve the replication configuration." / Replication statuses 00166, 0, "Online" 00167, 0, "Initializing" 00168, 0, "Background Stopped" 00169, 0, "Paused" 00170, 0, "Unknown" / Messages used by multiple commands 00501, 0, "unable to allocate a buffer" // *Cause: A request for process virtual memory failed. // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 00502, 0, "Failed to communicate with the ACFS driver. Verify the ACFS driver has been loaded." // *Cause: The ACFS control device could not be accessed. // *Action: Verify the ACFS driver is loaded and running. 00503, 0, "invalid numeric value specified: %s" 00504, 0, "Invalid unit specified: %s. Valid units are K|M|G|T|P." 00505, 0, "invalid signature requested" 00506, 0, "UNUSED" 00507, 0, "Failed to seek to %s prior to writing the volume disk header." // *Cause: A seek to the volume failed. This message is accompanied by // other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00508, 0, "unable to obtain device major and minor number for volume %s" // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00509, 0, "unsupported file type for %s, not a block device" // *Cause: Volume provided was not recognized as a block device. This message // is accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00510, 0, "unable to obtain volume id for %s" // *Cause: Volume id was not obtained. This message is accompanied by // other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00511, 0, "%s is mounted on at least one node of the cluster." 00512, 0, "A file system check of %s is in progress." 00513, 0, "unable to obtain ACFS driver version number" 00514, 0, "unable to close handle" // *Cause: Handle could not be closed. This message is accompanied by // other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00515, 0, "version mismatch: \n %s %s version \n %s ACFS kernel version" 00516, 0, "stat of %s failed" // *Cause: Stat() failed. This message is accompanied by // other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00517, 0, "unable to obtain block device sector size" // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00518, 0, "unable to obtain volume size in sectors" // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00519, 0, "too many arguments: %s" 00520, 0, "%s is not an ADVM volume." 00521, 0, "Failed to determine file type of %s." // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00522, 0, "unable to get drive structure" // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00523, 0, "%s is unsupported drive type %d." 00524, 0, "unable to obtain partition information" // *Cause: Failed to obtain volume information. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00525, 0, "failed to seek to %s" // *Cause: Failed to seek to volume. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00526, 0, "read of volume disk header failed" // *Cause: Failed to read volume. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00527, 0, "unable to dismount volume" // *Cause: Could not dismount volume. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00528, 0, "Volume %s is already mounted on %s." 00529, 0, "This partition has not been formatted with ACFS." 00530, 0, "setting volume online again" 00531, 0, "write of volume disk header failed" // *Cause: Write to volume failed. This message is accompanied // by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00532, 0, "invalid option: %s" 00533, 0, "%s requires an argument" 00534, 0, "A valid numeric string is required." 00535, 0, "insufficient arguments" 00536, 0, "unknown extra argument: %s" 00537, 0, "not implemented yet" 00538, 0, "invalid command or command is not unique: %s" 00539, 0, "missing arguments" 00540, 0, "incorrect number of arguments" 00542, 0, "argument is not an integer" 00543, 0, "invalid command" 00544, 0, "option spelling is not unique: %s" 00545, 0, "%s does not support a value: %s=%s" 00546, 0, "failed to change on-disk signature" 00547, 0, "Both the primary and alternate superblocks are damaged." // *Cause: The file system metadata was found to be damaged. // *Action: Run fsck/acfschkdsk.exe as soon as possible to fix // the metadata inconsistency. 00548, 0, "Failed to communicate with the ACFS driver. Verify that cluster membership has been established." // *Cause: The ACFS driver's control device could not be accessed. // *Action: Verify the driver is loaded and running. Also, verify that // the ASM instance is accessible. 00549, 0, "mount path %s already contains a volume mount point for volume %s" // *Cause: The mount path contained a reparse point that references a // a different volume than the mount request. // *Action: Verify the path is correct. If it is, the existing volume // mount point must be removed before a new one can be created. // Use acfsdismount to remove the mount point. 00550, 0, "checksums for both superblocks are bad" 00551, 0, "unable to process input from the command line" 00552, 0, "End-of-file received instead of 'y' or 'n'" 00553, 0, "Did not find expected ACFS SuperBlock metadata on this volume. Verify that this is an ACFS volume. If you continue, an ACFS signature will be written to the ACFS SuperBlock location on this volume.\nDo you want to continue [y|n]? " 00554, 0, "Unable to obtain group name for gid: %ld" 00555, 0, "unsupported file type for %s, not a device file" // *Cause: Volume provided was not recognized as a device file. This message // is accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 00556, 0, "invalid vfs name %s" // *Cause: a helper command was called with an unexpected vfs name argument // *Action: Verify that ACFS helper commands are installed in the // '/sbin/helpers/acfs' directory and that '/etc/vfs' contains // the correct information for ACFS. If the solution is not clear, // contact Oracle Support Services. 00557, 0, " [%so] - %s options follow" 00558, 0, " [h] - Prints out this usage message" 00559, 0, " [v] - Verbose mode" 00560, 0, "Operation not applicable for FSType %s" 00561, 0, " [vv] - Very verbose mode" 00562, 0, "An attempt to create Oracle Registry ACFS key %s resulted in a registry error. %s" // *Cause: An error was returned by the Oracle Registry service when // attempting to create an ACFS key. This message is // accompanied by other message(s) that provide details // as to the exact cause of the failure. // *Action: Correct the problem indicated by the other message(s). If the cause // of the problem is unclear, contact Oracle Support Services. 00564, 0, "unable to delete Oracle Registry key %s while trying to recover from an error %s" // *Cause: Removal of a key from the Oracle Registry failed. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 00565, 0, "unable to delete Oracle Registry key %s %s" // *Cause: Removal of mount key from Oracle Registry failed. // *Action: Use acfsutil registry to verify the mount key exists in the // Oracle Registry. 00566, 0, "invalid handle received when attempting to close an ACFS mount key within Oracle Registry" // *Cause: An error was returned during the closing of a key in the Oracle // Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. // Report to Oracle Support Services. 00567, 0, "unknown Oracle Registry error encountered closing key" // *Cause: An error was returned while closing the key from the Oracle // Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. // Report to Oracle Support Services. 00568, 0, "closing of a key resulted in Oracle Registry error %d" // *Cause: An error was returned during the closing of a key in the Oracle // Registry. // *Action: Verify the Oracle Registry is accessible. If it is not accessible // and the cause is unclear, report this error to Oracle Support // Services. 00569, 0, "invalid handle received when attempting to delete an ACFS mount key within Oracle Registry" // *Cause: An error was returned while removing a key from the Oracle // Registry. // *Action: Report this error to Oracle Support Services. 00570, 0, "The ACFS mount key specified for deletion does not exist within Oracle Registry." // *Cause: The mount key could not be located in the Oracle Registry. // *Action: Use acfsutil registry to ensure the mount entry exists in // the Oracle Registry. 00571, 0, "The ACFS mount key specified for deletion is not empty." // *Cause: The mount key specified for deletion from the Oracle Registry // contained dependent subkeys. // *Action: View the mount entries in the Oracle Registry using \"acfsutil // registry\" and remove any dependent mount entries before retrying // this operation. 00572, 0, "permission denied to delete the ACFS mount entry from Oracle Registry" // *Cause: The user permissions were insufficient to remove the key from the // Oracle Registry. // *Action: Verify the Oracle Registry is accessible and that command is being // run from a properly authorized user ID. 00573, 0, "Oracle Registry error encountered while deleting an ACFS mount key" // *Cause: An error was returned while removing the key from the Oracle // Registry. // *Action: Report this error to Oracle Support Services. 00574, 0, "UNUSED" 00575, 0, "deletion request of key resulted in Oracle Registry error %d" // *Cause: An error was returned while removing a key from the Oracle // Registry. // *Action: Run ocrcheck to verify that Oracle Registry is working properly. // If problem persists, report to Oracle Support Services. 00584, 0, "failed to look up ACFS mount points in the Oracle Registry %s" // *Cause: An error was returned while looking up a mount point in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. // If problem persists, report to Oracle Support Services. 00585, 0, "null parameter received" // *Cause: A null parameter was passed to the Oracle Registry. // *Action: Run ocrcheck to verify that Oracle Registry is working properly. // If problem persists, report to Oracle Support Services. 00587, 0, "unknown Oracle Registry error encountered during operation on ACFS mount entry" // *Cause: An error was returned while accessing the key from the Oracle // Registry. // *Action: Run ocrcheck to verify that Oracle Registry is working properly. // If problem persists, report to Oracle Support Services. 00588, 0, "UNUSED" 00589, 0, "key operation resulted in Oracle Registry error %d" // *Cause: An error was returned during a key operation with the Oracle // Registry. // *Action: Run ocrcheck to verify that Oracle Registry is working properly. // If problem persists, report to Oracle Support Services. 00591, 0, "error found in volume disk header" 00592, 0, "Seek to volume failed. Verify the volume exists." // *Cause: Seek to a location on the volume failed. // *Action: Verify the volume exists on this node and that it is // accessible. 00593, 0, "The Oracle Registry returned the following error while attempting to access ACFS key %s %s" // *Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or // SYSTEM.ACFS.Mounts keys in Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working // properly. Examine the appended error message from the Oracle // Registry service. 00594, 0, "Failed to access ACFS mount information. The Oracle Registry returned the appended error for ACFS key %s. %s" // *Cause: Failed to access ACFS mount information from the Oracle Registry. // *Action: Examine the appended error message from the Oracle Registry. 00595, 0, "Failed to access ACFS mount value information. The Oracle Registry returned the appended error for ACFS key %s. %s" // *Cause: Failed to access ACFS mount value information from the Oracle // Registry. This might be due to Oracle Registry corruption or // a sudden loss of the Oracle Registry service. // *Action: Examine the appended error message from the Oracle Registry. // Run ocrcheck to verify the Oracle Registry is working properly. 00596, 0, "A failure occurred while accessing the Oracle Registry ACFS key \"SYSTEM\" for security purposes and follows this message: %s" // *Cause: Failed to retrieve key access rights for the Oracle Registry // ACFS key "SYSTEM" // *Action: Run ocrcheck to verify the Oracle Registry is working properly. // Evaluate the error message returned from the Oracle Registry // appended to this message. If necessary, run ocrdump and make // sure the "SYSTEM" key exists and is accessible. 00597, 0, "Failed to initialize the Oracle Registry's SCLS context. The SCLS error is included with this message." // *Cause: An operating system initialization failed. // *Action: Evaluate the attached SCLS error message. // Run ocrcheck to verify the Oracle Registry is functioning // correctly. 00598, 0, "An error occurred while looking up the current user's operating system account name. The error is included with this message." // *Cause: ACFS was attempting to add an entry to the Oracle Registry. // During this attempt a lookup of the current user's name failed // in the operating system failed. // *Action: Evaluate the attached error message to determine why the current // user name could not obtained from the operating system. 00599, 0, "The Oracle Registry returned the following error while attempting to close the ACFS key %s %s" // *Cause: Possibly due to Oracle Registry corruption or // a sudden loss of the Oracle Registry service. // *Action: Examine the appended error message from the Oracle Registry. // Run ocrcheck to verify the Oracle Registry is working properly. 00600, 0, "Failed to access ACFS mount subkey information. The Oracle Registry returned the appended error. %s" // *Cause: Failed to access ACFS mount information from the Oracle Registry. // *Action: Examine the appended error message from the Oracle Registry. 00601, 0, "Failed to initialize this utility's access to the Oracle Registry. Verify the registry service has started." // *Cause: Either the Oracle Registry service was unavailable or // the registry configuration was incomplete/inaccurate. // *Action: Run ocrcheck to verify the registry service is working properly. 00602, 0, "An internal error (BADARG) occurred while trying to determine the Oracle Registry configuration." // *Cause: An Oracle internal error. // *Action: Contact Oracle. 00603, 0, "Failed to retrieve the Oracle Cluster Registry, OCR, configuration" // *Cause: Failed to obtain OCR information. // *Action: Run ocrcheck to verify OCR is working properly. 00604, 0, "Failed to retrieve the Oracle Local Registry, OLR, configuration" // *Cause: Failed to obtain Oracle Local Registry information. // *Action: Run ocrcheck -local to verify the OLR is working properly. 00605, 0, "Failed to retrieve the Oracle Registry configuration for an unknown reason" // *Cause: Failed to obtain Oracle Registry information. // *Action: Run ocrcheck to verify the registry is working properly. 00606, 0, "Could not determine if the system is configured for RAC or Oracle Restart environment." // *Cause: The Oracle Registry service configuration could not be detected // *Action: Run ocrcheck to verify the Oracle registry service. 00607, 0, "Failed to access or create Oracle Registry keys required for ACFS operation" // *Cause: Oracle Registry keys required for operation either could not // be accessed or created. // *Action: Another error message number will follow this message. Analyze its // output. Run ocrcheck to verify the Oracle registry is functioning // properly. Also, verify acfsutil was invoked with administrative // rights when attempting to add the ACFS mount points. 00608, 0, "Invalid option combination: %s conflicts with another option." // 610-617 are for stdout info display 00610, 0, "Device : %s : Mount Point : %s : Options : %s : Nodes : %s : Disk Group : %s : Volume : %s" 00611, 0, "Mount Object:" 00612, 0, " Device: %s" 00613, 0, " Mount Point: %s" 00614, 0, " Disk Group: %s" 00615, 0, " Volume: %s" 00616, 0, " Options: %s" 00617, 0, " Nodes: %s" 00618, 0, "A circular list has been encountered." 00619, 0, "This is a %(1)s computer, but the file system was created on a %(2)s %(3)s computer." // *Cause: The file system was created on a computer which has a different // Endian than the current system. Little Endian machines (such as // the intel x86 based systems) store the Least Significant bit in the // first byte of an integer value. Big Endian machines (such as // Solaris SPARC and AIX Power based systems) store the Most // Significant bit in the first byte of an integer value. // *Action: Use a system with the same Endian as the system which created the // file system. 00620, 0, "This feature is not available for Oracle version %s or lower on this platform." // *Cause: Informational. // *Action: None. / / Messages for acfsformat/mkfs.acfs 01001, 0, "Size specified cannot exceed size of volume." // *Cause: Volume size was smaller than the requested size. // *Action: Select a size that is less than or equal to the volume size and // retry the ACFS format command. 01002, 0, "ACFS requires a minimum volume size of %dMB." // *Cause: Volume was too small. // *Action: Select a larger volume and retry. 01003, 0, "Failed to generate a unique file system ID." 01004, 0, "%s was not formatted." // *Cause: An error occurred during the formatting of the volume. // *Action: This message is accompanied by another error message. Respond as // indicated for that message." 01005, 0, "unable to allocate a buffer" // *Cause: A request for process virtual memory by the ACFS format command // failed. This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 01006, 0, "unable to open volume %s" // *Cause: Volume could not be opened. This message is accompanied by other // message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If the cause // of the problem is unclear, contact Oracle Support Services. 01007, 0, "unable to close volume handle" 01008, 0, "unable to open file system %s" // *Cause: File system was not accessible. // *Action: Verify the volume associated with the file system is enabled // and online before retrying. 01009, 0, "unable to close file system handle" 01010, 0, "Volume already contains an ACFS file system. To reformat the volume, reissue %s with the %sf option." // *Cause: The on-disk metadata indicated that an ACFS file system is // located on the volume. // *Action: Verify the intended volume and reissue the format command with // the force flag to overwrite the existing ACFS file system. 01011, 0, "Volume contains an ACFS file system that is being checked. To reformat the volume, reissue %s with the %sf option." // *Cause: The volume contained a file system that was in the process of // being checked by the ACFS checker (fsck on *nix, acfschkdsk.exe // on Windows). // *Action: Verify the intended volume and reissue the format command with // the force flag to overwrite the existing ACFS file system. 01012, 0, "version = %s" 01013, 0, "Version %s" 01014, 0, "write of volume label failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 01015, 0, "Failed to clear the contents of the volume." 01016, 0, "%dK is an invalid block size. Specify a number between 4K and 1024K." 01017, 0, "Length of file system name cannot exceed %u." 01018, 0, "failed to allocate a buffer for %u bytes" // *Cause: A request for process virtual memory by the ACFS format command // failed. This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 01019, 0, "This volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on all nodes." // *Cause: The volume was in use by another file system. // *Action: Dismount the ACFS file system with acfsdismount and retry the // command. 01020, 0, "This volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'." // *Cause: The volume was in use by another non-ACFS file system. // *Action: Dismount the non-ACFS file system with 'advmutil dismount' and // retry the command. 01021, 0, "Length of volume name cannot exceed %u." 01022, 0, "failed to bring ADVM volume %s online" 01023, 0, "P flag not implemented" 01024, 0, "A valid ACFS profile must be provided." 01025, 0, "Failed to generate a file system id." 01026, 0, "UNUSED" 01027, 0, "UNUSED" 01028, 0, "UNUSED" 01029, 0, "UNUSED" 01030, 0, "UNUSED" 01031, 0, "UNUSED" 01032, 0, "UNUSED" 01033, 0, "write to volume failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01034, 0, "UNUSED" 01035, 0, "UNUSED" 01036, 0, "UNUSED" 01037, 0, "UNUSED" 01038, 0, "write failed during setup of root directory entry" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01039, 0, "UNUSED" 01040, 0, "UNUSED" 01041, 0, "write of snaps directory entry failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01042, 0, "UNUSED" 01043, 0, "write of lost+found directory entry failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01044, 0, "write of file entry table failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01045, 0, "write of global bitmap failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01046, 0, "read of global bitmap file entry failed" // *Cause: A read of the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01047, 0, "write of global bitmap file entry failed" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01048, 0, "UNUSED" 01049, 0, "seek to snap map header failure" // *Cause: A seek to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01050, 0, "write to snap map header failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01051, 0, "partial write to snap map header failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01052, 0, "write to snap map info entry failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01053, 0, "partial write to snap map info entry failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01054, 0, "write to snap map storage entry failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01055, 0, "partial write to snap map storage entry failure" // *Cause: A write to the volume during file system creation failed. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 01056, 0, "Usage: [%sh] [%sv] [%sf] [%sb blksz] [%sn name]%s [size]" 01057, 0, " [%sh] - Prints out this usage message" 01058, 0, " [%sv] - Verbose mode" 01059, 0, " [%sf] - Force file system format, use to overwrite an existing file system" 01061, 0, " [%sb blksz] - Block size used by new file system" 01062, 0, " [%sn name] - Name of file system to be created" 01063, 0, " - ACFS primary volume pathname" 01064, 0, " [size] - Desired size of the file system in bytes or in units of K|M|G|T|P" 01065, 0, "Create an ACFS file system." 01066, 0, "on-disk version = %u.%u" 01067, 0, "volume = %s" 01068, 0, "volume space used = %d" 01069, 0, "bytes per sector = %d" 01070, 0, "volume label = %s" 01071, 0, "file system ID = %u" 01072, 0, "writing volume label" 01073, 0, "initializing FETA" 01074, 0, "initializing root dirnode" 01075, 0, "initializing .ACFS dirnode" 01076, 0, "initializing lost+found directory" 01077, 0, "initializing Snap Map" 01078, 0, "initializing Global Bitmap" 01079, 0, "writing volume header" 01080, 0, "Format complete." 01081, 0, "block size = %dK" 01082, 0, "block size = %dM" 01083, 0, "VolSignature = %s" 01084, 0, "VolMountPoint = %s" 01085, 0, "VolMountPointLength = %d" 01086, 0, "VolSerialNumber = %u" 01087, 0, "VolLength = %u" 01088, 0, "VolClusterSize = %u" 01089, 0, "VolFETAOffset = %u" 01090, 0, "VolExtentHeaderSize = %u" 01091, 0, "VolEAContainerUnitBlkSize = %u" 01092, 0, "VolExclusiveMount = %d" 01093, 0, "volume size = %u" 01094, 0, "%s is not an ADVM volume" 01095, 0, "unable to determine current directory" 01096, 0, "Length of volume path cannot exceed %d." 01097, 0, "Usage: -V acfs [%sv name] [%ss size] [%so [h],[v],[f],[b=blksz]%s] " 01098, 0, " [%sv name] - Name of file system to be created" 01099, 0, " [%ss size] - Desired size of the file system in 512-byte units or in units of K|M|G|T|P" 01103, 0, " [f] - Force file system format, use to overwrite an existing file system" 01104, 0, " [b=blksz] - Block size used by new file system" 01110, 0, "Usage: [%so [h],[v],[f],[b=blksz]%s,[n=name]] [size]" 01111, 0, " [n=name] - Name of file system to be created" 01150, 0, "unable to synchronize in-memory file data to disk" // *Cause: A request to flush all in-memory copies of buffers associated // with the open handle failed. This message is accompanied by other // message(s) providing details on the error. // *Action: Correct the problem identified by the other message(s). If the // problem has been resolved and the file system is unusable, // retry the ACFS format command. 01151, 0, "Ignoring invalid block size %(1)d, using %(2)d" // *Cause: An ACFS format command unsupported block size was specified. // *Action: No action required. A supported block size will be used. / / Messages for mount.acfs/acfsmountvol 02001, 0, "unable to allocate a buffer" // *Cause: A request for process virtual memory by mount command failed. // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 02002, 0, "Version %s" 02003, 0, "Volume %s is mounted on %s." 02004, 0, "volume: %s, mount point: %s" 02006, 0, "unable to terminate the Oracle Registry connection" // *Cause: Either the Oracle Registry service was unavailable or // the Oracle Registry configuration was incomplete/inaccurate. // *Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry // are working properly. If they are not accessible and the cause is // unclear, report this error to Oracle Support Services. 02009, 0, "total mounts: %d" 02010, 0, "attempting to mount: %s on %s" 02011, 0, "mount %s depends on %s, not mounting." 02012, 0, "Mount of %s failed, volume %s does not exist. Verify that %s exists on this node." // *Cause: Could not mount the file system retrieved from the Oracle Registry. // *Action: Verify the volume exists on this node and that it is // accessible. 02013, 0, "Successfully mounted %s." 02014, 0, "Mount of %s failed. Error %d was returned." // *Cause: Mount operation failed. // *Action: Verify the mount point and volume both exist and are accessible // before retrying the mount command. 02015, 0, "Failed to open mount point %s. Verify the mount point exists." // *Cause: Mount point could not be opened. // *Action: Verify the mount point exists and is accessible before // retrying the mount command. 02016, 0, "Mount point, %s, is in use by another file system." 02017, 0, "Failed to open volume %s. Verify the volume exists." // *Cause: The volume could not be opened. // *Action: Verify the ASM instance is operational and the volume is // enabled and accessible before retrying the mount command. 02018, 0, "Volume %s contains an ACFS file system that is being checked. Allow the file system check to complete." // *Cause: The volume contained a file system that was in the process of // being checked by the ACFS checker. // *Action: Allow the ACFS checker to complete before retrying the mount. // If the ACFS checker is not running on this file system and a // file system check was previously interrupted, reissue the // ACFS checker. 02019, 0, "options: %s" 02020, 0, "options length exceeded %d" 02021, 0, "Mount path paired with volume %s exceeded %d characters." 02022, 0, "no options" 02023, 0, "no update /etc/mtab entry option specified" 02024, 0, "verbose option specified" 02025, 0, "command string: %s." 02026, 0, "unable to verify the host names passed in are part of the cluster" // *Cause: Either CSS was unavailable or the CSS configuration // was incomplete/inaccurate. // *Action: Run crs_stat to verify CSS is working properly. 02027, 0, "unable to obtain the local CSS node name" // *Cause: Either CSS was unavailable or the CSS configuration // was incomplete/inaccurate. // *Action: Run crs_stat to verify CSS is working properly. 02028, 0, "unable to retrieve the list of volumes associated with %s" 02029, 0, "Silently ignoring requested duplicate mount of %s on %s." 02030, 0, "Usage: [%so] [%sh] [%sv] [%sn] " 02031, 0, " [%so] - Standard mount options" 02032, 0, " [%sh] - Prints out this usage message" 02033, 0, " [%sv] - Verbose mode" 02034, 0, " [%sn] - Do not update /etc/mtab" 02035, 0, " - Volume to mount" 02036, 0, " - Root of file system on volume" 02037, 0, "File system not created on a %s system. Cannot mount." 02038, 0, "File system created on an incompatible system (endian). Cannot mount." / Messages for acfsmountvol 02039, 0, "Length of path cannot exceed %d." 02040, 0, "Path must be a valid directory or drive letter." 02041, 0, "Length of volume name cannot exceed %d." 02042, 0, "volume: %s" 02043, 0, "volume %s in use by a non-ACFS file system" 02044, 0, "%s does not contain a valid ACFS file system. Verify volumes contents using acfschkdsk.exe." 02045, 0, "%s is in use by another non-ADVM volume" 02046, 0, "Volume %s cannot be mounted. Examine the system event log for possible causes." // *Cause: The volume mount failed. This could be caused by an out of // space condition if this is the first mount of a file system // on a node. // *Action: Examine the system event log for more detail. 02048, 0, "unable to retrieve full path name for path %s" 02049, 0, "conversion of reparse data Unicode string to ANSI string failed" 02050, 0, "unable to set in-memory mount information" // *Cause: Could not communicate with the mounted file system. // *Action: Verify the ASM instance is operational and the volume // is enabled and accessible before retrying. 02051, 0, "failed to create symbolic link with path %s" 02052, 0, "broadcast of new symbolic link %s failed" 02053, 0, "failed to create mount point on directory %s" 02054, 0, "unable to retrieve a list of active ACFS file systems" 02055, 0, "Usage: %s [/v] [/all]" 02056, 0, " %s [/v] " 02057, 0, " %s [/h] " 02058, 0, " %s - List of mounted file systems" 02059, 0, " [/h] - Print out this usage message" 02060, 0, " [/v] - Verbose mode" 02061, 0, " [/all] - Mount all the file systems in ACFS registry" 02062, 0, " - Drive letter or mount point" 02063, 0, " - ACFS primary volume pathname" 02064, 0, "Example: %s /v E:\mnt\ asm_vol1-22" 02065, 0, "Example: %s /v E: E:" 02066, 0, "Version: %s" 02080, 0, "version mismatch: \n volume %s version is %d \n ACFS kernel version is %d" 02081, 0, "Warning: acfschkdsk.exe should be run on volume %s at your earliest convenience" // *Cause: A flag in the superblock indicates that a metadata inconsistency // has been found on this volume. // *Action: Run acfschkdsk.exe as soon as possible to fix // the metadata inconsistency. 02082, 0, "unable to verify if the host names provided are part of the cluster" // *Cause: Could not obtain information about the cluster. // *Action: Run crs_stat to verify health of CSS. 02083, 0, "cannot get the local CSS node name" // *Cause: Could not obtain local CSS node name. // *Action: Run crs_stat to verify health of CSS. 02084, 0, "verifying volume state" 02085, 0, "creating drive letter" 02086, 0, "creating mount point" 02087, 0, "unable to lock volume" 02088, 0, "failed to unlock the volume" 02089, 0, "Info: failed to change the volume signature, but continuing with dismount anyway. No action required" 02090, 0, "unable to access ACFS mount information from the Oracle Registry" // *Cause: Failed to access mount information in the Oracle Registry. // *Action: Analyze the error messages that follow this message. 02091, 0, "Mount an ACFS file system." 02092, 0, "Mount of %s failed, node %s is not a member of the CSS cluster." // *Cause: Could not mount the file system retrieved from the Oracle Registry. // *Action: Verify the node listed in the entry is a member of the CSS cluster. 02093, 0, " [%so] all - Mount all the file systems in ACFS registry" / Note to translators: Please do not translate 'set uid to root' in msg 2094 02094, 0, " [%so] norootsuid [,...] - Do not allow the execution of set uid to root executables" 02095, 0, " [%so] rootsuid [,...] - Allow the execution of set uid to root executables" 02096, 0, " [%so] nodevices [,...] - Do not interpret character or block special devices" 02097, 0, " [%so] devices [,...] - Interpret character or block special devices" 02098, 0, "Usage: [%sr] [%so] " 02099, 0, " [%so] h [,...] - Prints out this usage message" 02100, 0, " [%so] v [,...] - Verbose mode" 02101, 0, " [%so] all - Mount all the file systems in ACFS registry" 02102, 0, " [%so] norootsuid [,...] - Do not allow the execution of set uid to root executables" 02103, 0, " [%so] rootsuid [,...] - Allow the execution of set uid to root executables" 02104, 0, " [%so] nodev [,...] - Specifies that you cannot open devices from this mount" 02105, 0, " [%so] nosuid [,...] - Specifies that the execution of setuid and setgid programs by way of this mount is not allowed." 02106, 0, " [%so] rw [,...] - Mount in read/write mode" 02107, 0, " [%so] ro [,...] - Mount in read-only mode" 02108, 0, " - Volume to mount" 02109, 0, " - Root of file system on volume" 02110, 0, "Unable to mount %s on %s." 02111, 0, " [%so] - Standard mount options" 02112, 0, " [%sr] - Mount in read-only mode" 02113, 0, "Usage: [%so] " 02114, 0, " [%so] setuid|nosetuid [,...] - Allow or disallow setuid or setgid execution" 02115, 0, " [%so] devices|nodevices [,...]- Allow or disallow opening any character or block special devices" 02116, 0, " [%so] suid|nosuid [,...]- Allow or disallow setuid or setgid execution and opening any character or block special devices" 02117, 0, " [%so] rootsuid|norootsuid [,...]- Allow or disallow the execution of setuid to root executables" 02118, 0, " [%so] exec|noexec [,...]- Allow or disallow executing programs in the file system" 02119, 0, "creating administrative network share for mount point %s at share name '%s'" // *Cause: Informational // *Action: None 02120, 0, "administrative network share for mount point %s already exists at share name '%s'" // *Cause: Informational // *Action: None 02121, 0, "administrative network share '%s' already exists, but does not share mount point %s" // *Cause: Attempted to create an administrative network share for the // specified ACFS mount point, but the required share name was // already in use. // *Action: Remove the conflicting network share using 'net share // /delete'. Remount the ACFS file system to retry creating an // administrative network share for the mount point. 02122, 0, "retrieving information for administrative network share '%s' failed" // *Cause: While creating an administrative network share for the specified // ACFS mount point, failed to retrieve information on any network // share that might already exist at the required share name. This // message is accompanied by other messages providing details on the // error. // *Action: Correct the error indicated by the accompanying messages. // Remount the ACFS file system to retry creating an administrative // network share for the mount point. 02123, 0, "creating administrative network share for mount point %s at share name '%s' failed" // *Cause: Failed to create an administrative network share for the // specified ACFS mount point. This message is accompanied by other // messages providing details on the error. // *Action: Correct the error indicated by the accompanying messages. // Remount the ACFS file system to retry creating an administrative // network share for the mount point. 02124, 0, "could not create administrative network share for mount point %s at share name '%s'" // *Cause: Failed to create an administrative network share for the // specified ACFS mount point. This message is accompanied by other // messages providing details on the error. // *Action: Correct the error indicated by the accompanying messages. 02125, 0, "volume '%s' is already in use" // *Cause: The volume was in use by another file system. // *Action: Verify the volume specified. / / Messages for acfsutil 03001, 0, "Failed to open %s. Verify that %s exists." // *Cause: The mount point or file could not be opened. // *Action: Verify the mount point or file is accessible before retrying. 03002, 0, "unable to obtain file system information for %s" 03003, 0, "Cannot decrease the volume by this amount." // *Cause: Requested size exceeded the size of the file system. // *Action: Select a size that is smaller than the size of the file system and // retry. 03004, 0, "Cannot reduce volume size below 200 MB." // *Cause: Requested size was below the minimum volume size of 200MB." // *Action: Select a volume that is 200MB or larger." 03005, 0, "unable to resize %s" 03006, 0, "smallest size, without loss of data, is: %u (%uMB)" 03007, 0, "insufficient storage - largest size is: %u (%uMB)" 03008, 0, "The volume could not be resized. The volume expansion limit has been reached." // *Cause: The file system's internal storage bitmap has a five extent limit. // Growing the file system may fail if it has already been grown four // or more times, using up all available storage bitmap extents. // *Action: If the file system has been grown four or more times, running the // ACFS Fixer may allow future volume expansions. 03009, 0, "The volume could not be resized at this time. Try again later." 03010, 0, "new file system size: %u (%uMB)" 03011, 0, "The volume size did not change because space is always rounded to multiples of the ASM resize increment." 03012, 0, "Length of volume name cannot exceed %d." 03013, 0, "unable to open %s" // *Cause: Volume could not be opened to remove the file system. // *Action: Verify the volume is not mounted on any node in the cluster // before retrying. 03014, 0, "file system not removed" 03015, 0, "invalid IP address: %s" 03016, 0, "invalid node number" 03017, 0, "Number of nodes cannot exceed %d." 03018, 0, "missing node configuration" 03019, 0, "node is not accessible" 03020, 0, "node number for this node (%d) exceeded number of cluster members" 03021, 0, "comm setup call failed" 03022, 0, "membership call failed" 03023, 0, "socket call failed" 03024, 0, "error path ioctl failed" 03025, 0, "ioctl call to panic the system failed" 03026, 0, "ioctl call to set recovery breakpoints failed" 03027, 0, "Invalid product name. Valid product names are OKS, OFS, and AVD." 03028, 0, "Product name not specified. Valid product names are OKS, OFS, and AVD." 03029, 0, "product name requires a debug level or context" 03030, 0, "unable to get log buffer size" 03031, 0, "unable to set debug context or level" 03032, 0, "unable to retrieve log" 03033, 0, "unable to open %s" // *Cause: The log file specified could not be created and/or opened. // *Action: If a file exists by the same name as the log file specified, // verify that this is a file that can be overwritten. 03034, 0, "write of log file failed" 03035, 0, "unable to retrieve mount entries" 03036, 0, "no mounted ACFS file systems" 03037, 0, "not an ACFS file system" 03038, 0, "unable to retrieve list of volumes associated with %s" 03039, 0, "ioctl call to unregister the ACFS driver failed" 03040, 0, "Volumes are still mounted. All ACFS file systems must be dismounted before the ACFS driver can be unregistered." 03041, 0, "unable to unregister ACFS driver" /Obsolete: 03042 is superceded by message 03203. 03042, 0, "Invalid snap command. Valid commands are 'acfsutil snap create' and 'acfsutil snap delete'." 03043, 0, "name of snapshot cannot exceed %d bytes" 03044, 0, "Failed to open mount point %s. Verify the mount point exists." // *Cause: Mount point could not be opened for snapshot operation. // *Action: Verify the mount point exists and is accessible before // retrying the snap command. 03045, 0, "%s is not a mount point" 03046, 0, "unable to perform snapshot operation on %s" 03047, 0, "waiting for another snapshot operation to complete" 03048, 0, "Snapshot operation could not complete." 03049, 0, "There are too many snapshots for the file system associated with %s. Reduce the number of snapshots before proceeding." 03050, 0, "Cannot create snapshot %s. It already exists." 03051, 0, "Snapshot %s does not exist." 03052, 0, "unable to delete snapshot %s due to open files" // *Cause: There are files open in the snapshot. // *Action: Use lsof or similar tool to find the processes with open files. // No files can be open in the snapshot for the snapshot delete // operation to succeed. 03053, 0, "Delete of snapshot %s succeeded but some disk storage could not be freed. When convenient, run fsck/acfschkdsk to free the storage." 03054, 0, "snapshot %s is not a valid snapshot name" 03055, 0, "Snapshot operation failed due to an error on another node. Check error logs on other nodes for more details." 03056, 0, "Snapshot operation is complete." 03057, 0, " ACFS Version: %u.%u.%u.%u.%u.%u" 03058, 0, " flags: %s" 03059, 0, " primary volume: %s" 03060, 0, " mount time: %s" 03061, 0, " volumes: %u" 03062, 0, " total size: %u" 03063, 0, " total free: %u" 03064, 0, " label: %s" 03065, 0, " flags: %s" 03066, 0, " on-disk version: %u.%u" 03067, 0, " allocation unit: %u" 03068, 0, " major, minor: %u, %u" 03069, 0, " size: %u" 03070, 0, " free: %u" 03071, 0, " ADVM diskgroup %s" 03072, 0, " ADVM resize increment: %u" 03073, 0, " ADVM redundancy: %s" 03074, 0, " ADVM stripe columns: %u" 03075, 0, " ADVM stripe width: %u" 03076, 0, " inode: %u" 03077, 0, " owner: %u" 03078, 0, " group: %u" 03079, 0, " size: %u" 03080, 0, " allocated: %u" 03081, 0, " hardlinks: %u" 03082, 0, " device index: %u" 03083, 0, " major, minor: %u,%u" 03084, 0, " access time: %s" 03085, 0, " modify time: %s" 03086, 0, " change time: %s" 03087, 0, " extents:" 03088, 0, "%u.%u.%u.%u.%u" 03089, 0, "permission denied" 03090, 0, "%s is an invalid %s number" 03091, 0, "Failed to open %s. This may mean the %s driver is not loaded/running" // *Cause: The driver's control device could not be accessed. // *Action: Verify the driver is loaded and running. 03092, 0, "error reading driver tunables" 03093, 0, "no %s tunables for this platform" 03094, 0, "internal inconsistency %d %d" 03095, 0, "tunable parameter %s not found" 03096, 0, "error opening configuration file %s" // *Cause: The configuration file cannot be created and/or opened. // *Action: If the configuration file exists, verify the file can // be opened. 03097, 0, "error accessing configuration file %s" // *Cause: Seek to the end of the configuration file failed. // *Action: If the configuration file exists, verify the file is // accessible. 03098, 0, "error writing to configuration file %s" 03099, 0, "error updating driver tunables" 03100, 0, " %*.*soffset ----length | -dev --------offset" 03101, 0, " %*u %10u | %4d %14u" 03102, 0, " %*u %10u | " 03103, 0, " %*u %10u | %4d %14u " 03104, 0, " extent count: %d" 03105, 0, "socket call returned %d" 03106, 0, "Invalid combination of arguments. %sa was previously specified to add an ACFS mount point to Oracle Registry." // *Cause: Invalid option combination. // *Action: Retry the command with one set of operations. 03107, 0, "Invalid combination of arguments. %sd was previously specified to remove an ACFS mount point from the Oracle Registry." // *Cause: Invalid option combination. // *Action: Retry the command with one set of operations. 03108, 0, "Neither %s nor %s is an ADVM volume." // *Cause: Volume specified was not an ADVM volume. // *Action: Retry the command with an ADVM volume. 03110, 0, "unable to access the Oracle Registry %s" // *Cause: Either the Oracle Registry service was unavailable or // the registry configuration was incomplete/inaccurate. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. // Analyze the appended Oracle Registry service error message. 03111, 0, "unable to add ACFS mount %s within Oracle Registry" 03112, 0, "unable to remove mount point %s from Oracle Registry" 03113, 0, "successfully removed ACFS mount point %s from Oracle Registry" 03114, 0, "unable to allocate a buffer" // *Cause: A request for process virtual memory by acfsutil registry failed // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 03115, 0, "an error occurred while attempting to disconnect from Oracle Registry" // *Cause: Either the Oracle Registry service was unavailable or // the Oracle Registry configuration was incomplete/inaccurate. // *Action: Run ocrcheck to verify the Oracle Registry service is // working properly. If the cause of the problem is unclear, // contact Oracle Support Services. 03116, 0, "mount point %s successfully added to Oracle Registry" 03117, 0, "unable to verify if the hostnames provided are part of the cluster" // *Cause: Could not obtain information about the cluster. // *Action: Run crs_stat to verify health of CSS. 03118, 0, "cannot obtain the node number of host %s via CSS or the Oracle Registry" // *Cause: Could not determine the node number for the specified host. // *Action: Verify that the specified host is a member of this cluster. 03119, 0, "UNUSED" 03120, 0, "UNUSED" 03121, 0, "UNUSED" 03122, 0, "failed to create Oracle Registry ACFS key %s %s" // *Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or SYSTEM.ACFS.Mounts // in the Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry service is // working properly. // Verify acfsutil is executed with operating system administrator // privileges. 03123, 0, "failed to create Oracle Registry ACFS key %s because it already exists" // *Cause: The Oracle Registry ACFS key already exists. // *Action: Run ocrcheck to verify the Oracle Registry service is // working properly. 03124, 0, "failed to create Oracle Registry ACFS subkey because it already exists" // *Cause: The Oracle Registry mounts subkey already exists. // *Action: Run ocrcheck to verify the Oracle Registry service is // working properly. If the ACFS mount entry is in an inconsistent // state delete it, then re-add it using acfsutil with the registry // option. If the problem persists, contact Oracle Support Services. 03125, 0, "error retrieving the volume using Oracle Registry key: %s" // *Cause: Could not retrieve volume information from mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03126, 0, "error retrieving the mount point using Oracle Registry key: %s" // *Cause: Could not retrieve mount point information from mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03127, 0, "error retrieving the mount options using Oracle Registry key: %s" // *Cause: Could not retrieve mount options from mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03128, 0, "error retrieving the version using Oracle Registry key: %s" // *Cause: Could not retrieve the version for mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03129, 0, "error retrieving the nodes list using Oracle Registry key: %s " // *Cause: Could not retrieve the nodes list for mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03131, 0, "volume %s already exists in the Oracle Registry as:" 03132, 0, "mount point %s already exists in the Oracle Registry as:" 03133, 0, "The Oracle Registry returned the following error while attempting to access the security attributes of key %s: \n %s" // *Cause: Could not access the security information of Oracle Registry. // This message is accompanied by other message(s) from the // Registry providing details on the error. // *Action: Correct the problem identified by the other message(s). If the // cause is unclear, contact Oracle Support Services. 03134, 0, "An error occurred while accessing Oracle Registry for a delete mount point operation. %s" // *Cause: Could not retrieve data from the Oracle Registry. This message is // accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If the cause // of the problem is unclear, contact Oracle Support Services. 03135, 0, "unable to locate mount point %s in Oracle Registry" // *Cause: Failed to locate mount point in the Oracle Registry. // *Action: Verify the mount point exists in the Oracle Registry // using the acfsutil registry command. 03136, 0, "unable to locate volume %s in Oracle Registry." // *Cause: Failed to locate volume in the Oracle Registry. // *Action: Verify the volume exists in the Oracle Registry // using the acfsutil registry command. 03137, 0, "Multiple entries exist for the mount point %s. Rerun the command with the volume name." // *Cause: Could not locate unique entry for mount point in the Oracle // Registry. // *Action: Retry acfsutil registry with volume name. 03138, 0, "failed to create and set Oracle Registry ACFS mount info key %s" // *Cause: Could not create and set a mount info key in the Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03139, 0, "error retrieving the disk group name using Oracle Registry key: %s" // *Cause: Could not retrieve the disk group name from the mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 03140, 0, "error retrieving the volume name using Oracle Registry key: %s" // *Cause: Could not retrieve the volume name from the mount entry in the // Oracle Registry. // *Action: Run ocrcheck to verify the Oracle Registry is working properly. 003141, 0, "unable to open device %s" // *Cause: The device could not be opened. // *Action: Check the diskgroup is mounted and the specified volume is enabled. 03142, 0, "Failed to retrieve the diskgroup and volume name for device %s. See the attached error." // *Cause: Possible internal error. // *Action: Check the attached error. If not serviceable, contact Oracle. 03143, 0, "The specified mount point does not exist and therefore cannot be deleted." // *Cause: The Oracle Registry has not been configured for ACFS or the // specified mount point does not exist. // *Action: Run "acfsutil registry" to list out the available ACFS mount points. 03144, 0, "successfully removed ACFS volume %s from Oracle Registry" 03145, 0, "unable to remove ACFS volume %s from Oracle Registry" // *Cause: Could not remove volume from Oracle Registry. // *Action: Verify the volume exists in the Oracle Registry // using the acfsutil registry command. 03146, 0, "Warning: The ACFS mount point group ownership cannot be re-initialized in the Oracle Registry. The registry is initialized from the ACFS control device on first use, and may have changed ownership since then. Current Key Ownership: %s" // *Cause: An attempt was made to re-initialize the ACFS mount point group // ownership in the Oracle Registry. This may be because the ACFS // control device /dev/ofsctl or /dev/acfsctl has changed owners. // *Action: Re-initializing the ACFS mount point group ownership in the Oracle // Registry is not supported. 03147, 0, "invalid ACFS file identifier provided" // *Cause: The ACFS file identifier provided by the user had an illegal // value. // *Action: Re-enter a number other than 0 or -1. 03148, 0, "ioctl call to obtain pathname associated with file id %u failed" // *Cause: An internal ioctl operation to map from an ACFS file identifier to // a pathname failed. This message is accompanied by other message(s) // providing details on the error. // *Action: Correct the problem indicated by the other message(s). If the cause // of the problem is unclear, contact Oracle Support Services. 03149, 0, "constructed pathname is too large" // *Cause: The length of the pathname being constructed has exceeded the // system limit of %d characters. This may be due to changes in the // file system namespace while the command is running. // *Action: Try the command again. If the problem persists, contact // Oracle Support Services. 03150, 0, "the pathname is: %s" 03151, 0, "The ACFS file identifier provided is not associated with a user file or directory." // *Cause: The ACFS file identifier, although valid, was not for a user file // or directory. // *Action: None. There is no pathname associated with this ACFS file // identifier. 03152, 0, "The ACFS file identifier provided is invalid for the mountpoint specified." // *Cause: The ACFS file identifier was not a valid identifier for the // mountpoint specified. // *Action: Verify that the correct ACFS file identifier and mountpoint were // specified. 03153, 0, "The file system name space has changed and a pathname cannot be obtained." // *Cause: The ACFS file identifier was valid, but could not be used to obtain // a full file pathname. // *Action: Verify that the correct ACFS file identifier and mountpoint were // specified. 03154, 0, "Failed to determine the full pathname. Too many directory levels." // *Cause: acfsutil has received information from the operating system that it // could not process fully. // *Action: Report this error to Oracle Support Services. 03157, 0, "unsupported file type for %s, not a mount point" // *Cause: An invalid entry was passed on the command line. // *Action: The acfsutil info acfs command requires that the input be a mount // point. 03158, 0, "unsupported file type for %s, not a mount point or a file" // *Cause: An invalid entry was passed on the command line. // *Action: The acfsutil size command requires that the input be a mount point // or a file. 03159, 0, " snapshot space usage: %u" 03160, 0, " number of snapshots: %u" // 03161, 0, "Device : %s : Mount Point : %s already exists in the Oracle Registry" // *Cause: This entry has already been added to the Oracle Registry. // *Action: None. 03162, 0, "Warning: The file system was resized, but an error occurred while resizing the ADVM volume. File system size now %u MB, volume size %u MB." // *Cause: An error occurred during ADVM volume resize. // *Action: Reissue the resize command. 03163, 0, "%s" 03164, 0, " ACFS Version: %s" 03165, 0, "Unable to add the file system on device %s to the ACFS registry. It is currently managed by CRS." // *Cause: The file system is currently managed by CRS and a file system cannot be managed by both CRS and the ACFS registry. // *Action: Remove the file system resource from CRS or continue to use CRS to manage the file system. 03166, 0, "Unable to add a STOP_DEPENDENCY to the ACFS registry for device %s." // *Cause: The ACFS registry resource could not be updated. // *Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p') 03167, 0, "Unable to remove the STOP_DEPENDENCY for device %s from the ACFS registry." // *Cause: The ACFS registry resource could not be updated. // *Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p') 03168, 0, "Internal error: %s %d" // *Cause: An Oracle internal error. // *Action: Contact Oracle Support Services. 03169, 0, "Unable to set log file size." // *Cause: The ACFS driver was unable to set the log file size. // *Action: Check the log file to see the reason of failure. 03170, 0, "Minimum log file size is %d." // *Cause: The ACFS driver was unable to set the log file size. // *Action: Log file size has to be bigger than or equal to the minimum size. 03171, 0, "Insufficient contiguous free ASM Diskgroup space. Check the ASM alert log." // *Cause: ADVM could not resize the volume because ASM did not have enough // contiguous free diskgroup storage. // *Action: Increase the free space in the diskgroup. Check the ASM alert log. 03172, 0, "ADVM is busy with Mirror recovery. Try again later." // *Cause: ADVM could not resize the volume because it is recovering the // mirrored volumes. // *Action: Try again later. The system console log will contain mirror // recovery started and completed messages. For example: // [Oracle ADVM] Mirror recovery for volume asm/volume-name started. // [Oracle ADVM] Mirror recovery for volume asm/volume-name completed. 03173, 0, "ADVM or ASM is unable to resize the volume. Check the ASM alert log." // *Cause: ADVM or ASM is unable to resize the volume. // *Action: Check the ASM alert log. 03174, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 11.2.0.3.0." // *Cause: The ADVM compatibility attribute for the disk group was not set to // version 11.2.0.3.0 or higher to allow the creation of a read/write // snapshot. // *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL // statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute. 03175, 0, " %u (delete pending)" 03176, 0, " number of snapshots: %u (active)" 03177, 0, "maximum log file size cannot exceed %d MB" // *Cause: The ACFS driver was unable to set the log file size. // *Action: Retry the command with a log file size that is smaller than the // maximum size. 03178, 0, "unable to delete snapshot %s while cluster is in rolling migration" // *Cause: The cluster was in rolling migration. Snapshot deletions are not // allowed during rolling migration. // *Action: Complete the rolling migration and then delete the snapshot. 03200, 0, "snapshot name: %s" 03201, 0, "RO snapshot or RW snapshot: %s" 03202, 0, "snapshot creation time: %s\n" 03203, 0, "Invalid snap command." // *Cause: An invalid entry was passed on the command line. // *Action: Use a valid 'acfsutil snap' command combination. Valid commands are // 'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info' 03300, 0, "unable to set tag name on file %s" // *Cause: The ACFS driver was unable to complete the request. // *Action: Verify memory or storage resources are sufficient. 03301, 0, "unable to unset tag name on file %s" // *Cause: The ACFS driver was unable to complete the request. // *Action: Verify memory or storage resources are sufficient. 03302, 0, "tag name syntax invalid or length too long" // *Cause: Tag name contains invalid characters or has too many characters. // *Action: Change tag name to use valid characters or shorten the tag name. 03303, 0, "invalid combination of arguments" // *Cause: The acfsutil tag info -t or -r arguments work only on // file pathnames. // *Action: Remove the -t or -r arguments from the ofsutil tag info command. 03304, 0, "Unable to open mount point %s. Verify that the mount point exists." // *Cause: Mount point cannot be opened to display tag name information. // *Action: Verify that the mount point exists and is accessible before // retrying the tag info command. 03305, 0, "unable to retrieve all tag names for %s" // *Cause: Unable to return the full list of tag names. // *Action: Verify there is sufficient memory resources available. 03306, 0, "tag name does not exist in file %s" // *Cause: Cannot unset a tag name on a file that does not exist. // *Action: Verify the tag name to unset is correct. 03307, 0, " Tags: %s" 03308, 0, "The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil repl and tag commands." // *Cause: The ADVM compatibility attribute has not been upgraded to // version 11.2.0.2.0 or beyond. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute. 03309, 0, "path name %s does not resolve to an ACFS file system" // *Cause: A path name supplied on an 'acfsutil tag' command did not // resolve to an ACFS file system. // *Action: Remove the non-ACFS path name from the 'acfsutil tag' command. 03310, 0, " amount of change since mount: %.2f MB" // *Cause: Informational // *Action: None 03311, 0, " average rate of change since mount: %u KB/s" // *Cause: Informational // *Action: None 03312, 0, " amount of change: %.2f MB rate of change: %u KB/s" // *Cause: Informational // *Action: None 03313, 0, "unable to collect ACFS statistics for mount point %s" // *Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS // driver. // *Action: Verify that the file system is online and that the ADVM/ACFS // drivers are loaded and running. 03314, 0, "interval cannot exceed %d seconds" // *Cause: Statistics interval exceeded maximum number of seconds per // interval. // *Action: Select an interval that is less than or equal to 2592000 seconds // and retry "acfsutil info fs -s". 03315, 0, "count cannot exceed %d" // *Cause: Number of statistics intervals exceeded maximum number allowed. // *Action: Select a total count that is less than or equal to // 2^63-1 and retry "acfsutil info fs -s". 03316, 0, "interval must be a positive integer" // *Cause: A zero or negative integer was provided. // *Action: Provide a positive integer for the statistics interval. 03317, 0, "unable to set tag on file \"%s\" because its tag name storage is full" // *Cause: The limit of the file's tag name storage has been reached. // *Action: Remove any unused tags on this file and try the command again. 03318, 0, "unable to set tag name \"%s\" because this name is reserved" // *Cause: The tag name specified is reserved. // *Action: Choose another tag name which is not reserved. 03319, 0, "Set tag on file: %s" // *Cause: Informational // *Action: None 03320, 0, "Removing tag(s) on file: %s" // *Cause: Informational // *Action: None 03321, 0, "The ADVM compatibility attribute for the diskgroup is below the required version (%s) for the 'acfsutil tag' commands." // *Cause: The ADVM compatibility attribute has not been upgraded to a // version that supports tagging. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute to the specified version. 03322, 0, "The ADVM compatibility attribute for the diskgroup is below the required version (%s) for the 'acfsutil repl' commands." // *Cause: The ADVM compatibility attribute has not been upgraded to a // version that supports replication. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute to the specified version. 03400, 0, "Invalid repl toggle command." 03401, 0, "primary replication is %s" 03402, 0, " replication status: %s" //* Document: NO 03450, 0, "Continue to panic the cluster [y|n] ?" // *Cause: The 'acfsutil panic' command was issued to panic the cluster. // *Action: Respond Y(yes) to proceed or N(no) to cancel. 03451, 0, "Continue to panic the system [y|n] ?" // *Cause: The 'acfsutil panic' command was issued to panic the system. // *Action: Respond Y(yes) to proceed or N(no) to cancel. / Persistent log 03500, 0, "Unable to access kernel persistent log entries." // *Cause: Could not get or set persistent log configuration data. // *Action: Make sure that the Oracle kernel drivers are loaded/started // (run 'acfsdriverstate loaded'). // If loaded/started, make sure that you have root/administrator // privileges. 03501, 0, "The 'query' option may not be used with any other options." // *Cause: Additional options to 'query' were specified on the command line. // *Action: Do not use any other options with the 'query' option. 03502, 0, "The specified maximum log file size is less than %d MB or is greater than %d MB." // *Cause: An invalid log file size was entered on the command line. // *Action: Specify a value equal to or greater than the minimum size and // equal to or less than the maximum size. 03503, 0, "The specified interval is less than %d seconds." // *Cause: An invalid interval value was entered on the command line. // *Action: Enter an interval value equal to or greater than the minimum. 03504, 0, "An invalid high water level value (%d percent) was specified." // *Cause: The high water level must be greater than the low water level and // less than 100 percent. // *Action: Enter a valid high water level value. 03505, 0, "An invalid low water level value (%d percent) was specified." // *Cause: The low water level must be greater than zero and less than // the high water level. // *Action: Enter a valid low water level value. 3506, 0, "The selected percentage does not generate an even integer. Changing to %d percent." // *Cause: The specified percentage of the buffer size generates a remainder. // *Action: None. Informational. 03507, 0, "The specified buffer size is less than %d KB or is greater than %d KB." // *Cause: An invalid buffer size value was entered on the command line." // *Action: Enter a value equal to or greater than the minimum or equal // to or less than the maximum size. 03508, 0, "The specified maximum number of log files is less than %d or greater than %d." // *Cause: An invalid maximum number of log files was entered on the // command line. // *Action: Specify a value equal to or greater than the minimum and equal to // or less than the maximum. 03509, 0, "%s is not a Grid infrastructure home." // *Cause: An invalid Grid infrastructure home was entered on the command line. // *Action: Specify a valid Grid infrastructure home. 03510, 0, "There are more log files on the system than are being configured. Removing the oldest files." // *Cause: A new, lower, maximum number of allowable OKS persistent log files // was configured and there are currently more log files on the system. // Deleting the oldest files." // *Action: None. Informational. 03511, 0, "Deleting %s." // *Cause: A log file was deleted to satisfy the new configuration. // *Action: None. Informational. 03512, 0, "Renaming %s to %s." // *Cause: A log file was renamed to place it in time modified // sequential order. // *Action: None. Informational. 03513, 0, "The OKS persistent log configuration settings cannot be queried." // *Cause: The OKS persistent log was not running. // *Action: Start the log with 'acfsutil plogconfig -d '. 3514, 0, " The directory '%s' can not be converted to an absolute path." // *Cause: A directory name was specified that could not be converted to // an absolute path. The name was either an invalid relative path or, // on Windows, included an invalid drive letter. // *Action: Specify the directory name in the form of an absolute path. // On Windows, the absolute path includes the drive letter. 03520, 0, "Log Directory Name : %s : Buffer Size (KB) : %d : Low Water Level (KB) : %d : High Water Level (KB) : %d : Timer Interval (Seconds) : %d : Maximum Number of Log Files : %d : Maximum Log File Size (MB) : %d." 03521, 0, "Log Directory Name : %s" 03522, 0, "Buffer Size (KB) : %d" 03523, 0, "Low Water Level (percent) : %d" 03524, 0, "High Water Level (percent) : %d" 03525, 0, "Timer Interval (Seconds) : %d" 03526, 0, "Maximum Number of Log Files : %d" 03527, 0, "Maximum Log File Size (MB) : %d" / / Messages for acfsdismount 04001, 0, "Failed to open path %s. Verify that %s exists." // *Cause: Path could not be opened. // *Action: Verify the path is accessible before retrying. 04002, 0, "unable to allocate a buffer" // *Cause: A request for process virtual memory by acfsdismount command // failed. This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 04003, 0, "volume %s in use by a non-ACFS file system" 04004, 0, "error removing symbolic link for %s" 04005, 0, "error removing DOS definition for %s" 04006, 0, "unable to remove the reparse point on %s" 04007, 0, "dismount failed due to open files on the volume" 04008, 0, "failed to unlock the volume" 04009, 0, "unable to retrieve the volume name associated with %s" 04010, 0, "Conversion of reparse data Unicode string to ANSI string failed." 04011, 0, "Failed to open volume %s. Verify that %s exists." // *Cause: Volume could not be opened. // *Action: Verify the ASM instance is operational and the volume is // enabled and accessible before retrying. 04012, 0, "Info: failed to change the volume signature, but continuing with dismount anyway. No action required." 04013, 0, "acfsdismount /all operation did not complete. Unable to retrieve a mount point from the list of active ACFS file systems to dismount. It is possible that not all file systems were dismounted." // *Cause: Failed to obtain the next file system to dismount. // *Action: Use acfsmountvol to determine if there are any file systems // still mounted and reissue 'acfsdismount /all' if necessary. 04014, 0, "unmounting %s" 04015, 0, "valid path name: %s" 04016, 0, "opening handle to volume %s" 04017, 0, "locking volume %s" 04018, 0, "dismounting volume %s" 04019, 0, "removing volume mount point on %s" 04020, 0, "closing handle to volume %s and exiting cleanly" 04021, 0, "Usage: %s [/v] [/all] " 04022, 0, " %s [/v] [/P] " 04023, 0, " %s [/h]" 04024, 0, " [/all] - Unmount all ACFS mount points" 04025, 0, " [/v] - Verbose" 04026, 0, " [/P] - Preserve the drive letter" 04027, 0, " [/h] - Display this message" 04028, 0, " - Drive letter or mount point" 04029, 0, "Example: %s /v E:\mnt\ " 04030, 0, "Version: %s" 04031, 0, "Dismount an ACFS file system." 04032, 0, "removing administrative network share for mount point %s at share name '%s'" // *Cause: Informational // *Action: None 04033, 0, "administrative network share '%s' does not share mount point %s as expected" // *Cause: Attempted to remove the administrative network share associated // with the specified ACFS mount point, but the network share does // not share the specified ACFS mount point as expected. // *Action: Examine the network share at the specified share name. If the // network share shares an unmounted ACFS file system, manually // remove the network share using 'net share /delete' 04034, 0, "administrative network share for mount point %s does not exist at share name '%s'" // *Cause: Informational // *Action: None 04035, 0, "retrieving information for administrative network share '%s' failed" // *Cause: While removing the administrative network share associated with // the specified ACFS mount point, failed to retrieve information on // the administrative network share. This message is accompanied by // other messages providing details on the error. // *Action: Check for a network share at the specified share name. If a // network share exists at the specified share name and it shares // an unmounted ACFS file system, manually remove the network share // using 'net share /delete' 04036, 0, "removing administrative network share for mount point %s at share name '%s' failed" // *Cause: Failed to remove the administrative network share associated with // the specified ACFS mount point. This message is accompanied by // other messages providing details on the error. // *Action: Manually remove the administrative network share at the specified // share name using 'net share /delete' 04037, 0, "could not remove administrative network share for mount point %s at share name '%s'" // *Cause: Failed to remove the administrative network share associated with // the specified ACFS mount point. This message is accompanied by // other messages providing details on the error. // *Action: Correct the error indicated by the accompanying messages. / / Messages for umount on Linux 04050, 0, "Usage: [%sh] [%sv] [%sn] [%sl] [%sr] " 04051, 0, " [%sh] - Prints out this usage message" 04052, 0, " [%sv] - Verbose mode" 04053, 0, " [%sn] - Do not update /etc/mtab" 04054, 0, " [%sl] - Lazy unmount" 04055, 0, " [%sr] - If umount fails, remount read-only" 04056, 0, " - Directory to unmount" 04057, 0, "Unmount an ACFS file system." 04058, 0, "Ignoring unsupported ACFS command option: '%s'" // *Cause: An unsupported 'umount.acfs' command option was specified. // *Action: No action required. The unmount will proceed without the option. / / Messages for Replication 05001, 0, "must specify 'primary' or 'standby'" // *Cause: Command syntax requires 'primary' or 'standby' argument. // *Action: At command line, indicate primary or standby for replication // command. 05002, 0, "must provide an Oracle Net alias to the primary replication site" // *Cause: The Oracle Net alias to connect to the primary replication site // was not specified. // *Action: Provide Oracle Net alias to connect to the primary replication // site. 05003, 0, "must provide a primary mount point" // *Cause: The mount point on the replication primary site for the file system // to be replicated was not provided. // *Action: Provide an existing mount point on the primary site for the file // system to be replicated. 05004, 0, "cannot allocate a list of tag names" // *Cause: A request for process virtual memory failed. // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 05005, 0, "invalid tag name: %s" // *Cause: User specified a tag name that has incorrect syntax. // *Action: See the platform specific Oracle documentation for correct // syntax for ACFS tag names. 05006, 0, "unable to initialize replication process data structures" // *Cause: Failed to determine path names for replication directories. // *Action: Verify the specified mount point is an ACFS file system. 05007, 0, "cannot initialize interrupt signal handler" // *Cause: The system could not initialize the mechanism to handle // interrupts. // *Action: Contact Oracle Support Services. 05008, 0, "cannot lock file %s to serialize ACFS replication commands" // *Cause: Failed to open and lock the specified file. This message // accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 05009, 0, "ACFS replication initialization is already in progress." // *Cause: Initialization was in progress on the replication site. // *Action: Wait for the other initialization on replication site to complete. 05010, 0, "ACFS replication initialization is still in progress." // *Cause: The command cannot be run until replication initialization // completes. // *Action: Monitor initialization progress with the 'acfsutil repl info' // command. 05011, 0, "cannot open directory: %s" // *Cause: Failed to open the specified directory. This message is // accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 05012, 0, "ACFS replication is already initialized." // *Cause: ACFS replication has already been initialized on this system. // *Action: Initialization cannot be undone unless replication is terminated // or the file system is reformatted. 05013, 0, "ACFS replication cannot be initialized." // *Cause: This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 05014, 0, "cannot verify replication configuration" // *Cause: This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the // cause of the problem is unclear, contact Oracle Support Services. 05015, 0, "cannot cleanup replication directories" // *Cause: The application failed to cleanup from a previous replication // instantiation. // *Action: Verify user permissions and that the replication directory is // available. 05016, 0, "cannot update replication configuration with new trace level" // *Cause: The application was unable to communicate with the ACFS driver. // *Action: Verify that the ADVM/ACFS drivers are loaded and running. 05017, 0, "cannot create file: %s" // *Cause: The application failed to create the specified file. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 05018, 0, "cannot get primary ADVM volume information for %s" // *Cause: The application failed to get the ADVM volume path for the mounted // ACFS file system. // *Action: Verify that the file system is mounted and of type ACFS. 05019, 0, "cannot allocate space for the ADVM volume path" // *Cause: A request for process virtual memory failed. // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). If // possible, change options to reduce required memory and/or take // steps to increase memory available to the process. Otherwise, // report this error to Oracle Support Services. 05020, 0, "cannot start replication daemons" // *Cause: CRS has failed to start the replication daemons. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the replication daemons failed to start. 05021, 0, "cannot stop replication daemons" // *Cause: CRS has failed to stop the replication daemons. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the replication daemons failed to stop. 05022, 0, "internal CRS error" // *Cause: The application failed to initialize communication with CRS. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the replication daemons failed to start. 05023, 0, "error checking for file: %s" // *Cause: Informational // *Action: None 05024, 0, "The standby replication site is initialized. ACFS replication will begin." // *Cause: Informational // *Action: None 05025, 0, "waiting for the standby replication site to initialize" // *Cause: Informational // *Action: None 05026, 0, "caught interrupt; ACFS replication initialization is shutting down." // *Cause: Informational // *Action: None 05027, 0, "cannot remove file: %s" // *Cause: File system was not accessible. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05028, 0, "cannot obtain current time for events log" // *Cause: The application failed to get the current time for logging. // *Action: Contact Oracle Support Services. 05029, 0, "cannot write to the events log" // *Cause: The application failed to write to the specified file. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 05030, 0, "cannot clean up configuration file" // *Cause: Initialization failed and the configuration file created during // failed initialization could not be removed. // *Action: Contact Oracle Support Services. 05031, 0, "standby file system is not empty" // *Cause: The file system was not empty. // *Action: Use an empty standby file system; either reformat the file system // or remove all files and directories under /. 05032, 0, "unable to determine user permissions" // *Cause: An error occurred attempting to acquire the user permissions. // This message is accompanied by other message(s) providing // details on the error. // *Action: Correct the problem indicated by the other message(s). Otherwise, // report this error to Oracle Support Services. 05033, 0, "must provide a standby mount point" // *Cause: A mount point on the standby replication site was not provided. // *Action: Provide an existing mount point with an empty file system on the // standby replication site. 05034, 0, "cannot obtain path for directory: %s" // *Cause: The application failed to locate the specified directory. // *Action: Verify that the replication directory is available. 05035, 0, "cannot open file for write: %s" // *Cause: The application failed to open the specified file. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 05036, 0, "cannot write to file: %s" // *Cause: The application failed to write to the specified file. // This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If // the solution is not clear, contact Oracle Support Services. 05037, 0, "cannot move file %s to directory %s" // *Cause: The application failed move the specified file. // *Action: Verify that the replication directory is available. 05038, 0, "cannot register Oracle Net service name" // *Cause: Unable to register the Oracle Net service name with the // ASM instance. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05039, 0, "cannot unregister Oracle Net service name" // *Cause: Unable to unregister the Oracle Net service name from the ASM // instance. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05040, 0, "cannot obtain Oracle Net service name from alias provided" // *Cause: Unable obtain the Oracle Net service name from the Oracle // Net alias provided on the command line. // *Action: Verify that the Oracle Net alias exists and is properly formed. 05041, 0, "Oracle Net service name is greater than %s bytes" // *Cause: The Oracle Net service name specified for replication is greater // than the maximum allowed. // *Action: Reduce the size of the Oracle Net service name being used for // replication. 05042, 0, "insufficient privileges to perform replication command. Administrator access is required." // *Cause: The caller does not have sufficient privileges to perform the // replication command. // *Action: Execute the replication command from a user with administrator // access. 05043, 0, "insufficient privileges to perform replication command. ASM administrator group access is required." // *Cause: The caller does not have sufficient privileges to perform the // replication command. // *Action: Execute the replication command from a user with ASM administrator // group access. 05044, 0, "cannot obtain node name" // *Cause: Unable to get local node name through CRS. // *Action: Verify that CRS is running. 05045, 0, "invalid interval specified for replication statistics" // *Cause: The caller specified an invalid time interval for replication // statistics. // *Action: Verify the syntax of the time interval using // 'acfsutil repl info' help flag and retry. 05046, 0, "invalid date range specified for replication statistics" // *Cause: The caller specified an invalid date range for replication // statistics. // *Action: Verify the syntax of the date range using // 'acfsutil repl info' help flag and retry. 05047, 0, "time specified is in the future" // *Cause: The caller specified a date in the future. // *Action: Verify the time specified is before the current time. 05048, 0, "start time specified is newer than the end time specified" // *Cause: The caller specified a date range where the start time was more // recent the end time. // *Action: Verify the start time is before the end time. 05049, 0, "validating the remote connection" // *Cause: Informational // *Action: None 05050, 0, "remote connection cannot be established" // *Cause: The user name, password, or Oracle Net alias used to connect to // the remote site was not correct or the remote site was unreachable. // *Action: Verify the connection information is correct and the status of // the remote site. 05051, 0, "remote connection has been established" // *Cause: Informational // *Action: None 05052, 0, "standby replication site requires reinitialization" // *Cause: Initialization was unable to complete on the primary replication // site and left the standby replication site in an indeterminate // state. // *Action: On the standby replication site, run 'acfsutil repl terminate' // and 'acfsutil repl init' before retrying initialization on the // the primary replication site. 05053, 0, "replication's Oracle Net service name conflicts with the existing ASM service name" // *Cause: The service name for replication specified in the Oracle Net // alias conflicts eith the Oracle Net service name that ASM uses. // *Action: Review the Oracle Net alias for replication in tnsnames.ora and use // a different service name for the replication alias. 05054, 0, "standby replication file system is mounted on more than one cluster node" // *Cause: The standby replication file system was mounted on more than // one node in the cluster. // *Action: Unmount the file system on all but one node on the standby // replication site and retry the initialization. 05055, 0, "invalid connection string for the primary replication site" // *Cause: The user name, password, or Oracle Net alias used to connect to // the primary replication site was not correct or was unreachable. // *Action: Verify the connection information is correct and the status of // the primary replication site. 05056, 0, "invalid connection string for the standby replication site" // *Cause: The user name, password, or Oracle Net alias used to connect to // the standby replication site was not correct or was unreachable. // *Action: Verify the connection information is correct and the status of // the standby replication site. 05057, 0, "invalid arguments" 05058, 0, "command issued on the incorrect replication site" // *Cause: The command was issued on the incorrect replication site. // *Action: Verify the command syntax. If issued on the primary file // system, reissue on the standby file system. If issued on // the standby file system, reissue on the primary file system. 05059, 0, "ACFS replication not initialized" // *Cause: ACFS replication information cannot be retrieved as replication // has not been initialized. // *Action: None 05060, 0, "waiting for ACFS replication to terminate" // *Cause: Informational // *Action: None 05061, 0, "ACFS replication command interrupted" // *Cause: Informational // *Action: None 05062, 0, "cannot query CRS resource" // *Cause: The application failed to communicate with CRS. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the CRS resource is not responding. 05063, 0, "cannot relocate CRS resource" // *Cause: The application failed to relocate CRS resource. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the CRS resource cannot be relocated. 05064, 0, "the service name '%s' is not registered on the standby site" // *Cause: Possible causes include: // 1.) Replication was not initialized on the standby site. // 2.) Mismatched service names. If the -c option is not used, the // service name specified in the alias for the standby file system // did not match the service name specified for the primary // file system in the alias on the standby site. // 3.) The alias for the standby site referred to the wrong set of // nodes. // *Action: Possible actions include: // 1.) Verify replication is initialized on the standby site. // 2.) Verify the service name used to connect to the standby site // matches the one registered on the standby site. // Run 'lsnrctl status' on the standby site to verify. // 3.) Verify that the nodes listed in the standby alias have // the standby file system mounted. 05065, 0, "cannot transfer files to the standby file system '%s'" // *Cause: Possible causes include: // 1.) The standby mount point did not exist or was not an ACFS // file system. // 2.) The standby file system was full. // *Action: Possible actions include: // 1.) Verify that the standby mount point exists and is an ACFS // file system. // 2.) Verify that there is free space on the standby file system. 05066, 0, "ACFS replication is already paused" // *Cause: ACFS replication was paused by a previous call. // *Action: None 05067, 0, "cannot rename file %s to %s in directory %s" // *Cause: The application failed to rename the specified file. // *Action: Verify that the replication directory is available. 05068, 0, "ACFS replication has not been paused" // *Cause: ACFS replication was not paused. Resume operation is not // needed. // *Action: None 05069, 0, "ACFS replication update must specify at least one attribute" // *Cause: The command to update the replication configuration did not // specify any attributes to update. // *Action: Specify at least one replication attribute to be updated. 05070, 0, "command must be run on the primary replication site" // *Cause: 'acfsutil repl update' command was not run on the primary // replication site. // *Action: Execute 'acfsutil repl update' on the primary replication site. 05071, 0, "invalid username or password used to connect to the standby site" // *Cause: The username or password specified on the command line or in the // wallet was incorrect. // *Action: Verify the username and password are correct when connecting to // the standby site. 05072, 0, "cannot open events file %s" // *Cause: Failed to open events log file. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05073, 0, "cannot query events log file" // *Cause: Failed to query events log file. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05074, 0, "invalid number of days specified" 05075, 0, "cannot terminate replication" // *Cause: Failed to terminate replication. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05076, 0, "unable to determine CRS user/group" // *Cause: The application failed to determine CRS user and/or group. // *Action: Verify that CRS is running. Check the CRS logs to determine // why the CRS user and/or group cannot be determined. 05077, 0, "could not complete replication synchronization" // *Cause: Failed to complete synchronization of primary and standby // replication sites. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05078, 0, "failed to synchronize primary and standby replication sites" // *Cause: Failed to synchronize replication sites. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05079, 0, "waiting for replication update to complete" // *Cause: Informational // *Action: None 05080, 0, "Resource: %s" 05081, 0, "Target State: %s" 05082, 0, "Current State: %s %s" 05083, 0, "Initialization of the primary file system could not complete because the standby is already configured for replication." // *Cause: The standby file system was not expecting initialization data from // this primary. // Possible causes include: // 1. Stale replication state detected on standby file system from a // previous instantiation. // 2. An incorrect replication standby site was supplied. // 3. An incorrect replication standby file system was supplied. // *Action: 1. Run 'acfsutil repl terminate' on the standby site for the // standby file system before retrying the initialization of the // primary. // 2. Verify the correct standby site is used. // 3. Verify the correct standby file system is used. 05084, 0, "The replication standby file system has been newly initialized and is refusing files from the primary. The primary may need to be terminated and newly initialized." // *Cause: The standby file system was not expecting any data from the primary // except initialization data. // A possible cause may be the standby file system was terminated and // newly initialized, but the primary was not. // *Action: Verify the primary site and primary file system. Run // 'acfsutil repl terminate' on the primary site for the primary file // system before retrying the initialization of the standby. 05085, 0, "cannot start replication because incompatible ACFS features already exist" // *Cause: Failed to start replication: // Either security or encryption or both is enabled on the file system. // *Action: Undo security or encryption or both, then try to initialize // replication again. To undo encryption and security respectively: // acfsutil encr set -m -u // acfsutil sec prepare -m -u 05086, 0, "listener is not running on the standby site" // *Cause: The listener was not started on the remote site or an incorrect node // name was specified in the standby alias definition. // *Action: Verify the listener is started on the standby site. Check that the // standby alias contains the correct node names. 05087, 0, "The event log does not cover the time range specifed." // *Cause: The events log did not cover any portion of the time range specified in the command. // *Action: Change the time range or use an events log that covers the range specified. 05088, 0, "replicated file system size is below the minimum of %sG" // *Cause: An attempt was made to initialize replication on a file system that did not have sufficient space. // *Action: Resize the file system to at least the minimum size specified. 05089, 0, "replication statistics cannot be queried on the standby site" // *Cause: An attempt was made to query the replication statistics on the standby site. // *Action: Query the replication statistics from the primary site. 05090, 0, "interval is greater than %s years" // *Cause: The interval specified was greater than the maximum allowed. // *Action: Retry the command with a lower interval value. 05091, 0, "The mount path specified exceeds the maximum length allowed on this platform." // *Cause: The specified mount path exceeded the maximum length on this platform. // *Action: Use a valid mount path. 05092, 0, "replicated file system free space is near the minimum threshold of %sGB per active node, continuing with initialization" // *Cause: Initialization of replication was issued on a file system that is near the minimum threshold of free space. // *Action: Consider resizing the file system to allow for optimal replication performance. 05093, 0, "could not retrieve active node count on file system: %s, error: %s" // *Cause: Could not get the number of nodes active on the specified file // system. // *Action: Verify at least one cluster node has the file system mounted, or // address the specified operating system dependent error code // provided. If the solution is not clear, contact Oracle Support // Services. 05094, 0, "replicated file system free space is below the minimum of %sGB per active node, actual free space left: %sGB" // *Cause: An attempt was made to initialize replication on a file system that did not have sufficient space. // *Action: Resize the file system such that free space is at least the minimum size specified. / Replication Configuration Information Messages 05095, 0, "Background Resources: %s of %s Online" 05096, 0, "Log compression: %s" 05097, 0, "Debug log level: %s" 05098, 0, "Standby Oracle Net service name: %s" 05099, 0, "Primary Oracle Net service name: %s" 05100, 0, "Site: %s" 05101, 0, "Primary Oracle Net alias: %s" 05102, 0, "Primary mount point: %s" 05103, 0, "Primary status: %s" 05104, 0, "Standby Oracle Net alias: %s" 05105, 0, "Standby mount point: %s" 05106, 0, "Standby status: %s" 05107, 0, "Replicated tags: %s" / Replication Event Information 05108, 0, "Time: %s" 05109, 0, "Event: Replication Initialization Started" 05110, 0, "Initialization Start Time: %s" 05111, 0, "Event: Primary Site Initialization Progress" 05112, 0, "Number of Files Processed: %s" 05113, 0, "Number of Files Enabled: %s" 05114, 0, "Number of Files Remaining: %s" 05115, 0, "Percentage Complete: %s" 05116, 0, "Event: Standby Site Initialization Progress" 05117, 0, "Number of Files Enabled: %s" 05118, 0, "Number of Files Initialized: %s" 05119, 0, "Percentage Complete: %s" 05120, 0, "Event: Initialization Files Complete" 05121, 0, "Cord Number: %s" 05122, 0, "Initialized Files in Cord: %s" 05123, 0, "Event: Error" 05124, 0, "Severity: %s" 05125, 0, "Message: %s" 05126, 0, "Event: Transmitted Log" 05127, 0, "Cord Number: %s" 05128, 0, "Capture Time: %s" 05129, 0, "Acknowledged Time: %s" 05130, 0, "Event: Applied Log" 05131, 0, "Cord Number: %s" 05132, 0, "Log Create Time: %s" 05133, 0, "Log Apply Complete Time: %s" 05134, 0, "Event: Retransmitted Log" 05135, 0, "Cord Number: %s" 05136, 0, "Node Number: %s" 05137, 0, "Event: Replication Paused" 05138, 0, "Pause Time: %s" 05139, 0, "Pause Site: %s" 05140, 0, "Event: Replication Resumed" 05141, 0, "Resume Time: %s" 05142, 0, "Resume Site: %s" 05143, 0, "Event: Replication Synchronized" 05144, 0, "Sync Time: %s" 05145, 0, "Logs were applied" 05146, 0, "Event: Replication Terminated" 05147, 0, "Terminate Time: %s" 05148, 0, "Terminate immediate" 05149, 0, "Event: Information Message" 05150, 0, "Message: %s" 05151, 0, "Unknown record type-%s" 05152, 0, " %s%% complete" // *Removed: 05153, 0, " Standby: %s%% complete" 05154, 0, "Events Log: %s" 05155, 0, " Scanning directories: %s found" 05170, 0, "Cannot initialize replication while the cluster is in rolling migration" // *Cause: An attempt to initialize replication was rejected because the // cluster was in rolling migration. Replication initialization is // not allowed during rolling migration. // *Action: Complete the rolling migration and then initialize replication. 05171, 0, "Cannot terminate replication while the cluster is in rolling migration" // *Cause: An attempt to terminate replication was rejected because the // cluster was in rolling migration and the file system was mounted // on more than one node. // *Action: Either complete the rolling migration and then terminate // replication, or unmount this file system on the other nodes and // then terminate replication. 05200, 0, "Stopping ACFS replication daemons on %s" // *Cause: Informational // *Action: None 05201, 0, "Starting ACFS replication daemons on %s" // *Cause: Informational // *Action: None 05202, 0, "ACFS replication daemons started successfully on %s" // *Cause: Informational // *Action: None 05203, 0, "ACFS replication daemons stopped successfully on %s" // *Cause: Informational // *Action: None 05204, 0, "Attempting to restart replication daemons on %s" // *Cause: Informational // *Action: None /Replication Statistics 05300, 0, "Data replicated: %.2fGB" 05301, 0, " From writes: %.2fGB" 05302, 0, " From memory mapped updates: %.2fGB" 05303, 0, "Avg. rate of data replication: %.2fMB/minute" 05304, 0, "Last rlog capture to apply: %s" 05306, 0, "File operations replicated: %s" 05307, 0, "Avg. rate of file op. replication: %.2f/minute" 05308, 0, "Last rlog capture time: %s" 05309, 0, "Last rlog apply time: %s" 05310, 0, "Avg. time from capture to apply: %s" 05311, 0, "Min. time from capture to apply: %s" 05312, 0, "Max. time from capture to apply: %s" 05313, 0, "Avg. time before rlog transport: %s" 05314, 0, "Min. time before rlog transport: %s" 05315, 0, "Max. time before rlog transport: %s" 05316, 0, "Avg. time to transport rlog: %s" 05317, 0, "Min. time to transport rlog: %s" 05318, 0, "Max. time to transport rlog: %s" 05319, 0, "Avg. time before rlog preprocessing: %s" 05320, 0, "Min. time before rlog preprocessing: %s" 05321, 0, "Max. time before rlog preprocessing: %s" 05322, 0, "Avg. time for rlog preprocessing: %s" 05323, 0, "Min. time for rlog preprocessing: %s" 05324, 0, "Max. time for rlog preprocessing: %s" 05325, 0, "Avg. time before applying rlog changes: %s" 05326, 0, "Min. time before applying rlog changes: %s" 05327, 0, "Max. time before applying rlog changes: %s" 05328, 0, "Avg. time to apply rlog changes: %s" 05329, 0, "Min. time to apply rlog changes: %s" 05330, 0, "Max. time to apply rlog changes: %s" 05331, 0, "Node %s:" 05332, 0, "Avg. time before rlog transport: %s" 05333, 0, "Min. time before rlog transport: %s" 05334, 0, "Max. time before rlog transport: %s" 05335, 0, "Avg. time to transport rlog: %s" 05336, 0, "Min. time to transport rlog: %s" 05337, 0, "Max. time to transport rlog: %s" 05338, 0, "Data replicated: %.2fGB" 05339, 0, " From writes: %.2fGB" 05340, 0, " From memory mapped updates: %.2fGB" 05341, 0, "Avg. rate of data replication: %.2fMB/minute" 05342, 0, "Time before rlog preprocessing: %s" 05343, 0, "Time for rlog preprocessing: %s" 05344, 0, "File operations replicated: %s" 05345, 0, "Avg. rate of file op. replication: %.2f/minute" 05346, 0, "Avg. time from apply to receipt: %s" 05347, 0, "Max time from apply to receipt: %s" 05348, 0, "Min time from apply to receipt: %s" 05349, 0, "Time before applying rlog changes: %s" 05350, 0, "Time to apply rlog changes: %s" 05351, 0, "Time from apply to receipt: %s" 05352, 0, "Time before rlog transport: %s" 05353, 0, "Time to transport rlog: %s" 05354, 0, "Clock difference detected between primary and standby replication sites." // *Cause: A difference in the system clocks has been detected between the // primary and standby replication sites. // *Action: Update the time on the primary and standby replication sites // to match, and reissue the 'acfsutil repl info -s' command with // a new time interval. 05355, 0, "Lag Time: %s" 05356, 0, "The Oracle Local Registry, OLR, cannot be accessed to query the software version." // *Cause: The OLR is not accessible or is not configured correctly. // *Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly. 05500, 0, "ACFS replication error. Contact Oracle Support Services. %s" // *Cause: An ACFS replication operation failed. // *Action: Contact Oracle Support Services. 05501, 0, "ACFS replication error. Customer action required. %s" // *Cause: This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s) immediately. // If the cause of the problem is unclear, contact Oracle Support // Services. 05502, 0, "ACFS replication error. System administration needed. %s" // *Cause: This message is accompanied by other message(s) providing details // on the error. // *Action: The replication daemon(s) will try to correct this situation by // moving to another node in the cluster, if available. The problem // indicated by the other message(s) should be addressed as soon as // possible for replication to continue without further error. If // the cause of the problem is unclear, contact Oracle Support // Services. 05503, 0, "ACFS replication %s daemon shutting down. %s" // *Cause: This message is accompanied by other message(s) providing details // on the error. // *Action: Correct the problem indicated by the other message(s). If the cause // of the problem is unclear, contact Oracle Support Services. 05504, 0, "Retry" // *Document: NO 05505, 0, "The standby replication file system is full." // *Cause: The standby replication file system is out of space. // *Action: Resize the standby file system or delete snapshots from the standby // file system if any exist; otherwise, replication may not proceed. 05506, 0, "The primary replication file system is full." // *Cause: The primary replication file system is out of space. // *Action: Delete unnecessary files from the primary file system to free up // space, resize the primary file system, or delete snapshots from the // primary if any exist; otherwise, replication may not proceed. 05507, 0, "The standby replication site failed %d times to transport replication files from host %s." // *Cause: The replication transport mechanism failed to transport files // from the standby replication site. // *Action: Make sure the replication transport daemon is running and that // proper permissions are set on the replication file systems. 05508, 0, "The primary replication site failed %d times to transport replication files from host %s." // *Cause: The replication transport daemon failed to transfer files // from the primary replication site. // *Action: Make sure the replication transport daemon is running and that // proper permissions are set on the replication file systems. 05511, 0, "The standby replication site host, %s, is experiencing %d I/O errors." // *Cause: I/O on the standby replication site failed. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05512, 0, "The primary replication site host, %s, has experienced %d I/O errors." // *Cause: I/O on the primary replication site failed. // *Action: Verify the ASM instance is operational and the state of the // file system using 'acfsutil info fs' before retrying the // command. 05513, 0, "replication monitor daemon has detected a problem" // *Cause: An error log file was received. // *Action: Check the ACFS alert logs and 'acfsutil repl info' to determine // the cause. 05514, 0, "The replication monitor daemon has not received receipt or error files within the set threshold." // *Cause: The time allowed for receiving receipt or error files has // surpassed. // *Action: Make sure all replication resources are running using // 'acfsutil repl bg info' on both the primary and standby // replication sites. 05515, 0, "The replication monitor received an invalid receipt file and will not process it." // *Cause: The receipt file that the replication monitor process received // is not valid. // *Action: Make sure proper permissions are set on the replication // directories and that I/O requests can be processed. 05516, 0, "The apply daemon failed to regenerate an apply file." // *Cause: The apply daemon has requested more than the allowed number of // regnerations on an apply file. // *Action: Restart the file system replication resource using // 'acfsutil repl bg start'. 05517, 0, "ACFS replication on %s: %s" // *Cause: Informational // *Action: None 05518, 0, "%s is not an ACFS mount point" // *Cause: The command required an ACFS mount point for execution. // *Action: Retry the command using an ACFS mount point. 05519, 0, "must provide an Oracle Net alias to the standby replication site" // *Cause: The Oracle Net alias, which is used to connect to the standby // replication site, was not specified. // *Action: Provide the Oracle Net alias to connect to the standby replication // site. 05520, 0, "cannot update replication configuration" // *Cause: The application was unable to communicate with the ACFS driver. // *Action: Verify that the ADVM/ACFS drivers are loaded and running. 05521, 0, "cannot initialize replication configuration" // *Cause: The application was unable to communicate with the ACFS driver. // *Action: Verify that the ADVM/ACFS drivers are loaded and running. 05522, 0, "Cannot terminate replication. Pending operations are unable to complete because the replication standby file system is full." // *Cause: The standby replication file system is full and replication could // not complete applying data before terminating. // *Action: Resize the standby file system, delete snapshots from the standby // file system if any exist, or use 'acfsutil repl terminate // immediate' to force a terminate on the standby without applying any // outstanding replication data. Any outstanding replication data will // be lost if 'acfsutil repl terminate immediate' is issued. //05600-05604 reserved for replication exceptions 05605, 0, "ACFS replication daemon %s is exiting due to replication termination. %s" // *Cause: Informational // *Action: None //05606-05625 reserved for replication exceptions //05700-05800 reserved for acfsutil repl compare 05700, 0, "All the tag names specified during the \"acfsutil repl init\" operation must exactly match those specified on the command line." // *Cause: Either at least one tag name was not specified during replication // initialization or a specified tag name does not match that used // during the "acfsutil repl init" operation. // *Action: Use the exact tag names specified during the "acfsutil repl init" // operation. 05701, 0, "Comparing primary mount point (<<<) to standby mount point (>>>):" // *Cause: Informational // *Action: None 05702, 0, "Testing for extra files on standby.\nStandby mount point (<<<) to primary mount point (>>>):" // *Cause: Informational // *Action: None 05703, 0, "Results for file comparison of primary to standby mount points:" // *Cause: Informational // *Action: None 05704, 0, " Files successfully compared = %d" // *Cause: Informational // *Action: None 05705, 0, " Files which failed comparison = %d" // *Cause: Informational // *Action: None 05706, 0, "Results for extra files on standby test:" // *Cause: Informational // *Action: None 05707, 0, " Total files checked = %d" // *Cause: Informational // *Action: None 05708, 0, " Extra files found = %d" // *Cause: Informational // *Action: None 05709, 0, "A status check on a file failed. Skipping file: %s" // *Cause: Either the primary file system is actively being modified or an // internal error occurred. // *Action: If possible, ensure the primary file system is not changing while // the tool is running. 05710, 0, "ACFS tags do not support character devices. Skipping file: %s" // *Cause: Informational // *Action: None 05711, 0, "ACFS tags do not support block devices. Skipping file: %s" // *Cause: Informational // *Action: None 05712, 0, "ACFS tags do not support FIFOs. Skipping file: %s" // *Cause: Informational // *Action: None 05713, 0, "ACFS tags do not support sockets. Skipping file: %s" // *Cause: Informational // *Action: None 05714, 0, "<<< %s\n>>> File missing!" // *Cause: The specified file was not replicated to the standby file system. // *Action: None 05715, 0, "Found: %s" // *Cause: The specified file is an extra file on the standby file system. // *Action: None 05716, 0, "<<< Tag names exist on file %s\n>>> No tag names exist on file %s" // *Cause: The file on the primary file system has tag names but the file on // the standby file system has no tag names. // *Action: Tag names on files can be displayed with the "acfsutil tag info" // command. 05717, 0, "<<< Extended attribute mismatch for %s\n>>> Extended attribute mismatch for %s" // *Cause: Informational // *Action: None 05718, 0, "An unexpected result occurred during primary to standby comparison. Continuing. Affected files: %s %s" // *Cause: An unexpected result occurred when comparing the primary to the // standby. // *Action: None. The file was skipped. 05719, 0, "An unexpected result occurred during standby to primary comparison. Continuing. Affected files: %s %s" // *Cause: An unexpected result occurred when comparing the standby to the // primary. // *Action: None. The file was skipped. 05720, 0, "File type was not recognized. Continuing. Affected files \"%s\" and \"%s\"" // *Cause: An unrecognized file type was encountered which will be ignored. // *Action: Informational 05721, 0, "Could not open the file specified for a checksum operation: %s" // *Cause: Either the primary file system was modified or an internal error // occurred. // *Action: If possible, do not modify files on the primary file system when // running this tool. 05722, 0, "A file read failed during a checksum operation: %s " // *Cause: Either the primary file system was modified or an internal error // occurred. // *Action: If possible, do not modify files on the primary file system when // running this tool. 05723, 0, "Unable to obtain security attributes on file \"%s\"" // *Cause: Check the access rights on the indicated file. // *Action: Ensure the files security attributes can be read using a file // manager. 05724, 0, "Unable to convert a security descriptor to a string on file \"%s\"" // *Cause: The Windows security identifier (SID) may not be available on this // system. // *Action: Check the Windows SID is available on this host. /05725, 0, "UNUSED" /05726, 0, "UNUSED" /05727, 0, "UNUSED" 05728, 0, "Failed to retrieve file system status information from a system call for mount point \"%s.\"" // *Cause: A system call for the status of the file system failed. // *Action: Ensure the file system is accessible via "acfsutil info fs". 05730, 0, "Mount point \"%s\" does not support Oracle ACFS tagging." // *Cause: The "-a" option was passed on the command line to compare ACFS tags. // A file system being checked did not support ACFS tagging. // *Action: Disable ACFS tag name comparison by omitting the "-a" option. 05731, 0, "Mount point \"%s\" does not support extended attributes, therefore, the ACFS tag name portion of the comparisons will not be performed." // *Cause: Informational. // *Action: None. 05732, 0, "The specified standby mount point does not exist: \"%s\" ." // *Cause: Failed to access the specified standby mount point. // *Action: Use a networked file system to provide access to the standby // file system on the primary node where the 'acfsutil repl compare' // will be preformed. 05733, 0, "Successfully compared: %s %s" // *Cause: Informational. // *Action: None. 05734, 0, "Successfully verified existence: %s %s" // *Cause: Informational. // *Action: None. /05735, 0, "UNUSED" /05736, 0, "UNUSED" 05737, 0, "%s file attribute comparison failed: permissions=%s, links=%d, uid=%d, gid=%d, bytes=%ld, file: %s" // *Cause: Informational. // *Action: None. 05738, 0, "%s file size or file contents comparison failed, file: %s" // *Cause: Informational. // *Action: None. 05739, 0, "%s security descriptor comparison failed, file: %s" // *Cause: Informational. // *Action: None. 05740, 0, "%s file type comparison failed, file: %s" // *Cause: Informational. // *Action: None. 05741, 0, "%s file type comparison failed, directory: %s" // *Cause: Informational. // *Action: None. 05742, 0, "%s file type comparison failed, soft link: %s" // *Cause: Informational. // *Action: None. 05743, 0, "%s file type comparison failed, socket: %s" // *Cause: Informational. // *Action: None. 05744, 0, "%s file type comparison failed, character device: %s" // *Cause: Informational. // *Action: None. 05745, 0, "%s file type comparison failed, block device: %s" // *Cause: Informational. // *Action: None. 05746, 0, "%s file type comparison failed, FIFO: %s" // *Cause: Informational. // *Action: None. / Replication messages for free space warnings 05801, 0, "The primary replication file system is at least %u%% full." // *Cause: The primary replication file system may be running low on space. // *Action: Delete unnecessary files from the primary file system to free up // space, resize the primary file system, or delete snapshots from the // primary if any exist; otherwise, replication may not proceed. 05802, 0, "The primary replication file system has %uGB or less space available per active node." // *Cause: The primary replication file system was found to be running low on // space. // *Action: Delete unnecessary files from the primary file system to free up // space, resize the primary file system, or delete snapshots from the // primary if any exist; otherwise, replication may not proceed. 05803, 0, "The primary replication file system has 2GB or less space available per active node. Replication will be terminated." // *Cause: The primary replication file system was found to be too low on // space in order to run efficiently. // *Action: Restart replication with a larger primary file system that has free // space equal to at least 4GB x number of active nodes. 05804, 0, "The standby replication file system is out of sync with the primary by at least %u minutes." // *Cause: The time period to process changes on the standby file system was // exceeded. // *Action: Check the network connectivity between the primary and standby // replication systems. 05805, 0, "The standby replication file system is out of sync with the primary by at least 60 minutes." // *Cause: The standby replication file system finished applying changes from // the primary that were more than 60 minutes old. // *Action: Check the network connectivity between the primary and standby // replication systems. 05806, 0, "The primary replication file system has reached an appropriate free space level." // *Cause: The primary replication file system reached an appropriate // level of free space for replication to run efficiently. // *Action: None. 05807, 0, "The primary replication file system has reached an appropriate lag time level." // *Cause: The primary and standby replication sites reached an // appropriate level of lag time for replication to run efficiently. // *Action: None. / Messages for fsck / To translators: / / Many of the messages in 7000-7999 range make use of phrases such as: / " found: %s, but expected to find: %s " / " found: %u, but expected to find: %u " / " found: %u, but expected to find: %d " / / The values passed via parameters within these phrases are typically a single / numeric value, a decimal-hexadecimal pair of values, or a keyword used / within fsck. Following are several examples of output for these phrases: / / found: 1234567 (0x12d687), but expected to find: 23334912 (0x1641000) / / found: 0x0f500005 (OFS_EXTENT_TYPE_HDR), but expected to find: 0x0f500006 / (OFS_EXTENT_TYPE_DATA) / / found: 0, but expected to find: 32 (OFS_ATTRIB_REG) / / found: 4. but expected to find: 3 / / found: 3, but expected to find: -1 / 07000, 0, "Validate or repair an ACFS file system" 07001, 0, "Usage: [%(1)sh] [%(2)sa | %(3)sf] [%(4)sv] [%(5)sy | %(6)sn] %(7)s " 07002, 0, " %(1)sh - Prints out this usage message" 07003, 0, " %(1)sa - Automatically fix file system" 07004, 0, " %(1)sv - Verbose mode" / / To message translators: / Since message 7005 exceeds 80 characters, it will wrap and not be properly / aligned when displaying usage output. The message is split into two parts / by a newline with spaces added after the newline character to align the / second part of the message with the text of the first part. The number of / spaces added for alignment varies depending on the length of the program / name since the program name is included in the message. These additional / spaces are passed as the second parameter. / You may split the message as needed for translation purposes and still / ensure proper alignment by relocating '\n%(2)s' as needed. Be sure to / include exactly one space after '\n%(2)s' when relocating it to ensure / proper alignment. 07005, 0, " %(1)sf - Force file system into mountable state without\n%(2)s completing file system checks or repairs" 07006, 0, " %(1)sy - Assume a response of yes to any question" 07007, 0, " %(1)sn - Assume a response of no to any question" 07008, 0, " volume - ACFS primary volume path name" 07009, 0, "View on-disk structures for an ACFS file system" 07010, 0, "Usage: [%(1)sh] [%(2)sr] [%(3)sl] %(4)s " 07011, 0, " %(1)sr - Read-only mode" 07012, 0, " %(1)sl - Process metadata log files" 07013, 0, " %(1)svv - Very verbose mode" 07014, 0, "Message removed - do not reuse message number" 07015, 0, "Usage: [%(1)sh] [%(2)sa | %(3)sf] [%(4)sv] [%(5)sy | %(6)sn] [%(7)svv] %(8)s " 07016, 0, "metadata read failed at disk offset: %(1)s size: %(2)u bytes" // *Cause: An attempt to read metadata at the indicated disk offset failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / Section 7000 comments above explain how this message will be used. 07017, 0, "metadata read failed at disk offset: %(1)s\n bytes requested: %(2)u bytes returned: %(3)u" // *Cause: A metadata read at the indicated offset was incomplete. The amount // of data returned did not match the amount requested. Refer to the // accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07018, 0, "metadata write failed at disk offset: %(1)s size: %(2)u bytes" // *Cause: An attempt to write metadata at the indicated disk offset failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07019, 0, "metadata write failed at disk offset: %(1)s\n bytes requested: %(2)u bytes written: %(3)u bytes" // *Cause: A metadata write at the indicated offset was incomplete. The amount // of data written did not match the amount requested. Refer to the // accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07020, 0, "ACFS file system created at: %(1)s" 07021, 0, "The File_Entry_Table is corrupt and many of the files in the file system may \nnot be recoverable. It is strongly recommended that the file system be restored \nfrom a backup copy." // *Cause: The ACFS Checker/Fixer found an inconsistency with the // File_Entry_Table metadata. The File_Entry_Table is a critical // system structure that is necessary for a functioning file system. // *Action: Restore the file system from a backup copy. 07022, 0, "I/O request for (disk offset + size): %(1)s exceeds file system size: %(2)s\nfor structure:\n%(3)s" // *Cause: An I/O request was made for data that exceeded the size of the // file system." // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07023, 0, "read failed for metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor structure:\n%(4)s" // *Cause: An attempt to read a metadata structure from disk failed. Refer // to accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07024, 0, "File_Entry_Table entry: %(1)s exceeds the maximum value for this file system: %(2)s" // *Cause: An entry was referenced that exceeded the File_Entry_Table limit. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07025, 0, "File_Entry_Table entry: %(1)s already processed for structure:\n%(2)s" // *Cause: File_Entry_Table entries must be unique within a file system, but // there were multiple references for this specific entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07026, 0, "file extent exceeds file system size: %(1)s\nextent: _FileOffset: %(2)s _Length: %(3)s _PhysicalDiskOffset: %(4)s\nfor file:\n%(5)s" // *Cause: The extent values of the indicated file referenced data beyond the // size of the file system. // There are two possible causes: // 1. The extent _Length and/or _PhysicalDiskOffset property were // incorrect. // 2. The file system size value was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07027, 0, "metadata structure at disk offset: %(1)s contains incorrect or invalid type\n found: %(2)s, but expected to find: %(3)s or %(4)s\nfor structure:\n%(5)s" // *Cause: The type property of the indicated metadata structure was not // valid. The type must be a DATA extent or a HEADER extent. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07028, 0, "DATA extent structure has incorrect _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor structure:\n%(3)s" // *Cause: The _granularity property of the indicated DATA extent structure // was invalid. Its value must be -1. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07029, 0, "HEADER extent structure has incorrect _granularity value\n found: %(1)d, but expected to find: >= 0\nfor structure:\n%(2)s" // *Cause: The _granularity property of the indicated HEADER extent structure // was invalid. Its value must be greater than or equal to zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07030, 0, "file has invalid _FE_OsdSecurity value\nfor file:\n%(1)s" // *Cause: The _FE_OsdSecurity property of the indicated file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07031, 0, "extent structure has incorrect _ExtentOffset value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _ExtentOffset property of the indicated extent structure did // not match its disk offset. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07032, 0, "extent structure has incorrect _UpHeaderNodePtr value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _UpHeaderNodePtr property of the indicated extent structure // was incorrect. // There are two possible causes: // 1. The _UpHeaderNodePtr property did not match its parent. // 2. The parent identifier property was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07033, 0, "extent structure has incorrect _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor structure:\n%(3)s" // *Cause: The _granularity property of the indicated extent structure did // not match its calculated depth. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07034, 0, "extent structure has incorrect _NextFreeExtent value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _NextFreeExtent property of the indicated extent structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07035, 0, "extent[%(1)u] appears to be uninitialized\nfor structure:\n%(2)s" // *Cause: An extent of the indicated extent structure appeared to be in use, // but all of its values were zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07036, 0, "extent[%(1)u] has invalid _Length value\n found: 0, but expected to find: > 0\nfor structure:\n%(2)s" // *Cause: The _Length property of an extent of the indicated extent structure // had a value of zero. _Length values must be greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07037, 0, "extent[%(1)u] has incorrect _SnapIncarnationNumber value\n found: %(2)u maximum: %(3)u\nfor structure:\n%(4)s" // *Cause: The _SnapIncarnationNumber property of the indicated extent // structure exceeded the maximum value for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07038, 0, "extent[%(1)u] has a non-contiguous _FileOffset value\n found: %(2)s, but expected to find: %(3)s\nfor structure:\n%(4)s" // *Cause: The _FileOffset property of an extent of the indicated extent // structure was not contiguous with the _FileOffset of the previous // extent. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07039, 0, "extent[%(1)u] is not in use but it contains non-zero values:\n _FileOffset: %(2)s\n _Length: %(3)s\n _PhysicalDiskOffset: %(4)s\n _SnapIncarnationNumber: %(5)u\nfor structure:\n%(6)s" // *Cause: An extent of the indicated extent structure was not in use, but it // contained non-zero values. // There are two possible causes: // 1. The extent values were not reset to zero when the extent was // freed. // 2. The _NextFreeExtent property of the extent structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07040, 0, "calculated extent structure allocation size (sum of data sizes) does not match expected value\n calculated: %(1)s, but expected to find:%(2)s\nfor structure:\n%(3)s" // *Cause: The sum of all valid extents within the indicated extent structure // did not match the value of the corresponding extent in the parent // extent structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07041, 0, "DATA extent list not found\nfor file:\n%(1)s" // *Cause: The list of DATA extent structures of the indicated file did not // include the initial DATA extent structure. // There are two possible causes: // 1. The _LastExtentPointer property of the file was incorrect. // 2. The structure identified by the _LastExtentPointer value was // not a DATA extent structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07042, 0, "DATA extent node list missing entry for extent structure:\n%(1)s" // *Cause: The list of DATA extent structures of the indicated file was // incomplete. One or more DATA extent structures was missing. // There are three possible causes: // 1. The _LastExtentPointer property of the file was incorrect. // 2. The structure identified by the _LastExtentPointer value was // not a valid DATA extent structure. // 3. The _NextDataExtent property of one or more DATA extent // structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07043, 0, "metadata structure has invalid or incorrect type:\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The type property of the indicated metadata structure did not // match the type expected for this structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07044, 0, "DATA extent list has more nodes than expected\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The list of DATA extent structures of the indicated file contained // more nodes than expected. The _NextDataExtent property of one or // more DATA extent structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07045, 0, "DATA extent list has fewer nodes than expected\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The list of DATA extent structures of the indicated file contained // fewer nodes than expected. // There are two possible causes: // 1. One or more of the DATA extent structures did not have a valid // structure header. // 2. The _NextDataExtent property of one or more DATA extent // structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07046, 0, "file has _LastExtentPointer that does not match calculated value\n calculated: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _LastExtentPointer property of the indicated file did not match // the file's last DATA extent structure. // There are three possible causes: // 1. The _LastExtentPointer value was incorrect. // 2. The last DATA extent structure was not found because the // The _NextDataExtent property of one or more DATA extent // structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07047, 0, "extent node list missing entry for extent structure:\n%(1)s" // *Cause: The list of extent structures of the indicated file was incomplete. // One or more extent structures was missing. // There are three possible causes: // 1. The _LastExtentPointer property of the file was incorrect. // 2. One or more extent structures did not have a valid structure // header. // 3. The _LastExtentPointer property of one or more extent structures // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07048, 0, "metadata structure has invalid _generation_number value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _generation_number property of the indicated metadata structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07049, 0, "extent list has more nodes than expected\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The list extent structures of the indicated file contained more // nodes than expected. The _LastExtentPointer property of one or // more extent structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07050, 0, "extent list has fewer nodes than expected\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The list of extent structures of the indicated file contained // fewer nodes than expected. // There are two possible causes: // 1. One or more of the extent structures did not have a valid // structure header. // 2. The _LastExtentPointer property of one or more extent // structures was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07051, 0, "file has incorrect _LinkCount value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _LinkCount property of the indicated file did not match the // number of hard links found for the file. // There are four possible causes: // 1. The _LinkCount property was incorrect. // 2. One or more directory entries for this file was invalid or was // not found. // 3. A Directory_Entry structure for this file had an incorrect file // identifier. // 4. The _LinkCount property of an ACFS Internal File was not equal // to one. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07052, 0, "file has invalid _ProtectionBits value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _ProtectionBits property of the indicated files was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07053, 0, "file has invalid _ParentID value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _ParentID property of the indicated file was not correct. // There are two possible causes: // 1. The _ParentID value did not match the file's parent directory. // 2. The _ParentID value did not match any valid directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07054, 0, "file has invalid _WindowsAttributes value(s)\n found: %(1)s\n, but expected to find: 0\nfor file:\n%(2)s" // *Cause: The _WindowsAttributes property of the indicated file was invalid. // The _WindowsAttributes value must be zero since file was not // created on a Windows system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07055, 0, "extent[%(1)u] is not in use but it contains non-zero values:\n _FileOffset: %(2)s\n _Length: %(3)s\n _PhysicalDiskOffset: %(4)s\nfor file:\n%(5)s" // *Cause: One of the extents of the indicated file was not in use, but it // contained non-zero values. // There are two possible causes: // 1. The extent values were not reset to zero when the extent was // freed. // 2. The _NextFreeExtent property of the file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07056, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07057, 0, "extent[%(1)u] has incorrect _FileOffset\n found: %(2)s, but expected to find: 0\nfor file:\n%(3)s" // *Cause: The _FileOffset property of the initial extent of the indicated // file was not zero. The _FileOffset for a file's initial extent // must be zero as it identifies the beginning of the file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07058, 0, "file with local extents has invalid _LastExtentPointer value\n found: %(1)s, but expected to find: 0\nfor file:\n%(2)s" // *Cause: The _LastExtentPointer property of the indicated file was not // zero which is required for files with local extents. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07059, 0, "Message removed - do not reuse message number" 07060, 0, "extent[%(1)u] appears to be uninitialized\nfor file:\n%(2)s" // *Cause: An extent of the indicated file appeared to be in use, but all // of its values were zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07061, 0, "extent[%(1)u] has invalid _Length value\n found: 0, but expected to find: > 0\nfor file:\n%(2)s" // *Cause: The _Length property of an extent of the indicated file had a value // of zero. _Length values must be greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07062, 0, "extent[%(1)u] has incorrect _SnapIncarnationNumber value\n found: %(2)u maximum: %(3)u\nfor file:\n%(4)s" // *Cause: The _SnapIncarnationNumber property of the indicated file exceeded // the maximum value for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07063, 0, "extent[%(1)u] has a non-contiguous _FileOffset value\n found: %(2)s, but expected to find: %(3)s\nfor file:\n%(4)s" // *Cause: The _FileOffset property of an extent of the indicated file was not // contiguous with the _FileOffset of the previous extent. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem / Section 7000 comments above explain how this message will be used. 07064, 0, "file _AllocationSize value not equal to sum of extents\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated file was not equal // to the sum of the _Length properties of the file's extents. // There are three possible causes: // 1. The _AllocationSize value was incorrect. // 2. The _Length property of one or more of the file's extents was // incorrect. // 3. The _NextFreeExtent property of the file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07065, 0, "File_Entry_Table calculated allocation size (sum of data extents) does not match its _FileSize value\n found: %(1)s calculated: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of File_Entry_Table did not match the sum // of the file's extent _Length values. // There are two possible causes: // 1. The _Length property of one or more extents of the // File_Entry_Table was incorrect. // 2. The _FileSize property of the File_Entry_Table was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07066, 0, "extent[%(1)u] is not in use but it contains non-zero values:\n _FileOffset: %(2)s\n _Length: %(3)s\n _PhysicalDiskOffset: %(4)s\n _SnapIncarnationNumber: %(5)u\nfor file:\n%(6)s" // *Cause: One of the extents of the indicated file was not in use, but it // contained non-zero values. // There are two possible causes: // 1. The extent values were not reset to zero when the extent was // freed. // 2. The _NextFreeExtent property of the file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07067, 0, "Message removed - do not reuse message number" 07068, 0, "Message removed - do not reuse message number" 07069, 0, "Message removed - do not reuse message number" 07070, 0, "Message removed - do not reuse message number" 07071, 0, "Message removed - do not reuse message number" 07072, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07073, 0, "file has _FileEntry structure with incorrect or invalid _FileEntryType value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileEntryType property of the indicated file did not match // its expected value. // There are two possible causes: // 1. The _FileEntryType value was incorrect for this particular file. // 2. The _FileEntryType value was not on the list of valid values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07074, 0, "file has _FileEntry structure with incorrect file identifier\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The file identifier property of the indicated file did not match its // position within the File_Entry_Table entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07075, 0, "file has incorrect _FileSize value\n found: %(1)s minimum: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07076, 0, "file has invalid _AllocationSize value\n found: %(1)s minimum: %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated file was invalid. // The _AllocationSize value for this file cannot be less than // the value described in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07077, 0, "Local_Bitmap has incorrect _FileOffset value for Extent[1]\n found: %(1)s, but expected to find: 0\nfor file:\n%(2)s" // *Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap // was not zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07078, 0, "Local_Bitmap has incorrect _Length value in Extent[1]\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _Length property in Extent[1] of the indicated Local_Bitmap // did not match the file system's allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07079, 0, "Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]\n found: 0, but expected to find: > 0\nfor file:\n%(1)s" // *Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated // Local_Bitmap was equal to zero. This _PhysicalDiskOffset value // must be greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07080, 0, "Local_Bitmap has incorrect _PhysicalDiskOffset value for Extent[1]\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s" // *Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated // Local_Bitmap exceeded the size of the file system. / Section 7000 comments above explain how this message will be used. 07081, 0, "file has invalid _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor file:\n%(3)s" // *Cause: The _granularity property of the indicated system file was // incorrect. Many system files require local extents which is // indicated by a _granularity value of -1. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07082, 0, "Global_BitMap space requirement exceeds _AllocationSize value. Bitmap requires %(1)s bytes, allocated space: %(2)s bytes\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the Global_BitMap was not large // enough to store the Global_BitMap data. // There are two possible causes: // 1. The _AllocationSize value was incorrect. // 2. The value used to indicate the number of bits needed to map // file system storage was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07083, 0, "Global_BitMap has invalid _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor file:\n%(3)s" // *Cause: The _granularity property of the indicated Global_BitMap was // incorrect. The Global_BitMap file must have a _granularity value // of -1 which indicates that the file has local extents. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07084, 0, "Snap_Map has mismatch between _FileSize and _AllocationSize values\n _FileSize: %(1)s _AllocationSize: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize and _AllocationSize properties of the indicated // Snap_Map file did not match. The values for these properties // must match for a Snap_Map file. One or both values was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07085, 0, "file has _FileSize value that exceeds _AllocationSize value\n _FileSize: %(1)s _AllocationSize: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated file exceeded the amount // of storage allocated to the file. The _AllocationSize property // describes the amount of storage available for the file. One of // of these properties was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07086, 0, "file has _AllocationSize value that is invalid for the file system\n found: %(1)s, but expected to find: multiple of %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated file was incorrect. // Its value must be a multiple of the file system allocation unit // size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07087, 0, "file has _AllocationSize value but no extent information\n _AllocationSize: %(1)s\nfor file:\n%(2)s" // *Cause: The _AllocationSize property of the indicated file was greater // than 0, but there was no corresponding extent information. // There are two possible causes: // 1. The _AllocationSize should have been zero. // 2. The _NextFreeExtent value was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07088, 0, "Map_File has incorrect _FileSize value\n found: %(1)s, but expected to find: multiple of %(2)u\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated Map_File was incorrect. // The _FileSize value for a Map_File must be a multiple of the // META_MAP_ENTRY size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07089, 0, "Volume_Log has invalid _FileSize value\n found: %(1)s, but expected to find: 0\nfor file:\n%(2)s" // *Cause: The _FileSize property of the indicated Volume_Log file was not // equal to zero. The _FileSize value for a Volume_Log must be zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07090, 0, "Volume_Log has invalid _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor file:\n%(3)s" // *Cause: The _granularity property of the indicated Volume_Log file was // incorrect. Volume_Log files must have a _granularity value of -1 // which indicates that the file has local extents. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07091, 0, "Volume_Log has incorrect _NextFreeExtent value\n found: %(1)u, but expected to find: 0 or 1\nfor file:\n%(2)s" // *Cause: The _NextFreeExtent property of the indicated Volume_Log file was // incorrect. A Volume_Log file can have at most one extent. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07092, 0, "file has invalid _security_data_offset value\nfor file:\n%(1)s" // *Cause: The _security_data_offset property of the indicated file did not // have a corresponding entry in any Security_Metadata file. // There are three possible causes: // 1. The _security_data value was incorrect. // 2. The Security_Metadata file had incorrect data at the // corresponding offset. // 3. The Security_Metadata file was not found. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07093, 0, "Message removed - do not reuse message number" 07094, 0, "file has invalid _SnapMetaIncarnationNumber value\n found: %(1)u maximum: %(2)u\nfor file:\n%(3)s" // *Cause: The _SnapIncarnationNumber property of the indicated file exceeded // the maximum _SnapIncarnationNumber value for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07095, 0, "CHARACTER special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\n%(1)s" // *Cause: The major_device_number property of the indicated CHARACTER // special file was invalid. major_device_number values must be // greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07096, 0, "file has incorrect _EAOffset value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _EAOffset property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07097, 0, "file has invalid _TimeofCreation value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _TimeofCreation property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07098, 0, "file has invalid _TimeLastAccessed value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _TimeLastAccessed property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07099, 0, "file has invalid _TimeLastModified value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _TimeLastModified property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07100, 0, "file has invalid _FileSize value\n found: %(1)s minimum: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated file was invalid. The // _FileSize value for this file cannot be less than the value // described in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07101, 0, "file has invalid _TimeLastChanged value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _TimeLastChanged property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07102, 0, "file has invalid _TimeofCreation value\n found: 0\nfor file:\n%(1)s" // *Cause: The _TimeofCreation property of the indicated file was invalid. // The _TimeofCreation value must be non-zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07103, 0, "file has invalid _TimeLastAccessed value\n found: 0\nfor file:\n%(1)s" // *Cause: The _TimeLastAccessed property of the indicated file was invalid. // The _TimeLastAccessed value must be non-zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07104, 0, "file has invalid _TimeLastModified value\n found: 0\nfor file:\n%(1)s" // *Cause: The _TimeLastModified property of the indicated file was invalid. // The _TimeLastModified value must be non-zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07105, 0, "file has invalid _TimeLastChanged value\n found: 0\nfor file:\n%(1)s" // *Cause: The _TimeLastChanged property of the indicated file was invalid. // The _TimeLastChanged value must be non-zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07106, 0, "file has invalid _WindowsAttributes value(s)\n found: %(1)s\n valid values: %(2)s\nfor file:\n%(3)s" // *Cause: The _WindowsAttributes property of the indicated file was invalid. // One or more of the _WindowsAttributes values were not within the // range of valid values. Refer to the corresponding messages for // a list of valid values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07107, 0, "file has incorrect _rep_incarnation value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _repFE_incarnation_number property of the indicated file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07108, 0, "file has incorrect _rep_VFN value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _rep_VFN property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07109, 0, "file has incorrect _rep_SCN value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _rep_SCN property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07110, 0, "file has incorrect _EncrMetaOffset value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _EncrMetaOffset property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07111, 0, "file has incorrect _Vault_MetaOffset value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _Vault_MetaOffset property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07112, 0, "file has incorrect _EncrSecFlags value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _EncrSecFlags property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07113, 0, "file has incorrect _EA_ContainerUnits value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _EA_ContainerUnits property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07114, 0, " Files checked in %(1)s: %(2)d%%" / Section 7000 comments above explain how this message will be used. 07115, 0, "Local_Bitmap has incorrect _FileSize value\n found: %(1)s, but expected to find: 0\nfor file:\n%(2)s" // *Cause: The _FileSize property of the indicated Local_Bitmap was invalid. // The _FileSize value for a Local_Bitmap must be zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07116, 0, "BLOCK special file has invalid major_device_number value\n found: 0, but expected to find: > 0\nfor file:\n%(1)s" // *Cause: The major_device_number property of the indicated BLOCK special // file was invalid. major_device_number values must be greater // than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07117, 0, "Directory_Entry structure has invalid file identifier value:\n found: %(1)s maximum: %(2)s\nfor structure:\n%(3)s" // *Cause: The file identifier property of the indicated Directory_Entry // structure exceeded the maximum file identifier for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07118, 0, "System metadata file is corrupt and cannot be repaired\nfor file:\n%(1)s" // *Cause: The ACFS Checker/Fixer found an inconsistency with the // indicated system metadata file. This metadata file cannot // be repaired due to the nature of the corruption. // *Action: Restore the file system from a backup copy. / Section 7000 comments above explain how this message will be used. 07119, 0, "_Locator structure has incorrect _global_dir_blk value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _global_dir_blk property of the indicated structure was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07120, 0, "_Locator structure has invalid node identifier for entry %(1)d in _node_number array\n found: %(2)u maximum: %(3)u\nfor structure:\n%(4)s" // *Cause: A node identifier in the _node_number array of the indicated // structure that exceeded the maximum value for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07121, 0, "_Locator structure has invalid file identifier for entry %(1)d in _local_dir_blk array\n found: s%(2) maximum: %(3)s\nfor structure:\n%(4)s" // *Cause: A file identifier for a Local_Metadata_Directory in the // _local_dir_blk array of the indicated _Locator structure exceeded // the maximum file identifier for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07122, 0, "_Locator structure has incorrect _local_dir_blk_disk_offset for entry %(1)d in _local_dir_blk_disk_offset array\n found: %(2)s, but expected to find: %(3)s\nfor structure:\n%(4)s" // *Cause: The disk offset for a Local_Metadata_Directory in the // _local_dir_blk_disk_offset array of the indicated _Locator // structure was incorrect. // There are two possible causes: // 1. The _local_dir_blk_disk_offset value was incorrect. // 2. The structure at the _local_dir_blk_disk_offset was not a // Local_Metadata_Directory structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07123, 0, "_Locator structure has duplicate entries for node %(1)u\nfor structure:\n%(2)s" // *Cause: There was more than one entry for the same node within the _Locator // structure(s). Node identifies must be unique. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07124, 0, "_Locator structure has duplicate entries for Local_Metadata_Directory: %(1)s\nfor structure:\n%(2)s" // *Cause: There was more than one entry for the same Local_Metadata_Directory // within the _Locator structure(s). Local_Metadata_Directory file // identifiers must be unique. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07125, 0, "_Locator structure has incorrect _node_count value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _node_count property of the indicated _Locator structure did // not match the number of valid nodes found. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07126, 0, "_Locator structure has incorrect _next_locator_blk_disk_offset value\n found: %(1)s\nfor structure:\n%(2)s" // *Cause: The _next_locator_blk_disk_offset property of the indicated // _Locator structure was incorrect. // There are two possible causes: // 1. The _next_locator_blk_disk_offset was incorrect. // 2. The structure at the _next_locator_blk_disk_offset was not a // _Locator structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07127, 0, "Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNGroup value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repFreeVFNGroup property of the indicated // Global_Virtual_FileID_Pool structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07128, 0, "Global_Virtual_FileID_Pool structure has incorrect _repFreeVFNIncarnNum value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repFreeVFNIncarnNum property of the indicated // Global_Virtual_FileID_Pool structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07129, 0, "Replication_Log_Initiator structure has incorrect _initiator_node_id value\n found: %(1)d, but expected to find: %(2)d\nfor structure:\n%(3)s" // *Cause: The _initiator_node_id property of the indicated // Replication_Log_Initiator structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07130, 0, "Replication_Log_Initiator structure has incorrect _new_rlog_recovered value\n found: %(1)d, but expected to find: %(2)d\nfor structure:\n%(3)s" // *Cause: The _it_rep_logs_processed property of the indicated // Replication_Log_Initiator structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07131, 0, "Replication_Log_Initiator structure has incorrect _next_cord_id value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _next_cord_id property of the indicated // Replication_Log_Initiator structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07132, 0, "Replication_Log_Initiator structure has incorrect _next_segment_id value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _next_segment_id property of the indicated // Replication_Log_Initiator structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07133, 0, "Local_Bitmap has incorrect _AllocationSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated Local_Bitmap did // not match the _Length value of its first extent. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07134, 0, "invalid global_dir_fileid value\n found: %(1)s, but expected to find: %(2)s" // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07135, 0, "Global_Metadata_Directory structure has incorrect _node_number value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _node_number property of the indicated Global_Metadata_Directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07136, 0, "Global_Metadata_Directory structure has incorrect _global_free_blk_list value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _global_free_blk_list property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07137, 0, "Global_Metadata_Directory structure has incorrect _global_bitmap_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _global_bitmap_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07138, 0, "Global_Metadata_Directory structure has incorrect _SuperBlock_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _SuperBlock_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07139, 0, "Global_Metadata_Directory structure has incorrect _gdrfl_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _gdrfl_fileid property of the // indicated Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07140, 0, "Global_Metadata_Directory structure has incorrect _dotofs_dir_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _dotofs_dir_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07141, 0, "Global_Metadata_Directory structure has incorrect _ready_dir_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _ready_dir_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07142, 0, "Global_Metadata_Directory structure has incorrect _repl_config_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repl_config_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07143, 0, "Global_Metadata_Directory structure has incorrect _mmap_log_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _mmap_log_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07144, 0, "Global_Metadata_Directory structure has incorrect _repGlobalVFNPool_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repGlobalVFNPool_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07145, 0, "Global_Metadata_Directory structure has incorrect _repl_config_tbl_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repl_config_tbl_fileid property of the // indicated Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07146, 0, "Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repLogCutInitiatorBlock_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07147, 0, "Global_Metadata_Directory structure has incorrect _repLogCutInitiatorBlock_offset value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repLogCutInitiatorBlock_offset property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07148, 0, "Global_Metadata_Directory structure has incorrect _snap_map_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _snap_map_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07149, 0, "Global_Metadata_Directory structure has incorrect _snaps_dir_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _snaps_dir_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07150, 0, "Global_Metadata_Directory structure has incorrect _global_tagdir_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _global_tagdir_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07151, 0, "Global_Metadata_Directory structure has incorrect _ea_change_fileid\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _ea_change_fileid property of the indicated // Global_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07152, 0, "orphan directory '%(1)s' (file identifier: %(2)s) \nadded to 'lost+found' directory" // *Cause: The indicated directory did not have a valid entry in any parent // directory. The ACFS Fixer move the file to the 'lost+found' // directory. // *Action: No further action is needed. 07153, 0, "Message removed - do not reuse message number" 07154, 0, "An attempt to create a low-fragmentation memory heap failed.\n%(1)s will attempt to continue with the standard memory heap but may run out of memory." // *Cause: A call to the Windows HeapCreate function failed. Refer to the // accompanying message(s) for more information on the error. // *Action: No further action is required unless there is an error using the // standard memory heap. If there is an error using the standard // memory heap then refer to the accompanying message(s) for // information to resolve the problem. 07155, 0, "An attempt to initialize a low-fragmentation memory heap failed.\n%(1)s will attempt to continue with the standard memory heap but may run out of memory." // *Cause: A call to the Windows HeapSetInformation function failed. Refer // to the accompanying message(s) for more information on the // error. // *Action: The program will automatically attempt to continue with the // standard memory heap but could run out of memory. No further // action is required unless there is an error using the standard // memory heap. To use low-fragmentation heaps, refer to Microsoft // documentation on GlobalFlags values for executables that are not // compatible with low-fragmentation heaps. Then use the regedit // utility to unset those flags on the executable. / Section 7000 comments above explain how this message will be used. 07156, 0, "Local_Metadata_Directory structure has incorrect _map_file_disk_offset value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _map_file_disk_offset property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07157, 0, "Local_Metadata_Directory structure has incorrect _vol_log_disk_offset value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _vol_log_disk_offset property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07158, 0, "unable to create Security_Metadata file offset list\nfor file:\n%(1)s" // *Cause: The ACFS Checker could not create the Security_Metadata file offset // list. Refer to the accompanying message(s) for more information on // the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07159, 0, "Local_Metadata_Directory structure has incorrect _smf_fileid value \n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _smf_fileid property of the indicated Local_Metadata_Directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07160, 0, "Local_Metadata_Directory structure has incorrect _it_rlog_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _it_rlog_fileid property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07161, 0, "Local_Metadata_Directory structure has incorrect _rlog_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07162, 0, "Local_Metadata_Directory structure has incorrect _it_rmap_file_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _it_rmap_file_fileid property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07163, 0, "Local_Metadata_Directory structure has incorrect _rmap_file_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _rmap_file_fileid property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07164, 0, "Local_Metadata_Directory structure has incorrect _repLocalVFNPool_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _repLocalVFNPool_fileid property of the indicated // Local_Metadata_Directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07165, 0, "invalid file identifier: %(1)s" // *Cause: The file identifier enetered must be a valid numeric value, greater // than or equal to 0, and less than the maximum file identifier value // for the file system. // *Action: Re-enter a valid file identifier value. 07166, 0, "Message removed - do not reuse message number" / 07167, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07168, 0, "Global_BitMap has incorrect value for bitmap size\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The bitmap size property of the indicated Global_BitMap file was // incorrect. Its value did not the bitmap size that was calculated // for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07169, 0, "Global_BitMap has incorrect _AllocationSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated Global_BitMap file // was incorrect. The _AllocationSize value was not large enough to // store the Global_BitMap data as determined by the ACFS Checker. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07170, 0, "Global_BitMap has incorrect values for Extent[0]\n found: _FileOffset: %(1)s _Length: %(2)s _PhysicalDiskOffset: %(3)s\n, but expected to find: _FileOffset: %(4)s _Length: %(5)s _PhysicalDiskOffset: %(6)s\nfor file:\n%(7)s" // *Cause: The _PhysicalDiskOffset property of the first extent of the // indicated Global_BitMap file was incorrect. The Global_BitMap data // must begin at the disk offset described in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07171, 0, "attempt to read SuperBlock FileEntry failed\nfor file:\n%(1)s" // *Cause: An attempt to read SuperBlock metadata failed. Refer to the // accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / Section 7000 comments above explain how this message will be used. 07172, 0, "file has incorrect values for Extent[%(1)u] \n found: _FileOffset: %(2)s _Length: %(3)s _PhysicalDiskOffset: %(4)s \n, but expected to find: _FileOffset: %(5)s _Length: %(6)s _PhysicalDiskOffset: %(7)s \nfor file:\n%(8)s" // *Cause: One or more values of an extent of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07173, 0, "Message removed - do not reuse message number" 07174, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07175, 0, "file has incorrect values for Extent[%(1)u]\n found: _FileOffset: %(2)s _Length: %(3)s \n, but expected to find: _FileOffset: %(4)s _Length: %(5)s\nfor file: \n%(6)s" // *Cause: One or more values of an extent of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07176, 0, "file has invalid _AllocationSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _AllocationSize property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07177, 0, "file has incorrect _FileSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07178, 0, "file has incorrect _granularity value\n found: %(1)d, but expected to find: %(2)d\nfor file:\n%(3)s" // *Cause: The _granularity property of the indicated file was incorrect. // Some ACFS internal files must have a _granularity value equal to // -1 which indicates that the file has local extents. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07179, 0, "file has incorrect _NextFreeExtent value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _NextFreeExtent property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07180, 0, "UNUSED" 07181, 0, "Message removed - do not reuse message number" 07182, 0, "Message removed - do not reuse message number" 07183, 0, "Volume_Log recovery on node %(1)u not needed" 07184, 0, "Log_File not processed for node %(1)u\nfor file:\n%(2)s" // *Cause: A Log_File was found but not processed. Unprocessed Log_Files // could result in false errors being reported because transaction // data was not applied to the file system. // *Action: There are two actions possible: // 1. Run the ACFS Fixer which will automatically process all valid // Log_Files. // 2. Run the ACFS Checker and respond yes to any question pertaining // to Log_File processing. 07185, 0, "\nThere is an inconsistency between the ACFS Map_File and the ACFS Log_File. \nThe ACFS Map _FileSize: %(1)u indicates that there is transaction data \nto be processed, but the ACFS Log _AllocationSize: %(2)u indicates that \nthere is no data available. \nACFS Map_File:\n%(3)s \nACFS Log_File: \nfor file: \n%(4)s" // *Cause: An inconsistency was found between the ACFS Map and Log Files // which prevented the processing of transaction data. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07186, 0, "Volume_Log recovery running for node %(1)u\nfor file:\n%(2)s" 07187, 0, "Map_Entry: _Length: %(1)s _LogOff: %(2)s _MetaOff: %(3)s" 07188, 0, "Map_File has entry with incorrect _Length value\n found: %(1)u\nfor file:\n%(2)s" // *Cause: There are two possible causes: // 1. The Map_File entry's _Length was equal to zero. // 2. The Map_File entry's _Length was not a multiple of the volume's // sector size as detailed in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07189, 0, "Map_File has entry with incorrect _ActualDiskOffset value\n found: %(1)s minimum: %(2)s\nfor file:\n%(3)s" // *Cause: The _ActualDiskOffset property for an entry in the indicated // Map_File was incorrect. The _ActualDiskOffset value in a Map_File // entry must be greater than the previous entry's _ActualDiskOffset. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07190, 0, "Map_File has an entry with invalid _LogDiskOffset value\n found: %(1)s minimum: %(2)s maximum: %(3)s\nfor file:\n%(4)s" // *Cause: The _LogDiskOffset property for an entry in the indicated Map_File // was incorrect. The _LogDiskOffset value in a Map_File entry must // be within the corresponding Log_File data. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07191, 0, "Map_File has duplicate entries for _ActualDiskOffset:%(1)s\nfor file:\n%(2)s" // *Cause: The indicated Map_File contained more than one entry for the same // disk offset. _ActualDiskOffset values must be unique within a // Map File. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07192, 0, "Map_File has incorrect Map_Entry _Length for the Volume_Disk_Header\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _Length property for an entry in the indicated Map_File was // incorrect. The entry was for a Volume_Disk_Header structure, but // its _Length value did not match the size of a Volume_Disk_Header // structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07193, 0, "Map_File entry with an invalid _ActualDiskOffset value\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s" // *Cause: The _ActualDiskOffset property for an entry in the indicated // Map_File was incorrect. The _ActualDiskOffset value that // exceeded the size of this file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07194, 0, "Message removed - do not reuse message number" 07195, 0, "metadata write failed while processing Volume_Log transaction data at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An error occurred while writing Volume_Log transaction data to the // file system. Refer to the accompanying message(s) for // more information. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07196, 0, "write failed for Map_File metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file:\n%(4)s" // *Cause: An attempt to write a metadata structure to disk failed. Refer // to accompanying message(s) for more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07197, 0, "discarding Volume_Log and Map_File contents on node %(1)u due to processing error" // *Cause: An error occurred while processing file system transaction data. // Refer to the accompanying message(s) for more information on the // problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07198, 0, "Message removed - do not reuse message number" 07199, 0, "write failed for Volume_Log metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file:\n%(4)s" // *Cause: An attempt to update a metadata structure of the indicated // Volume_Log file failed. Refer to accompanying message(s) for // more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / 07200, 0, "UNUSED" 07201, 0, "Global_Free_Block list is corrupt" // *Cause: A metadata inconsistency was found within the Global_Free_Block // list for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07202, 0, "Free_Block_List has incorrect _free_blk_count value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _free_blk_count property of the indicated Free_Block_List was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07203, 0, "UNUSED" 07204, 0, "write failed for Global_BitMap metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file:\n%(4)s" // *Cause: An attempt to update a metadata structure of the indicated // Global_BitMap file failed. Refer to accompanying message(s) for // more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / 07205, 0, "UNUSED" 07206, 0, "read failed for Local_BitMap metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file:\n%(4)s" // *Cause: An attempt to read a metadata structure of the indicated // Local_BitMap file failed. Refer to accompanying message(s) for // more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem / 07207, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07208, 0, "Local_BitMap (file identifier: %(1)s) has incorrect size\n found: %(2)s, but expected to find: %(3)s \nfor file:\n%(4)s" // *Cause: The size property of the indicated Local_BitMap was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07209, 0, "Local_BitMap (file identifier: %(1)s) has incorrect Global_BitMap file offset: %(2)s or incorrect disk offset: %(3)s \nfor file:\n%(4)s" // *Cause: The Global_BitMap offset property of the indicated Local_BitMap // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07210, 0, "Message removed - do not reuse message number" 07211, 0, "mismatch between Local_BitMap (file identifier: %(1)s) and temporary Global_BitMap for disk offset: %(2)s" // *Cause: The bitmap data of the indicated Local_BitMap did not match the // corresponding bitmap data of the temporary Global_BitMap for the // described disk offset. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07212, 0, "temporary Global_BitMap bit set for disk offset: %(1)s exceeds maximum offset: %(2)s" // *Cause: The bitmap data of the temporary Global_BitMap referenced storage // that is beyond the size of this file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07213, 0, "Message removed - do not reuse message number" 07214, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07215, 0, "Volume_Disk_Header has invalid _VolSignature value\n found: '%(1)s'\n, but expected to find: %(2)s, %(3)s, %(4)s, or %(5)s\nfor structure:\n%(6)s" // *Cause: The _VolSignature property of the indicated Volume_Disk_Header was // not a valid ACFS volume signature. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07216, 0, "Volume_Disk_Header has incorrect _Checksum value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _Checksum property of the indicated Volume_Disk_Header did // not match its calculated value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07217, 0, "Volume_Disk_Header version does not match %(1)s version\n found: %(2)u.%(3)u, but expected to find: %(4)u.%(5)u\nfor structure:\n%(6)s" // *Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the // indicated Volume_Disk_Header did not match the version of the // ACFS Checker/Fixer or ACFS debug utility that was being used. // The ACFS Checker/Fixer or ACFS debug utility was not compatible // with this file system. // There are two possible causes: // 1. The version information in the Volume_Disk_Header structure // was not correct. // 2. The ACFS Checker/Fixer or ACFS debug utility was not the // correct version for the file system. // *Action: There are two possible actions: // 1. If the file system version displayed in the message is valid // then run a compatible version of the ACFS Checker/Fixer or // ACFS debug utility. // 2. If the file system version displayed in the message is not // valid then restore the file system from backup. 07218, 0, "Volume_Disk_Header has incorrect _VolVolumeSize value\n found: %(1)s maximum: %(2)s\n- temporarily assuming Volume Size: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header // exceeded the size of the volume. The ACFS Checker temporarily // assumed the maximum volume size during processing. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07219, 0, "Volume_Disk_Header has incorrect _VolVolumeSize value\n found: %(1)s minimum: %(2)s\n- temporarily assuming Volume Size: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header // was less than the minimum supported volume size as detailed in // the message. The ACFS Checker temporarily assumed the maximum // volume size during processing. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07220, 0, "Volume_Disk_Header has incorrect _VolClusterSize value\n found: %(1)s, but expected to find: %(2)s\n- assuming default size: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolClusterSize property of the indicated Volume_Disk_Header // was incorrect. The ACFS Checker temporarily assumed the default // value during processing. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07221, 0, "Volume_Disk_Header has incorrect _VolFETALPosition value\n found: %(1)s, but expected to find: %(2)s\n- assuming default File_Entry_Table offset: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header // was incorrect. The ACFS Checker temporarily assumed the default // File_Entry_Table offset during processing. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07222, 0, "Volume_Disk_Header has incorrect _VolOrigVolumeSize value\n found: %(1)s must be aligned on a %(2)s byte boundary\nfor structure:\n%(3)s" // *Cause: The _VolOrigVolumeSize property of the indicated Volume_Disk_Header // was incorrect. Its value must be aligned on the byte boundary // described in the message. // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07223, 0, "Volume_Disk_Header has incorrect _VolExtentHeaderSize value\n found: %(1)s, but expected to find: %(2)s\n- assuming default value: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolExtentHeaderSize property of the indicated // Volume_Disk_Header was incorrect. The ACFS Checker temporarily // assumed the default value during processing. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07224, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07225, 0, "Volume_Disk_Header has invalid _VolFileSystemEndian value\n found: %(1)c, but expected to find: %(2)s or %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolFileSystemEndian property of the indicated // Volume_Disk_Header was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07226, 0, "Volume_Disk_Header has invalid _VolStateFlag values\n found: %(1)s\n, but expected to find: %(2)s or\n, but expected to find: %(3)s\nfor structure:\n%(4)s" // *Cause: The _VolStateFlag property of the indicated Volume_Disk_Header // contained one or more invalid values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07227, 0, "UNUSED" 07228, 0, "cannot determine disk geometry for volume: %(1)s" // *Cause: The program was unable to determine the geometry of the indicated // volume. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / Section 7000 comments above explain how this message will be used. 07229, 0, "volume: %(1)s has invalid sector size\n found: %(2)u, but expected to find: %(3)u\n- assuming default value: %(4)u" // *Cause: The sector size of the indicated volume was invalid. The ACFS // Checker temporarily assumed the default sector size during // processing. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. If the problem cannot // be resolved then allow the ACFS Checker/Fixer to continue // running with the default value. 07230, 0, "cannot determine size for volume: %(1)s" // *Cause: The program was unable to determine the size of the indicated // volume. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07231, 0, "seek to end of volume failed for volume: %(1)s offset: %(2)s" // *Cause: The program was unable to seek to the end of the indicated // volume. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07232, 0, "seek to end of volume failed for volume: %(1)s\n requested offset: %(2)s returned offset: %(3)s" // *Cause: The request to seek to the end of the indicated volume failed. The // offset set returned did not match the offset requested. Refer to // the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07233, 0, "read failed for Primary Volume_Disk_Header at disk offset: %(1)s" // *Cause: An attempt to read the Primary Volume_Disk_Header at the indicated // disk offset failed. Refer to the accompanying message(s) for more // information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07234, 0, "read failed for Alternate Volume_Disk_Header at disk offset: %(1)s" // *Cause: An attempt to read the Alternate Volume_Disk_Header at the // indicated disk offset failed. Refer to the accompanying message(s) // for more information on the problem. // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07235, 0, "extent[%(1)u] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor file:\n%(2)s" // *Cause: The _PhysicalDiskOffset property of an extent structure of the // indicated file had a value of zero. _PhysicalDiskOffset values // must be greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07236, 0, "extent[%(1)u] has invalid _PhysicalDiskOffset value\n found: 0, but expected to find: greater than 0\nfor structure:\n%(2)s" // *Cause: The _PhysicalDiskOffset property of an extent of the indicated // extent structure had a value of zero. _PhysicalDiskOffset values // must be greater than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07237, 0, "read failed for File_Entry_Table extent metadata structure at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An attempt to read an extent metadata structure of the indicated // file failed. Refer to the accompanying message(s) for more // information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07238, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07239, 0, "File_Entry_Table count incorrect\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The number of entries found in the File_Entry_Table file did not // match the expected number of entries. One or more of the extent // structures was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07240, 0, "UNUSED" 07241, 0, "Security_Metadata file has invalid _security_descriptor record\nfor file:\n%(1)s" // *Cause: A _security_descriptor record of the indicated // Security_Metadata file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07242, 0, "number of Security_Metadata file records: %(1)u" 07243, 0, "Security_Metadata file has no valid _security_data records\nfor file:\n%(1)s" // *Cause: The indicated Security_Metadata file did not contain any valid // valid _security_data records. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07244, 0, "Message removed - do not reuse message number" 07245, 0, "Security_Metadata file contains invalid _security_descriptor data\nfor file:\n%(1)s" // *Cause: The indicated Security_Metadata file contained at least one invalid // _security_data record. Refer to the accompanying message(s) for // more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07246, 0, "Security_Metadata file _Private structure is invalid for:\nfor file:\n%(1)s" // *Cause: The _Private structure of the indicated Security_Metadata file // was invalid. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07247, 0, "Security_Metadata file has invalid Hash_Table data\nfor file:\n%(1)s" // *Cause: The Hash_Table of the indicated Security_Metadata file contained // inconsistent data. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07248, 0, "validation complete for Security_Metadata file Hash_Table\nfor file:\n%(1)s" 07249, 0, "validation complete for Security_Metadata file\nfor file:\n%(1)s" 07250, 0, "Security_Metadata file _Private structure has invalid _maxFree value\n found: %(1)u minimum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _maxFree property of the indicated _Private metadata structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07251, 0, "Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: %(1)u minimum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _freeDataListTail property of the indicated _Private metadata // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07252, 0, "Security_Metadata file node not on _freeDataList\nfor file:\n%(1)s" // *Cause: One or more of the _security_data nodes of the indicated // Security_Metadata file was not found on the free data node list. // The _next property for one or more of the _security_data nodes // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07253, 0, "Message removed - do not reuse message number" 07254, 0, "Security_Metadata file has invalid _security_record for _Administrator default\nfor file:\n%(1)s" // *Cause: The default _Administrator _security_record of the indicated // Security_Metadata file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07255, 0, "validation complete for Security_Metadata file _Private structure and _Administrator record\nfor file:\n%(1)s" // *Document: NO 07256, 0, "file has unexpected _ProtectionBits value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _ProtectionBits property of the indicated files was not // expected. // *Action: No action is needed if the protection bits were intentionally set // differently from the default. / 07257, 0, "UNUSED" / 07258, 0, "UNUSED" 07259, 0, "file system does not contain a valid Local_Metadata_Directory" // *Cause: There was no valid Local_Metadata_Directory in the file system. // At least one Local_Metadata_Directory is required. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07260, 0, "Volume_Disk_Header has incorrect _VolNumOFSNodes value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header // structure was incorrect. Its value did not match the number of // valid ACFS nodes found. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07261, 0, "UNUSED" / 07262, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07263, 0, "Free_Block_List has incorrect _first_free_group value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _first_free_group property of the indicated Free_Block_List // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07264, 0, "Free_Block_List has incorrect _last_free_blk value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _last_free_blk property of the indicated Free_Block_List // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07265, 0, "write failed for Free_Block metadata structure at disk offset: %(1)s size: %(2)u bytes\nfor structure:\n%(3)s" // *Cause: An attempt to write a Free_Block metadata structure to disk failed. // Refer to accompanying message(s) for more information on the // problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07266, 0, "write failed for Free_Block_List metadata structure at disk offset: %(1)s size: %(2)u bytes\nfor structure:\n%(3)s" // *Cause: An attempt to write a Free_Block_List metadata structure to disk // failed. Refer to accompanying message(s) for more information on // the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07267, 0, "file marked for deletion (file identifier: %(1)s, disk offset: %(2)s) cannot be removed due to inconsistent file metadata" // *Cause: Inconsistent metadata was found for the indicated file that was // marked for deletion. The file could not be deleted. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07268, 0, "file marked for deletion (file identifier: %(1)s, disk offset: %(2)s) has invalid _LinkCount value\n found: %(3)u, but expected to find: 0" // *Cause: The indicated file was marked for deletion, but its _LinkCount // property was not zero. Files to be deleted must have a _LinkCount // value of zero. The file could not be deleted. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07269, 0, "file marked for deletion (file identifier: %(1)s, disk offset: %(2)s) has invalid _SynchFlag value\n found: %(3)s\n, but expected to find: %(4)s" // *Cause: The _SynchFlag property of the indicated file was incorrect. The // file was marked for deletion but its _SynchFlag did not have the // appropriate value. The file could not be deleted. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07270, 0, "Message removed - do not reuse message number" 07271, 0, "orphan file : %(1)s (file identifier: %(2)s) added to 'lost+found' directory" // *Cause: The indicated file did not have a valid entry in any parent // directory. The ACFS Fixer move the file to the 'lost+found' // directory. // *Action: No further action is needed. 07272, 0, "read failed for extent metadata structure at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An attempt to read an extent metadata structure for the // indicated file failed. Refer to the accompanying message(s) for // more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07273, 0, "Message removed - do not reuse message number" / 07274, 0, "UNUSED" 07275, 0, "cannot read File_Entry_Table _FileEntry metadata structure\n- file system validation cannot continue" // *Cause: An attempt to read the _FileEntry metadata structure of the // File_Entry_Table failed. The File_Entry_Table is a critical ACFS // metadata structure that is required for file system validation // or repairs. The ACFS Checker/Fixer could not process the file // system. // NOTE: It is also possible that there was no ACFS file system on // this volume. // *Action: Correct the problem indicated by the accompanying messages if // possible and rerun the ACFS Checker/Fixer. If the problem cannot // be resolved then restore the file system from a backup copy. 07276, 0, "File_Entry_Table _FileEntry metadata structure is invalid\n- file system validation cannot continue" // *Cause: The File_Entry_Table's _FileEntry metadata structure is either // corrupt or is missing critical information. // NOTE: It is also possible that there is no ACFS file system on // the volume. // *Action: Restore the file system from a backup copy. 07277, 0, "checking File_Entry_Table for unprocessed entries" // *Document: NO 07278, 0, "Message removed - do not reuse message number" 07279, 0, "File_Entry_Table entry: %(1)s already processed" 07280, 0, "checking File_Entry_Table entry: %(1)s at disk offset: %(2)s" // *Cause: The ACFS Checker found a File_Entry_Table entry that has not been // processed. This entry was an orphan file or an orphan internal // metadata structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07281, 0, "Message removed - do not reuse message number" 07282, 0, "read failed for File_Entry_Table entry: %(1)s at disk offset %(2)s" // *Cause: An attempt to read a File_Entry_Table entry failed. Refer to the // accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07283, 0, "orphan File_Entry_Table metadata structure found for\n identifier: %(1)s at disk offset: %(2)s\n structure type: %(3)s" // *Cause: A File_Entry_Table entry was found that had not been processed. // This entry was an orphan file or an invalid internal metadata // structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07284, 0, "orphan system file found for file identifier: %(1)s at disk offset:%(2)s" // *Cause: The indicated system file did not have a valid parent directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07285, 0, "UNUSED" 07286, 0, "orphan file found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated file did not have a valid parent directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07287, 0, "orphan Free_Block metadata structure found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated Free_Block metadata structure was not found on any // free block list. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07288, 0, "orphan file '%(1)s' (file identifier: %(2)s) \nadded to 'lost+found' directory" // *Cause: The indicated file did not have a valid entry in any directory // which meant that the file did not have a valid file name. The file // was given the generic name described in the message and moved to // the 'lost+found' directory. // *Action: No further action is needed. 07289, 0, "orphan Local_Metadata_Directory metadata structure found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated Local_Metadata_Directory metadata structure was not // found on any _Locator list for Local_Metadata_Directory structures. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07290, 0, "orphan Free_List_Header metadata structure found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated Free_List_Header metadata structure was not found // on any valid Local_Metadata_Directory structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07291, 0, "orphan _Locator metadata structure found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated _Locator metadata structure was not found in any // list of valid _Locator structures. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07292, 0, "orphan Global_Metadata_Directory metadata structure found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory // metadata structure. Global_Metadata_Directory structures must be // unique. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07293, 0, "File_Entry_Table metadata structure for (file identifier: %(1)s disk offset: %(2)s) is a Reserved Block." /// *Document: NO 07294, 0, "orphan Global_Virtual_FileID_Pool metadata structure found for identifier: %(1)s at disk offset: %(2)s" // *Cause: The File_Entry_Table contained a duplicate entry for the // Global_Virtual_FileID_Pool metadata structure. // Global_Virtual_FileID_Pool structures must be unique. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07295, 0, "orphan Local_Virtual_FileID_Pool metadata structure found for identifier: %(1)s at disk offset: %(2)s" // *Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not // found on any valid Local_Metadata_Directory structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07296, 0, "orphan Replication_Log_Initiator metadata structure found for identifier: %(1)s at disk offset: %(2)s" // *Cause: The File_Entry_Table contained a duplicate entry for a // Replication_Log_Initiator metadata structure. // Replication_Log_Initiator structures must be unique. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07297, 0, "File_Entry_Table entry: %(1)s at disk offset: %(2)s is not a valid metadata structure" // *Cause: The indicated entry in the File_Entry_Table was not a metadata // structure recognized by ACFS. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07298, 0, "UNUSED" 07299, 0, "check for unprocessed File_Entry_Table entries complete" /// *Document: NO 07300, 0, "directory Hash_Table contains duplicate entries for offset: %(1)s\nfor file:\n%(2)s" // *Cause: The Hash_Table of the indicated directory file had duplicate // entries for the offset described in the message. Hash_Table // entries must map to unique offsets. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07301, 0, "directory _hash_key: %(1)s for offset: %(2)s has no corresponding file entry\nfor file:\n%(3)s" // *Cause: The _hash_key property of the indicated directory file was invalid. // Its value did not reference a valid file entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07302, 0, "directory _hash_key for offset: %(1)s is incorrect\n found: %(2)s, but expected to find: %(3)s\nfor file:\n%(4)s" // *Cause: The _hash_key property of the indicated directory file was // incorrect. Its value did not match the hash value calculated for // the corresponding file entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07303, 0, "Security_Metadata file Hash_Table contains multiple entries for offset: %(1)s\nfor file:\n%(2)s" // *Cause: The Hash_Table of the indicated Security_Metadata file had // duplicate entries for the offset described in the message. // Hash_Table entries must map to unique offsets. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07304, 0, "Security_Metadata file _hash_key: %(1)s for offset: %(2)s has no corresponding entry\nfor file:\n%(3)s" // *Cause: The _hash_key property of the indicated Security_Metadata file was // invalid. Its value did not reference a valid entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07305, 0, "Security_Metadata file _hash_key for offset: %(1)s is incorrect\n found: %(2)s, but expected to find: %(3)s\nfor file:\n%(4)s" // *Cause: The _hash_key property of the indicated Security_Metadata file // was incorrect. Its value did not match the hash value calculated // for the corresponding entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07306, 0, "Hash_Table _hash_key order is incorrect\nfor file:\n%(1)s" // *Cause: The _hash_key properties of the Hash_Table of the indicated file // were not ordered correctly. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07307, 0, "Message removed - do not reuse message number" 07308, 0, "Hash_File_Index structure for block %(1)u at disk offset: %(2)s already processed\nfor file:\n%(3)s" // *Cause: The Hash_File node list of the indicated file was invalid. // One or more of the Hash_File structures had an invalid _next // property. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07309, 0, "cannot access Hash_File_Index node metadata structure at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An attempt to access the indicated Hash_File_Index metadata // structure failed. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07310, 0, "Hash_File_Index node has incorrect _next value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _next property of the indicated Hash_File_Index structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07311, 0, "Hash_Bucket for block %(1)u at disk offset: %(2)s already processed\nfor structure:\n%(3)s" // *Cause: The Hash_Bucket structure of the indicated file has already // been processed. One or more of the Hash_File structures had an // invalid _next property. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07312, 0, "cannot access Hash_Bucket metadata structure at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An attempt to access the indicated Hash_Bucket metadata structure // failed. Refer to the accompanying message(s) for more information // on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07313, 0, "Hash_Bucket has incorrect _controlling_bkt value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _controlling_bkt property of the indicated Hash_Bucket // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07314, 0, "Hash_Bucket has incorrect _split_count value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _split_count property of the indicated Hash_Bucket structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07315, 0, "Hash_Bucket has incorrect _next value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _next property of the indicated Hash_Bucket structure was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07316, 0, "cannot access Hash_File_Master_Block metadata structure at disk offset: %(1)s\nfor file:\n%(2)s" // *Cause: An attempt to access the indicated Hash_File_Master_Block metadata // structure failed. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07317, 0, "Hash_File metadata structure for block:%(1)u at disk offset: %(2)s already processed\nfor file:\n%(3)s" // *Cause: The list of nodes of the indicated Hash_File file was invalid. One // or more of the Hash_File structures had an invalid _next property. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07318, 0, "Hash_File_Master_Block structure has incorrect _initial_bkt_count value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _initial_bkt_count property of the indicated // Hash_File_Master_Block structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07319, 0, "Hash_File_Master_Block structure has incorrect _double_count value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _double_count property of the indicated Hash_File_Master_Block // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07320, 0, "Hash_File_Master_Block structure has incorrect value for entry %(1)u in _hash_bucket_group array\n found: %(2)u, but expected to find: %(3)u\nfor structure:\n%(4)s" // *Cause: The entry in _hash_bucket_group array of the indicated // Hash_File_Master_Block was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07321, 0, "_hash_entry %(1)u has no corresponding entry\nfor file:\n%(2)s" // *Cause: The _hash_entry property in the Hash_Table of the indicated file // did not have a valid entry associated with it. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07322, 0, "metadata read failed at disk offset: %(1)s size: %(2)u bytes\nfor file:\n%(3)s" // *Cause: An attempt to read metadata of the indicated file failed. Refer to // the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07323, 0, "Message removed - do not reuse message number" 07324, 0, "Message removed - do not reuse message number" 07325, 0, "Message removed - do not reuse message number" 07326, 0, "metadata read failed at disk offset: %(1)s\n bytes requested: %(2)u bytes returned: %(3)u\nfor file:\n%(4)s" // *Cause: An attempt to read metadata of the indicated file failed. The // amount of data returned did not match the amount requested. Refer // to the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07327, 0, "metadata write failed at disk offset: %(1)s size: %(2)u bytes\nfor file:\n%(3)s" // *Cause: An attempt to write metadata of the indicated file failed. Refer // to accompanying message(s) for more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07328, 0, "Message removed - do not reuse message number" 07329, 0, "Message removed - do not reuse message number" 07330, 0, "Message removed - do not reuse message number" 07331, 0, "metadata write failed at disk offset: %(1)s\n bytes requested: %(2)u bytes written: %(3)u\nfor file:\n%(4)s" // *Cause: An attempt to write metadata of the indicated file failed. The // amount of data written did not match the amount requested. Refer // to the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07332, 0, "UNUSED" / 07333, 0, "UNUSED" / 07334, 0, "UNUSED" 07335, 0, "Directory_Node has invalid _dir_entry_free_list_tail value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _dir_entry_free_list_tail property of the indicated // Directory_Node structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07336, 0, "Directory_Node structure has invalid _next_free_dirnode value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _next_free_dirnode property of the indicated Directory_Node // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07337, 0, "Directory_Entry structure has incorrect file identifier for file '%(1)s'\n found: %(2)s, but expected to find: %(3)s\nfor structure:\n%(4)s" // *Cause: The file identifier property of the indicated Directory_Entry // structure did not match the file identifier of the corresponding // file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07338, 0, "Directory_Entry structure has incorrect _rec_len value for file '%(1)s'\n found: %(2)u, but expected to find: %(3)u\nfor structure:\n%(4)s" // *Cause: The _rec_len property of the indicated Directory_Entry structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07339, 0, "Directory_Entry structure has incorrect _name_len value for file '%(1)s'\n found: %(2)u, but expected to find: %(3)u\nfor structure:\n%(4)s" // *Cause: The _name_len property of the indicated Directory_Entry structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07340, 0, "Directory_Entry structure has invalid or incorrect _attributes for file '%(1)s'\n found: %(2)s\n, but expected to find: %(3)s\nfor structure:\n%(4)s" // *Cause: The _attributes property of the indicated Directory_Entry structure // did not match the _attributes property of the corresponding file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07341, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07342, 0, "Directory_Entry structure has incorrect filename for file\n found: '%(1)s', but expected to find: '%(2)s'\nfor structure:\n%(3)s" // *Cause: The filename property of the indicated Directory_Entry structure // did not match the name of the file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07343, 0, "unused Directory_Entry structure has incorrect _name_len value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _name_len property of the indicated Directory_Entry structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07344, 0, "Directory_Entry structure has incorrect _rec_len value for file '%(1)s'\n found: %(2)u maximum: %(3)d\nfor structure:\n%(4)s" // *Cause: The _rec_len property of the indicated Directory_Entry structure // was greater than the maximum value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07345, 0, "Directory_Entry structure has incorrect _rec_len value for file '%(1)s'\n found: %(2)u minimum: %(3)d\nfor structure:\n%(4)s" // *Cause: The _rec_len property of the indicated Directory_Entry structure // was less than the minimum value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07346, 0, "Directory_Entry structure has invalid _name_len value\n found: %(1)u operating system maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _name_len property of the indicated Directory_Entry structure // was greater than the maximum value for this operating system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07347, 0, "Directory_Entry structure has incorrect _name_len value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _name_len property of the indicated Directory_Entry structure // was greater than the maximum value for this entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07348, 0, "checking file '%(1)s%(2)s'" 07349, 0, "Message removed - do not reuse message number" / 07350, 0, "UNUSED" / 07351, 0, "UNUSED" 07352, 0, "snapshot directory contains files with incorrect attributes; attempting to continue processing" // *Cause: The _attributes property for a file in the indicated snapshot // directory was incorrect. The _attributes value indicated that the // file was not a directory. All files in a snapshot directory must // be directories. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07353, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07354, 0, "file has incorrect or invalid _attributes value\n found: %(1)s\n, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _attributes property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07355, 0, "UNUSED" 07356, 0, "file is a symbolic link but has no storage for the target name \nfor file:\n%(1)s" // *Cause: The indicated file was a symbolic link but did have a target. The // target of a symbolic link must have storage. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07357, 0, "Message removed - do not reuse message number" 07358, 0, "Message removed - do not reuse message number" 07359, 0, "Message removed - do not reuse message number" 07360, 0, "deleting file due to invalid _attributes: %(1)s\nfile:\n%(2)s" // *Cause: The _attributes property of the indicated file was invalid. The // file must be deleted in order to preserve the integrity of the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07361, 0, "truncating file '%(1)s' to %(2)u bytes\nfor file:\n%(3)s" // *Cause: The indicated file was truncated in order to preserve file system // integrity. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07362, 0, "\n\nPlease supply the following output to Oracle support.\n\nUnfixed errors: \n\n" // *Document: NO / 07363, 0, "UNUSED" 07364, 0, "file has incorrect values for Extent[%(1)u]\n found: _Length: %(2)s _PhysicalDiskOffset: %(3)s\n, but expected to find: _Length: %(4)s _PhysicalDiskOffset: %(5)s\nfor file:\n%(6)s" // *Cause: One or more or the extent properties of the indicated file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07365, 0, "extent metadata structure has incorrect values for Extent[%(1)u]\n found: _FileOffset: %(2)s _Length: %(3)s _PhysicalDiskOffset: %(4)s \n, but expected to find: _FileOffset: %(5)s _Length: %(6)s _PhysicalDiskOffset: %(7)s \nfor structure:\n%(8)s" // *Cause: One or more properties of the indicated extent metadata structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07366, 0, "directory has incorrect _attributes value\n found: %(1)s\n, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _attributes property of the indicated directory file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07367, 0, "UNUSED" 07368, 0, "checking directory:\nfor file:\n%(1)s" 07369, 0, "directory has invalid _FileSize value\n found: %(1)u minimum: %(2)u\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated directory file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07370, 0, "directory has invalid _FileSize: %(1)s _AllocationSize: %(2)s values\nfor file:\n%(3)s" // *Cause: The _FileSize and _AllocationSize properties of the indicated // directory file were incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07371, 0, "Message removed - do not reuse message number" 07372, 0, "Message removed - do not reuse message number" 07373, 0, "Message removed - do not reuse message number" 07374, 0, "cannot access directory _Private structure for block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s" // *Cause: An attempt to access the indicated directory _Private metadata // structure failed. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07375, 0, "directory _Private structure at disk offset: %(1)s contains invalid data\nfor file:\n%(2)s" // *Cause: The _Private structure of the indicated directory file contained // invalid data. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07376, 0, "directory _Private structure has incorrect header type at disk offset: %(1)s, this file may not be a directory\n found: %(2)s, but expected to find: %(3)s\nfor file:\n%(4)s" // *Cause: The indicated file did not contain a _Private directory metadata // structure as required for directory files. It appeared that the // file was incorrectly identified as being a directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07377, 0, "directory has invalid node list\nfor file:\n%(1)s" // *Cause: The node list of the indicated directory file was invalid. // There are three possible causes: // 1. One or more of the file's directory structures had an invalid // structure header. // 2. The _next_dirnode property of one or more of the file's // directory structures was incorrect. // 3. The _first_dirnode property of the _Private directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07378, 0, "directory _Private structure has incorrect _last_dirnode value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _last_dirnode property of the indicated _Private directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07379, 0, "directory has invalid free block list\nfor file:\n%(1)s" // *Cause: The free block list of the indicated directory file was invalid. // There are three possible causes: // 1. One or more of the file's directory structures had an invalid // structure header. // 2. The _next_free_dirnode property of one or more of the file's // directory structures was incorrect. // 3. The _dir_entry_free_list_head property of the _Private directory // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07380, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07381, 0, "directory _Private structure has incorrect _dir_entry_free_list_tail value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _ dir_entry_free_list_tail property of the indicated _Private // directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07382, 0, "directory has invalid hash block free list; invalid reference for free hash block\n found: %(1)u maximum: %(2)u\nfor file:\n%(3)s" // *Cause: The hash block free list of the indicated directory file was // invalid. // There are two possible causes: // 1. The _hash_blk_free_list property of the _Private directory // structure referenced a block that exceeded the directory's // size. // 2. The _next_free_blk property of a directory free block referenced // a block that exceeded the directory's size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07383, 0, "directory has invalid hash block free list\nfor file:\n%(1)s" // *Cause: The free hash block list of the indicated directory file was // invalid. // There are three possible causes: // 1. One or more of the file's directory structures had an invalid // structure header. // 2. The next_free_blk property of one or more of the file's // directory structures was incorrect. // 3. The hash_blk_free_list property of the _Private // directory structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / 07384, 0, "UNUSED" 07385, 0, "directory has orphan Directory_Node metadata structure for block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s" // *Cause: The indicated directory file had a Directory_Node metadata // structure that was not found on any directory node list. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07386, 0, "directory has incorrect _FileSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated directory file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07387, 0, "Message removed - do not reuse message number" 07388, 0, "directory contains invalid _Private structure for block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s" // *Cause: A _Private metadata structure of the indicated directory file // was found in the wrong block. _Private metadata structures must // be located at block one of a directory's metadata. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07389, 0, "directory has orphan free block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s" // *Cause: The indicated directory file had a free block that was not found // on the directory's free list. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07390, 0, "Message removed - do not reuse message number" 07391, 0, "directory has invalid metadata structure %(1)s type for block %(2)u at disk offset: %(3)s\nfor file:\n%(4)s" // *Cause: The structure found at the block of the indicated directory file // was not a valid directory metadata structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07392, 0, "Directory_Entry has incorrect or invalid _attributes value\n found: %(1)s\n, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _attributes property of the indicated Directory_Entry was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07393, 0, "Message removed - do not reuse message number" 07394, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07395, 0, "directory has incorrect or invalid _attributes values\n found: %(1)s\n, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The _attributes property of the indicated directory file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07396, 0, "directory has incorrect Hash_Table data\nfor file:\n%(1)s" // *Cause: The Hash_Table of the indicated directory file contained // inconsistent data. Refer to the accompanying message(s) for more // information on the problem. // *Action: Correct the problem described in the accompanying messages if // // possible and rerun the ACFS Checker/Fixer. 07397, 0, "Message removed - do not reuse message number" 07398, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07399, 0, "directory has incorrect _LinkCount value\n found: %(1)u, but expected to find: %(2)u\nfor file:\n%(3)s" // *Cause: The _LinkCount property of the indicated directory file was // incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07400, 0, "UNUSED" 07401, 0, "write failed for Deferred_Remove_File_List metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file:\n%(4)s" // *Cause: An attempt to write metadata on the indicated file failed. Refer // to accompanying message(s) for more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07402, 0, "Deferred_Delete_Storage_List structure has invalid delete list pointers: _PrevDeferredListLink: %(1)s _NextDeferredListLink: %(2)s\nfor structure:\n%(3)s" // *Cause: The _PrevDeferredListLink or _NextDeferredListLink property of // of the indicated structure were incorrect. Both values must be // zero or non-zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07403, 0, "write failed for Deferred_Remove_Storage_List metadata structure at disk offset: %(1)s size: %(2)u bytes\nstructure type: %(3)s \nfor file: \n%(4)s" // *Cause: An attempt to write metadata of the indicated failed. Refer // to accompanying message(s) for more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07404, 0, "Message removed - do not reuse message number" 07405, 0, "Message removed - do not reuse message number" 07406, 0, "Message removed - do not reuse message number" / 07407, 0, "UNUSED" / 07408, 0, "UNUSED" 07409, 0, "checking primary file system" 07410, 0, "attempting to continue processing" 07411, 0, "snapshot metadata checking will be limited due to an error reading snapshot metadata" // *Cause: An attempt to read snapshot metadata failed. Snapshot validation // was limited since not all snapshot metadata was not available. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07412, 0, "UNUSED" 07413, 0, "unable to create internal structure needed for processing" // *Cause: Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07414, 0, "UNUSED" / 07415, 0, "UNUSED" 07416, 0, "file has invalid _FileSize value\n found: %(1)u minimum: %(2)u\nfor file:\n%(3)s" // *Cause: The _FileSize property of the indicated file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07417, 0, "Snap_Map_Header structure has invalid _snap_incarnation values; _SnapHighestActiveIncarnNumber: %(1)u must be less than _SnapNextIncarnationNumber: %(2)u\nfor structure:\n%(3)s" // *Cause: One or both of the _SnapHighestActiveIncarnNumber and // _SnapNextIncarnationNumber properties of the indicated // Snap_Map_Header metadata structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07418, 0, "Snap_Map_Header structure has invalid _SnapCreatePending value\n found: %(1)u, but expected to find: %(2)u or < %(3)u\nfor structure:\n%(4)s" // *Cause: The _SnapCreatePending property of the indicated Snap_Map_Header // metadata structure was incorrect. The _SnapCreatePending value // must be zero or less than the value indicated in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07419, 0, "Snap_Map_Header structure has invalid _SnapDeletePending value\n found: %(1)u, but expected to find: %(2)u or < %(3)u\nfor structure:\n%(4)s" // *Cause: The _SnapDeletePending property of the indicated Snap_Map_Header // metadata structure was incorrect. The _SnapDeletePending value // must be zero or less than the value indicated in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07420, 0, "found partially created snapshot for snapshot: '%(1)s'" // *Cause: Initialization of the indicated snapshot did not complete. // There are two possible causes: // 1. The volume went offline while the snapshot was being created. // 2. The process creating the snapshot was unexpectedly terminated // do to a shutdown of the system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. // The ACFS Fixer will remove this snapshot. 07421, 0, "found partially deleted snapshot" // *Cause: A snapshot was not completely deleted. // There are several possible causes: // 1. The volume was unmounted before the asynchronous phase of // snapshot deletion had completed. // 2. The volume went offline while the snapshot was being deleted. // 3. The process deleting the snapshot was unexpectedly terminated // do to a shutdown of the system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. // The ACFS Fixer will remove this snapshot. 07422, 0, "Message removed - do not reuse message number" 07423, 0, "snapshot '%(1)s' has invalid file identifier\n found: %(2)s maximum: %(3)s\nfor structure:\n%(4)s" // *Cause: The file identifier property of the indicated snapshot was invalid. // Its value exceeded the maximum value for the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07424, 0, "snapshot '%(1)s' has invalid _SnapIncarnationNumber value\n found: %(2)u maximum: %(3)u\nfor structure:\n%(4)s" // *Cause: The _SnapIncarnationNumber property of the indicated snapshot was // invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07425, 0, "snapshot (snapid: %(1)u) has invalid name: '%(2)s'\nfor structure:\n%(3)s" // *Cause: The name of indicated snapshot contained invalid characters. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07426, 0, "snapshot '%(1)s' has invalid _SnapVisibility value\n found: %(2)u, but expected to find: %(3)u or %(4)u\nfor structure:\n%(5)s" // *Cause: The _SnapVisibility property of the indicated snapshot was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07427, 0, "duplicate _SnapIncarnationNumber: %(1)u found for snapshots '%(2)s' and '%(3)s'" // *Cause: The _SnapIncarnationNumber property of the indicated snapshots // had the same value. _SnapIncarnationNumber values must be unique // across all snapshots. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer will delete the second snapshot. 07428, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07429, 0, "Snap_Map_Header structure has incorrect _SnapCount value\n found: %(1)u, but expected to find: %(2)u\nfor structure:\n%(3)s" // *Cause: The _SnapCount property of the indicated Snap_Map_Header metadata // structure was incorrect. The _SnapCount value did not match the // number of valid snapshots found. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07430, 0, "cannot determine free space for volume associated with directory '%(1)s'; attempting to continue with current directory '%(2)s'" // *Cause: A temporary file is needed to store information during processing. // This file was targeted for the indicated directory. The ACFS // Checker was unable to determine the mount of space available for // the volume associated with the directory. Refer to the accompanying // message(s) for more information on the problem. // *Action: No further action is needed. The ACFS Checker/Fixer will attempt to // continue processing with the current directory. 07431, 0, "cannot determine free space for volume associated with current directory '%(1)s'" // *Cause: A temporary file is needed to store information during processing. // This file was targeted for the current directory. The ACFS // Checker was unable to determine the mount of space available for // the volume associated with the directory. Refer to the accompanying // message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07432, 0, "insufficient space available to store temporary file in\ndirectory '%(1)s' or directory '%(2)s'\nspace needed: %(3)u bytes\n- unable to continue" // *Cause: A temporary file is needed to store information during processing // but there was not enough space to store the file in either of the // The size of this file is dependent on the size of the file system. // indicated directories. // *Action: Provide sufficient space as described in the message to store the // the temporary file in either of the indicated directories. Rerun // the ACFS Checker/Fixer once there is sufficient storage to store // the temporary file. 07433, 0, "Message removed - do not reuse message number" 07434, 0, "creating temporary file '%(1)s'" 07435, 0, "invalid path name length for temporary file\n length: %(1)u minimum: %(2)u maximum: %(3)u" // *Cause: The path name for a temporary file does not exist or its length // exceeds the maximum for this system. Refer to the accompanying // message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07436, 0, "%(1)s has encountered an internal error: invalid parameter passed to fb_create" // *Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an // unexpected, internal error. // *Action: Contact Oracle Support Services. 07437, 0, "%(1)s has encountered an internal error: invalid parameter passed to fb_ref\n disk offset: %(2)s size: %(3)s fbSize: %(4)s fbCacheSize: %(5)s" // *Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an // unexpected, internal error. // *Action: Contact Oracle Support Services. 07438, 0, "file has storage allocated to it that is also allocated to another file\nfor file:\n%(1)s" // *Cause: Storage allocated to the indicated file was also allocated to at // least one other file. Storage can only be allocated to a single // file. Storage can never be allocated to multiple files. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07439, 0, "Snapshot_BitMap conflicts with the Global_BitMap for disk offset: %(1)s" // *Cause: One or more snapshot bitmaps claimed storage that was also claimed // by the Global_BitMap. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. // The ACFS Fixer will remove all snapshots whose bitmap conflicts // with the Global_BitMap. 07440, 0, "Snapshot_BitMap has bit set for non-existing snapshot for disk offset: %(1)s" // *Cause: One or more bitmaps reserved for unused snapshot incorrectly // claimed storage. Bitmaps for snapshots that are not in use cannot // claim any storage. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07441, 0, "Snapshot_BitMap has bits set for storage at disk offset: %(1)s that is beyond the file system size" // *Cause: One or more snapshot bitmaps incorrectly claimed storage that // exceeded the size of the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07442, 0, "UNUSED" 07443, 0, "Global_BitMap has invalid value for number of bits set\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s" // *Cause: The Global_BitMap property that indicates the number of bits set // exceeded the size of the bitmap. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07444, 0, "Global_BitMap has invalid value for number of bits set\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The Global_BitMap property that indicates the number of bits set // did not match the amount of storage allocated to all valid files. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07445, 0, "UNUSED" 07446, 0, "mismatch between temporary Global_BitMap and on-disk Global_BitMap" // *Cause: The temporary Global_BitMap that was populated by traversing all // valid file system data did not match the on-disk copy of the // Global_BitMap. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07447, 0, "UNUSED" / 07448, 0, "UNUSED" 07449, 0, "snapshot '%(1)s' storage bitmap is incorrectly set for disk offset: %(2)s" // *Cause: The bitmap of the indicated snapshot claimed storage that was // allocated to allocated file. Storage can only be allocated to a // single file. Storage can never be allocated to multiple files. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. // The ACFS Fixer will remove this snapshot. 07450, 0, "snapshot '%(1)s' storage bitmap is not set for disk offset: %(2)s" // *Cause: The bitmap of the indicated snapshot did not claim storage that // was allocated to one of its files. A snapshot's bitmap must claim // all storage allocated to its files. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. // The ACFS Fixer will remove this snapshot. 07451, 0, "snapshot '%(1)s' storage bitmap is incorrectly set for disk offset: %(2)s with no corresponding file data" // *Cause: The bitmap of the indicated snapshot claimed storage but the // storage was not allocated to any file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07452, 0, "unable to locate directory for snapshot '%(1)s' (id: %(2)u)\n processing will continue for other snapshots" // *Cause: The directory of the indicated snapshot was not found. This // snapshot could not be processed. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07453, 0, "Snap_Root_Directory file identifier for snapshot '%(1)s' was incorrect\n found: %(2)s, but expected to find: %(3)s\n- attempting to continue processing\nfor structure:\n%(4)s" // *Cause: The Snap_Root_Directory file identifier property of the indicated // snapshot was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07454, 0, "checking snapshot '%(1)s', %(2)u of %(3)u snapshots" 07455, 0, "unable to open file: '%(1)s'" // *Cause: An attempt to open a file failed. Refer to the accompanying // message(s) for more information on the error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07456, 0, "UNUSED" 07457, 0, "Message removed - do not reuse message number" 07458, 0, "The request to cancel %(1)s was incomplete because volume %(2)s was not accessible. The file system cannot be mounted in this state.\nRerun %(3)s once the volume is accessible to enable file system mounts." // *Cause: The ACFS Checker/Fixer could not reset the volume to allow for // file system mounts because the volume was not accessible. Refer // to the accompanying message(s) for more information on the error. // *Action: Rerun the ACFS Checker/Fixer once the volume is accessible to // enable file system mounts. 07459, 0, "Volume_Label metadata structure has invalid _VolLabelLength value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _VolLabelLength property of the indicated Volume_Label metadata // structure exceeded the maximum value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07460, 0, "Volume_Label metadata structure has invalid _VolIDLength value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _VolIDLength property of the indicated Volume_Label metadata // structure exceeded the maximum value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07461, 0, "Volume_Label metadata structure has invalid _ClusterNameLength value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _ClusterNameLength property of the indicated Volume_Label // metadata structure exceeded the maximum value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07462, 0, "file has incorrect or invalid _attributes values\n found: %(1)s\n valid values: %(2)s\nfor file:\n%(3)s" // *Cause: The _attributes property of the indicated file contained invalid // and/or incorrect values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07463, 0, "UNUSED" 07464, 0, "file has invalid _attributes value\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The _attributes property of the indicated file contained invalid // values. These values are not supported on Windows systems. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07465, 0, "file has _attributes set that are mutually exclusive\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The _attributes property of the indicated file describe more than // one type of file. File types are mutually exclusive. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07466, 0, "file has no _attributes value\nfor file:\n%(1)s" // *Cause: The _attributes property of the indicated file did not describe // a file type. The _attributes property must describe a valid file // type. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07467, 0, "metadata structure has a non-zero value for field: %(1)s\nfor structure:\n%(2)s" // *Cause: The indicated ACFS metadata structure had a reserved or unused // field that contained a non-zero value. The field was overwritten // or was not initialized correctly. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07468, 0, "file has invalid _SynchFlags value\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The _SynchFlags property of the indicated file contained values // that were not within the range of valid values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07469, 0, "file cannot be modified; _SynchFlag value:\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The indicated file had an internal inconsistency that prevented it // from being modified. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07470, 0, "file cannot be accessed; _SynchFlag value:\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The indicated file had an internal inconsistency that prevented it // from being accessed. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07471, 0, "file incorrectly marked for deletion with _SynchFlag value:\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The _SynchFlag property of the indicated file incorrectly identified // the file as marked for deletion while it was still part of a valid // directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07472, 0, "Message removed - do not reuse message number" 07473, 0, "Message removed - do not reuse message number" / Section 7000 comments above explain how this message will be used. 07474, 0, "invalid program name\n found: %(1)s, but expected to find: %(2)s or %(3)s" // *Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a // value that is not recognized. // *Action: Rename the program to the corresponding value listed in the // message and rerun the program. 07475, 0, "attempting to continue with standard memory heap" 07476, 0, "temporary directory '%(1)s'" 07477, 0, "current directory '%(1)s'" 07478, 0, "Oracle ASM Cluster File System (ACFS) On-Disk Structure Version: %(1)u.%(2)u" 07479, 0, "*****************************" 07480, 0, "********** Pass: %(1)u **********" 07481, 0, "An I/O error occurred while reading ACFS metadata, some snapshot metadata checks will not be performed." // *Cause: The I/O error prevented full snapshot checking because required // ACFS metadata was not available. Refer to the accompanying // message(s) for more information on the error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07482, 0, "UNUSED" / 07483, 0, "UNUSED" 07484, 0, "valid ACFS volume path name required" // *Cause: A valid volume path name was not entered. // *Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS // volume path name as the final argument. 07485, 0, "unable to determine temporary directory" // *Cause: An attempt to determine the system's temporary directory failed. // For UNIX systems this directory is either "/usr/tmp" or "/tmp". // For Windows systems this directory is the system's temporary folder. // Refer to the accompanying message(s) for more information on the // error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07486, 0, "unable to determine current directory" // *Cause: An attempt to determine the current directory failed. Refer to // the accompanying message(s) for more information on the error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07487, 0, "unable to open volume: '%(1)s'" // *Cause: An attempt to open a volume failed. Refer to the accompanying // message(s) for more information on the error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07488, 0, "This volume is now in a mountable state. \nThe file system was not checked before changing the volume's state. \nUse of this file system may encounter serious errors since it has \nnot been checked." // *Cause: The volume was forced into a mountable state without checking // the integrity of the file system. The file system may contain // incorrect or invalid data. // *Action: Run the ACFS Checker/Fixer before attempting to mount the file // system. 07489, 0, "maximum number of passes: %(1)u exceeded, program terminating" // *Cause: There are two possible causes: // 1. There is a problem with the file system that the ACFS Fixer // cannot repair. // 2. The ACFS Fixer has encountered an internal problem. // *Action: Contact Oracle Support Services. / 07490, 0, "UNUSED" 07491, 0, "%(1)s: Checker/Fixer completed with the following results:\n File System Errors: %(2)u\n Fixed: %(3)u\n Not Fixed: %(4)u" // *Document: NO 07492, 0, "Checker completed with no errors." // *Document: NO 07493, 0, "File: '%(1)s%(2)s'\n file identifier: %(3)s disk offset: %(4)s" // *Document: NO 07494, 0, "ACFS Internal File: %(1)s%(2)s\n file identifier: %(3)s disk offset: %(4)s" // *Document: NO 07495, 0, "ACFS Internal Structure: %(1)s%(2)s\n file identifier: %(3)s disk offset: %(4)s" // *Document: NO 07496, 0, "Parent Directory: %(1)s%(2)s\n file identifier: %(3)s disk offset: %(4)s" // *Document: NO 07497, 0, "Parent Structure: %(1)s%(2)s\n file identifier: %(3)s disk offset: %(4)s" // *Document: NO 07498, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor file:\n%(4)s" // *Cause: The _Length property of an extent structure of the indicated file // was invalid. _Length values must be a multiple of the file system // allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07499, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor structure:\n%(4)s" // *Cause: The _Length property of an extent of the indicated extent structure // was invalid. _Length values must be a multiple of the file system // allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07500, 0, "extent[%(1)u] has invalid _FileOffset value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor file:\n%(4)s" // *Cause: The _FileOffset property of an extent structure of the indicated // file was invalid. _FileOffset values must be a multiple of the file // system allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07501, 0, "extent[%(1)u] has invalid _FileOffset value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor structure:\n%(4)s" // *Cause: The _FileOffset property of an extent of the indicated extent // structure was invalid. _FileOffset values must be a multiple of the // file system allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07502, 0, "extent[%(1)u] has invalid _PhysicalDiskOffset value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor file:\n%(4)s" // *Cause: The _PhysicalDiskOffset property of an extent structure of the // indicated file was invalid. _PhysicalDiskOffset values must be a // multiple of the file system allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07503, 0, "extent[%(1)u] has invalid _PhysicalDiskOffset value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor structure:\n%(4)s" // *Cause: The _PhysicalDiskOffset property of an extent of the indicated // extent structure was invalid. _PhysicalDiskOffset values must be a // multiple of the file system allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / 07504, 0, "UNUSED" 07505, 0, "metadata structure read failed at disk offset: %(1)s for structure: %(2)s" // *Cause: An attempt to read the indicated metadata structure at the // described disk offset failed. Refer to the accompanying message(s) // for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the program. 07506, 0, " Value Found Expected Value" 07507, 0, " ------------------------ ------------------------" 07508, 0, " File Identifier: %(1)-28s %(2)s" 07509, 0, " File Identifier: %(1)-28s %(2)s\n %(3)-28s %(4)s" 07510, 0, " Struct_Type: %(1)-28s %(2)s\n %(3)-28s %(4)s" 07511, 0, " Endian_Format: %(1)-28s %(2)s" 07512, 0, " OSCreatedOn: %(1)-28s %(2)s" 07513, 0, " Struct_Version: %(1)-28u %(2)u" 07514, 0, " FileSystemID: %(1)-28s %(2)s" 07515, 0, " CheckSum: %(1)-28s %(2)s\n" //07516 - reserved for future on-disk header info //07517 - reserved for future on-disk header info //07518 - reserved for future on-disk header info / [07519 - 07533], 0, "UNUSED" 07534, 0, "request for disk offset: %(1)s exceeds the size for this file system: %(2)s" // *Cause: A request was made for a disk offset that exceeded the size of the // file system. // *Action: Reenter the command with a disk offset that is within the limits // of the file system. / [07535 - 07552], 0, "UNUSED" 07553, 0, "Message removed - do not reuse message number" / [07554 - 07568], 0, "UNUSED" 07569, 0, "Message removed - do not reuse message number" / 07570, 0, "UNUSED" / 07571, 0, "UNUSED" / 07572, 0, "UNUSED" / 07573, 0, "UNUSED" / 07574, 0, "UNUSED" 07575, 0, "command takes no arguments" // *Cause: The command entered does not take any arguments. // *Action: Reenter the command with no arguments. / 07576, 0, "UNUSED" / 07577, 0, "UNUSED" / 07578, 0, "UNUSED" / 07579, 0, "UNUSED" 07580, 0, "Message removed - do not reuse message number" / 07581, 0, "UNUSED" / 07582, 0, "UNUSED" / 07583, 0, "UNUSED" / 07584, 0, "UNUSED" 07585, 0, "unable to set File_Entry_Table context" // *Cause: The ACFS Debug utility was not able to set the File_Entry_Table // context. Lookups by file identifier were disabled. Refer to the // accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible by rerunning the ACFS Fixer. 07586, 0, "Do you want to continue [y|n] ?" // *Cause: The ACFS Checker/Fixer or Debug utility detected a situation // that could leave the file system in an inconsistent or unusable // state. Refer to the corresponding error message for more // information. // *Action: Respond Y(yes) to proceed or N(no) to cancel. 07587, 0, "metadata read at disk offset: %(1)s size: %(2)s bytes" // *Document: NO 07588, 0, "metadata read failed at disk offset: %(1)s size: %(2)s bytes \n- cannot read beyond file system size: %(3)s" // *Cause: An attempt to read metadata failed because the data requested was // beyond the size of the file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07589, 0, "metadata write at disk offset: %(1)s size: %(2)s bytes" // *Document: NO 07590, 0, "metadata write failed at disk offset: %(1)s size: %(2)s bytes\n- cannot write beyond file system size: %(3)s" // *Cause: An attempt to write metadata failed because the write location was // beyond the size of the file system. // *Action: The ACFS Fixer will resolve the problem. No further action is // needed. 07591, 0, "Message removed - do not reuse message number" 07592, 0, "metadata structure has incorrect header for:\n%(1)s" // *Cause: One or more properties of the header of the indicated metadata // structure contained invalid or incorrect values. Refer to // accompanying messages for more information on the error. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07593, 0, "Message removed - do not reuse message number" 07594, 0, "Message removed - do not reuse message number" 07595, 0, "Message removed - do not reuse message number" 07596, 0, "Message removed - do not reuse message number" 07597, 0, "Message removed - do not reuse message number" / 07598, 0, "UNUSED" 07599, 0, "Message removed - do not reuse message number" / 07600, 0, "UNUSED" 07601, 0, "unable to determine size of file: %(1)s" // *Cause: An attempt to determine the size of the indicated file failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer or Debug utility. 07602, 0, "failed to create temporary paging file '%(1)s'" // *Cause: An attempt to create the indicated temporary paging file failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07603, 0, "write failed at position: %(1)s for temporary paging file '%(2)s'" // *Cause: An attempt to write to the indicated temporary paging file failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07604, 0, "seek failed at position: %(1)s for temporary paging file '%(2)s'" // *Cause: An attempt to seek within the indicated temporary paging file // failed. Refer to the accompanying message(s) for more // information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07605, 0, "Message removed - do not reuse message number" 07606, 0, "read failed at position: %(1)s for temporary paging file '%(2)s'" // *Cause: An attempt to read the indicated temporary paging file failed. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07607, 0, "metadata read failed at disk offset: %(1)s\n bytes requested: %(2)u bytes returned: %(3)u" // *Cause: An attempt to read metadata at the indicated offset was incomplete. // The amount of data read did not match the amount requested. Refer // to the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07608, 0, "UNUSED" / 07609, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07610, 0, "Volume_Disk_Header has incorrect _VolVolumeSize value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s" // *Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header // metadata structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07611, 0, "Global_BitMap has bits incorrectly set for storage beyond the file system size\nfor file:\n%(1)s" // *Cause: The Global_BitMap had bits set in an area reserved for future // expansion. All of these storage bits must be zero. There is no // valid storage associated with these bits. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07612, 0, "file has invalid _NextFreeExtent value:\n found: %(1)u minimum: %(2)u\nfor file:\n%(3)s" // *Cause: The _NextFreeExtent property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07613, 0, "file has invalid _NextFreeExtent value:\n found: %(1)u maximum: %(2)u\nfor file:\n%(3)s" // *Cause: The _NextFreeExtent property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. / Section 7000 comments above explain how this message will be used. 07614, 0, "Global_BitMap's first extent is not located at the expected disk offset\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The first extent of the indicated Global_BitMap was not located at // the correct disk offset. The Global_BitMap's first extent must be // located at the disk offset described in the message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07615, 0, "Global_BitMap file has extents that overlap\n Extent[%(1)d] _Length: %(2)s _PhysicalDiskOffset: %(3)s\n Extent[%(4)d] _Length: %(5)s _PhysicalDiskOffset: %(6)s\nfor file:\n%(7)s" // *Cause: The extents of the indicated Global_BitMap mapped some or all of // the same storage. All extents within a file must map storage // that is mutually exclusive. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07616, 0, "%(1)s has encountered an internal error: could not post error to ACFS Fixer" // *Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an // unexpected, internal error. Refer to the accompanying message(s) for // more information on the problem. // *Action: Contact Oracle Support Services. 07617, 0, "problems processed: %(1)d%%" 07618, 0, "fixing file system\n\n" 07619, 0, "truncating file from %(1)u bytes to %(2)u bytes to ensure metadata consistency; file content following file offset: %(3)u has been lost\nfor file:\n%(4)s" // *Cause: The ACFS Fixer was not able to fully repair the indicated file // due to an inconsistency within its metadata. The file had to be // truncated to maintain the integrity of the file system. // *Action: Restore the file from a backup copy. 07620, 0, "the contents of snapshot '%(1)s' (id: %(2)u) have changed due to the truncation of the file described in the accompanying message" // *Document: NO // *Document: NO / 07621, 0, "UNUSED" 07622, 0, "resetting _security_descriptor to administrator default value for:\nfor file:\n%(1)s" // *Cause: The _security_descriptor the indicated file was invalid or // incorrect. It was reset to the default administrator value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will reset the _security_descriptor to // the administrator default value for the file. 07623, 0, "unable to repair problem with file _attributes; deleting file to maintain file system integrity\nfor file:\n%(1)s" // *Cause: The ACFS Fixer was not able to resolve a problem with the // _attributes property of the indicated file. The file had to be // deleted to maintain the integrity of the file system. // *Action: Restore the file from a backup copy. 07624, 0, "file cannot be repaired; deleting file to maintain file system integrity\nfor file:\n%(1)s" // *Cause: The ACFS Fixer was not able to repair a problem with the // indicated file. The file had to be deleted to maintain file // system integrity. // *Action: Restore the file from a backup copy. 07625, 0, "failed to create system directory\nfor file:\n%(1)s" // *Cause: The ACFS Fixer was not able to create a directory for the // indicated internal system file. Refer to the accompanying // message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07626, 0, "UNUSED" / 07627, 0, "UNUSED" 07628, 0, "invalid snapshot name '%(1)s' entered" // *Cause: The snapshot entered did not exist. // *Action: Enter the name of a valid snapshot to continue. 07629, 0, "numeric argument too large: %(1)u" // *Cause: The numeric value entered as an argument exceeded the largest // possible value for this type of argument. // *Action: Enter a value that is within the valid range of values for the // type of argument. / [07630 - 07646], 0, "UNUSED" 07647, 0, "local extent limit reached for extending files; indirect extents not supported for extending files\nfor file:\n%(1)s" // *Cause: The ACFS Fixer was not able to create an indirect extent to // extend the indicated file. // *Action: Restore the file from a backup copy. 07648, 0, "cannot set Global_BitMap bits for offset: %(1)s for %(2)u bytes\nfor file:\n%(3)s" // *Cause: The ACFS Fixer was unable to set the range of bits described in the // message. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07649, 0, "deleting snapshot to maintain file system integrity" // *Cause: The ACFS Fixer had to delete a snapshot to maintain // the integrity of the file system. Refer to the corresponding // message(s) for more information on the problem(s) associated with // the snapshot. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07650, 0, "unable to repair _VolStateFlag value in Volume_Disk_Header" // *Cause: The ACFS Fixer was unable to update the _VolStateFlag in the // Volume_Disk_Header. Refer to the accompanying message(s) for more // information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. / 07651, 0, "UNUSED" / Section 7000 comments above explain how this message will be used. 07652, 0, "Volume_Disk_Header has invalid _VolOSCreatedOn value\n found: %(1)u, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4 (AIX)\nfor structure:\n%(2)s" // *Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header // was incorrect. Its value must be one of the values listed in the // message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. / Section 7000 comments above explain how this message will be used. 07653, 0, "Security_Metadata file _Private structure has invalid _freeDataListTail value\n found: 0, but expected to find: > 0\nfor structure:\n%(1)s" // *Cause: The _freeDataListTail property of the indicated Security_Metadata // _Private metadata structure was invalid. The value must be greater // than zero. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07654, 0, "Message removed - do not reuse message number" 07655, 0, "This file system had been removed. It has now been restored." // *Cause: This file system was removed via the acfsutil rmfs utility. It has // now been restored by the ACFS Fixer. // *Action: The ACFS Fixer has restored the file system. No further action // is required. 07656, 0, "unable to continue" // *Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal // error and cannot continue. Refer to the accompanying message(s) // for more information on the error. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07657, 0, "%(1)s utility is operating in read-only mode" // *Document: NO 07658, 0, "Ensure that volume %(1)s is not mounted on this node. \nNote that data displayed may not be current if volume %(2)s is mounted on any other node due to file system caching" // *Cause: The volume cannot be mounted on this node while running the acfsdbg // utility in read-only mode. This restriction is limited to Windows // systems. // The acfsdbg utility reads metadata directly from disk and data may // not be current if the file system is mount on any other nodes due // file system caching. // *Action: Check to determine if the volume is mounted on any node. The volume // must be unmounted on this node before continuing. // The volume should also be unmounted on all others node if possible. // If the volume cannot be unmounted on other nodes, then reenter any // request if the metadata values displayed appear to be stale. // Note: You may have to reenter the request several times to // retrieve the latest metadata. 07659, 0, "command is disabled in read-only mode" // *Cause: The command entered attempted to modify file system metadata while // running in read-only mode. Modifications to file system metadata // are not allowed when running the ACFS Debug utility in read-only // mode. // *Action: Rerun the acfsdbg utility in write mode to modify metadata. 07660, 0, "unable to modify metadata for volume %(1)s; volume is not open" // *Cause: An attempt to modify metadata failed because the volume was not // open. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07661, 0, "metadata lookup by file identifier is disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap ' to set the context" // *Cause: The acfsdbg utility could not process the request because there // was no File_Entry_Table context. The acfsdbg utility requires a // valid File_Entry_Table context for lookups by file identifier // since the same file identifier may appear in multiple snapshots. // *Action: Enter the 'primary' or 'snap ' command to set context. 07662, 0, "unable to set snapshot context due to Snap_Map file metadata inconsistency" // *Cause: An attempt to set the metadata lookup context to a snapshot failed // because there was a problem accessing the SnapMap metadata. Refer // to the accompanying message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS debug utility. 07663, 0, "disk offset request: %(1)s is not aligned on a sector: %(2)u bytes; results may be inconsistent" // *Cause: The disk offset entered was not sector aligned. All ACFS metadata // structures are sector aligned. // *Action: Reenter the offset so that is properly aligned as described in // the corresponding message. 07664, 0, "read failed for metadata structure at disk offset: %(1)s for %(2)u bytes" // *Cause: An attempt to read a metadata structure at the indicted disk offset // failed. Refer to accompanying message(s) for more information on // the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS debug utility. / 07665, 0, "UNUSED" 07666, 0, "unrecognized metadata found at disk offset: %(1)s" // *Cause: The data found at the indicated disk offset did not contain a // valid ACFS metadata structure type. // There are two possible causes: // 1. The data at the disk offset was not an ACFS metadata structure. // 2. The metadata structure at the disk offset was in an inconsistent // state. // *Action: If the data at the disk offset should be an ACFS metadata // structure, then run the ACFS Fixer to resolve the problem. 07667, 0, "request for file identifier: %(1)s exceeds the maximum value for this file system: %(2)s" // *Cause: A request was made for a file identifier that exceeded the maximum // for the file system. // *Action: Reenter the command with a file identifier that is within the // limits of the file system. 07668, 0, "attempting to continuing processing even though errors were reported" 07669, 0, "metadata lookup by file identifier is disabled due to File_Entry_Table metadata inconsistency" // *Cause: A problem was found with the File_Entry_Table's metadata that // prevented lookup by file identifier. Refer to the accompanying // message(s) for more information on the problem. // *Action: Correct the problem described in the accompanying messages if // possible by run the ACFS Fixer. / [07670 - 07681], 0, "UNUSED" 07682, 0, "file system check has been cancelled" / 07683, 0, "UNUSED" / 07684, 0, "UNUSED" 07685, 0, "%(1)s is unable to detect the ACFS driver on this system. \nProceeding could leave the file system in an inconsistent and possibly \nunusable state if the file system is mounted or being fixed on another system." // *Cause: The ACFS Checker/Fixer or Debug utility issued a system call to // the ACFS driver that failed. It appeared that the ACFS driver was // not loaded on this system. // *Action: The ACFS driver should be loaded on all nodes if possible. Verify // that the file system is not mounted or being fixed on any node. // Rerun the ACFS Checker/Fixer or Debug utility once these steps // are complete. / 07686, 0, "UNUSED" / 07687, 0, "UNUSED" / 07688, 0, "UNUSED" / 07689, 0, "UNUSED" 07690, 0, "data displayed may not be current if volume %(1)s is mounted on any node due to file system caching" // *Cause: The acfsdbg utility reads metadata directly from disk. Metadata // updates to disk may be delayed due standard file system caching. // *Action: Check to determine if the volume is mounted on any node. Unmount the // volume on all nodes if possible. If the volume cannot be unmounted // from all nodes, then reenter any request if the metadata values // displayed appear to be stale. // Note: You may have to reenter a request several times to retrieve // the latest metadata. 07691, 0, "command entered: '%(1)s' is invalid or not unique" // *Cause: There are two possible causes: // 1. The command entered was not recognized by the acfsdbg utility. // 2. A partial command name was entered and there was more than // one command that matched the characters entered. // *Action: Use the acfsdbg utility help (-h) option for a list of valid // commands. Renter the command, ensuring that enough of the command // name is entered to make it unique. 07692, 0, "cannot convert disk offset as specified: %(1)s" // *Cause: The format entered for the disk offset was invalid. // *Action: Use the acfsdbg utility help (-h) option for a list of commands // and format options for entering data. 07693, 0, "Volume_Disk_Header has invalid _VolVolumeSize value\n found: %(1)s must be aligned on a %(2)u byte boundary\nfor structure:\n%(3)s" // *Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. // Its value must be aligned on the byte boundary described in the // message. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07694, 0, "too many arguments for string" // *Cause: Too many arguments were supplied for the string option. The // string option takes one argument. // *Action: Reenter the command with only one argument for the string option. 07695, 0, "The ACFS driver should be loaded on all nodes for a safe check of this file system." // *Cause: The ACFS Checker/Fixer or Debug utility issued a system call to // the ACFS driver that failed. It appeared that the ACFS driver // was not loaded on this system. // *Action: The ACFS driver should be loaded on all nodes if possible. Verify // that the file system is not mounted or being checked on any node. // Rerun the ACFS Checker/Fixer or Debug utility once these steps // are complete. 07696, 0, "The file system on volume %(1)s is currently in the %(2)s state. This state indicates that a file system check is currently in progress." // *Cause: There are two possible causes: // 1. The file system on this volume was being checked on this system // or another system in the cluster. // 2. The ACFS Checker/Fixer was unexpectedly terminated leaving the // file system state incorrectly set. // *Action: Verify that the file system is not being checked on any node. // There are a two possible options if the file system is not being // checked on any node: // 1. Respond Y(yes) when prompted to run the ACFS Checker/Fixer. // 2. Run the ACFS Fixer with the [f] option to reset the file // system state to allow the file system to be mounted. // NOTE: Use caution with this option as file system repairs from // a previous run of the ACFS Checker/Fixer may be incomplete. 07697, 0, "unable to determine program name" // *Cause: The ACFS Checker/Fixer or Debug utility was invoked in a // non-standard way such that the program name could not be // determined. // *Action: Run the ACFS Checker/Fixer or Debug utility using a standard // method. 07698, 0, "orphan directory found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: No parent directory entry was found for the indicated directory // file. // 1. The directory file had no corresponding parent directory entry. // 2. The directory file had a parent directory entry, but there was // a problem with corresponding parent directory file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. If the ACFS Checker is running, then run the ACFS Fixer to // resolve the problem. The ACFS Fixer will attempt to repair any // directories that are in an inconsistent state first. Any directory // file that does not have a valid parent directory entry following // directory repairs will be moved to the 'lost+found' directory with // all of its files. / 07699, 0, "UNUSED" / 07700, 0, "UNUSED" 07701, 0, "There are metadata transaction log file(s) that have not been processed. Failure \nto process these transaction logs may result in metadata inconsistencies. \nDo you want to process the transaction log(s)? [y|n]" // *Cause: Transaction Log files contain updates to the file system's // metadata. The ACFS Checker found at least one transaction log // that was not completely processed. This indicates that metadata // updates were not completed which could leave the file system // in an inconsistent state. // *Action: Respond yes to process metadata transaction log(s). / 07702, 0, "UNUSED" 07703, 0, "Metadata Transaction Log_File not processed\nfor file:\n%(1)s" // *Document: NO 07704, 0, "processing Metadata Transaction Log_File\nfor file:\n%(1)s" // *Document: NO 07705, 0, "There are files marked for deletion that have not been removed from the \nfile system. Failure to remove these files could result in false errors \nbeing reported. \nDo you want to remove files that are marked for deletion? [y|n]" // *Cause: The ACFS Checker found files that were marked for deletion but // had not been removed from the file system. False errors may be // reported due to the presence of there files. // *Action: Respond yes to remove these files. 07706, 0, "files marked for deletion will not be removed from the file system" 07707, 0, "removing files marked for deletion" 07708, 0, "unable to read File_Entry_Table entry: %(1)s at disk offset: %(2)s" // *Cause: An attempt to read the File_Entry_Table for the indicated entry // failed. Refer to the accompanying message(s) for more information // on the problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Checker/Fixer. 07709, 0, "orphan file (file identifier: %(1)s, disk offset: %(2)s) marked for deletion not on delete list" // *Cause: The indicated file was marked for deletion but it was not found // on any of the delete file lists. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07710, 0, "orphan file found for file identifier: %(1)s at disk offset: %(2)s" // *Cause: No directory entry was found for the indicated file. // There are two possible causes: // 1. The file had no corresponding directory entry. // 2. The file had a directory entry, but there was a problem with // corresponding directory file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. If the ACFS Checker is running, then run the ACFS Fixer // to // resolve the problem. The ACFS Fixer will attempt to repair any // directories that are in an inconsistent state first. Any file that // does not have a valid directory entry following directory // repairs will be moved to the 'lost+found' directory. 07711, 0, "orphan metadata structure (type: %(1)s) found for file identifier: %(2)s at disk offset: %(3)s" // *Cause: The indicated metadata structure was found but had no corresponding // parent metadata structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will move the structure to the free list. // If the ACFS Checker is running, then run the ACFS Fixer to resolve // the problem. / 07712, 0, "UNUSED" / 07713, 0, "UNUSED" / 07714, 0, "UNUSED" / 07715, 0, "UNUSED" / 07716, 0, "UNUSED" 07717, 0, "Message removed - do not reuse message number" / 07718, 0, "UNUSED" / 07719, 0, "UNUSED" 07720, 0, "new allocation size is invalid\n found: %(1)u, but expected to find multiple of: %(2)u\nfor file:\n%(3)s" // *Cause: The new allocation size property of the indicated file was // incorrect. Its value must be a multiple of the file system // allocation unit size. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07721, 0, "file has invalid _NextFreeExtent value\n found: %(1)u maximum: %(2)u\nfor file:\n%(3)s" // *Cause: The _NextFreeExtent property of the indicated file was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07722, 0, "file has invalid _NextFreeExtent value:\n found: %(1)u minimum: 1\nfor file:\n%(2)s" // *Cause: The _NextFreeExtent property of the indicated file was incorrect. // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07723, 0, "could not clear temporary Global_BitMap bits at offset: %(1)s for %(2)u bits" // *Cause: The ACFS Fixer was unable to free the indicated storage on the // temporary Global_BitMap. // *Action: See the preceding error message, and take corrective action. 07724, 0, "unable to set temporary Global_BitMap bits at offset: %(1)s for %(2)u bits" // *Cause: The ACFS Fixer was unable to reserve the indicated storage on the // temporary Global_BitMap. // *Action: See the preceding error message, and take corrective action. 07725, 0, "unable to allocate storage; file system has no free space" // *Cause: The ACFS Fixer was unable to allocate storage because there // was no free storage available. // *Action: There are two options: // 1. Free up some storage by deleting some files. // 2. Add available storage by increasing the size of the file // system via the 'acfsutil size' command. 07726, 0, "could not find sufficient free storage to rebuild Global_BitMap extent\n found: %(1)s requested: %(2)s\nfor file:\n%(3)s" // *Cause: The ACFS Fixer could not find enough contiguous storage to // rebuild the Global_BitMap file's extent map. // *Action: There are two options: // 1. Free up some storage by deleting some files. // 2. Add available storage by increasing the size of the file // system via the 'acfsutil size' command. 07727, 0, "could not rewrite Global_Bitmap data for file:\n%(1)s" // *Cause: The ACFS Fixer could not update the file system's storage bitmap. // Refer to the accompanying message(s) for more information on the // problem. // *Action: Correct the problem described in the accompanying messages if // possible and rerun the ACFS Fixer. 07728, 0, "The Global_BitMap file has reached the maximum number of extents (%(1)u). The file system can no longer be expanded. Running %(2)s in fixer mode will attempt to consolidate the storage bitmap into fewer extents which would allow for file system expansion via the 'acfsutil size' command." // *Cause: The ACFS Checker found the file system's storage bitmap // was using its maximum number of extents. // *Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to // consolidate the file system's storage bitmap into two extents // allowing future file system expansion using 'acfsutil size', // assuming additional storage is available. 07729, 0, "The Global_Bitmap file has been\n consolidated into %(1)u extents.\nThis may allow for file system expansion via the 'acfsutil size' command." // *Cause: The Global_Bitmap file was using the maximum number of extents // supported. The ACFS Fixer has consolidated the Global_Bitmap file // into fewer extents thus allowing future file system growth using // the 'acfsutil size' command if unused storage is available. // *Action: No Action Needed. / 07730, 0, "UNUSED" / 07731, 0, "UNUSED" / 07732, 0, "UNUSED" 07733, 0, "directory _Private structure has invalid _first_dirnode value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _first_dirnode property of the indicated _Private directory // structure was invalid. Its value exceeded the maximum value for // the directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07734, 0, "directory _Private structure has invalid _last_dirnode value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _last_dirnode property of the indicated _Private directory // structure was invalid. Its value exceeded the maximum value for // the directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07735, 0, "directory _Private structure has invalid _hash_blk_free_list value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _hash_blk_free_list property of the indicated _Private directory // structure was invalid. Its value exceeded the maximum value for // the directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07736, 0, "directory _Private structure has invalid _dir_entry_free_list_head value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _dir_entry_free_list_head property of the indicated _Private // directory structure was invalid. Its value exceeded the maximum // value for the directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07737, 0, "directory _Private structure has invalid _dir_entry_free_list_tail value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _dir_entry_free_list_tail property of the indicated _Private // directory structure was invalid. Its value exceeded the maximum // value for the directory. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07738, 0, "file system check starting for volume: %(1)s" 07739, 0, "file system check starting for file system file: %(1)s" 07740, 0, "Could not consolidate the file system's temporary\n storage bitmap to less than %(1)d extents. Need\n at least %(2)d bytes free contiguous storage." // *Cause: The file system's internal storage bitmap could not be consolidated // to less than five extents because there was insufficient free // contiguous storage. // *Action: Deleting some files larger than the amount of contiguous storage // needed may free up sufficient contiguous storage so consolidation // of the file system's internal storage bitmap may occur. The // 'acfsutil info file filename' command may be used to examine a // candidate file's contiguous extents. 07741, 0, "could not rebuild file system storage bitmap\n free contiguous bytes found: %(1)u\n contiguous bytes requested: %(2)u\nfor file: %(3)s" // *Cause: The ACFS Fixer could not find enough contiguous free storage to // rebuild the file system's storage bitmap. // *Action: Deleting some files larger than the amount of contiguous storage // needed may free up sufficient contiguous storage so consolidation // of the file system's internal storage bitmap may occur. The // 'acfsutil info file filename' command may be used to examine a // candidate file's contiguous extents. 07742, 0, "_ustEAContainerEntry property has an invalid value\n found: %(1)u for structure:\n%(2)s" // *Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer // structure was not within the range of valid offset values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible information. 07743, 0, "_ustEAEntryHdrFlags property has an invalid value\n found: %(1)s for _ustEAContainerEntry at offset: %(2)s for structure:\n%(3)s" // *Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer // structure contained one or more invalid values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07744, 0, "_ustEAEntryHdrNextFreeOffset property has an invalid value\n found: %(1)u, but expected to find: %(2)u for _ustEAContainerEntry at offset: %(3)u for structure:\n%(4)s" // *Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated // _ustEAContainer structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07745, 0, "_ustEAEntryHdrNameLen property has an invalid value\n found: %(1)u, but expected to find no greater than: %(2)u\n for _ustEAContainerEntry at offset: %(3)s for structure:\n%(4)s" // *Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr // property at the _ustEAContainerEntry offset for the indicated _ustEAContainer // structure was invalid. Its value exceeded the maximum length for an // extended attribute name or ACFS tag name. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07746, 0, "ACFS tag name contains invalid syntax\n found: %(1)s for _ustEAContainerEntry at offset: %(2)s for structure:\n%(3)s" // *Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry property // in the _ustEAContainer structure contained invalid syntax // for an ACFS tag name. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07747, 0, "_ustEAEntryValueLen property has an invalid value\n found: %(1)u, but expected to find: %(2)u\n for _ustEAEntry offset: %(3)s for structure:\n%(4)s" // *Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property // in the _ustEAEntryContainer structure contained an invalid value length. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07748, 0, "_ustEAEntryValue property has an invalid value\n found: %(1)s, but expected to find: %(2)s\n for _ustEAEntry offset: %(3)s for structure:\n%(4)s" // *Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property // in the _ustEAEntryContainer structure contained an invalid value string // for an ACFS tag name. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07749, 0, "_ustEAContainerHdrNextContainer property has an invalid value\n found: %(1)s for structure:\n%(2)s" // *Cause: The _ustEAContainerHdrNextContainer property of the indicated // _ustEAContainer structure contained an invalid offset value. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07750, 0, "_ustEAContainerHdrNumEAEntries property has an invalid value\n found: %(1)u, but expected to find: %(2)u for structure:\n%(3)s" // *Cause: The _ustEAContainerHdrNumEAEntries property of the indicated // _ustEAContainer structure contained an incorrect count of valid // entries. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07751, 0, "Inconsistent amount of available space\n found: %(1)u, but expected to find: %(2)u\n for structure:\n%(3)s" // *Cause: The _ustEAContainer structure had an incorrect amount of free space. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07752, 0, "_LocalTags property has invalid characters for _FileEntry:\n%(1)s" // *Cause: The _LocalTags property of the indicted _FileEntry structure contained // invalid characters for ACFS tag names. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07753, 0, "_ustEAEntry property offset: %(1)u is marked free\n but is missing from the free list for structure:\n%(2)s" // *Cause: The _ustEAContainer structure had an incorrect amount of free space. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07754, 0, "_ustEAContainer property has inconsistent\n total free and assigned _ustEAContainerEntry property space\n found: %(1)u, but expected to find: %(2)u for structure:\n%(3)s" // *Cause: The _ustEAContainer structure contained free and active _ustEAContainerEntry // property entries that indicate its total space exceeded the size // of a _ustEAContainer structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07755, 0, "_ustEAContainerHdrNextFreeOffset property has an invalid value\n found: %(1)u, but expected to find less than: %(2)u for structure:\n%(3)s" // *Cause: The ustEAContainerHdrNextFreeOffset property of the indicated // _ustEAContainer structure was not within the range of valid // offset values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible information. 07756, 0, "_ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has an invalid value\n found: %(1)u, but expected to find less than: %(2)u for _ustEAContainerEntry at offset: %(3)u for structure:\n%(4)s" // *Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the // indicated _ustEAContainerEntry property for the _ustEAContainer structure // was not within the range of valid offset values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible information. 07757, 0, "file extended attribute container structure exceeds file system size: %(1)s\n _Length: %(2)s\nfor structure:\n%(3)s" // *Cause: The extended attribute container structure of the indicated file // referenced meta data beyond the size of the file system. // There are two possible causes: // 1. The extended attribute container structure disk offset was // incorrect. // 2. The file system size value was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07758, 0, "_ustEAEntryHdrNameLen property has an invalid value\n found: %(1)u, but expected non-zero value\n for _ustEAContainerEntry at offset: %(2)s for structure:\n%(3)s" // *Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr // property at the _ustEAContainerEntry offset for the indicated _ustEAContainer // structure was invalid. Its value was zero but must be non-zero for an // extended attribute name entry. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07759, 0, "_ustEAEntryValueLen property has an invalid value\n found: %(1)u, but expected to find less than: %(2)u\n for _ustEAEntry offset: %(3)s for structure:\n%(4)s" // *Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property // in the _ustEAEntryContainer structure contained an invalid value length // that was larger than expected for this structure. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible or invalid information. 07760, 0, "_ustEAContainerHdrNextFreeOffset property has an invalid value\n found: %(1)u, but expected to find: %(2)u for structure:\n%(3)s" // *Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated // _ustEAContainer structure was not within the range of valid // offset values. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. The ACFS Fixer reconstructs the structure to retain // as much valid information as possible and may eliminate // inaccessible information. / [07761 - 07863], 0, "UNUSED" 07864, 0, "A request to cancel %(1)s was made \nwhile the file system was being repaired. This could leave the file system \nin an inconsistent state. It is strongly recommended that %(2)s \nbe rerun to complete file system repairs." // *Cause: The ACFS fixer was cancelled before all file system repairs were // completed. // *Action: Rerun the ACFS fixer to complete file system repairs. / [07865 - 07899], 0, "UNUSED" 07900, 0, "Security_Metadata file _Private structure has invalid _freeDataList value\n found: %(1)u maximum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _freeDataList property of the _Private structure of the // indicated Security_Metadata file was incorrect. The _freeDataList // value exceeded the maximum value for this Security_Metadata // file. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the // problem. 07901, 0, "Hash_Bucket metadata structure has incorrect _controlling_bkt value\n found: %(1)s maximum: %(2)s\nfor structure:\n%(3)s" // *Cause: The _controlling_bkt property of the indicated Hash_Bucket // structure was incorrect. Its value exceeded the maximum value // for the hash table. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07902, 0, "Hash_File_Master_Block metadata structure has incorrect value for entry %(1)u in _hash_bucket_group array\n found: %(2)u minimum: %(3)u\nfor structure:\n%(4)s" // *Cause: The entry in _hash_bucket_group array of the indicated // Hash_File_Master_Block structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07903, 0, "Hash_Bucket metadata structure has invalid data; expected all zeros\nfor structure:\n%(1)s" // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07904, 0, " Files moved to lost+found: %(1)u" 07905, 0, " Snapshots deleted: %(1)u" 07906, 0, " Snapshots modified: %(1)u" 07907, 0, "directory file has no storage allocated to it\nfor file:\n%(1)s" // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07908, 0, "Root_Directory cannot be repaired\nfile:\n%(1)s" // *Cause: The ACFS Checker/Fixer found an inconsistency with the // Root_Directory metadata. // *Action: The Root_Directory is a critical system file that is necessary // for a functioning file system. // Restore the file system from a backup copy. 07909, 0, "System metadata was truncated, possibly resulting in the deletion of files." // *Cause: The ACFS Checker/Fixer found an inconsistency within the // file system. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07910, 0, " Files deleted: %(1)u" 07911, 0, " Files truncated: %(1)u" 07912, 0, "Usage: -V acfs [%(1)sy | %(2)sn] [%(3)so h,v,[a|f]%(4)s] " 07913, 0, " %(1)so - Acfs options follow" 07914, 0, " [a] - Automatically fix file system" 07915, 0, " [f] - Force file system into mountable state without completing file system check or fix" 07916, 0, " [%sy] - Assume an answer of yes to any question" 07917, 0, " [%sn] - Assume an answer of no to any question" 07918, 0, "Usage: -V acfs [%(1)sy | %(2)sn] [%(3)so h,v,vv,[a|f]%(4)s] " / 07919, 0, "UNUSED" 07920, 0, "Usage: [%sn|%sN|%sy|%sY] [%so h,v,[a|f]%s] " 07921, 0, " [%sn|%sN] - Assume an answer of no to any question" 07922, 0, " [%sy|%sY] - Assume an answer of yes to any question" 07923, 0, "Check but do not repair is the default behavior for ACFS." 07924, 0, "Snap_Map_header has invalid value for RW snap storage not in map\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The Snap_Map_header property that indicates the amount of RW snap // storage not recorded in the Snap_Map file is incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07925, 0, "Snap_Map_header has invalid value for snap storage in map\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s" // *Cause: The Snap_Map_header property that indicates the amount of snap // storage recorded in the Snap_Map file is incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07926, 0, "Snap_Map_header has invalid value for snap map flags\n found: %(1)s\nfor file:\n%(2)s" // *Cause: The Snap_Map_header flags field is invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 07927, 0, "Usage: [%sn|%sN|%sy|%sY] [%so h,v,vv,[a|f]%s] " / [07928 - 7999], 0, "UNUSED" / / Messages for advmutil 09000, 0, "Invalid drive letter specification: %s" 09001, 0, "Error reading ORACLE_HOME environmental variable" 09002, 0, "NOTE: The volume %s contains an ACFS filesystem" 09003, 0, "Executing: %s" 09004, 0, "CreateProcess of acfsmountvol failed, %s" 09005, 0, "Error running %s" 09006, 0, "Error opening volume %s" 09007, 0, "Error setting file pointer on volume %s" 09008, 0, "Error reading from volume %s" 09009, 0, "Error closing volume %s" 09010, 0, "Error locking volume %s" 09011, 0, "Error dismounting file system on volume %s" 09012, 0, "Error opening the Windows Registry" 09013, 0, "Error reading the Windows Registry" 09014, 0, "Drive Letter ASM Volume\n=====================================================" 09015, 0, "The volume %s was not found. Verify the diskgroup is mounted and the volume is enabled." 09016, 0, "Error mounting volume %s on %s" 09017, 0, "ASM volume %s mounted on %s" 09018, 0, "Error broadcasting mount of volume %s on %s" 09019, 0, "Error opening volume on %s" 09020, 0, "Error dismounting %s" 09021, 0, "Error broadcasting dismount of %s" 09022, 0, "ASM volume dismounted from %s" 09023, 0, "Volume %s is currently assigned to drive %s" 09024, 0, "Drive letter %s is currently assigned to volume %s" 09025, 0, "Failed to update the Windows Registry for volume %s." // *Cause: An attempt to store data in the Windows registry failed. // This message is accompanied by other message(s) that provide details // as to the exact cause of the failure. // *Action: Correct the problem indicated by the accompanying messages and // retry the operation. 09026, 0, "Drive letter %s assigned to %s" 09027, 0, "Error deleting the drive letter assignment %s" 09028, 0, "Assignment for drive letter %s not found" 09029, 0, "Drive letter %s unassigned from %s" 09030, 0, "Error unassigning drive letter %s from volume %s" 09031, 0, "The volume %s contains an ACFS filesystem. Use acfsmountvol, or use acfsutil rmfs to remove the ACFS file system" 09032, 0, "WARNING: Unsupported force option in effect. Proceeding with mount of ACFS volume %s" 09033, 0, "WARNING: Unsupported force option in effect. Ignoring previous error. VolumeName=%s" 09034, 0, "Error taking %s offline" 09035, 0, "Error unlocking %s" 09036, 0, "Error bringing %s online" 09037, 0, "Error reading reparse point %s" 09038, 0, "Volume %s contains an ACFS filesystem and must be dismounted with acfsdismount" 09039, 0, "Mount point %s is already in use" / / advmutil volinfo / 09050 obsolete - see 09061 09050, 0, "Interface Version : %d : Size (MB) : %ld : Resize Increment (MB) : %d : Redundancy : %s : Stripe Columns : %d : Stripe Width (KB) : %d : Disk Group : %s : Volume : %s : Compatible.advm : %s" 09051, 0, "Interface Version: %d" 09052, 0, "Size (MB): %ld" 09053, 0, "Resize Increment (MB): %d" 09054, 0, "Redundancy: %s" 09055, 0, "Stripe Columns: %d" 09056, 0, "Stripe Width (KB): %d" 09057, 0, "Disk Group: %s" 09058, 0, "Volume: %s" 09059, 0, "Compatible.advm: %s" 09060, 0, "Device: %s" 09061, 0, "Device : %s : Interface Version : %d : Size (MB) : %ld : Resize Increment (MB) : %d : Redundancy : %s : Stripe Columns : %d : Stripe Width (KB) : %d : Disk Group : %s : Volume : %s : Compatible.advm : %s" / advmutil usage 09075, 0, "Usage: %s [one of the options below]" 09076, 0, "help - display this message" 09077, 0, "tune - list all tunable parameters" 09078, 0, "tune - list named tunable parameter" 09079, 0, "tune = - set named tunable parameter to \n (root/admin access required)" 09080, 0, "volinfo [] - print ADVM volume information\n (one descriptor per line format)" / 09081 obsolete - see 09090 09081, 0, "volinfo [%sL] [] - print ADVM volume information\n (colon separated format)" 09082, 0, "mount /all - mount all registered ADVM volumes" 09083, 0, "mount [/register] - register drive\n letter to the specified ADVM volume" 09084, 0, " mount /dg= - mount the specified disk group" 09085, 0, "dismount [/unregister] /all - unregister all drive letters" 09086, 0, "dismount [/unregister] - unregister an\n ADVM volume drive letter" 09087, 0, "dismount [/unregister] /dg= - unregister the\n specified disk group" 09088, 0, "list /registry - list all registered ADVM volumes" 09089, 0, "canonical - print operating system standard name\n for ADVM volume." 09090, 0, "volinfo [%sl] [] - print ADVM volume information\n (colon separated format with labels)" 09091, 0, "volinfo [%sL] [] - print ADVM volume information\n (space separated format - no labels)" / / USM install / runtime tools / / acfslib and other common messages 09100, 0, "Creating volume '%s' in diskgroup '%s'." // *Cause: Informational // *Action: None 09101, 0, "Failed to create volume '%s' in diskgroup '%s'." // *Cause: The volume was unable to be created in the diskgroup. // Possible Causes: // 1) ASM is not running. // 2) User is not part of the ASMADMIN group. // 3) An ASM specific error occurred. // *Action: // 1) Verify that ASM is running ('srvctl status asm') // 2) Verify that the user is part of the ASMADMIN group. // 3) Check the ASM logs and output for an ASM specific error. 09102, 0, "Unable to verify creation of ACFS Oracle database Home." // *Cause: A command was given to ASM to create the specified volume and no // errors were detected. However, post creation checks failed to // find that the volume that was created and/or enabled. // *Action: Run sqlplus (or asmcmd) to manually create the volume. 09103, 0, "Enabling volume '%s' on diskgroup '%s'." // *Cause: Informational // *Action: None 09104, 0, "Enable of volume '%s' failed." // *Cause: ASM was instructed to enable the specified volume and failed. // *Action: Attempt a manual enable via sqlplus or asmcmd. 09105, 0, "Volume '%s' not found in '%s'." // *Cause: The specified volume does not exist. // *Action: Create volume via sqlplus or asmcmd. 09106, 0, "Diskgroup '%s' not found." // *Cause: The specified diskgroup does not exist. // *Action: Create diskgroup via sqlplus or asmcmd. 09107, 0, "ASM mounting diskgroup '%s'." // *Cause: Informational // *Action: None 09108, 0, "ASM mount of diskgroup '%s' failed." // *Cause: ASM found the specified diskgroup but could not mount it. // *Action: Try mounting the diskgroup manually via sqlplus. If the mount // fails, check ASM logs for errors related to the diskgroup, // clear errors, and try again. 09109, 0, "%s driver failed to load." // *Cause: The driver failed to load. // *Action: View the system specific OS kernel log // (for instance, /var/log/messages on Linux, Event Log on Windows). // If the drivers have not previously been unloaded // ('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is // not possible to reload them. // If a specific error has occurred, than clear the error condition // and try again. If the OS and\or architecture is not // supported by the drivers, than contact // Oracle Support Services for an updated driver package. 09110, 0, "Offline mount point '%s' was dismounted for recovery." // *Cause: Informational. The mount point referenced was fenced due to an // underlying volume failure. In this case, the mount point was // successfully dismounted for recovery. // *Action: None. 09111, 0, "Offline mount point '%s' was recovered." // *Cause: Informational - the mount point referenced was fenced due to an // underlying volume failure. In this case, the mount point was // successfully remounted, which has renabled IO to the file system. // *Action: None. 09112, 0, "The following process IDs have open references on mount point '%s':" // *Cause: During shutdown of the CRS stack, it was determined that a process // had files open on the mount point in the process of being // dismounted. This prevents the dismount from succeeding. // *Action: Terminate any process\applications that are using files on the // mount point that is being dismounted before stopping the CRS stack. 09113, 0, "These processes will now be terminated." // *Cause: Informational // *Action: None 09114, 0, "completed" // *Cause: Informational // *Action: None 09115, 0, "The command '%s' returned an unexpected value." // *Cause: This is an internal error. // *Action: An internal error occurred during the installation process. // Restart the installation process. 09116, 0, "Offline mount point '%s' was not recovered." // *Cause: An inaccessible mount point could not be restored // to working condition. // *Action: Manual intervention is required to clear the offline mount point. // Dismount the mount point and remount it manually to restore // access to the mount point. 09117, 0, "Manual intervention is required." // *Cause: Informational, from previous errors. // *Action: Clear previous errors and retry. 09118, 0, "%s driver in use - cannot unload." // *Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or // 'acfsroot uninstall'. Applications (possibly ASM) have open // references on the driver. // *Action: Terminate applications, including ASM, that may be using the driver // and retry. 09119, 0, "%s driver failed to unload." // *Cause: An unknown error has occurred when trying to unload the driver. // *Action: Check system specific logs (/var/adm/messages on Linux, // Event Log on Windows) and clear any error conditions that are // preventing the unload. 09120, 0, "The '%s' machine architecture not supported." // *Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type // or OS. This occurs when the customer manually tries to load the // drivers on an architecture or system OS type that ACFS is not // supported, such as VMS. // *Action: Contact Oracle Support Services to determine if an updated driver // is available for this OS and architecture, or install ACFS on a // supported architecture and OS. 09121, 0, "Failed to detect control device '%s'." // *Cause: ADVM/ACFS device drivers have been started but the devices // that should have been created have not been. // *Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the // crs stack - 'crsctl stop crs', 'crsctl start crs'. If the control // devices still do not exist, contact Oracle Support Services. 09122, 0, "ADVM device not determined from mount point '%s'." // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. 09123, 0, "'%s' command not found." // *Cause: A required component of ACFS is missing. This could be an // incomplete install, removal of files from the system after install, // or an unknown cause. // *Action: Re-install by running 'acfsroot install'. If that does not work, // than contact Oracle Support Services. In the event that handle.exe // is not found, than please install handle from sysinternals.com or // another site, and make sure that the PATH environment variable // contains the install location. Retry the operation. 09124, 0, "%s driver failed to detach from the system driver stack." // *Cause: The ACFS driver is being used by one or more mounted file systems. // *Action: Unmount all ACFS file systems and retry the operation. 09125, 0, "ADVM/ACFS is not supported on this OS: '%s'" // *Cause: ADVM/ACFS device drivers have not been ported to this OS. // *Action: None. 09126, 0, "Attempting to terminate the program '%s' with OS process ID '%s'." // *Cause: The process was using an ACFS file system, which was being forcibly // unmounted. A kill signal was sent to allow the unmount to proceed. // *Action: This message is informational. 09127, 0, "Not all ADVM/ACFS drivers have been loaded." // *Cause: ADVM/ACFS device drivers have been started but not all // of them are detected as running. // *Action: Try 'acfsload stop' followed by 'acfsload start'. // If that does not start all drivers, than contact Oracle Support // Services. 09128, 0, "unknown query type '%s'" // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. 09129, 0, "ADVM/ACFS not installed" // *Cause: No ADVM/ACFS drivers or commands have been found on the system. // All ADVM and ACFS actions will be disabled. // *Action: Install components using 'acfsroot install '. No ACFS // file systems or ADVM volume devices will be available until // ADVM/ACFS has been installed. 09130, 0, "Root access required" // *Cause: The user this command is executing as does not have sufficient // privileges to run this command. // *Action: Run this command as a user with administrative privileges. 09131, 0, " [-s] - silent mode (error messages only)" 09132, 0, " [-h] - print help/usage information" 09133, 0, " %s" 09134, 0, "usage:" 09135, 0, "%s installation aborted." // *Cause: Informational // *Action: See preceding error message for more information. 09136, 0, "PID %s could not be killed." // *Cause: Failed to kill a Process ID during a force unmount of a file system. // *Action: Manually kill the process and retry the unmount. 09137, 0, "Failed to set group on directory '%s'." // *Cause: The group of the directory could not be changed. // *Action: Make sure the user has permission to do so. 09138, 0, "command '%s' completed with an error: %s" // *Cause: 'acfsutil' did not successfully run. // *Action: Correct the problem described in the accompanying error message // from 'acfsutil'. If this error was returned within the context // of a CRS resource execution, retry the CRS action after the // problem is resolved. 09139, 0, "Attempting recovery of offline mount point '%s'" // *Cause: An ACFS mount point reported by the 'acfsutil' command was not // accessible. // *Action: This message is informational. CRS will attempt to recover the // mount point. 09140, 0, "Unable to determine the correct drivers for this version of Windows: ID:%s Major:%s Minor:%s Product Type:%s" // *Cause: Error. ACFS is not supported on this Windows Version. // *Action: Report this message to Oracle Support Services to determine // if an update to ACFS is available. 09141, 0, " COMMAND %s" 09142, 0, " STATUS %s" 09143, 0, " USER %s" 09144, 0, " CPU_TIME %s" 09145, 0, " MEM %s" 09146, 0, " STAT %s" 09147, 0, " %MEM %s" 09148, 0, " %CPU %s" 09149, 0, "unable to determine device mount status - unsupported OS name '%s'" // *Cause: The standard method to determine mount state of a device was // unavailable. It is possible that ADVM/ACFS is not supported on the OS. // *Action: Report the value of OS to Oracle Support Services. 09150, 0, "Unexpected output from 'acfsutil info fs': '%s'." // *Cause: Informational // *Action: None 09151, 0, "Ignoring request to mount due to existence of \"oracle_nomounts\" file: %s" // *Cause: "An "oracle_nomounts" file was present, causing file system mount // processing to be skipped during a CRS resource operation." // *Action: Normal mount operations can be resumed by removing the \"oracle_nomounts\" file. 09152, 0, "Program '%s' with OS process ID '%s' will not be terminated." // *Cause: The process is using an ACFS file system which is being forcibly // unmounted but it will not be terminated because it is a // system critical process. // *Action: Manual intervention may be required. 09153, 0, "Program '%s' with OS process ID '%s' is using mount point '%s'." // *Cause: The process is using the mount point. // *Action: None - Informational. 09154, 0, "Loading '%s' driver." // *Cause: Informational. // *Action: None. 09155, 0, "Checking for existing '%s' driver installation." // *Cause: Informational. // *Action: None. 09156, 0, "Detecting control device '%s'." // *Cause: Informational. // *Action: None. 09157, 0, "Detecting driver '%s'." // *Cause: Informational. // *Action: None. 09158, 0, "Configuration file '%s' in the /boot directory is not accessible." // *Cause: A populated /boot directory, which contains static files required // to install kernel modules, was not detected on the system. // *Action: After restoring the /boot directory and the kernel configuration // files, re-run "acfsroot install". 09159, 0, " [-v] - verbose mode" 09160, 0, "Can not use the silent and verbose options at the same time." // *Cause: The -s and -v options were used in the command. These options are // mutually exclusive. // *Action: Re-execute the command with one of the options or neither. 09161, 0, " acfsroot install: Install ADVM/ACFS components." // *Cause: Informational. // *Action: None. 09162, 0, " acfsroot uninstall: Uninstall ADVM/ACFS components." // *Cause: Informational. // *Action: None. 09163, 0, " acfsroot version_check: Check ADVM/ACFS version." // *Cause: Informational. // *Action: None. 09164, 0, " acfsroot enable: Enable ADVM/ACFS CRS resources." // *Cause: Informational. // *Action: None. 09165, 0, " acfsroot disable: Disable ADVM/ACFS CRS resources." // *Cause: Informational. // *Action: None. 09166, 0, " %s [-h] [-s | -v]" // *Cause: Informational. // *Action: None. 09167, 0, "ADVM/ACFS is not installed or loaded. Run 'acfsroot install'." // *Cause: An operation was requested that requires ADVM/ACFS to be running. // *Action: Run 'acfsroot install' and then run the requested operation. / / acfsdriverstate 09200, 0, "Supported" // *Cause: ADVM/ACFS device drivers have been ported // to this OS or CPU type. // *Action: None - Informational. 09201, 0, "Not Supported" // *Cause: ADVM/ACFS device drivers have not yet been ported // to this OS or CPU type. // *Action: None. 09202, 0, "UNUSED" 09203, 0, "true" // *Cause: ADVM/ACFS device drivers were installed/loaded. // *Action: None. 09204, 0, "false" // *Cause: ADVM/ACFS device drivers were not installed/loaded. // *Action: None. 09205, 0, "UNUSED." 09206, 0, "usage: %s [-orahome ] [-s]" 09207, 0, "The user this command is executing as does not have permission to execute Perl in '%s'." // *Cause: Perl permissions are read/write/execute owner (0700). The user this // command is executing as is not the owner of the perl binary. // *Action: Enter the db home as an argument to -orahome. Ensure that // the user executing the command has execute permission on the // perl binary in that db home. 09208, 0, "Enter the location of the db home for this database to '-orahome'." // *Cause: Perl permissions are read/write/execute owner (0700). The user this // command is executing as is not the owner of the perl binary. // *Action: Enter the db home as an argument to -orahome. Ensure that // the user executing the command has execute permission on the // perl binary in that db home. / / acfsload 09225, 0, "Failed to start OKS persistent logging." // *Cause: The drivers were successfully loaded but OKS persistent // logging failed to start. // *Action: run "acfsutil plogconfig -d " to perform a manual start. 09226, 0, "ADVM/ACFS drivers not correct for this OS - cannot load." // *Cause: The device drivers installed are not compatible with the // currently running operating system // *Action: run "acfsroot install " to install the correct drivers. 09227, 0, "UNUSED." 09228, 0, "usage: %s {start|stop} [-s]" / / acfsregistrymount / acfssinglefsmount 09250, 0, "Unable to get the ASM administrator user name from the ASM process." // *Cause: ASM processes have not been found running on this system. // This will prevent the requested action from being completed. // *Action: Start ASM ('srvctl start asm') and retry the operation. 09251, 0, "Mount point '%s' unmounted." // *Cause: Informational. // *Action: None. 09252, 0, "The following process IDs have open references on mount point '%s':" // *Cause: Informational. // *Action: None. 09253, 0, "Failed to unmount mount point '%s'. Mount point likely in use." // *Cause: Other processes have outstanding open references on the mount point. // *Action: Terminate applications using files on the mountpoint than retry the // operation (' crsctl stop crs' ). 09254, 0, "Manual intervention is required." // *Cause: Follow up message to ACFS-9253. // *Action: None - Informational. 09255, 0, "Creating '%s' mount point." // *Cause: Informational. // *Action: None. 09256, 0, "Failed to create mountpoint '%s'." // *Cause: The mount point may already exist, the user executing the command // may have insufficient permission, or a system specific error may // have occurred. // *Action: Choose another mount point, execute the action from an account // with the required permissions, or resolve the specified error // shown before this message. 09257, 0, "Mounting device '%s' on mount point '%s'." // *Cause: Informational. // *Action: None. 09258, 0, "Failed to mount device '%s' on mount point '%s'." // *Cause: The mount point may be in use, the user executing this command may // have insufficient permissions, or another system specific error // may have occurred. // *Action: Make sure that the mount point is available, ensure the user // executing the command has the correct permissions, or resolve any // system error shown before this message. 09259, 0, "Mount point '%s' already has a device mounted on it." // *Cause: There is already a device mounted on this mount point. // *Action: If the new device is meant to replace the old device on this mount // point, unmount the old one first and retry the operation. // Otherwise this error may be ignored. 09260, 0, "Failed to connect to the ASM instance." // *Cause: ASM connection attempt failed. // *Action: Ensure that the ORACLE_SID environment variable is correctly set to // the value of the ASM instance. In addition, verify that ASM is // running ('crsctl stat res ora.asm'). 09261, 0, "Invalid _ORA_NAME format." // *Cause: This is an internal error. // *Action: Report this to Oracle Support Services. 09262, 0, "Invalid sub-command '%s'." // *Cause: This is an internal error or the user attempted to run the script // manually with an incorrect sub-command. // *Action: Contact Oracle Support Services or use a correct sub-command. 09263, 0, " Valid sub-commands are 'start', 'stop', 'check', and 'clean'." // *Cause: This results in an incorrect usage of the command. // *Action: Run the command with an option (command) that is supported, // such as 'start', 'stop', 'check', or 'clean'. 09264, 0, "Mount point '%s' is not mounted." // *Cause: Informational. // *Action: None. 09265, 0, " start|stop|clean|check [-d diskgroup] [-v volume] [-h] [-s]" 09266, 0, "The following environment variables must be set:" 09267, 0, " _ORA_NAME ora...acfs" 09268, 0, " _ORA_VOLUME_DEVICE " 09269, 0, " _ORA_MOUNTPOINT_PATH " 09270, 0, "or" 09271, 0, " start [-d device -g diskgroup -m mount_point]" 09272, 0, " stop [-m mount_point]" 09273, 0, " check [-m mount_point]" 09274, 0, "Resource '%s' is not online." // *Cause: Informational. // *Action: None. 09275, 0, "The clean failed to unmount the required mountpoint(s) - re-trying." // *Cause: Informational. A file system could not be unmounted. This could be // due to new process being started just before the unmount. // *Action: None. // 9276 - 9288 UNUSED 09289, 0, "%s not set in environment." // *Cause: The referenced environment variable was not set. // This makes it impossible to continue with the requested action. // *Action: Ensure that the referenced variable is set and retry the operation. 09290, 0, "Waiting for ASM to shutdown." // *Cause: The resource cannot be terminated while ASM is running. // *Action: Wait for ASM to stop. Stop it manually if that does not happen. / / acfsroot 09300, 0, "ADVM/ACFS distribution files found." // *Cause: Informational. // *Action: None. 09301, 0, "ADVM/ACFS installation cannot proceed:" // *Cause: Previous errors have caused the installation to reach a point where // it cannot continue. // *Action: Fix previous errors. 09302, 0, "UNUSED." 09303, 0, "No installation files found for OS kernel version %s." // *Cause: If -k (kernel version) was specified, the version may not be valid. // *Action: Choose a proper OS kernel version, as dictated by the OS platform. // If -k was not specified, the running OS kernel version may not be // supported. Contact Oracle Support Services for an updated ACFS // package. 09304, 0, "Installation cannot proceed: Failed to unload ADVM/ACFS drivers." // *Cause: Applications (possibly ASM) have open references on the drivers. // *Action: Terminate applications and ASM that may be using the drivers, // and retry the installation. 09305, 0, "ADVM/ACFS installation cannot proceed:" // *Cause: Informational. // *Action: Clear previous error and retry. 09306, 0, "Failed to uninstall previous installation." // *Cause: Could not remove ADVM/ACFS commands and or drivers. // *Action: Commands and/or drivers are likely in use. Wait for operations to // finish, unload the drivers, and retry the installation. 09307, 0, "Installing requested ADVM/ACFS software." // *Cause: Informational. // *Action: None. 09308, 0, "Loading installed ADVM/ACFS drivers." // *Cause: Informational. // *Action: None. 09309, 0, "ADVM/ACFS installation correctness verified." // *Cause: Informational. // *Action: None. 09310, 0, "ADVM/ACFS installation failed." // *Cause: A previous error caused this installation to fail. // *Action: Correct previous error and retry the installation. 09311, 0, "not all components were detected after the installation." // *Cause: ADVM/ACFS commands and drivers were found in the installation area // but did not get placed in their assigned locations. // *Action: Re-install using 'acfsroot install -l '. // If necessary, contact Oracle Support Services. 09312, 0, "Existing ADVM/ACFS installation detected." // *Cause: Informational. // *Action: None. 09313, 0, "No ADVM/ACFS installation detected." // *Cause: An attempt was made to un-install ADVM/ACFS components that // did not exist on the system. // *Action: None - there is no problem. 09314, 0, "Removing previous ADVM/ACFS installation." // *Cause: Informational. // *Action: None. 09315, 0, "Previous ADVM/ACFS components successfully removed." // *Cause: Informational. // *Action: None. 09316, 0, "Valid ADVM/ACFS distribution media detected at: '%s'" // *Cause: Informational. // *Action: None. 09317, 0, "No ADVM/ACFS distribution media detected at location: '%s'" // *Cause: If -l (location) is used, the directory specified may be invalid. // *Action: Use the correct directory. 09318, 0, "ORACLE_HOME is not set." // *Cause: This is an internal error. // *Action: Report this to Oracle Support Services. 09319, 0, "Unknown OS kernel version '%s' detected." // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. 09320, 0, "Missing file: '%s'." // *Cause: A required command or driver is not found on the // installation media (pre install) or system (post install). // *Action: If post install, try running acfsroot again. Otherwise, // contact Oracle Support Services. 09321, 0, "Creating udev for ADVM/ACFS." // *Cause: Informational. // *Action: None. 09322, 0, "completed" // *Cause: Informational. // *Action: None. 09323, 0, "Creating module dependencies - this may take some time." // *Cause: Informational. // *Action: None. 09324, 0, "Alternate drivers installed." // *Cause: Informational. // *Action: None. 09325, 0, " Driver OS kernel version = %s." 09326, 0, " Driver Oracle version = %s." 09327, 0, "Verifying ADVM/ACFS devices." // *Cause: Informational. // *Action: None. 09328, 0, "unknown query type '%s'." // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. 09329, 0, "Failed to uninstall driver: '%s'." // *Cause: Acfsinstall failed to uninstall the driver. // *Action: Drivers may be in use. Correct previously reported errors and // retry uninstall. If that fails, contact Oracle Support Services. 09330, 0, "Binary '%s' not installed." // *Cause: A component that should have been installed was not installed. // *Action: Rerun 'acfsroot install'. 09331, 0, " %s [-h] [-s | -v] [-l ] [-k ]" 09332, 0, " [-l ] - location of the distribution files" 09333, 0, " (if not the default location)" 09334, 0, " (comma separated if more than one location specified)" 09335, 0, " [-k ] - install kernel version number" 09336, 0, " (if not the current kernel version)" 09337, 0, "Usage: acfsroot [arguments]" 09338, 0, " Usage: acfsroot uninstall [-h] [-s | -v]" 09339, 0, "The environment variable ORACLE_HOME is not set." // *Cause: This is an internal error. // *Action: Contact Oracle Support Services. 09340, 0, "failed to install %s driver." // *Cause: Acfsinstall failed to install the driver. // *Action: Run acfsinstall manually to see reported errors, resolve them, and // retry. 09341, 0, "Binary '%s' not found." // *Cause: One of the binaries that make up the ACFS package is missing. // *Action: Reinstall the ACFS package and retry the operation. 09342, 0, "unknown." 09343, 0, "Unable to retrieve OS kernel version from module %s." // *Cause: Running modinfo against the usm driver failed. // *Action: None - the current OS kernel version will be used instead. 09344, 0, "Missing directory: '%s'." // *Cause: A required directory is not found on the system. // *Action: Contact Oracle Support Services. 09345, 0, "Unable to create directory: '%s'." // *Cause: Creation of a required directory failed. // *Action: Contact Oracle Support Services. 09346, 0, "Unable to install file: '%s'." // *Cause: Copying to the given destination failed. // *Action: Rerun acfsroot after correcting the OS error. 09347, 0, "Unable to set permission bits (%s) on: '%s'." // *Cause: Setting the given permission bits failed. // *Action: Manually set the permissions to the required level. 09348, 0, "Unable to remove '%s'." // *Cause: A previously installed file was unable to be removed. // *Action: Attempt to manually remove the file. 09349, 0, "Unable to configure driver '%s'." // *Cause: A driver was installed but add_drv failed to write a configuration // file. // *Action: Correct the OS error and re-run acfsroot install. 09350, 0, "Failed to create a symbolic link from '%s' to '%s'." // *Cause: Creating a symbolic link failed. // *Action: Rerun acfsroot after correcting the OS error. 09351, 0, "Unable to remove devlink entry for '%s'." // *Cause: An entry for the driver was found in /etc/devlink.tab but it was // not possible to remove the entry. // *Action: Manually remove the entry from /etc/devlink.tab // and re-run acfsroot uninstall 09352, 0, "Unable to write to '%s'." // *Cause: A file required modifications but it was not possible to write to it. // *Action: Check the file permissions. 09353, 0, "Unable to unconfigure %s." // *Cause: A call to rem_drv failed. // *Action: Correct the OS error and re-run acfsroot uninstall. 09354, 0, "Unable to create symlink: '%s'." // *Cause: Ensure that a file with the same name does not already exist and the user has permission. // *Action: Remove the existing file and make sure the user has the required permission. 09355, 0, "Performing AIX setup failed with error code '%s'." // *Cause: Running AIX initial setup has failed. // *Action: Correct the error and re-run the root install script. 09356, 0, "Saving the AIX ODM changes for '%s' failed with error code '%s'." // *Cause: Running the AIX savebase command failed. // *Action: Correct the error and re-run the root install script. 09357, 0, "Getting the ASMADMIN group failed with error code '%s'." // *Cause: Previous installation steps may have failed. // *Action: Correct the preceding error and re-run the root install script. 09358, 0, "Adding the AIX ODM entry for '%s' failed with error code '%s'." // *Cause: Running the AIX odmadd command failed. // *Action: Correct the error and re-run the root install script. 09359, 0, "The AIX ODM entry for '%s' was successfully added." // *Document: NO 09360, 0, "The command aixsetup failed with error code '%s'." // *Cause: Running the aixsetup script failed. // *Action: Correct the error and re-run the root install script. 09361, 0, "Removing device '%s' failed with error code '%s'." // *Cause: Running the device's undefine method failed. // *Action: Correct the error and re-run the root uninstall script. 09362, 0, "Warning: deleting the AIX ODM entry for '%s' failed with error code '%s'." // *Cause: Running the odmdelete command failed. // *Action: Manually remove the entry or ignore the message. 09363, 0, "Opening the file /etc/vfs for read failed." // *Cause: The /etc/vfs file is not readable. // *Action: Check the permission of the file and ensure it has read permission. 09364, 0, "Opening the file /etc/vfs for append failed." // *Cause: The /etc/vfs file is not writable. // *Action: Check the permission of the file and ensure it has write permission. 09365, 0, "The directory '%s' is not being removed." // *Cause: The directory was scheduled to be uninstalled, but it contained // files that were not installed by acfsroot. // *Action: Manually remove the directory. 09366, 0, "Relative path for mount point '%s' is not supported." // *Cause: Mount point was provided as a relative path. // *Action: Specify the mount point in the form of an absolute path. 09367, 0, "Adding ACFS registry resource failed." // *Document: NO 09368, 0, "Adding ACFS registry resource succeeded." // *Document: NO 09369, 0, "Deleting ACFS registry resource failed." // *Document: NO 09370, 0, "Deleting ACFS registry resource succeeded." // *Document: NO 09371, 0, "Starting ACFS registry resource failed." // *Document: NO 09372, 0, "Starting ACFS registry resource succeeded." // *Document: NO 09373, 0, "Stopping ACFS registry resource failed." // *Document: NO 09374, 0, "Stopping ACFS registry resource succeeded." // *Document: NO 09375, 0, "Adding ADVM/ACFS drivers resource failed." // *Document: NO 09376, 0, "Adding ADVM/ACFS drivers resource succeeded." // *Document: NO 09377, 0, "Deleting ADVM/ACFS drivers resource failed." // *Document: NO 09378, 0, "Deleting ADVM/ACFS drivers resource succeeded." // *Document: NO 09379, 0, "Starting ADVM/ACFS drivers resource failed." // *Document: NO 09380, 0, "Starting ADVM/ACFS drivers resource succeeded." // *Document: NO 09381, 0, "Modification of ADVM/ACFS drivers resource failed." // *Cause: An attempt to modify the ACFS drivers resource resulted in an error. // *Action: Contact Oracle Support Services. 09382, 0, "Modification of ADVM/ACFS drivers resource succeeded." // *Cause: Informational. // *Action: None. 09383, 0, "ADVM/ACFS uninstall cannot proceed" // *Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message // is accompanied by other message(s) providing details on the error. // *Action: Correct the problem indicated in the other messages. 09384, 0, "Invalid OS kernel variation '%s'." // *Cause: The command found an OS kernel variation (e.g., "el5", etc) // that it did not recognize as a valid ADVM/ACFS supported kernel. // *Action: Boot a supported kernel 09385, 0, " Usage: acfsroot version_check [-h] [-l ] [-k ]" 09386, 0, " For more information, use acfsroot -h" 09387, 0, " [-p] - preserve tunable parameters" 09388, 0, "An absolute path name must be specified for the alternate location." // *Cause: A relative path name to the distribution files was specified. // *Action: Enter the absolute path name instead. 09390, 0, "The command '%s' returned unexpected output that may be important for system configuration:" // *Cause: One of the operating system commands used to configure the system // returned an unexpected error. This message is accompanied by other // message(s) providing details of the error. // *Action: See the operating system documentation for the specific command // for more information on this error. 09391, 0, "Checking for existing ADVM/ACFS installation." // *Cause: Informational. // *Action: None. 09392, 0, "Validating ADVM/ACFS installation files for operating system." // *Cause: Informational. // *Action: None. 09393, 0, "Verifying ASM Administrator setup." // *Cause: Informational. // *Action: None. 09394, 0, "The installed driver %s has a build date of %s which does not match the loaded kernel module build date of %s." // *Cause: The most likely cause is that an upgrade or patch procedure // failed to unload the kernel module. // *Action: Reboot the system before attempting to use ACFS. 09395, 0, "Environment variable ODMDIR is not set, unable to proceed with system configuration." // *Cause: Environment variable ODMDIR was not set. // *Action: Ensure that the ODMDIR environment variable is set to the location // of a valid AIX ODM device configuration database. 09396, 0, "Environment variable ODMDIR specifies a nonexistent path, unable to proceed with system configuration." // *Cause: Environment variable ODMDIR specified a nonexistent path. // *Action: Ensure that the ODMDIR environment variable is set to the location // of a valid AIX ODM device configuration database. 09397, 0, "Modification of ADVM/ACFS registry resource failed." // *Cause: An attempt to modify the ACFS registry resource resulted in // an error. // *Action: Contact Oracle Support Services. 09398, 0, "Modification of ADVM/ACFS registry resource succeeded." // *Cause: Informational. // *Action: None. 09399, 0, "Calling 'acfsroot install' to install compatible ADVM/ACFS drivers." // *Cause: Informational. // *Action: None. / / / acfsinstall.exe messages (NT only) / 09400, 0, "Could not open the Service Control Manager." // *Cause: You do not have administrator access. // *Action: Log onto a user account with administrator privileges and retry. 09401, 0, "Failed to install the driver." // *Cause: The specified driver could not be installed. // *Action: Respond based on the accompanying error message. 09402, 0, "The driver file path is too long." // *Cause: The path to the driver exceeded system limits. // *Action: Move the driver to a shorter path or create a shorter link. 09403, 0, "The driver can be either installed or removed, not both." // *Cause: The /i and the /u switches are mutually exclusive. // *Action: Use either /i to install or /u to uninstall the driver. 09404, 0, "Specify either /i (install) or /u (uninstall)." // *Cause: Either /i to install or /u to uninstall the driver is required. // *Action: The /i or the /u switch must be specified. 09405, 0, "Only one driver can be installed at a time." // *Cause: Multiple drivers were specified with the /i option. // *Action: Enter only one driver on the command line. 09406, 0, "Specify either /a (ADVM) or /o (ACFS) or /l (OKS)." // *Cause: The driver to be installed or uninstalled was not specified. // *Action: Enter the driver option on the command line. 09407, 0, "Could not find driver \"%s\" in the current directory." // *Cause: The driver could not be found in the directory specified. // *Action: Verify and enter the correct driver path name. 09408, 0, " The current directory is %\"s\"." // *Cause: Informational. // *Action: None. 09409, 0, "CreateService failed (ERROR_SERVICE_EXISTS)." // *Cause: The driver service already exists. // *Action: None. The service is active. 09410, 0, "CreateService failed." // *Cause: The driver service could not be created. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09411, 0, "CreateService succeeded." // *Cause: Informational. // *Action: None. 09412, 0, "The driver was installed successfully." // *Cause: Informational. // *Action: None. 09413, 0, "RegCreateKeyEx failed." // *Cause: Failed to create a Windows registry key. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09414, 0, "RegSetValueEx (TypesSupported) failed." // *Cause: Failed to set the Windows registry key. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09415, 0, "RegSetValueEx (EventMessageFile) failed." // *Cause: Failed to set the Windows registry key. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09416, 0, "OpenService failed." // *Cause: Could not start the driver. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09417, 0, "The driver was started successfully." // *Cause: Informational. // *Action: None. 09418, 0, "StartService failed (SERVICE_ALREADY_RUNNING)." // *Cause: Informational. // *Action: None. The driver is already running. 09419, 0, "StartService failed." // *Cause: The driver failed to start. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09420, 0, "The driver is not currently installed on this node." // *Cause: The driver is not installed to start. // *Action: Install the driver using the '/i' option. 09421, 0, "The driver is already installed on this node." // *Cause: An attempt was made to install a driver that is already installed. // *Action: none. 09422, 0, "The driver was removed successfully." // *Cause: Informational. // *Action: None. 09423, 0, "Failure trying to remove the driver, DeleteService failed.\n The driver service is pending deletion or is in an invalid state." // *Cause: The driver could not be removed. // *Action: Make sure that all references to the driver have been removed // and, if the driver is "oracleacfs.sys", that "acfsutil detach" // has been run. Verify that the driver is in the STOPPED state and // then retry the operation. If the driver removal // still fails, you probably need to reboot the node." 09424, 0, "The driver was stopped successfully." // *Cause: Informational. // *Action: None. 09425, 0, "The driver could not be stopped: StopService failed." // *Cause: The driver could not be stopped. // *Action: Correct the problem indicated by the accompanying error message // and retry the operation. 09426, 0, "Unable to set the file attributes for file %s." // *Cause: The file attributes for the oject file could not be set. // *Action: Reset the attributes with "attrib -r " // and then retry the operation. 09427, 0, "Failed to unload ADVM/ACFS drivers. A system reboot is recommended." // *Cause: An unexpected condition has been detected for which a system // reboot is the best cause of action. // *Action: Reboot the system. //09428 - 09439 AVAILABLE 09440, 0, "Usage: %s [/i | /u] [/a | /o | /l] " 09441, 0, "/i Install the driver" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. 09442, 0, "/u Uninstall the driver" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. 09443, 0, "/a Perform the operation for the ADVM driver" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. 09444, 0, "/o Perform the operation for the ACFS driver" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. 09445, 0, "/l Perform the operation for the OKS driver" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. 09446, 0, " Path to the driver. If not specified,\n defaults to oracleadvm.sys, oracleacfs.sys, or\n oracleoks.sys in the current directory\n" // *Cause: Syntax error. // *Action: Use syntax as specified in the 'Usage' message. / 9447 - 9449 - AVAILABLE 09450, 0, "Examples:" // *Cause: Informational. // *Action: None. 09451, 0, "%s /i /a (Install the ADVM driver from the current directory)" // *Cause: Informational. // *Action: None. 09452, 0, "%s /u /o (Uninstall the ACFS driver)" // *Cause: Informational. // *Action: None. 09453, 0, "%s /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified file)" // *Cause: Informational. // *Action: None. 09454, 0, "Unable to delete the driver file %s after stopping driver." // *Cause: A call to the Windows DeleteFile function to delete the driver file // failed. // *Action: Manually delete the specified driver file using Windows Explorer. // If you were installing the driver please retry after deletion. 09455, 0, "Unable to copy driver file %s to the path %s." // *Cause: Could not copy the driver file to the specified directory because // the Windows CopyFile function failed. // *Action: Manually delete any previous driver file from the specified // directory using Windows Explorer and retry the install. 09456, 0, "An attempt to stop the driver %s failed." // *Cause: The driver could not be properly stopped; it is in an invalid // state. // *Action: Reboot system. 09457, 0, "The driver file does not match the driver chosen to install." // *Cause: The driver file is not consistent with the driver option used. // *Action: Specify a path to oracleoks.sys when using the /l option. // path to oracleacfs.sys with the /o option // and path to oracleadvm.sys with the /a option. 09458, 0, "The Windows '%s' service is in an invalid state. The new driver cannot be installed." // *Cause: An attempt to install the new driver failed because the existing // service could not be stopped properly. // *Action: Reboot system and then retry the install. 09459, 0, "ADVM/ACFS is not supported on this OS version: '%s'" // *Cause: ADVM/ACFS device drivers have not been ported to this OS version. // *Action: None. / / ACFS Security and Encryption messages / 10101, 0, "Authentication failed." //* Cause: The specified ACFS Security administrator password was wrong. //* Action: Re execute the command and provide the correct ACFS Security // administrator password at the prompt. 10120, 0, "ACFS Encryption not initialized." //* Cause: ACFS Encryption was not initialized. //* Action: Run 'acfsutil encr init [-p]' as system administrator to initialize encryption. 10149, 0, "Realm description cannot exceed %d characters" // *Cause: Realm description cannot exceed 255 characters // *Action: Select a shorter realm name and retry. 10150, 0, "Realm description not specified within double quotation marks" // *Cause: Invalid description specified for realm. // *Action: Enclose the realm description within double quotation marks. 10151, 0, "Unmatched single quote or double quote." // *Cause: Matching quote was not found. // *Action: Add a matching quote and retry. 10152, 0, "Realm name cannot exceed %d characters." // *Cause: Realm name length exceeded 255 characters. // *Action: Select a shorter realm name and retry. 10153, 0, "Realm '%s' not found on mount point '%s'." // *Cause: Realm was not found on mount point. // *Action: Ensure that the realm exists using the command 'acfsutil sec info -m -n'. 10154, 0, "Failed to create realm '%s' on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10155, 0, "Realm '%s' created." // *Cause: Realm was created. // *Action: None 10156, 0, "Failed to destroy realm '%s' on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10157, 0, "Realm '%s' destroyed." // *Cause: Realm was destroyed. // *Action: None 10158, 0, "Improper value specified for -l option." // *Cause: Invalid argument format was specified for -l option. // *Action: Specify the argument in the format 'commandrule:ruleset'. A comma separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example: // * - acfsutil sec realm add r1 -m /mnt -l READ:rs1 // * - acfsutil sec realm add r1 -m /mnt -l READ:rs1,MKDIR:rs2 10159, 0, "The command requires at least one of the options -u, -G, -l, -f, or -e." // *Cause: None of the options -u, -G, -l, -f, or -e were specified with this command. // *Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command. 10160, 0, "Failed to add user '%s' to the realm '%s'." // *Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10161, 0, "Added user '%s' to realm '%s'." // *Cause: User was added to realm. //* Action: None. 10162, 0, "Failed to add group '%s' to realm '%s'." // *Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10163, 0, "Added group '%s' to the realm '%s'." //* Cause: Group was added to the realm. //* Action: None. 10164, 0, "Failed to add filter '%s:%s' to the realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10165, 0, "Added filter '%s:%s' to the realm '%s'." //* Cause: Filter was added to the realm. //* Action: None. 10166, 0, "Failed to add '%s' to the realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10167, 0, "Added '%s' to the realm '%s'." //* Cause: Pathname was added to the realm. //* Action: None. 10168, 0, "Failed to turn encryption ON for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10169, 0, "Encryption turned ON for realm '%s'." //* Cause: Encryption was turned ON for realm. //* Action: None. 10170, 0, "Failed to delete user '%s' from realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10171, 0, "Deleted user '%s' from realm '%s'." //* Cause: User was deleted from realm. //* Action: None. 10172, 0, "Failed to delete group '%s' from the realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10173, 0, "Deleted group '%s' from realm '%s'." //* Cause: Group was deleted from realm. //* Action: None. 10174, 0, "Failed to delete filter '%s:%s' from the realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10175, 0, "Deleted filter '%s:%s' from realm '%s'." //* Cause: Filter was deleted from realm. //* Action: None. 10176, 0, "Failed to delete '%s' from realm '%s'." //* Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10177, 0, "Deleted '%s' from realm '%s'." //* Cause: Pathname was deleted from realm. //* Action: None. 10178, 0, "Failed to turn encryption OFF for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10179, 0, "Encryption turned OFF for realm '%s'." // *Cause: Encryption was turned OFF for realm. // *Action: None. 10180, 0, "Failed to get realm files or directories for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10181, 0, "Failed to get groups for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10182, 0, "Failed to get users for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10183, 0, "Failed to get filters for realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10184, 0, "Failed to get realm encryption attributes of realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10185, 0, "'-e' requires both '-a' and '-k'." // *Cause: At least one of the options -a or -k is missing with -e option. // *Action: Specify both '-a' and '-k' with '-e' and retry. 10186, 0, "Realm '%s' already exists on mount point '%s'." // *Cause: Realm was already found on mount point. // *Action: Specify another realm name and retry. 10187, 0, "Failed to get all realms on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10188, 0, "Attributes of realm '%s' retrieved." //* Cause: Realm attributes were retrieved. //* Action: None. 10189, 0, "Failed to update attributes of realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10190, 0, "Updated attributes of realm '%s'." //* Cause: Updated realm attributes. //* Action: None. 10191, 0, "Ofssec group name cannot exceed %d characters." 10192, 0, "Group '%s' not found." 10193, 0, "Failed to perform group create operation on '%s'." 10194, 0, "Group create operation is complete." 10195, 0, "None of the options -a, -d, are specified with the edit command." 10196, 0, "Failed to add user '%s' to the group." 10197, 0, "Additions of user '%s' to the group is complete." 10198, 0, "Failed to delete user '%s' from the group." 10199, 0, "Deletion of user '%s' from the group is complete." 10200, 0, "Failed to perform group destroy operation on '%s'." 10201, 0, "Group destroy operation is complete." 10202, 0, "Failed to get users belonging to this group." 10203, 0, "Group '%s' already exists." 10204, 0, "The %s '%s' will neither be added nor be deleted." 10205, 0, "The option -f should be specified at the end after all other options." 10206, 0, "File or directory '%s' does not belong to an ACFS file system" // *Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did not // belong to an ACFS file system. // *Action: Specify only ACFS file or directory in the command 'acfsutil sec realm add/delete'. 10221, 0, "Rule name cannot exceed %d characters." // *Cause: Rule name length exceeded 255 characters. // *Action: Select a rule name that is smaller than 255 characters and retry. 10223, 0, "Invalid rule type is specified." // *Cause: Invalid rule type was provided on the command line with '-t'. // *Action: Provide one of the following with '-t': //* - username //* - application //* - time , //* - hostname 10224, 0, "Rule type 'username', 'application' or 'hostname' must have only one rule value." // *Cause: An incorrect number of arguments were provided with rule type 'username', // 'application' or 'hostname'. // *Action: Provide only one argument after the rule type 'username', 'application' // or 'hostname'. //* For example, '-t username alice' //* '-t application 'c:\programs\mozilla.exe' //* '-t application '/sbin/cat' //* '-t hostname myhost.domain.com' 10225, 0, "Rule type 'time' must have both start time and end time separated by a comma." // *Cause: Either the start time or end time was not provided. // *Action: Specify both start time and end time (comma separated) after rule type time. //* For example, '-t time 10:10:40,23:01:12' 10226, 0, "'-o' requires either 'ALLOW' or 'DENY'." // *Cause: A valid rule option was not provided. // *Action: Specify either 'ALLOW' or 'DENY' as rule the option. 10227, 0, "Failed to perform rule create operation on '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10228, 0, "Rule '%s' is created." //* Cause: Rule was created. //* Action: None. 10229, 0, "Rule '%s' not found." // *Cause: Rule was not found. // *Action: Ensure that the rule exists by executing 'acfsutil sec info -m -l '. 10230, 0, "Failed to perform rule edit operation on '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10231, 0, "Rule '%s' updated." //* Cause: Rule was updated. //* Action: None. 10232, 0, "Failed to destroy rule '%s'." // *Cause: Internal error // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10233, 0, "Rule '%s' destroyed." //* Cause: Rule was destroyed. //* Action: None. 10234, 0, "Failed to get rule '%s' information." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10235, 0, "Rule '%s' already exists." // *Cause: Rule was already found on mount point. // *Action: Specify another rule name and retry. 10236, 0, "Time format %s must be HH:MM:SS. " // *Cause: The time format provided was not formatted as 'HH:MM: SS', where HH translates to hours, MM to minutes and SS to seconds. // *Action: Specify the time in correct format and retry. 10237, 0, "Rule type '%s' specified does not match the actual type '%s' of rule '%s'" // *Cause: The rule type specified did not match the actual rule typed. // *Action: Specify the actual rule type to update the rule value and retry. 10238, 0, "Failed to get all rules on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10239, 0, "Failed to get information for rule '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10240, 0, "Cannot destroy rule '%s'. The rule is in use by one or more rule sets." // *Cause: The rule was being used in one or more rule set(s) in the file // system. // *Action: Remove the rule from the rule set(s) and retry. 10241, 0, "Rule set name cannot exceed %d characters." // *Cause: Rule set name length exceeded 255 characters. // *Action: Select a shorter rule set name and retry. 10242, 0, "'-o' requires either ALL_TRUE or ANY_TRUE." // *Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE. // *Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'. 10243, 0, "Failed to create rule set '%s' on mount point '%s'." // *Cause: Internal error // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10244, 0, "Rule set '%s' is created." //* Cause: Rule set was created. //* Action: None. 10245, 0, "Rule set '%s' not found on mount point '%s'." // *Cause: Rule set was not found on mount point. // *Action: None. 10246, 0, "Failed to add rule '%s' to the rule set '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10247, 0, "Added rule '%s' to the rule set '%s'." //* Cause: Rule was added to the rule set. //* Action: None. 10248, 0, "Failed to delete rule '%s' from the rule set '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10249, 0, "Deleted rule '%s' from rule set '%s'." //* Cause: Rule was deleted from the rule set. //* Action: None. 10250, 0, "Failed to destroy rule set '%s' on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10251, 0, "Rule set '%s' destroyed." //* Cause: Rule set was destroyed. //* Action: None. 10252, 0, "Failed to get rules for rule set '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10253, 0, "Failed to get list of command rules." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10254, 0, "Rule set '%s' already exists." // *Cause: Rule set was already found on mount point. // *Action: Specify another rule set name and retry. 10255, 0, "Rule '%s' already exists in rule set '%s'." // *Cause: Rule was already part of rule set. // *Action: None. 10256, 0, "Rule '%s' is not found in rule set '%s'." // *Cause: Rule was not found in the rule set. // *Action: Ensure that the realm exists using the command 'acfsutil sec info -m <> -s '. 10257, 0, "Failed to get all rule sets on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10258, 0, "Failed to get information for rule set '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10259, 0, "Invalid command rule '%s'." //* Cause: Invalid command rule was specified. //* Action: Execute 'acfsutil sec info -m -c' to get all the valid command rules. //* Re-execute the command with valid command rule. 10260, 0, "File object '%s' and the realm '%s' should be in the same file system." //* Cause: File object was not in the same file system as that of the realm. //* Action: Specify file objects from the same file system as that of the realm. 10261, 0, "Cannot destroy rule set '%s'. The rule set is in use by one or more realms." // *Cause: The rule set is being used in filter(s) that are part of one or more realms in the file system. // *Action: Remove the filter(s) from the realms that are using this rule set and retry. 10262, 0, "Application path name for rule type 'application' cannot exceed '%d' characters." // *Cause: Application path name for rule type 'application' exceeded 511 characters // *Action: Select a shorter application path name for rule type 'application' and retry. 10263, 0, "Host name for rule type 'hostname' cannot exceed '%d' characters." // *Cause: Host name for rule type 'hostname' exceeded 255 characters. // *Action: Select a shorter host name for rule type 'hostname' and retry. 10264, 0, "Invalid value for rule type '%s' as the given path name '%s' is a symbolic link" // *Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic links are not supported for rule type 'application'. // *Action: Specify a path name which is not a symbolic link and re-execute the command. 10271, 0, "Encryption algorithm can be only 'AES'." // *Cause: The encryption algorithm provided was not 'AES'. // *Action: Specify 'AES' as the algorithm with '-a' and retry. 10272, 0, "Key length must be either 128, 192, or 256." // *Cause: The key length specified with '-k' was not 128, 192 or 256. // *Action: Specify either 128, 192, or 256 with '-k' and retry. 10273, 0, "Failed to set the encryption parameter on realm '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10274, 0, "Failed to update rule set option." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10275, 0, "Failed to get rule sets for mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10276, 0, "Rule set '%s' option updated to '%s'." //* Cause: Rule set option updated. //* Action: None. 10277, 0, "'-e' requires either ON or OFF." // *Cause: The realm encryption status specified with '-e' was not // 'on' or 'off' // *Action: Specify either 'on' or 'off' with -e and retry. 10278, 0, "Encryption parameters are not set on the file system, realm encryption is unavailable." // *Cause: The encryption parameters were not set on the file system. // *Action: A system administrator must execute an 'encr set' command 10281, 0, "Only on/off switch is valid." 10283, 0, "Clone realm does not exist." 10284, 0, "Failed to get security information for '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10285, 0, "Pathname '%s' does not exist." // *Cause: Specified pathname was not found. // *Action: Specify a valid pathname. 10286, 0, "User '%s' does not exist." // *Cause: User was not found. // *Action: Specify a valid user. 10287, 0, "Group '%s' does not exist." // *Cause: Group was not found // *Action: Specify a valid group. 10288, 0, "User '%s' already added to the realm '%s'." // *Cause: User was already added to the realm. // *Action: None 10289, 0, "Group '%s' already added to the realm '%s'." // *Cause: Group was already added to the realm // *Action: None. 10290, 0, "Realm filter '%s' already added to the realm '%s'." // *Cause: Filter was already added to the realm. // *Action: None. 10291, 0, "Pathname '%s' already added to the realm '%s'." // *Cause: Pathname was already added to the realm. // *Action: None. 10292, 0, "User '%s' is not part of the realm '%s'." // *Cause: User was not part of the realm. // *Action: None. 10293, 0, "Group '%s' is not part of the realm '%s'." // *Cause: Group was not part of the realm. // *Action: None. 10294, 0, "Pathname '%s' is not part of the realm '%s'." // *Cause: Pathname was not part of the realm. // *Action: None. 10295, 0, "Realm filter '%s' is not part of the realm '%s'." // *Cause: Filter was not part of the realm. // *Action: None. 10296, 0, "Realm filter '%s:%s' could not be added to the realm '%s'." // *Cause: The filter was not added because the filter with command rule 'ALL' was already part of the realm. // *Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. Individual command rules cannot be added when 'ALL' is already present. 10297, 0, "Realm filter 'ALL' could not be added since another filter exists in realm '%s'." // *Cause: Filter 'ALL' was not added because another filter existed in the realm . // *Action: Either add the command rules individually or add 'ALL' if all of the command rules are desired. 'ALL' command rule cannot be added when individual command rules are already present. 10298, 0, "User name cannot exceed %d characters." // *Cause: User name length exceeded 64 characters. // *Action: Select a shorter user name and retry. 10299, 0, "Group name cannot exceed %d characters." // *Cause: Group name length exceeded 64 characters. // *Action: Select a shorter group name and retry. 10300, 0, " %s" // *Document: NO 10301, 0, " ----NONE----" 10302, 0, " %s : %s" 10309, 0, "The following users have security administrative privileges:" // *Document: NO 10310, 0, "\nRealms present on mount point '%s' are as follows : " 10311, 0, "\nUsers present in realm '%s' are as follows : " 10312, 0, "\nUsers present in group '%s' are as follows : " 10313, 0, "\nRules present in rule set '%s' are as follows : " 10314, 0, "\nRules present on mount point '%s' are as follows : " 10315, 0, "\nInformation of rule '%s' are as follows : " 10316, 0, "\nRule sets present on mount point '%s' are as follows : " 10317, 0, "\nEncryption status : %s " 10318, 0, "Encryption algorithm : %s " 10319, 0, "Encryption key length : %d " 10320, 0, "\nGroups present in realm '%s' are as follows : " 10321, 0, "\nFilters present in realm '%s' are as follows : " 10322, 0, "System realm 'SYSTEM_SecurityMetadata' created." //* Cause: System realm 'SYSTEM_SecurityMetadata' was created. //* Action: None. 10323, 0, "System realm 'SYSTEM_Logs' created." //* Cause: System realm 'SYSTEM_Logs' was created. //* Action: None. 10324, 0, "Rulesets cannot be cloned before cloning rules on mount point '%s'." //* Cause: Rule sets were not cloned because some rules were not present on mount point. //* Action: Clone rules first using command 'acfsutil sec rule clone' and then clone rule sets. 10325, 0, "Realm status: %s" //* Document: NO 10326, 0, "Type : %s" //* Document: NO 10327, 0, "Value : %s" //* Document: NO 10328, 0, "Value : '%s' - '%s'" //* Document: NO 10329, 0, "Option : %s" //* Document: NO 10330, 0, "\nRealm description : '%s' " //* Document: NO 10331, 0, " Backup operator group : %s" //* Document: NO 10332, 0, " Encryption status: %s" //* Document: NO 10333, 0, "File system: %s" //* Document: NO 10334, 0, " Algorithm: %s %d-bits" //* Document: NO 10335, 0, " Key length: %d bytes" //* Document: NO 10336, 0, " Last rekey time: %s" //* Document: NO 10337, 0, "Failed to get security related information on mount point '%s'." //* Document: NO 10338, 0, " Security status: %s" //* Document: NO 10339, 0, "Encryption is not set on mount point '%s'." 10340, 0, "The path name '%s' is part of the following realms:" 10341, 0, "The path name '%s' is not part of any realm." 10342, 0, "System realm 'SYSTEM_BackupOperators' created." //* Cause: System realm 'SYSTEM_BackupOperators' was created. //* Action: None. 10343, 0, "Re-enter password for ACFS Encryption key store:" // *Document:NO 10344, 0, "Password for new ACFS Security administrator:" // *Document:NO 10345, 0, "New password:" // *Document:NO 10346, 0, "Re-enter password for new ACFS Security administrator:" // *Document:NO 10347, 0, "Re-enter new password:" // *Document:NO 10348, 0, "ACFS Security administrator password:" // *Document:NO 10349, 0, "Password for ACFS Encryption key store:" // *Document:NO 10350, 0, "Incorrect password was entered in all attempts to open the encryption key store. Encrypted files will not be available." // *Cause: Incorrect password was entered in all attempts to open the encryption key store during the mount command. // *Action: Unmount the file system and remount it, providing the correct password. Encrypted files will // not be available until the file system is unmounted and remounted with the correct password. 10351, 0, "Path name: '%s'" 10352, 0, " Realm membership:" 10353, 0, " Encryption details:" 10354, 0, " Realm membership: None" 10355, 0, "System realm 'SYSTEM_Antivirus' created." //* Cause: System realm 'SYSTEM_Antivirus' was created. //* Action: None. 10400, 0, "Encryption is set on mount point '%s'." //* Cause: Encryption was set on mount point. //* Action: None. 10401, 0, "Failed to set encryption parameters on mount point '%s'." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10402, 0, "Encryption turned '%s' on '%s'." //* Cause: Encryption was turned either ON or OFF on the pathname. //* Action: None. 10403, 0, "Failed to turn encryption '%s' on '%s'." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10404, 0, "Encryption info command execution is complete." 10405, 0, "Failed to get encryption information on '%s'." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10406, 0, "Re-key operation is complete on '%s'." //* Cause: Re-key operation was complete on the pathname. //* Action: None. 10407, 0, "Failed to perform re-key operation on '%s'." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10408, 0, "rekey cannot be performed on decrypted file\n" // *Document:NO 10409, 0, "file is part of a read-only snapshot, encryption operations are not allowed\n" // *Document:NO 10410, 0, "encryption is already disabled on the file system" // *Cause: Encryption was already disabled on the file system. // *Action: None, encryption is already disabled. 10411, 0, "encryption is already enabled on the file system" // *Cause: Encryption was already enabled on the file system. // *Action: None, encryption is already enabled. 10412, 0, "Encryption parameters were not provided, using default algorithm (%s) and key length (%d)." // *Cause: Encryption parameters were not provided. // *Action: None, default values have been used. 10413, 0, "The ADVM compatibility attribute for the diskgroup must be set to version 11.2.0.2.0 to allow the acfsutil encryption and security commands." // *Cause: The ADVM compatibility attribute has not been upgraded to // version 11.2.0.2.0 or beyond. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute. 10414, 0, "Encryption has been initialized for the cluster." // *Cause: An administrator initialized encryption for the cluster. // *Action: None. 10415, 0, "File system level encryption is on, file level encryption operations are not allowed" // *Cause: A file level encryption operation was attempted while file system level encryption was enabled. File level encryption operations are not allowed when file system level encryption is turned on. // *Action: None. 10416, 0, "File is realm secured\n" // *Cause: An encryption operation was attempted on a realm secured file and no action was performed. A realm secured file can only be encrypted and decrypted by changing the encryption parameters of containing realm(s) or by deleting the file from all realms. // *Action: If changing the encryption status of this file is required, contact a Security Administrator to modify the encryption parameters of the containing realm(s). 10417, 0, "File is already encrypted\n" // *Document: NO 10418, 0, "File is already decrypted\n" // *Document: NO 10419, 0, "Skipping directory '%s' because it does not belong to the file system mounted on '%s'" // *Cause: The directory does not belong to the specified mounted ACFS file system. // *Action: None. 10420, 0, "Encryption parameters specified for realm '%s' match existing settings." // *Cause: An attempt to set encryption parameters for a realm specified values the same as those already set. // *Action: None. 10421, 0, "The ADVM compatibility attribute for the diskgroup must be set to version '%s' to allow acfsutil encryption commands." // *Cause: An adminstrator attempted an encryption set or volume level rekey operation, but the ADVM compatibility attribute had not been upgraded to a supported version. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute. 10422, 0, "The ADVM compatibility attribute for the diskgroup must be set to version '%s' to allow 'acfsutil sec' commands." // *Cause: A security adminstrator attempted an ACFS Security operation, but the ADVM compatibility attribute had not been upgraded to a supported version. // *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade // COMPATIBLE.ADVM attribute and retry the operation. / / Encryption messages only sent to log files / 10450, 0, "Unauthorized encryption operation attempted on '%s'." // *Cause: A user attempted an encryption operation on the given file and the operation was denied. // *Action: None. 10451, 0, "File level encryption operation attempted on realm secured file '%s'." // *Cause: A user attempted to perform a file level encryption command on a realm secured file and the operation was denied. // *Action: None. 10452, 0, "Failed to decrypt '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10453, 0, "Unable to get encryption parameters for the file system mounted on '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10454, 0, "File system level encryption turned on for mount point '%s'." // *Cause: A system administrator enabled file system level encryption. // *Action: None. 10455, 0, "New volume encryption key generated for mount point '%s'." // *Cause: A system administrator updated the volume encryption key for the mount point. The file encryption keys for all encrypted files on the file system were re-encrypted using the new volume encryption key. // *Action: None. 10456, 0, "New file encryption key generated for file '%s'." // *Cause: A system administrator updated the volume encryption key for the file. The data in the file was re-encrypted using the new key. // *Action: None. 10457, 0, "New file encryption keys generated for all files in directory '%s'." // *Cause: A system administrator updated the volume encryption key for the files in the given directory. The file contents were re-encrypted using the new key. // *Action: None. 10458, 0, "Encryption turned off for path '%s'." // *Cause: A user successfully decrypted a file or directory. // *Action: None. 10459, 0, "Encryption turned off for directory '%s' and its contents." // *Cause: A user successfully decrypted a directory and its contents. // *Action: None. 10460, 0, "File system level encryption turned off for mount point '%s'." // *Cause: A system administrator disabled file system level encryption. // *Action: None. 10461, 0, "Encryption turned on for path '%s'." // *Cause: A user successfully encrypted a file or directory. // *Action: None. 10462, 0, "Encryption turned on for directory '%s' and its contents." // *Cause: A user successfully encrypted a directory and its contents. // *Action: None. 10500, 0, "Pathname cannot exceed %d characters." // *Cause: Pathname length exceeds 255 characters. // *Action: Select a name that is smaller than %d characters and retry. 10540, 0, "Wallet created." 10541, 0, "Wallet '%s' creation failed [error : %d %s]." 10542, 0, "Wallet '%s' save failed [error : %d %s]." 10543, 0, "Wallet '%s' open failed [error : %d %s]." 10544, 0, "Wallet delete succeeded." 10545, 0, "Wallet '%s' delete failed [error : %d %s]." 10546, 0, "Wallet now owned by '%s'." 10547, 0, "Wallet '%s' could not be owned by '%s:%s' [error : %d %s]." 10548, 0, "Wallet initialization failed [error : %d %s]." 10549, 0, "Wallet termination failed [error : %d %s]." / / More of security messages / 10550, 0, "Security wallet created." //* Cause: Security wallet was created. //* Action: None. 10551, 0, "Security wallet creation failed." //* Cause: Internal error. //* Action: Contact Oracle Support Services. 10552, 0, "Security wallet save failed." 10553, 0, "Security wallet open failed." 10554, 0, "Security wallet delete succeeded." 10555, 0, "Security wallet delete failed." 10556, 0, "Security wallet now owned by '%s'." 10557, 0, "Security wallet could not be owned by '%s'." 10558, 0, "Security wallet does not exist." 10559, 0, "Insufficient privileges to switch to %s '%s'." 10563, 0, "Current user does not have system administrative privileges to initialize encryption." 10564, 0, "Incorrect password for encryption key store." // *Cause: An incorrect password was entered while opening the encryption key store. // *Action: Retry the command and enter the correct password. 10565, 0, "Encryption key store created." //* Cause: Encryption key store was created. //* Action: None. 10566, 0, "Encryption key store creation failed." //* Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10567, 0, "Encryption key store save failed." 10568, 0, "Encryption key store open failed." 10569, 0, "Encryption key store delete succeeded." 10570, 0, "Encryption key store delete failed." 10571, 0, "Creating PKCS key store for encryption..." 10572, 0, "Creating SSO key store for encryption..." 10573, 0, "Encryption key store not found." // *Cause: Encryption key store did not exist. // *Action: Run 'acfsutil encr init' command and retry. 10574, 0, "ACFS encryption already initialized, cannot reinitialize." // *Cause: 'acfsutil encr init'can has already been executed and the encryption key store already existed. // *Action: None. 10575, 0, "Incorrect encryption key store." // *Cause: The encryption key store may have been deleted and re-created. // *Action: Recover the correct key store from a backup and retry. 10576, 0, "Incorrect encryption key, new volume encryption key not created." // *Cause: The encryption key store may have been deleted and re-created. // *Action: Recover the correct key store from a backup and retry. 10577, 0, "Encryption parameters not set." // *Cause: A command that requires encryption parameters to be set first was run before encryption parameters were set on the file system. // *Action: Run 'acfsutil encr set' and retry. 10578, 0, "Unable to communicate new encryption settings to cluster members." // *Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10579, 0, "Key store is not valid for encryption." // *Cause: The encryption key store was either not created using 'acfsutil encr init' or it was corrupted. // *Action: Restore the encryption key store from a backup and retry. 10580, 0, "Internal API error : [%d : %s]." 10581, 0, "Internal API error : [%s]." 10582, 0, "Internal API error : [%d : %s %s]." 10583, 0, "Internal API error : [%s, %d]." 10585, 0, "Ioctl '%s' failed in '%s' with error %d." 10586, 0, "Internal error." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10588, 0, "Internal error : WLT %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10589, 0, "Internal error : BSF %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10590, 0, "Internal error : XML %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10591, 0, "Internal error : TSP %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10592, 0, "Internal error : IOC %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10593, 0, "Internal error : UGP %d." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10594, 0, "Internal error : OCR %d : %s." // *Cause: Internal error occurred. // *Action: Contact Oracle support service. 10596, 0, "Unable to get the hostname for the current node." // *Cause: The current user does not have access to the requested information. // *Action: Contact Oracle Support Services. 10597, 0, "The user '%s' and the group '%s' do not belong to the same domain." // *Cause: The user and the group were not part of the same domain. // *Action: Use 'net user' command to verify and retry with user and group // that belong to the same domain. 10598, 0, "Unable to retrieve domain name information for '%s'." // *Cause: Unable to retrieve domain name information. // *Action: Make sure the node is part of proper domain. 10599, 0, "Current user does not have system administrative privileges to initialize ACFS security." // *Cause: The user was not part of system administrators group. // *Action: Run 'acfsutil sec init' with administrative privileges. 10600, 0, "Failed to store first security administrator '%s' in wallet." //* Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10601, 0, "Failed to update first security administrator '%s' information." //* Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10602, 0, "Passwords do not match." // *Cause: Verification of the password did not succeed. // *Action: Re-execute and provide the same password on both the prompts. 10603, 0, "Security administrator group already set in wallet." // *Cause: Security administrator group was already set in wallet. // *Action: None. 10604, 0, "Security administrator group not set in wallet." // *Cause: Internal error. // *Action: Contact Oracle Support Service. 10605, 0, "Unable to get security administrator group in wallet." 10606, 0, "User '%s' is not a security administrator." // *Cause: User was not a security administrator. // *Action: Only a security administrator has privilege to execute the security commands. Add the user to security administrator list by executing 'acfsutil sec admin add' and retry. 10607, 0, "User '%s' is not member of security administrator group." // *Cause: User was not a member of security administrator's group. // *Action: Add the user to the security administrator's group. 10608, 0, "User '%s' is not found in security wallet." 10609, 0, "Administrator update in driver failed." // *Cause: Internal error // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10610, 0, "Failed to get current user information." // *Cause: Internal error. // *Action: Contact Oracle Support Service. 10611, 0, "Failed to assign user '%s' as security administrator." // *Cause: Internal error // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10612, 0, "Failed to remove user '%s' from security administrator(s) list." // *Cause: Internal error // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10613, 0, "Failed to change ACFS Security administrator password for current user." // *Cause: Internal error // *Action: Contact Oracle Support Services. 10614, 0, "Security administrator '%s' already added." // *Cause: User was already a security administrator. // *Action: None. 10615, 0, "User '%s' is not a security administrator." //* Cause: User was not a security administrator. //* Action: None. 10616, 0, "Incorrect ACFS Security administrator password." // *Cause: The password supplied was incorrect. // *Action: Re-execute and provide the correct ACFS Security administrator // password for the current user. 10617, 0, "Password cannot exceed %d characters." //* Cause: The password entered exceeded the maximum allowed characters. //* Action: Enter the password within the specified number of characters. 10618, 0, "Security administrator '%s' could not be added." //* Cause: Security administrator was not added. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10619, 0, "Security administrator '%s' added." //* Cause: Security administrator was added. //* Action: None. 10620, 0, "Security administrator '%s' could not be removed." //* Cause: Security administrator was not removed. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10621, 0, "Removal of the last security administrator '%s' is not allowed." //* Cause: The security administrator was not removed being the only security administrator in this system. //* Action: Add another security administrator to remove the intended security administrator. 10622, 0, "Security administrator '%s' removed." //* Cause: Security administrator was removed. //* Action: None. 10623, 0, "ACFS security already initialized, cannot reinitialize." //* Cause: ACFS security was already initialized and could not be reinitialized. //* Action: None. 10624, 0, "User '%s' is not member of the group '%s'." // *Cause: The user was not member of the group. // *Action: Add the user to the group and retry. 10625, 0, "Failed to prepare file system for security operations on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10626, 0, "Mount point '%s' is already prepared for security." // *Cause: Mount point was already prepared for security. Prepare should be executed only once for an ACFS formatted file system that is mounted. // *Action: None. 10627, 0, "Mount point '%s' is now prepared for security operations." //* Cause: " Mount point was prepared for security operations. //* Action: None. 10628, 0, "Failed to prepare filesystem on mount point '%s'" 10629, 0, "Failed to enable security on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10630, 0, "Security is already enabled on mount point '%s'." // *Cause: Security was already enabled on mount point. // *Action: None. 10631, 0, "Security is now enabled on mount point '%s'." // *Cause: Security was enabled on mount point. // *Action: None. 10632, 0, "Security is already disabled on mount point '%s'." // *Cause: Security was already disabled on mount point. // *Action: None. 10633, 0, "Security is now disabled on mount point '%s'." // *Cause: Security was disabled on mount point. // *Action: None. 10634, 0, "Failed to disable security on mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10635, 0, "Failed to get security administrator group." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10636, 0, "Security administrator group retrieved." //* Cause: Security administrators group was retrieved. //* Action: None. 10637, 0, "File system is not prepared for ACFS security on mount point '%s'." // *Cause: File system was not prepared for security operations on mount point. // *Action: Execute 'acfsutil sec prepare' to prepare security operation on mount point. 10638, 0, "Backup and log directories created." //* Cause: Backup and log directories were created. //* Action: None. 10639, 0, "Failed to create directory '%s' on mount point '%s'." //* Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10640, 0, "Failed to create log directory on mount point '%s'." //* Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10641, 0, "Failed to create backup directory on mount point '%s'." //* Cause: Internal error. //* Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10642, 0, "Backup operator group '%s' does not exist" 10643, 0, "Security is already enabled on realm '%s'." //* Cause: Security was already enabled on realm. //* Action: None. 10644, 0, "Security is already disabled on realm '%s'." //* Cause: Security was already disabled on realm. //* Action: None. 10645, 0, "Failed to set owner of file '%s' to '%s'." //* Cause: Current user is not owner of the file. //* Action: Login as the file owner and re-run the command. 10646, 0, "Failed to create secbackup.xml file on mount point '%s'." //* Cause: Internal error. //* Action: Contact Oracle Support Services. 10647, 0, "Current user does not have system administrative privileges to initialize ACFS encryption." // *Cause: The user was not part of system administrators group. // *Action: Run 'acfsutil encr init' with administrative privileges. 10648, 0, "ACFS security already initialized, recovery failed." // *Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil sec init'. // *Action:Contact Oracle support services. 10649, 0, "ACFS encryption already initialized, recovery failed." // *Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed in the subsequent execution of 'acfsutil encr init'. // *Action:Contact Oracle support services. 10650, 0, "Invalid file name '%s' for ACFS security metadata." // *Cause: The file was invalid for saving or loading ACFS security metadata. // *Action: Specify a valid file. 10651, 0, "Failed to save ACFS security metadata of mount point '%s'." // *Cause: Internal error // *Action: Contact Oracle Support Services. 10652, 0, "Saved ACFS security metadata of mount point '%s'." // *Cause: ACFS security metadata of mount point '%s' was saved. // *Action: None. 10653, 0, "Failed to save ACFS security %s metadata of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10654, 0, "Directory '.Security' does not exist on mount point '%s'." // *Cause: Mount point was not prepared for ACFS security. // *Action: Execute 'acfsutil sec prepare' on the mount point. 10655, 0, "Failed to get hostname." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10656, 0, "Failed to get timestamp." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10657, 0, "Absolute and relative pathnames are not allowed with '-p' option." // *Cause: Filename was provided with absolute or relative path. // *Action: Specify only name of the file with '-p' option and retry. 10658, 0, "ACFS Security has been initialized on the cluster with user '%s' as the initial Security Administrator and '%s' as the Security Administrator group." // *Cause: An administrator initialized ACFS Security on the cluster. // *Action: None. 10659, 0, "Cannot destroy realm '%s' because it is a system-created realm." // *Cause: A request to destroy a system-created realm was denied because that operation is not allowed. // *Action: None. 10660, 0, "Current user does not have required OS privileges to set ACFS encryption parameters." // *Cause: Current user does not have root or administrator privileges to run 'acfsutil encr set'. // *Action: Run 'acfsutil encr set' as a user who has root or administrator privileges. 10661, 0, "Current user does not have required OS privileges to rekey the ACFS encryption parameters." // *Cause: Current user does not have root or administrator privileges to run 'acfsutil encr rekey'. // *Action: Run 'acfsutil encr rekey' as a user who has root or administrator privileges. 10662, 0, "Current user '%s' does not have security administrator privileges." // *Cause: A command requiring Security Administrator privileges was issued but the user is not in the Security Administrators group. // *Action: Add current user to the Security Administrators group or log on as a user who has the required privileges, then retry the command. 10663, 0, "User name '%s' is not a fully qualified name." // *Cause: Fully qualified name was not specified. The supplied user name was not prefixed with a Windows Server Domain name. // *Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name. 10664, 0, "Group name '%s' is not a fully qualified name." // *Cause: Fully qualified name was not specified.The supplied group name was not prefixed with a Windows Server Domain name. // *Action: Specify domain group name prefixed with Windows Server Domain name. For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name. 10665, 0,"Group '%s' is a local group and not a Windows Server Domain group." // *Cause: Specified group was not a Windows Server Domain group. // *Action: Specify a domain group name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a Windows Server Domain name and Doctors is the group name. 10666, 0,"User '%s' is a local user and not a Windows Server Domain user." // *Cause: Specified user was not a Windows Server Domain user. // *Action: Specify a domain user name prefixed with Windows Server Domain name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows Server Domain name and Alice is the user name. 10667, 0,"Windows Server Domain '%s' does not exist." // *Cause: Failed to get Windows Server Domain controller for the domain either because of not access to domain or domain does not exist. // *Action: Specify the name of an existing Windows Server Domain. 10675, 0, "Failed to load ACFS security metadata on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10676, 0, "Loaded ACFS security metadata on mount point '%s'." //* Cause: ACFS security metadata was loaded on mount point. //* Action: None. 10677, 0, "Failed to load %s on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10679, 0, "Unable to resolve the user id '%s'." // *Cause: The user was not found on the system. // *Action: None. 10680, 0, "XDK version not compatible." // *Cause: Oracle XDK version was incompatible. // *Action: Install the correct Oracle XDK version and retry. 10681, 0, "ACFS kernel version is not compatible. The kernel version on the system is '%s' while the expected kernel version is '%s' or above." // *Cause: ACFS kernel version was incompatible. // *Action: Install the correct version and retry. 10682, 0, "Kernel major version is not compatible." // *Cause: Kernel major version was incompatible. // *Action: Install the correct version and retry. 10683, 0, "Kernel release version is not compatible." // *Cause: Kernel release version was incompatible. // *Action: Install the correct version and retry. 10684, 0, "Kernel update version is not compatible." // *Cause: Kernel update version was incompatible. // *Action: Install the correct version and retry. 10685, 0, "Kernel port update version is not compatible." // *Cause: Kernel port version was incompatible. // *Action: Install the correct version and retry. 10686, 0, "Kernel patch version is not compatible." // *Cause: Kernel patch version was incompatible. // *Action: Install the correct version and retry. 10687, 0, "Kernel one off version is not compatible." // *Cause: Kernel one off version was incompatible. // *Action: Install the correct version and retry. 10688, 0, "Unable to resolve the group id '%s'." // *Cause: The OS group ID could not be resolved to a name. Usually this // occurs because the OS group has been removed. // *Action: None. 10689, 0, "Failed to update security administrators information in the driver, some of the subsequent commands may fail." // *Cause: Updating driver security administrator data failed during mount. The mount completes, but subsequent security commands may be affected. This is an internal error. // *Action: Contact Oracle Support Services. 10690, 0, "Cannot edit groups in realm '%s'." // *Cause: No changes were made to the groups in the realm as the operation is not allowed. // *Action: None. 10700, 0, "Failed to store volume encryption key." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10701, 0, "Failed to get volume encryption key." // *Cause: Internal error. // *Action: Refer to encryption log in '/.Security/encryption/logs/encr-.log'. 10702, 0, "Snapshots exist for the file system mounted on '%s'. New encryption parameters will not apply to files in these snapshots." // *Cause: One or more snapshots existed for the file system when this encryption operation was done. The new encryption // parameters set by this command will apply only to new files created in the file system and not to existing // files in any snapshots. Note that none of the encryption commands affect files in any snapshots. Any snapshots // created after the command was run will use the new encryption parameters. // *Action: None. 10703, 0, "Snapshots exist for the file system mounted on '%s'. Encryption status of files in these snapshots will not change." // *Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did // not modify file data in any snapshots on the file system, so this data may still be available on disk // unencrypted. Note that none of the encryption commands affect files in any snapshots. // *Action: If you plan to use snapshots and encryption together, it is recommended that any snapshots be created after // encrypting data on the file system. If the data on the file system was encrypted when some snapshots already // existed, you may delete existing snapshots to ensure that data is not available in unencrypted form via any // files in these snapshots. 10704, 0, "Snapshots exist for the file system mounted on '%s'. Encryption keys of files in these snapshots will not be rekeyed." // *Cause: One or more snapshots existed for the file system when this encryption operation was done. The operation did // not rekey FEKs of files in any snapshots of the file system, so the FEKs of these files will continue to // remain encrypted with the old parameters. Note that none of the encryption commands affect files in any // snapshots. // *Action: To ensure that all FEKs, including those of files in any snapshots, are encrypted with the new encryption // parameters, this command should be run when the file system has no snapshots. If the command was run when // some snapshots existed you may delete these snapshots. Any snapshots created after the command was run will // use the new encryption parameters. 10705, 0, "Cannot perform encryption operation because volume encryption keys for the file system mounted at '%s' are not available." // *Cause: The encryption operation failed because the required volume encryption keys for the file system were not available to the ACFS file system driver. This could happen because an incorrect key store password was supplied during mount or because of some other error during mount. // *Action: Remount the file system, providing the correct password during the mount operation if required. Address any other errors reported during mount. If the issue persists, contact Oracle Support Services. 10706, 0, "Cannot perform encryption operation because an encryption undo operation is in progress." // *Cause: The encryption operation failed because the system administrator was running encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a previous encryption undo operation had not completed cleanly. // *Action: There is no action to be taken by users who are not system administrators. If this message is seen by a system administrator and an encryption undo operation is not in progress, then a previous encryption operation did not complete properly. Run the 'acfsutil encr set -u' command again to complete the operation. 10707, 0, "Cannot perform encryption undo operation because file system level encryption is on." // *Cause: The encryption undo operation failed because file system level encryption was on. // *Action: Turn file system level encryption off and retry the operation. 10725, 0, "Failed to start encryption logging on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10726, 0, "Failed to start security logging on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10727, 0, "Failed to start global security and encryption logging." // *Cause: Global security and encryption logging services could not be started. The log file for this node will not be updated. // *Action: 10728, 0, "ACFS encryption logging directory not found on mount point '%s'." // *Cause: The ACFS encryption logging directory '/.Security/encryption/logs/' could not be opened. // *Action: Ensure the logging directory exists and the system administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality. 10729, 0, "ACFS security logging directory not found on mount point '%s'." // *Cause: The ACFS security logging directory '/.Security/realm/logs/' could not be opened. // *Action: Ensure the logging directory exists and the security administrator can open and create files in this directory, then unmount the file system and remount it manually to restore logging functionality. 10730, 0, "ACFS security and encryption logging directory not found in CRS_HOME." // *Cause: The ACFS security and encryption logging directory '/log//acfssec' could not be opened. // *Action: Ensure the logging directory exists and the system administrator can open and create files in this directory. 10731, 0, "Could not get local host name, ACFS encryption logging will not be available on mount point '%s'." // *Cause: The local host name could not be determined, ACFS encryption logs for this host in '/.Security/encryption/logs/' will not be written. // *Action: Ensure the operating system host name is set correctly and the system administrator can read this value, then unmount the file system and remount it manually to restore logging functionality. 10732, 0, "Could not get local host name, ACFS security logging will not be available on mount point '%s'." // *Cause: The local host name could not be determined, ACFS security logs for this host in '/.Security/realm/logs/' will not be written. // *Action: Ensure the operating system host name is set correctly and the security administrator can read this value, then unmount the file system and remount it manually to restore logging functionality. 10733, 0, "Could not get local host name, ACFS security and encryption logging will not be available for this host" // *Cause: The local host name could not be determined, ACFS security and encryption logs for this host in '/log//acfssec' will not be written. // *Action: Ensure the operating system host name is set correctly and the system administrator can read this value. 10750, 0, "Realm '%s' destroy in progress." 10751, 0, "Realm_Metadata file has invalid realm record\nfor file:\n%(1)s" // *Cause: A realm record of the indicated // Realm_Metadata file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10752, 0, "number of Realm_Metadata file records: %(1)u" 10753, 0, "Realm_Metadata file has no valid realm records\nfor file:\n%(1)s" // *Cause: The indicated Realm_Metadata file did not contain any valid // valid realm records. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10754, 0, "Message removed - do not reuse message number" 10755, 0, "Realm_Metadata file contains invalid realm record data\nfor file:\n%(1)s" // *Cause: The indicated Realm_Metadata file contained at least one invalid // realm record. Refer to the accompanying message(s) for // more information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10756, 0, "Realm_Metadata file _Private structure is invalid for:\nfor file:\n%(1)s" // *Cause: The _Private structure of the indicated Realm_Metadata file // was invalid. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10757, 0, "Realm_Metadata file has invalid Hash_Table data\nfor file:\n%(1)s" // *Cause: The Hash_Table of the indicated Realm_Metadata file contained // inconsistent data. Refer to the accompanying message(s) for more // information on the problem. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10758, 0, "validation complete for Realm_Metadata file Hash_Table\nfor file:\n%(1)s" 10759, 0, "validation complete for Realm_Metadata file\nfor file:\n%(1)s" 10760, 0, "Realm_Metadata file _Private structure has invalid _maxFree value\n found: %(1)u minimum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _maxFree property of the indicated _Private metadata structure // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10761, 0, "Realm_Metadata file _Private structure has invalid _freeDataListTail value\n found: %(1)u minimum: %(2)u\nfor structure:\n%(3)s" // *Cause: The _freeDataListTail property of the indicated _Private metadata // structure was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10762, 0, "Realm_Metadata file node not on _freeDataList\nfor file:\n%(1)s" // *Cause: One or more of the _security_data nodes of the indicated // Realm_Metadata file was not found on the free data node list. // The _next property for one or more of the _security_data nodes // was incorrect. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10763, 0, "Message removed - do not reuse message number" 10764, 0, "Realm_Metadata file has invalid _security_record for _Administrator default\nfor file:\n%(1)s" // *Cause: The default _Administrator _security_record of the indicated // Security_Metadata file was invalid. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10765, 0, "validation complete for Realm_Metadata file _Private structure and _Administrator record\nfor file:\n%(1)s" // *Document: NO 10766, 0, "Realm_Metadata file has no valid realm data records\nfor file:\n%(1)s" // *Cause: The indicated Realm_Metadata file did not contain any valid // valid realm data records. // *Action: If the ACFS Fixer is currently running, then no further action is // needed. The ACFS Fixer will resolve the problem. If the ACFS // Checker is running, then run the ACFS Fixer to resolve the problem. 10768, 0, "Number of realms created on mount point '%s' has reached the limit %d." //* Cause: A request to create a realm was denied because the number of realms created on the mount point has reached the limit. //* Action: Destroy any of the unused realms and retry the command. 10769, 0, "Number of rulesets created on mount point '%s' has reached the limit %d." //* Cause: A request to create a ruleset was denied because the number of rulesets created on the mount point has reached the limit. //* Action: Destroy any of the unused rulesets and retry the command. 10770, 0, "Number of rules created on mount point '%s' has reached the limit %d." //* Cause: A request to create a rule was denied because the number of rules created on the mount point has reached the limit. //* Action: Destroy any of the unused rules and retry the command. 10771, 0, "Number of realms that file '%s' is part of has reached the limit %d." //* Cause: A request to add the file to a realm was denied because the number of realms that the file is part of has reached the limit. //* Action: Remove the file from one or more realms and retry the command. 10772, 0, "Security at the realm level will not be in effect until file system-level security is enabled." //* Cause: Security is disabled at the file system level. When file system-level security is disabled, enabling realm-level security does not enable the authorization checks provided by the realm. //* Action: Enable Security at file system level. 10773, 0, "Unable to lock ACFS Security wallet." // *Cause: The ACFS Security wallet lock was not acquired. // *Action: Verify that Cluster Ready Services(CRS) stack is up by executing // 'crsctl check crs' and Cluster Synchronization Services(CSS) is // running by executing 'crsctl check css'. If the CRS stack is not up, // check with the CRS administrator to bring it up. If it does not // resolve the problem contact Oracle Support Services. 10774, 0, "Unable to unlock ACFS Security wallet." // *Cause: The ACFS Security wallet lock was not released. // *Action: Verify that Cluster Ready Services(CRS) stack is up by executing // 'crsctl check crs' and Cluster Synchronization Services(CSS) is // running by executing 'crsctl check css'. If the CRS stack is not up, // check with the CRS administrator to bring it up. If it does not // resolve the problem contact Oracle Support Services. 10775, 0, "Cannot proceed as another instance of 'acfsutil' command is updating the security administrator information." // *Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command. // *Action: Retry the command after some time. 10776, 0, "Invalid 'acfsutil' version '%s'" // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10777, 0, "Unable to lock ACFS encryption key store." // *Cause: The ACFS encryption key store lock could not be acquired. // *Action: Verify that Cluster Ready Services(CRS) stack is up by executing // 'crsctl check crs' and Cluster Synchronization Services(CSS) is // running by executing 'crsctl check css'. If the CRS stack is not up, // check with the CRS administrator to bring it up. If it does not // resolve the problem contact Oracle Support Services. 10778, 0, "Unable to unlock ACFS encryption key store." // *Cause: The ACFS encryption key store lock was not released. // *Action: Verify that Cluster Ready Services(CRS) stack is up by executing // 'crsctl check crs' and Cluster Synchronization Services(CSS) is // running by executing 'crsctl check css'. If the CRS stack is not up, // check with the CRS administrator to bring it up. If it does not // resolve the problem contact Oracle Support Services. 10779, 0, "Cannot proceed as another instance of 'acfsutil' command is updating the encryption key store." // *Cause: An acfsutil encryption request found the ACFS encryption key store locked by another instance of the acfsutil command. // *Action: Retry the command after some time. 10780, 0, "The file system mounted on '%s' has been prepared for ACFS Security, undo ACFS Security first." // *Cause: ACFS Encryption cannot be undone when the file system has been // prepared for ACFS Security. // *Action: Undo ACFS Security prepare on the mount point by executing // 'acfsutil sec prepare -m -u' as security // administrator and retry. 10781, 0, "One or more Snapshots exists for the file system mounted on '%s', remove all the snapshots before undoing ACFS Security or Encryption." // *Cause: ACFS Security or Encryption cannot be undone for a file system // with snapshots. // *Action: Remove all snapshots by executing 'acfsutil snap delete' and retry. 10782, 0, "The file system mounted on '%s' has not been prepared for ACFS Security, nothing to be undone." // *Cause: The file system was not prepared for ACFS Security. // *Action: None. 10783, 0, "ACFS Encryption is not set on the file system mounted on '%s', nothing to be undone." // *Cause: ACFS Encryption was not set on the file system. // *Action: None. 10784, 0, "Could not destroy all realms, unable to undo ACFS Security." // *Cause: All realms were not destroyed. // *Action: Re-execute the command. 10785, 0, "Could not destroy all rules, unable to undo ACFS Security." // *Cause: All rules were not destroyed. // *Action: Re-execute the command. 10786, 0, "Could not destroy all rulesets, unable to undo ACFS Security." // *Cause: All rulesets were not destroyed // *Action: Re-execute the command. 10787, 0, "Failed to prepare ACFS Security on mount point '%s' as replication is active on this mount point." // *Cause: Replication was active on the mount point. ACFS Replication and // ACFS Security cannot co-exist on the same mount point. // *Action: Terminate replication by using command 'acfsutil repl term' and // then retry. 10788, 0, "ACFS Security undo operation on mount point '%s' completed." // *Cause: ACFS Security undo operation on the mount point was completed. // *Action: None. 10789, 0, "Failed to undo ACFS Security on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10790, 0, "Failed to set ACFS Encryption on mount point '%s' as replication is active on this mount point." // *Cause: Replication was active on the mount point. ACFS Replication and // ACFS Encryption cannot co-exist on the same mount point. // *Action: Terminate replication by using command 'acfsutil repl term' and // then retry. 10791, 0, "Failed to undo ACFS encryption on mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10792, 0, "Cannot add filter '%s:%s' to the cloned realm as the rule set '%s' does not exist on the mount point '%s'." //* Cause: Filters could not be added to cloned realm because rule sets were not present on mount point. //* Action: Clone rules and rule sets first and then add command rules to the cloned realm using 'sec realm add' command. 10793, 0, "File objects cannot be added to cloned realm as file objects do not exist on destination mount point." //* Cause: File objects could not be added to cloned realm because file objects were not present on destination mount point. //* Action: Copy File objects to destination mount point and then add file objects to the cloned realm using 'sec realm add' command. 10794, 0, "File '%s' does not exist on mount point '%s'." //*Cause: Information of file could not be obtained, because either file name specified is not correct or file does not exist on given mount point. //*Action: Specify the correct file name or specify the mount point where the file exists. 10795, 0, "Cannot load ACFS security meta data because the destination mount point '%s' already has some user-created rules, rule sets or realms." //*Cause: ACFS security load was not done as the destination mount point had some user created rules, rule sets or realms. //*Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the destination mount point and then retry the command, or use a file system with no security objects (like realms, rules and rule sets) except system realms. 10796, 0, "A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a password-protected key store." // *Cause: A prior failed encryption initialization was not recovered for // this request because the prior initialization specified a // password-protected key store. // *Action: Execute the command 'acfsutil encr init' with option 'p'. 10797, 0, "A prior failed encryption initialization cannot be recovered for this request because the prior initialization specified a non-password-protected key store." // *Cause: A prior failed encryption initialization was not recovered for // this request because the prior initialization specified a // non-password-protected key store. //* Action: Execute the command "acfsutil encr init' without option 'p'. 10798, 0, "ACFS Encryption undo operation on mount point '%s' completed." // *Cause: ACFS Encryption undo operation on the mount point was completed. // *Action: None. 10799, 0, "For cloning realms with '%s' option, destination mount point must be different from source mount point." //*Cause: Cloning of file system objects is not supported if destination mount point is different from source mount point. //*Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the destination mount point, and then add files using 'acfsutil sec realm add' command. 10850, 0, "Password must have at least %d characters." //* Cause: The password was not long enough. //* Action: Provide the password with number of characters greater than // minimum required length. 10851, 0, "Password must have at least one digit and letter in it." //* Cause: The password did not have either a digit or a letter // in it. //* Action: Provide a password containing at least one digit and letter. 10901, 0, "Failed to add the read-only snapshot file '%s' to realm '%s'." // *Cause: A file specified for addition to a security realm was a read-only snapshot file. // *Action: None. 10902, 0, "Failed to add the read-write snapshot file '%s' to realm '%s'." // *Cause: A file specified for addition to a security realm was a read-write snapshot file. // *Action: None. 10903, 0, "Snapshot '%s' of mount point '%s' is not prepared for ACFS Security." // *Cause: Snapshot was not prepared for security operations on mount point. // *Action: None. 10904, 0, "Security status of snapshot '%s' of mount point '%s': '%s' " //* Document: NO 10905, 0, "\nRealms present in snapshot '%s' of mount point '%s' are as follows: " //* Document: NO 10906, 0, "\nRules present in snapshot '%s' of mount point '%s' are as follows: " //* Document: NO 10907, 0, "\nRule sets present in snapshot '%s' of mount point '%s' are as follows: " //* Document: NO 10908, 0, "\nUsers present in realm '%s' of snapshot '%s' are as follows: " //* Document: NO 10909, 0, "\nGroups present in realm '%s' of snapshot '%s' are as follows: " //* Document: NO 10910, 0, "\nFilters present in realm '%s' of snapshot '%s' are as follows: " //* Document: NO 10911, 0, "\nEncryption status of snapshot '%s': %s " //* Document: NO 10912, 0, "\nInformation of rule '%s' in snapshot '%s' is as follows:" //* Document: NO 10913, 0, "\nRules present in rule set '%s' in snapshot '%s' are as follows:" //* Document: NO 10914, 0, "Security is already enabled in snapshot '%s' of mount point '%s'." // *Cause: Security was already enabled in snasphot of mount point. // *Action: None. 10915, 0, "Security is already enabled on realm '%s' in snapshot '%s' of mount point '%s'" //* Cause: Security was already enabled on realm in snapshot. //* Action: None. 10916, 0, "Security is now enabled in snapshot '%s' of mount point '%s'." // *Cause: Security was enabled in snapshot of mount point. // *Action: None. 10917, 0, "Failed to enable security in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10918, 0, "Security is already disabled in snapshot '%s' of mount point '%s'." // *Cause: Security was already disabled in snapshot of mount point. // *Action: None. 10919, 0, "Security is already disabled on realm '%s' in snapshot '%s' of mount point '%s'." //* Cause: Security was already disabled on realm in snapshot. //* Action: None. 10920, 0, "Failed to disable security in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10921, 0, "Realm '%s' not found in snapshot '%s' of mount point '%s'." // *Cause: Realm was not found in snapshot of mount point. // *Action: Ensure that the realm exists using the command 'acfsutil sec info -m -S -n'. 10922, 0, "Failed to get security related information of snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10923, 0, "Failed to get users for realm '%s' in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10924, 0, "Failed to get groups for realm '%s' in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10925, 0, "Failed to get realm encryption attributes of realm '%s' in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10926, 0, "Attributes of realm '%s' in snapshot '%s' of mount point '%s' retrieved." //* Cause: Attributes of realm in snapshot were retrieved. //* Action: None. 10927, 0, "Failed to get all rules in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Refer to security log in '/.Security/realm/logs/sec-.log'. 10928, 0, "Failed to get information of rule '%s' in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10929, 0, "Rule '%s' not found in snapshot '%s' of mount point '%s'." // *Cause: Rule was not found in the snapshot. // *Action: Ensure that the rule exists by executing 'acfsutil sec info -m -S -l'. 10930, 0, "Failed to get all rule sets in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10931, 0, "Failed to get rules for rule set '%s' in snapshot '%s' of mount point '%s'." // *Cause: Internal error. // *Action: Contact Oracle Support Services. 10932, 0, "Rule set '%s' not found in snapshot '%s' of mount point '%s'." // *Cause: Rule set was not found in snapshot of mount point. // *Action: Ensure that the rule set exists by executing 'acfsutil sec info -m -S -s'. 10933, 0, "Failed to delete the read-only snapshot file '%s' from realm '%s'." // *Cause: Security operations cannot be performed on a read-only snapshot file. // *Action: None. 10934, 0, "Failed to delete the read-write snapshot file '%s' from realm '%s'." // *Cause: Security operations cannot be performed on a read-write snapshot file. // *Action: None. 10935, 0, "ACFS Security cannot be enabled or disabled because '%s' is a read-only snapshot" // *Cause: A request to enable or disable ACFS Security specified a read-only snapshot. // *Action: None. / / Device configuration tools messages / 11001, 0, "Error in parsing command line arguments." // *Cause: There was a syntax error is the command line arguments. // *Action: Check the command line syntax and re-run the command again. 11002, 0, "Error: a device name must be supplied with the -l option." // *Cause: Either the -l option was not present in the command line or it had no argument. // *Action: Make sure you run the command with the '-l device-name' option. 11003, 0, "AIX ODM initialization failed, odmerr %d" // *Cause: AIX ODM internal operation error. // *Action: Internal error - contact Oracle Customer Support. 11004, 0, "failed to lock AIX ODM database, odmerr %d" // *Cause: The method could not lock the AIX ODM database. // *Action: Check to see what other method has locked it. 11005, 0, "failed to look up AIX ODM PdDv object class, odmerr %d" // *Cause: The user may lack required permission or the entry may not exist. // *Action: Ensure that the object exists and that the user has the required // permission; otherwise, contact Oracle Customer Support. 11006, 0, "failed to open AIX ODM CuDv object class, odmerr %d" // *Cause: The user may lack required permission or the entry may not exist. // *Action: Ensure that the object exists and that the user has the required // permission; otherwise, contact Oracle Customer Support. 11007, 0, "failed to add to AIX ODM CuDv object class, odmerr %d" // *Cause: An attempt to add the device's entry to the ODM CuDv object class // failed. // *Action: Ensure the user has the required permission. 11008, 0, "failed to close the AIX ODM CuDv object class, odmerr %d" // *Cause: AIX ODM internal operation error. // *Action: Contact Oracle Customer Support. 11009, 0, "searching for %s in CuDv object class" // *Document: NO 11010, 0, "failed to look up AIX ODM CuDv object class, odmerr %d" // *Cause: The user may lack required permission or the entry may not exist. // *Action: Ensure that the object exists and that the user has the required // permission; otherwise, contact Oracle Customer Support. 11011, 0, "searching for %s in PdDv object class" // *Document: NO 11012, 0, "warning: driver %s is already loaded" // *Document: NO 11013, 0, "error: driver %s is already loaded" // *Document: NO 11014, 0, "loading kernel extension %s" // *Document: NO 11015, 0, "failed to load kernel extension %s, errno %d (%s)" // *Cause: Loading the kernel extension into the kernel failed. // *Action: Check the error message and resolve the error. 11016, 0, "configuring kernel extension %s, kmid 0x%x" // *Document: NO 11017, 0, "failed to configure kernel extension %s, errno %d (%s)" // *Cause: Could not configure the device's driver in the kernel. // *Action: Internal error - contact Oracle Customer Support. 11018, 0, "failed to get a major number for device %s" // *Cause: The method could not get a major number for the device. // *Action: Internal error - contact Oracle Customer Support. 11019, 0, "failed to get a minor number for device %s" // *Cause: The method could not get a minor number for the device. // *Action: Internal error - contact Oracle Customer Support. 11020, 0, "device major number is %d and minor number is %d" // *Document: NO 11021, 0, "configuring device %s with major number %d and minor number %d" // *Document: NO 11022, 0, "failed to configure device %s, errno %d (%s)" // *Cause: Attempt to configure the device's driver in the kernel got an error. // *Action: Internal error - contact Oracle Customer Support. 11023, 0, "removing the old device file %s" // *Document: NO 11024, 0, "failed to remove the old device file %s, errno %d (%s)" // *Cause: The method failed to remove the device file. // *Action: Ensure that the user has permission and no other application // is still using the device. 11025, 0, "creating new device file %s" // *Document: NO 11026, 0, "failed to create new device file %s, errno %d (%s)" // *Cause: The user may not have permission or a file with the same // name already exists. // *Action: Ensure that the file does not already exist and that the // user has the required permission to create it. 11027, 0, "setting permission of the new device file %s" // *Document: NO 11028, 0, "failed to set permission of the new device file %s, errno %d (%s)" // *Cause: The method failed to set permission of the device special file. // *Action: Ensure the user has the required privilege. 11029, 0, "getting group of the new device file %s" // *Document: NO 11030, 0, "failed to set group of the new device file %s, errno %d (%s)" // *Cause: The method failed to set the owning group of the device special file. // *Action: Ensure the user has the required privilege. 11031, 0, "failed to open the ASMADMIN group file, errno %d (%s)" // *Cause: The method could not open the file containing the group to own the device. // *Action: Ensure the installation completed successfully. 11032, 0, "failed to read from the ASMADMIN group file, errno %d (%s)" // *Cause: The method could not read the file containing the group to own the device. // *Action: Ensure the installation completed successfully. 11033, 0, "setting device state to AVAILABLE" // *Document: NO 11034, 0, "failed to set device state to AVAILABLE, odmerr %d" // *Cause: The method could not change the device's state. // *Action: AIX ODM internal error - contact Oracle Customer Support. 11035, 0, "Device state is already AVAILABLE. No operation was performed." // *Document: NO 11036, 0, "Device state is not DEFINED. No operation was performed." // *Document: NO 11037, 0, "unconfiguring kernel extension %s, kmid 0x%x" // *Document: NO 11038, 0, "failed to unconfigure kernel extension %s, errno %d (%s)" // *Cause: The method could not unconfigure the kernel extension. // *Action: Internal error - contact Oracle Customer Support. 11039, 0, "unloading kernel extension %s, kmid 0x%x" // *Document: NO 11040, 0, "failed to unload kernel extension %s, errno %d (%s)" // *Cause: The method could not unload the extension from kernel. // *Action: Internal error - contact Oracle Customer Support. 11041, 0, "trying to clean up after encountering an error" // *Document: NO 11042, 0, "Device %s is already unconfigured. No operation was performed." // *Document: NO 11043, 0, "Device %s is not in AVAILABLE state. No operation was performed." // *Document: NO 11044, 0, "no minor number was returned for device %s" // *Cause: The operating system did not return a device minor number as requested. // *Action: Internal error - contact Oracle Customer Support. 11045, 0, "unconfiguring device %s with major number %d and minor number %d" // *Document: NO 11046, 0, "failed to set device state to DEFINED, odmerr %d" // *Cause: The method failed to change the device's state. // *Action: Contact Oracle Customer Support. 11047, 0, "successfully set device state to DEFINED" // *Document: NO 11048, 0, "successfully set device state to AVAILABLE" // *Document: NO 11049, 0, "deleting all attributes of device %s" // *Document: NO 11050, 0, "failed to delete attributes of device %s, odmerr %d" // *Cause: The method failed to remove the device's attributes from // the AIX ODM CuAt object class. // *Action: Internal AIX ODM error - contact Oracle Customer Support. 11051, 0, "deleting customized device object of device %s" // *Document: NO 11052, 0, "failed to delete customized object of device %s, odmerr %d" // *Cause: The method failed to remove the device's entry from // the AIX ODM CuDv object class. // *Action: Internal AIX ODM error - contact Oracle Customer Support. 11053, 0, "failed to release major number for device %s" // *Cause: The method failed to release the device's major number. // *Action: Internal error - contact Oracle Customer Support. 11054, 0, "removing device special file %s" // *Document: NO 11055, 0, "failed to remove device special file %s, errno %d (%s)" // *Cause: The method failed to remove the device special file. // *Action: Check the error message and resolve it. 11056, 0, "successfully loaded kernel extension %s, kmid 0x%x" // *Document: NO 11057, 0, "successfully configured kernel extension %s" // *Document: NO 11058, 0, "successfully unconfigured kernel extension %s" // *Document: NO 11059, 0, "successfully unloaded kernel extension %s" // *Document: NO 11060, 0, "failed to unload kernel extension %s" // *Cause: Could not unload the extension from kernel. // *Action: Internal error - contact Oracle Customer Support. 11061, 0, "failed to look up the group id for group %s" // *Cause: The named group probably does not exist. // *Action: Make sure the group exists in the /etc/group file. 11062, 0, "failed to create directory %s, errno %d (%s)" // *Cause: The directory could not be created. // *Action: Check the permission of the base directory to make sure it is writeable. 11063, 0, "failed to set permission on directory %s, errno %d (%s)" // *Cause: The permission of the directory could not be changed. // *Action: Make sure the user has permission to do so. 11064, 0, "failed to set group on directory %s, errno %d (%s)" // *Cause: The group of the directory could not be changed. // *Action: Make sure the user has permission to do so. 11065, 0, "invalid device minor number %d" // *Cause: The device minor number being used is out of range. // *Action: Contact Oracle Customer Support. 11066, 0, "the ADVM driver is not loaded" // *Cause: The ADVM driver is expected to exist in the kernel but it does not. // *Action: Load the ADVM driver and then try it again. 11067, 0, "directory /dev/asm does not exist or is not accessible, errno %d (%s)" // *Cause: The ADVM driver probably has not been successfully loaded. // *Action: Load the ADVM driver and then try it again. 11068, 0, "The state of device %s is unknown. No operation was performed." // *Cause: Unknown. // *Action: Contact Oracle Customer Support. 11069, 0, "Error: device name is too long, exceeding 255 characters." // *Cause: The chosen device name exceeds the limit of 255 characters. // *Action: Use a device name that is shorter than the limit. / / / / ACFS catch-all message 11111, 0, "%s" // *Cause: None // *Action: None / / vim: ts=4 expandtab textwidth=0 wrapmargin=0