MINI MINI MANI MO

Path : /opt/oracle/product/18c/dbhomeXE/usm/mesg/

Current File : //opt/oracle/product/18c/dbhomeXE/usm/mesg/acfsus.msg

/* Copyright (c) 2009, 2018, 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
/ apfwkr 04/05/18 - Backport vyerrams_bug-27341181 from main
/ Due to BLR restrictions, existing messages
/ cannot be updated, so only add the new messages
/ apfwkr 04/05/18 - Backport mbahlke_fsckprekilorbm from main
/ vyerrams 02/01/18 - Bug 27341181: Update 3806.
/ Make 3808 generic.
/ Add 3809 - 3811
/ averhuls 02/22/18 - Backport averhuls_bug-27243810 from main
/ mbahlke 03/05/18 - Bug 27281934: Validate remap bitmap bits when
/ remapping internal GBM bits
/ mbahlke 03/05/18 - Bug 27525531: Add remapped offset to messages
/ displaying only the disk offset
/ averhuls 02/23/18 - Add missing single quote to 13315.
/ averhuls 10/26/17 - Add 13377.
/ crusman 10/22/17 - Bug 27006014: add 3534
/ raharris 10/17/17 - Bug 26987703
/ - Fix 7989, 8015, 8016, 8017, 8018 to use %d
/ instead of %s
/ vyerrams 10/16/17 - Bug 26977488: Add 3808
/ averhuls 10/09/17 - 'advmutil transport create': we no longer use
/ XML files so all of those related messages are
/ removed. Since the product has not shipped,
/ re-used some of the obsolete numbers for the
/ new command style.
/ mcarrell 10/04/17 - Change message 5085.
/ ethibaul 10/04/17 - 12.2.0.2->18.0.0.0.0
/ vyerrams 10/02/17 - Bug 26884482: Relocate 13319-13341 to 3785-3807
/ averhuls 10/02/17 - Minor change to unshipped 13308.
/ mbahlke 09/26/17 - Bug 26844019: add oversubscription and 7448
/ count handling and messages to fsck
/ vyerrams 09/22/17 - Bug 25897626: Add 03737, and 13319-13341
/ tmark 09/18/17 - Add 3356.
/ ethibaul 09/18/17 - Add 3017
/ dbolinge 09/11/17 - Bug 26614844: Add message 5524.
/ sverhuls 09/07/17 - Solaris accelerator under DNS only (26713545).
/ averhuls 08/24/17 - Add 9897, 13318, 13375, 13376. Fix 13316.
/ sverhuls 08/07/17 - Messages for meta collector (26453340).
/ hmishra 08/04/17 - Add message 5236-5243
/ tmark 08/04/17 - Bug 26407545: Add message 12270.
/ tmark 08/04/17 - Bug 26407545: Add message 12270.
/ averhuls 08/03/17 - 13045/6: add a space between 'cluster' and the
/ value.
/ rbreau 07/25/17 - Bug RTI 20469686
/ Remove parameter from message # 8008
/ averhuls 07/24/17 - Add 13265.
/ averhuls 07/14/17 - Add 13304. Minor change to (not shipped) 13254
/ ssprasad 07/11/17 - Update 9545/9552 messages
/ averhuls 07/10/17 - Restore 13308 that was removed in error.
/ Mark 13304 unused and available.
/ rbreau 06/29/17 - Bug 26423911
/ Add messages 08002 thru 8013
/ Modified message 7468
/ averhuls 07/05/17 - Minor change to (not shipped) 13025. Add 13032,
/ 13033.
/ Mark UNUSED not shipped 13065, 13175, 13308.
/ hmishra 06/21/17 - Bug 25750751: Added cause and action for old
/ security and encryption messages
/ jochoa 06/19/21 - Bug 26198673: Replace some references to 'OKS'
/ with approved wording.
/ gsanders 06/23/17 - Add 05952
/ certan 06/15/17 - Add messages for online fsck (3016, 7970-7998,
/ 8000-8001)
/ mbahlke 06/12/17 - Bug 25966987: Add dump local option to
/ 'acfsutil dumpstate'
/ averhuls 06/09/17 - Add ACFSR CRS messages 13300 -> 13317.
/ 13073 'StorageRepo'->'storageRepo'- bug 26075766
/ tmark 06/02/17 - Bug 26117423: Add message 7968.
/ hmishra 05/30/17 - Bug 26083137: Modified action for message 10958
/ hsinlee 05/25/17 - Bug 25765963 - Add documentation to log and
/ comm messages
/ ethibaul 05/22/17 - Add 03781, 03782, 03783, modify 03773, update
/ 13000 cause and action
/ ethibaul 05/18/17 - Add 03299, 03533
/ jorhuert 05/17/17 - Add scrubber messages to notify of BADFDA7A
/ found.
/ raharris 05/06/17 - Bug 25764672
/ - Remove trailing newline (\n) on messages
/ 03652
/ 03686
/ 03690
/ "acfsutil meta" will deal with the white space
/ formatting internally.
/ - Add acfsutil meta 03779 - "Expand: %(1)s"
/ - Add acfsutil meta 03780 - acfsutil meta -e
/ unknown file format.
/ - 03778 replace "OKS" with "Oracle Kernel
/ Services (OKS)"
/ madoming 05/05/17 - Add messages 9551 - 9562.
/ averhuls 05/05/17 - Add 13262-4. Minor changes to 13091 & 13092.
/ 13250 now unused. None of these msgs shipped.
/ jeabraha 05/03/17 - ACFS remote resize support
// madoming 05/03/17 - Add message 9194.
/ tdziedzi 05/02/17 - Bug 25884724: add fsck message 7583
/ ethibaul 04/24/17 - Update 'acfsutil info storage' summary output
/ crusman 04/19/17 - 25776382: Add missing cause/actions for 3675,
/ 3680,3681
/ himhmed 04/19/17 - Add messages 11100-11106
/ jorhuert 04/18/17 - Update transport_config messages to reflect you
/ need to specify the transport after
/ --refresh|--rescan.
/ averhuls 04/14/17 - Add remove dangling ']' on 13112.
/ tdziedzi 04/11/17 - Bug 8781927: remove unreferenced fsck messages
/ (7269, 7401, 7403, 7705, 7706, 7707)
/ averhuls 04/07/17 - 25750749: add cause/action for advmutil Windows
/ related msgs (9000-9039).
/ mnollen 04/06/17 - Change 9211 and 9326 messages. Added 9547,
/ 9548,9549,9550, for acfsdriverstate version
/ command.
/ ethibaul 04/05/17 - 25750828: Add missing cause/actions for snap
/ averhuls 04/04/17 - Add msg 13054. Minor 'cause/action' changes to
/ ethibaul 04/04/17 - 25750741: Add missing cause/actions for generic
/ 13050 and 13062 - the messages are the same but
/ one is a fatal error, the other informational.
/ ethibaul 03/30/17 - 25750804: Add missing cause/actions for size
/ ethibaul 03/30/17 - 25750745: Add missing cause/actions for mount,
/ acfsmountvol, acfsdismount, and umount
/ loguzman 03/28/17 - Add cause and action for 03111, 03112 and
/ 03132 messages.
/ kcorwin 03/28/17 - Bug 25713840 - Flag 'snap create' blocked by
/ in-progress repl v2 apply
/ sverhuls 03/27/17 - Add accelerator version check msg (24675541).
/ averhuls 03/22/17 - Add msg 13093.
/ ethibaul 03/20/17 - 25750743: Add missing cause/actions for mkfs
/ tmark 03/17/17 - Add more precision in reporting for
/ messages 3727 and 3728 as we support
/ file systems of size less than 1GB.
/ argardu 03/16/17 - Added 09546
/ argardu 03/14/17 - Added 09544 and 09545.
/ averhuls 03/08/17 - Make UNUSED or deprecated messages comments -
/ bug 25689265. Mark (never shipped) 13093 UNUSED.
/ jorhuert 03/08/17 - Update acfsremote usage messages.
/ ethibaul 03/07/17 - Modify action of 03777
/ gsanders 03/07/17 - Add 05949, 05950
/ averhuls 03/01/17 - Add msg 13261.
/ dbolinge 02/14/17 - Add 05523.
/ ethibaul 02/14/17 - Update 'acfsutil info storage' output
/ gsanders 02/08/17 - 23524136 '-' to %s for opt flag for '/'
/ gsanders 02/03/17 - 00184,05851,05852,05853,05854,05855
/ averhuls 02/03/17 - mark (not shipped) 13191 as UNUSED. Change
/ (not shipped) 13180 to mark '-n nodeName' as
/ optional. Minor formating fix to 13166.
/ kcorwin 02/01/17 - Bug 25433267 - 2 primary mounts can replicate
/ to the same standby mount
/ vyerrams 01/24/17 - Bug 25366007: Add 11099 for SIHA mode.
/ jorhuert 01/23/17 - Modify 9821 cause and action - it was not clear
/ that the 'acfsutil cluster credential' MC
/ registration could fail if the passed file did
/ not exist as we need to read it to retrieve
/ ASM-generated data.
/ bonelso 01/19/17 - Add 05947, "Snapshot %s must be writable."
/ qmcintos 01/05/17 - Add freeze and thaw to acfsutil usage 3734,3735
/ raharris 01/03/17 - Add error message if mix of metadata collector
/ files and real devices are opened.
/ tengle 01/18/17 - Bug 25341182 - wrong error message for
/ non-existent snap link. Add messages
/ 3531 and 3532. Update old messages 3051
/ and 3054 to match.
/ averhuls 01/17/17 - Minor changes to not yet shipped 13253, 13255.
/ Add 13260.
/ gsanders 01/15/17 - Add 05946
/ migugonz 01/10/17 - Added 09615 NFS_PATH is not supported.
/ ethibaul 01/05/17 - Add 3752-3773, info storage support
/ tengle 01/03/17 - GBM Lookup Table (GLUT) support
/ averhuls 12/21/16 - Move (unchanged) advmutil transport XML messages
/ 13105-13110 to 13250-13255 because more space
/ was needed. Add new 13256 - 13259.
/ jorhuert 12/19/16 - Add message to indicate the scrubber is running
/ in the background.
/ raharris 11/29/16 - Add some fsck/acfsdbg accelerator messages.
/ loguzman 12/16/16 - Add 3751 - Unable to modify the set of nodes
/ where a file system is running.
/ raharris 11/29/16 - Add some fsck/acfsdbg accelerator messages.
/ qmcintos 12/15/16 - Add 3295-3297, freeze support
/ jorhuert 12/14/16 - Add scrubber error message for offline
/ filesystem
/ sverhuls 12/12/16 - Add acfsutil meta messages (24592546).
/ averhuls 12/05/16 - Minor change to 13100 - 13102 now available
/ (neither have shipped). Add 'advmutil transport
/ create' XML validation messages 13105-13110.
/ madoming 12/02/16 - Add messsage 9214, the message 9837 was updated
/ raharris 11/29/16 - Add some fsck/acfsdbg accelerator messages.
/ jorhuert 11/22/16 - Add 9830 - invalid version format input
/ kcorwin 11/21/16 - bug 23722410 Verify repl id of standby when
/ updating ssh host
/ averhuls 11/15/16 - Minor changes to 13041, 13048
/ which have not yet shipped.
/ dakers 11/07/16 - Added fsck shrink messages
/ mnollen 11/03/16 - Bug-24685780 Add error message for accel
/ replace when user is required to run with
/ resource privileges message 3294
/ jorhuert 10/21/16 - Added acfsremote command usage messages.
/ raharris 09/20/16 - Add 00999 - unexpected assert message, contact
/ Oracle support.
/ Add 07999 - unexpected ACFS Checker/Fixer
/ assert, contact Oracle support.
/ averhuls 10/07/16 - Renumber ACFSR messages as they were allocated
/ in a previously reserved area.
/ mbahlke 09/29/16 - Bug 24349221: Add Snap FETA size to 'acfsutil
/ snap info'
/ averhuls 09/29/16 - ACFSR usage now displays '-' or '/' for switch
/ depending on platform.
/ mbahlke 09/27/16 - Bug 23544229: Add create time message
/ btsao 09/26/16 - Bug 24736947. Add msg 1178.
/ lcarvall 09/23/16 - Fix Bug 23122315 acfsdriverstate -v verbose
/ sverhuls 09/19/16 - Add msgs for Solaris accelerator (24435055).
/ dbolinge 08/24/16 - Bug 24455034: add message 5945.
/ ethibaul 08/23/16 - Bug 23623855: add 3348-3353
/ tengle 08/16/16 - Snapshot link support
/ agraves 08/12/16 - Finalize messages after review comments.
/ agraves 08/10/16 - Adjust messages after review.
/ bonelso 08/03/16 - Update 'repl compare' messages
/ crusman 07/19/16 - Bug 23581923: add messages 9542, 9543
/ averhuls 07/12/16 - Add 'advmutil export' messages.
/ ethibaul 07/08/16 - Bug 23623775: add message 3347
/ dbolinge 06/30/16 - Bug 23529177: add message 5944.
/ vyerrams 06/30/16 - Bug 22933596: Add message 11098
/ tdziedzi 06/29/16 - Fix formatting of 1098, 1099
/ kcorwin 06/16/16 - Bug 21293107: sbrepl: Verify that replication
/ apply user has sysasm privileges.
/ mnollen 06/07/16 - Add messages 3280, 3281 and 3282
/ jorhuert 06/03/16 - Add 9832 - Invalid permission string.
/ loguzman 06/02/16 - Add 627 and 628 messages.
/ dbolinge 05/26/16 - Bug 23144169: add message 5942.
/ rbreau 04/29/16 - Add messages 7577, 7578 and 7579
/ - Resolve performance issue with validating
/ the NextDataExtent chain.
/ - Bug 22878809
/ mcarrell 05/25/16 - Add message 5941.
/ btsao 05/24/16 - Bug 23285635. Add message 1176.
/ kcorwin 05/13/16 - bug 22640890 - sbrepl: sshStrictKey option
/ should be user-visible
/ crusman 05/18/15 - add 9541 (bug 23309009)
/ kcorwin 05/13/16 - bug 21922100: use less confusing usage line for
/ replv2 compression.
/ qmcintos 05/11/16 - Add messages 3280-3285
/ jorhuert 05/09/16 - Remove 9830.
/ jorhuert 05/09/16 - Add 9831 - Transport list message
/ crusman 05/18/15 - add 9541 (bug 23309009)
/ jorhuert 05/06/16 - Remove 9830.
/ raharris 05/04/16 - Bug 22756633
/ - Add additional Snap Remaster error messages to
/ request ACFS Plugins be disabled.
/ - Add Snap Remasger error messages to request
/ enhanced security and encryption be disabled.
/ averhuls 05/03/16 - Add 'advmutil export' messages.
/ mcarrell 04/27/16 - Add messages 5848 and 5940.
/ jbensson 04/26/16 - Add scrubber metadata cache messages.
/ mbahlke 04/22/16 - Bug 23143711: Update 'accel replace' ACFS-03268
/ mnollen 04/22/16 - Bug 22726810: Add acfsutil crs accel replace
/ messages
/ bonelso 04/17/16 - Add 5936, 5937,5938 and 5939
/ mbahlke 04/15/16 - Bug 23018066: Ensure helpful messages for
/ unmountable volumes
/ dbolinge 04/15/16 - Add message 5934
/ lcarvall 04/14/16 - Fix Bug 21764705 mounted acfs to a soft link
/ jorhuert 04/13/16 - Add 11096 - ACFS Remote mode
/ Add 11097 - ASM Storage mode
/ Modify 11079 to 'Oracle Appliance'
/ mbahlke 04/11/16 - Bug 23019335: Add messages for fsck fixing
/ accel sig
/ tengle 04/11/16 - Add message 3731
/ gsanders 03/24/16 - Add 05935
/ qmcintos 04/06/16 - add 3274
/ tengle 04/05/16 - Add message 3730
/ mbahlke 03/28/16 - Bug 22994675: Improve instructions for ACCELOP
/ signature message
/ jbensson 03/28/16 - Add scrubber error messages.
/ mbahlke 03/24/16 - Bug 22993826: Improve instructions for 'accel
/ replace'
/ ethibaul 03/22/16 - Add 3729
/ ethibaul 03/22/16 - 22923640: 3271
/ dbolinge 03/22/16 - Add 5933 for Bug 19637938
/ jbensson 03/21/16 - Update Scrubber CLI.
/ ethibaul 03/18/16 - Add 1175
/ qmcintosh 03/17/16 - Add 3726, 3727 and 3728 for resizing
/ ethibaul 03/16/16 - 22822839, 22602001: acfsutil usage messages
/ mbahlke 03/15/16 - Bug 22689989: Add acfsutil accel replace
/ messages
/ jorhuert 03/07/16 - Add 9830 - unable to retrieve crs resource
/ configuration variables. 22707770.
/ hmishra 03/04/16 - Bug 22297746: Added messages 10359-61
/ mcarrell 03/03/16 - Add message 5932.
/ crusman 02/27/16 - new msgs for fsck + compression + diskusage
/ gsanders 02/24/16 - Added 05931
/ jbensson 02/24/16 - Add scrubber messages.
/ ethibaul 02/19/16 - Add 1174
/ mlmiller 02/18/16 - Add msg 5930 for replv2 ssh key validation
/ jorhuert 02/16/16 - Add 9828 - cluster credential commands may only
/ be run in a DSC
/ bonelso 02/12/16 - Added 05929
/ crusman 02/10/16 - Add 7566,7567,7576 for Bug 22700785
/ tengle 02/03/16 - Range locking fsck support
/ jorhuert 02/02/16 - Add 9827 - acfs credentials not found in CMF.
/ josmith 02/02/16 - Bug 22498619: Add 03130
/ raharris 01/19/16 - Bug 22571665,22510407,22273859
/ Add fsck signal handler error message 7951 to
/ report the actual signal received, instead of
/ allowing the signal handler to just call
/ abort() that will give the fsck wrapper
/ SIGABRT(6) which will hide the real error, such
/ as SIGSEGV(11).
/ jorhuert 01/18/16 - Replace Member Cluster Data File with cluster
/ manifest.
/ stomar 01/07/16 - Bug 21810045: added 10479.
/ mlmiller 01/04/16 - Fix a number of things wrong with error message
/ 5890.
/ jorhuert 12/29/15 - Adding 9809, not sure why it's not there
/ already. Remove 9808, 9811, 9815, 9817.
/ These removed messages are not going to
/ be used for now.
/ qmcintos 12/26/15 - Fix an error in message 3692
/ mlmiller 12/22/15 - Add 5928, advm compatibility message for snap
/ dup cmds
/ mcarrell 12/21/15 - Add messages 5845-5847.
/ bonelso 12/16/15 - Updated 5914
/ gsanders 12/15/15 - Add 07564, 07565
/ mlmiller 12/15/15 - Add 5925 & 5926
/ mcarrell 12/09/15 - Add message 5927.
/ crusman 12/08/15 - Add 9540.
/ ravraran 12/04/15 - Added messages 10465-10478 for encryption
/ qmcintos 12/02/15 - Modify message 3691,92,94 to support ACFS
/ version
/ jbensson 11/30/15 - Add preliminary scrubber messages.
/ jorhuert 11/25/15 - Add acfsutil cluster credentials messages. Who
/ do I pay the $1.95 for the 9800-9999 message
/ range?
/ gsanders 11/25/15 - Bug message 05923, 05924
/ crusman 11/08/15 - Modify message 9521. Bug 22163079.
/ dbolinge 11/05/15 - Bug 21775162: add messages 5921, 5922
/ crusman 10/26/15 - Add message 9539. Bug 22097092.
/ mbahlke 10/19/15 - Bug 21935609 - Add granularity to info file
/ jeabraha 10/12/15 - Add mount msg 2137
/ hmishra 10/12/15 - Modified cause and action for the message 10781
/ jochoa 10/12/15 - Add message 09460.
/ dbolinge 10/09/15 - Bug 21699613: add message 5919
/ gsanders 10/08/15 - Bug message 05920
/ jbensson 09/29/15 - Remove volinfo version printing.
/ dbolinge 09/28/15 - Bug 21864687: add message 05918
/ dbolinge 09/28/15 - Bug 21864687: add message 5918
/ dbolinge 09/25/15 - Bug 21662548: add 5917; update 5913, 5914.
/ crusman 09/24/15 - modify 09536 (part of 21412401)
/ certan 09/22/15 - Add 9537, 9538
/ dbolinge 09/25/14 - Bug 21662548: add 5917; update 5913, 5914.
/ averhuls 09/14/15 - Add acfsutil blog messages.
/ mkeller 09/01/15 - Bug Bug 21475559 - Update 03610 action
/ raharris 08/25/15 - Bug 21495490
/ - Apply fixed based on code review feedback that
/ got deferred.
/ - Remove "status %(n)s" from Snap Remaster error
/ messages.
/ qmcintos 08/24/15 - bug 21669635, change message 3645
/ sverhuls 08/17/15 - Add -x to fsck usage (21480693).
/ btsao 08/13/15 - Bug 21410238. Revise message 1173 cause text.
/ gsanders 08/05/15 - Add message 05916
/ ethibaul 07/28/15 - 21459835: Update 11095 and cause/action
/ statements for snap & repl compat messages
/ qmcintos 07/27/15 - snap quota support
/ dakers 07/21/15 - Added resize accel messages.
/ mbahlke 07/21/15 - Bug 20672029 acfsutil info file usage
/ mbahlke 07/21/15 - Bug 20703290 fix leading %s in info file msgs
/ mcarrell 07/16/15 - Add message 5915.
/ himhmed 07/14/15 - Add 11095
/ sverhuls 07/09/15 - Add messages for meta collector (21330089)
/ jorhuert 07/01/15 - Adding 3243 - Number too large.
/ mcarrell 07/01/15 - Add messages 5913 and 5914.
/ ethibaul 07/01/15 - 21358240: move 3690->3700
/ bonelso 06/23/15 - Syntax change: 'snap clone' -> 'snap duplicate'
/ ssprasad 06/22/15 - Add 9213
/ tmark 06/06/15 - Add message 1172, modeled on message 1156.
/ ethibaul 06/19/15 - Bug 21226066: ACFS compatibility
/ mkeller 06/16/15 - 20746854: Add 3242
/ raharris 06/10/15 - Add Snap Remaster related Usage, information,
/ warning, and error messages (formerly known as
/ Snap Promote).
/ - Reserve the 12000 - 12999 range for Snap
/ Remaster messages.
/ - Update message 07215 to include the OfsRemaster
/ signature.
/ - Add 07947 fsck error about attempting to use a
/ mount point instead of a device or container
/ file.
/ - Add 00609 for generic end-of-file received.
/ mcarrell 06/10/15 - Add message 5153.
/ tmark 06/06/15 - Add message 1172, modeled on message 1156.
/ bonelso 06/23/15 - Syntax change: 'snap clone' -> 'snap duplicate'
/ crusman 06/15/15 - Bug 21235822. Add 3687,3688.
/ bonelso 06/13/15 - Syntax change: 'snap clone' -> 'snap duplicate'
/ mbahlke 06/11/15 - Bug 20949931: change message for info file file
/ allocation/size check
/ mcarrell 06/10/15 - Add message 5153.
/ jochoa 06/10/15 - Bug 20823177: Enhance ACFS-03171 message.
/ tmark 06/06/15 - Add message 1172, modeled on message 1156.
/ mcarrell 06/04/15 - Add message 5912.
/ lcarvall 05/23/15 - Fix Bug 20952520 - ACFS doesn't support LXC env
/ dbolinge 05/21/15 - Bug 20986819: Add 5911 for conflicting change
/ while repl v2 apply in progress; fix 5905.
/ dakers 05/20/15 - Add message 2137
/ crusman 05/20/15 - Fix 7544
/ madoming 05/11/15 - Add messages for acfshanfs command.
/ gsanders 05/08/15 - Add 05844, 0, "ssh command path"
/ btsao 05/05/15 - Add 7568 for MetadataSize field message.
/ tmark 04/09/15 - Add messages for meta I/O stats reporting
/ and ODA presence in acfsutil.
/ gsanders 04/06/15 - Add 05910 snap clone create new/old snapshot
/ dakers 03/23/15 - Port of PT.ODA1 fixes to MAIN
/ bonelso 03/12/15 - Add 05909 - "Snapshot %s must be read only."
/ crusman 02/27/15 - Bug 20601426: compression support
/ Add 3656-3685
/ jeabraha 02/23/15 - Snap async delete project
/ mbahlke 02/23/15 - Add snap rename messages
/ btsao 02/23/15 - Adjust 7563 cause text.
/ ethibaul 02/23/15 - 16583344: Add 3230,
/ delete pending -> delete in progress
/ btsao 02/18/15 - Add 4KB Metadata/sector format messages
/ 1102, 1106 1113, 1167, 1168, 1169, 3228, 7563.
/ Made 1112 and 1165 obsolete.
/ jochoa 02/16/15 - Bug 20430869: rootupgrade diagnostics for
/ an acfs error
/ vyerrams 01/30/15 - Bug 20182031: Add an extra %s to 11077
/ for printing node name.
/ crusman 01/20/15 - Bug 20190090: compression support
/ add 7630-7638
/ gsanders 01/15/15 - Bug 20003572 Add 05831 - 05842
/ gsanders 01/06/15 - Bug 20300017 fix message 03197 missing a "/"
/ gsanders 12/22/14 - Add messages 05907, 05908
/ crusman 12/22/14 - Bug 20032602: compression support
/ qmcintos 12/18/14 - Fix typos in 7543
/ gsanders 01/06/14 - Bug 20300017 fix message 03197 missing a "/"
/ qmcintos 11/21/14 - Add message 3229, 7542, 7543.
/ himhmed 11/20/14 - Add messages 11080-11090
/ averhuls 11/18/14 - Correct path in 9119 action.
/ rbreau 11/14/14 - Add/update fsck messages for Accelerator V2
/ - Added messages 7551 and 7552
/ - Modified messages 7588, 7590, 7598 and 7600
/ based on feedback from previous submit
/ - Renumbered messages 7542 through 7550 due to
/ collisions with new messages recently added to
/ MAIN:
/ 7542 to 7554
/ 7543 to 7555
/ 7544 to 7556
/ 7545 to 7557
/ 7546 to 7558
/ 7547 to 7559
/ 7548 to 7560
/ 7549 to 7561
/ 7550 to 7562
/ sverhuls 11/10/14 - Add ofsutil meta messages (3645-3655)
/ ethibaul 10/27/14 - Clarify message 2080, Add 2135 & 2136
/ jorhuert 10/14/14 - Adding error message when user specifies
/ an unknown ODA mode during installation (9192)
/ - Adding error message when user tries to install
/ in ODA mode on an unsupported OS (9193)
/ tengle 10/08/14 - Increase minimum auto-resize increment to 1G
/ rbreau 09/10/14 - Add and modify fsck messages for Accelerator V2
/ mnollen 08/22/14 - Add colon ':' to msg 03071,0
/ jorhuert 08/13/14 - bug-16995881 adding release version to
/ 'acfsdriverstate version'
/ tengle 08/11/14 - Add messages for ACFS auto-resize (3639-3644)
/ crusman 07/24/14 - Add compression messages.
/ bonelso 07/10/14 - Fix lots of repl message paramater types
/ jorhuert 07/01/14 - Editing error message 3149 to include size
/ limit
/ raharris 06/26/14 - Update the Cause/Action for a few error
/ messages that will reduce a lot of
/ ofsdebugmsg.pl -cause_action error reports.
/ 511,519,532,533,535,544,545,3043,7475,7682
/ - Fix 7929 by adding missing % positional
/ notation for %(2)s
/ - Fix 7931 where %(lowercase L) was used instead
/ of %(1)s
/ - Add new message 7944,7945,7946,10767 because the
/ original messages were removed, but not all the
/ code stopped using the messages.
/ - Fix 7262 by changing %(1) to %(1)s
/ - Fix 7202 by changing %(1)s to %(1)u as the
/ caller is using LSFUB8().
/ - Fix 7736,7737,7761,7769,7771 from %(1)u %(2)u
/ to %(1)s %(2)s because the callers are using
/ LSFTXTP().
/ - Fix 7743,7746,7758 from %(2)s to %(2)u
/ because the callers are using LSFIVALUE().
/ - Fix 7745,7747,7748,7759 from %(3)s to %(3)u
/ because the callers are using LSFIVALUE().
/ - Fix 3219 from %7s to %7d and %13s to %13d
/ - Fix 3609 from %s to %d
/ averhuls 06/25/14 - Add device argument to 3024, volume to 9025.
/ ifarfan 06/23/14 - Add 00146, 00147, 00626, 09092, 09700-09718.
/ averhuls 06/20/14 - Add 3637.
/ mcarrell 05/19/14 - Add additional repl v2 error messages 3197-3199
/ and 5902-5906.
/ hmishra 05/09/14 - Added messages 10358, 10718-10721
/ mlmiller 05/09/14 - Add 5749
/ averhuls 04/29/14 - Add 107 dup but with a cause and action.
/ mcarrell 04/21/14 - Add message 5901.
/ ethibaul 04/16/14 - Fix cause for 9427, 9428
/ vyerrams 04/08/14 - Bug 18043366: Add 11070 to 11078 for
/ "acfsutil clusterinfo"
/ hmishra 03/24/14 - Add messages 10714-10718
/ stomar 02/24/14 - Bug 16869766: expanded the cause for 10781
/ mcarrell 02/21/14 - Add additional repl v2 error messages 5893-5900.
/ mcarrell 02/20/14 - Add repl v2 error messages 142-145, 171-179,
/ 5812-5830, and 5887-5892.
/ rbreau 01/21/14 - Fix for message 7453
/ - Add messages 7447 and 7448 for kilosnaps support
/ mkeller 12/29/13 - Bug 17761866: info fs with -s and -d, msg 03344
/ tmark 11/27/13 - Add 1165 and 1166.
/ ethibaul 12/03/13 - 17561473: Add norstchown Solaris mount option
/ mperezh 11/15/13 - Add 1164 - Accelerator check on CRS
/ ssprasad 10/29/13 - Add 9508
/ madoming 09/26/13 - Add Current Device State and restructure 11036.
/ ifarfan 09/25/13 - Remove crsctl from 03135, 03136 and 09260.
/ himhmed 09/24/13 - NoUpHdrPtr support: Add 07363, 07400
/ rbreau 09/09/13 - New fsck messages for kilosnaps support
/ - fix for 7121
/ - restored 7240
/ hmishra 08/30/13 - Added messages 10801-10803
/ stomar 08/04/13 - Added 10464
/ oehmoda 08/09/13 - Modified 5801-5808.
/ sverhuls 08/07/13 - Add SI units to some messages. Bug 7281377
/ ethibaul 07/29/13 - Add 2126-2133
/ tmark 07/05/13 - Storage Accelerator Project phase 5.
/ ssprasad 06/26/13 - Add 10941,10942
/ rbreau 06/24/13 - Restore message 7355, fix 7764
/ ifarfan 06/10/13 - Add 09191, 09506 and 09507.
/ tmark 05/06/13 - Storage Accelerator Project phase 2.
/ bonelso 04/29/13 - fix typo in 9085
/ oehmoda 04/04/13 - Add 3225
/ ethibaul 04/01/13 - 11.2.0.4 translation based updates
/ averhuls 03/26/13 - Add 9190.
/ ethibaul 03/08/13 - Add 123,124, 3218-3224
/ gsanders 21/02/13 - Added message 05811
/ averhuls 02/28/13 - Add 3541, 3542, 3543.
/ gsanders 02/25/13 - Added 05809, 05810
/ oehmoda 02/25/13 - Added 03217.
/ bonelso 02/25/13 - Modified 9086
/ hmishra 02/24/13 - Added messages 10357, 10945-10946,
/ and 10712-10713
/ qmcintos 02/20/13 - add message 03626, 03627 for cluster log
/ mkeller 02/15/13 - Added 3324-3343, 3625
/ oehmoda 02/04/13 - Add cause and action statements to message
/ 03054
/ ethibaul 01/17/13 - Clean up platform specific
/ references in cause/action clauses
/ tmark 01/04/13 - Added 3120, obsoleted 3121.
/ jibeltz 12/26/12 - Added message 5808
/ hmishra 12/14/12 - Added message 11000
/ stomar 12/05/12 - Added 10936-40 (bug 15940786)
/ ssprasad 12/03/12 - Add msg: 10999 (bug 15926898 fix), 10356
/ averhuls 11/30/12 - Fix 3539 typo - missing '/" in cause.
/ rkiyer 11/29/12 - Added messages 10691,10947,10948,10949,10950
/ ssprasad 11/26/12 - Add messages: 10979, 10980
/ jeabraha 10/10/12 - Add message 3216
/ argardu 08/29/12 - Deleted 9209, added 9211
/ ssprasad 08/01/12 - Add 10800
/ ethibaul 07/26/12 - 13887279: Break up message 7185
/ into 7180 and 7185
/ ssprasad 07/25/12 - Add 10424
/ averhuls 07/24/12 - Add 3528-3530.
/ hmishra 07/18/12 - Add messages 10708-10711
/ ssprasad 07/17/12 - Add 05233, 05234, 05235
/ mlmiller 07/05/12 - Add 05172
/ argardu 06/27/12 - Added 9175-9189 inclusive
/ nagkumar 06/26/12 - Add message 10977, 10978.
/ rkiyer 06/18/12 - Updated messages 10421, 10422
/ averhuls 06/10/12 - acfssec -> acfs/security
/ crusman 06/10/12 - Add 7521
/ rasingar 06/01/12 - Added Messages 5230-5232.
/ nagkumar 05/29/12 - Add message 10976.
/ rasingar 05/19/12 - Added Messages 5221-5229, and 10998.
/ ethibaul 05/11/12 - Add 3215
/ ssprasad 05/09/12 - Add messages 5218, 5219, 5220
/ nagkumar 05/09/12 - Update messages 10991, 10992.
/ madoming 05/09/12 - Remove < and > from messages 9205 and 9206.
/ Add { and } to messages 9205, 9206.
/ and 9265. Change [ and ] to { and } in message
/ 9440 and add [ and ] to <path> in message 9940.
/ Change ORACLE_HOME to home_path in message 9205
/ Add [-h] to messages 9205, 9228.
/ Obsolete messages 9337 and 9386.
/ ethibaul 04/23/12 - Add message 4151
/ gsanders 04/30/12 - Add 03622, 03623, 03624
/ nagkumar 04/18/12 - Update message 10982.
/ crusman 04/17/12 - Fix 7425; add 7482, 7483, 7504
/ mkeller 04/17/12 - Add messages 3195+3196.
/ tengle 04/04/12 - Add message 3621
/ hmishra 04/02/12 - Add message 10975, 10993-10997
/ averhuls 03/28/12 - Add 506 & 3119 & 03539.
/ madoming 03/28/12 - Remove -b blksz option.
/ Add Messages 1060, 1100, 1112.
/ Obsolete messages 1056, 1061, 1097, 1104, 1110
/ mkeller 03/22/12 - Add 5159
/ rasingar 03/06/12 - Added Message 10463
/ rasingar 03/05/12 - Added messages 05215, 05216 and 05217.
/ hmishra 02/29/12 - Add message 10973, 10974
/ mkeller 02/28/12 - Add and fix a couple new messages
/ anjiwaji 02/22/12 - Add message for setting acfsutil in acfsroot
/ command location.
/ hmishra 02/14/12 - Add message 10972
/ mcarrell 02/13/12 - Add message 5158.
/ averhuls 02/09/12 - Add 'acfsutil version -v' messages 3616-3620
/ hmishra 02/08/12 - Edited the message 10799
/ mkeller 02/07/12 - Add 3180-3186, 3190-3194.
/ ssprasad 02/06/12 - Add 5213, 5214
/ madoming 02/01/12 - Add 4038
/ tengle 02/01/12 - Add message 7928
/ tmark 01/25/12 - Add 3179.
/ nagkumar 01/24/12 - Updated msg 10970(Bug fix - 13590032).
/ crusman 01/22/12 - Add 3214
/ rasingar 01/20/12 - Added messages 5208 - 5212.
/ crusman 01/12/12 - Add 3121
/ stomar 12/28/11 - Add message 10423
/ anjiwaji 12/20/11 - Add message 9500-9504 for acfsroot
/ averhuls 12/15/11 - Add 9428, 9429.
/ tengle 12/15/11 - Add message 3614
/ ssprasad 12/09/11 - Add message 5206,5207
/ nagkumar 12/08/11 - Add msgs 10969 - 10971.
/ tengle 12/08/11 - Add messages for directory bitmaps: 7761-7771
/ ssprasad 11/30/11 - Add message 5205
/ hmishra 11/24/11 - Added messages 10991-10992
/ crusman 11/19/11 - add 3213
/ nagkumar 10/24/11 - Add message 10968.
/ amilicia 11/03/11 - Add message 7445
/ crusman 09/25/11 - add snap-of-snap msgs 03209-03211; add 3212
/ gsanders 10/02/11 - 9291,9168,9169,9170,9171,9172,9173,9174,2090
/ averhuls 09/29/11 - Minor fix to 9385.
/ mkeller 09/28/11 - Add message 5748
/ tmark 09/21/11 - Snap Convert project.
/ averhuls 09/21/11 - 01006: change "volume" to "volume device".
/ tengle 09/15/11 - Add plug-in messages 03600-03615
/ mkeller 09/08/11 - Add message 5747
/ averhuls 09/02/11 - Add 'usmdriverstate validate' messages.
/ hsabbine 08/31/11 - Add messages 10951-1967; 10981-10990 to
/ provide auditing support
/ gsanders 07/26/11 - Add message 09291
/ mlmiller 08/17/11 - Add 5156 and 5157 for standby initialization
/ averhuls 08/17/11 - Add 3540.
/ himhmed 08/17/11 - add 4150.
/ averhuls 07/22/11 - add 9399.
/ certan 07/18/11 - Add messages 9395 and 9396
/ 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.
/ mkeller 06/28/11 - Add msg 3323
/ gsanders 06/26/11 - Add 09394
/ averhuls 06/22/11 - copy 3514 from 11.2.0.3.
/ 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
/ 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/29/11 - XbranchMerge rbreau_bug-11804103 from
/ st_usm_11.2
/ rbreau 04/27/11 - Add message 7165
/ certan 04/27/11 - Add message 4100-4102 for umount on Solaris
/ 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.
/ mkeller 04/06/11 - modify 5702,5716,5717, delete 5725,
/ new 5732-5734 + 5737-5746
/ 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.
/ sverhuls 03/21/11 - Fix a typo in action section of 3158
/ hmishra 03/18/11 - Modified msg 10421
/ rbreau 03/16/11 - Add message 7021 for corrupt FETA
/ - Add message 7118 for system files
/ that cannot be repaired
/ mcarrell 03/16/11 - Create message 9110 to replace incorrect
/ message 9111.
/ rkiyer 03/15/11 - Update message 10659
/ qmcintos 03/14/11 - Add 3177
/ averhuls 03/11/11 - Add 9158.
/ ethibaul 03/10/11 - 11820987: Add 4058
/ mkeller 03/07/11 - Add msgs 5730 + 5731.
/ 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
/ tmark 02/18/11 - Add 3175 and 3176.
/ mkeller 02/16/11 - Backport mkeller_acfsutilbugs from main
/ mkeller 02/15/11 - Added msgs 3319 + 3320
/ 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
/ ethibaul 02/03/11 - snapshot message updates
/ 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.
/ averhuls 01/10/11 - Add 09389.
/ 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
/ 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-09699
/ advmutil (again) 09700-09799
/ ACFS Remote 09800-09999
/ security 10000-10999
/ device config tools 11000-11999
/ Snap Remaster 12000-12999
/ advmutil ACFSR 13000-13999
/
/
//

/ 00100-00499 are words, phrases, fragments to be translated and used
/ without MsgId to display state information using, e.g. the
/ OFSMSG_TFRAG macro.
/
/ THESE MAY NOT BE COMBINED TO BUILD OTHER SENTENCES
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, "None"
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, "free:"
00124, 0, "used:"
00125, 0, "Could not synchronize replication. No storage left on device."
00126, 0, "Failed to synchronize replication primary and standby file sytems."
/ Message 00127 UNUSED and available
/ Message 00128 UNUSED and available
00129, 0, "The replication %s daemon is running with insufficient privileges."
00130, 0, "Write failed."
00131, 0, "Apply process is already stopped."
/ Message 00132 UNUSED and available

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."
/ Message 00140 UNUSED and available
00141, 0, "Apply daemon running with insufficient privileges."
/ Fragments 00142 and 00143 are used in a columnar output "report" with the
/ following message:
/ 05814, 0, "Background Resources: %s"
00142, 0, "Active"
00143, 0, "Stopped"
/ Fragments 00144 and 00145 are used in a columnar output "report" with the
/ following message:
/ 05830, 0, "Data transfer compression: %s"
00144, 0, "On"
00145, 0, "Off"
00146, 0, "[YES]"
00147, 0, "[NO ]"

00148, 0, "DISCLAIMER:"
00149, 0, "The determination of whether the current system configuration is supported \nor not is based on the list of approved kernels and OS versions at the time \nof shipment of the base code, together with any installed patches. At times, \nspecific kernel or OS versions may be unsupported due to known issues or OS \nbugs."
00150, 0, "For the latest information and notes on ACFS, including the most up to date \nsupport information with patches and PSU information, consult MOS note \n(Doc ID 1369107.1): ACFS Support On OS Platforms (Certification Matrix)."

/ Message 00160 UNUSED and available
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
/ Fragments 00166 - 00171 and 05848 are used in a columnar output "report" with
/ the following message:
/ 05103, 0, "Primary status: %s"
00166, 0, "Online"
00167, 0, "Initializing"
00168, 0, "Background Stopped"
00169, 0, "Paused"
00170, 0, "Unknown"
00171, 0, "Running"
/ Fragments 00172 - 00179 are used in a columnar output "report" with the
/ following message:
/ 05820, 0, "Status: %s"
00172, 0, "Send Completed"
00173, 0, "Send Failed"
00174, 0, "Receive Completed"
00175, 0, "Receive Failed"
00176, 0, "Sending initial copy"
00177, 0, "Receiving initial copy"
00178, 0, "Sending incremental differences"
00179, 0, "Receiving incremental differences"

/ Plug-in fragments
00180, 0, "Poll"
00181, 0, "Post"

/ acfsutil info storage fragment
00182, 0, "Not Available"
00183, 0, "(Offline)"

/ replication reversal fragments used with 05820
00184, 0, "Reversal in progress"

/ 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"
// *Cause: The command argument does not support the specified value.
// *Action: Review the command usage and retry the command providing valid
// input.
00504, 0, "Invalid unit specified: %s. Valid units are K|M|G|T|P."
// *Cause: The command does not support the specified unit.
// *Action: Review the command usage and retry the command providing valid
// input.
00505, 0, "invalid signature requested"
// *Cause: The command failed to verify the ACFS file system metadata.
// *Action: Contact Oracle Support Services.
00506, 0, "Failed to read '%s'."
// *Cause: An open file could not be read.
// *Action: The most likely cause is a file permission problem.
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."
// *Cause: Cluster was still using the file system.
// *Action: Make sure the file system is unmounted on all cluster nodes before
// running the file system checking utility.
00512, 0, "A file system check of %s is in progress."
// *Cause: The command failed because metadata showed that a file system
// check was either in progress or incomplete on the specified volume.
// *Action: Ensure that a file system check is not being run on another
// node or by another user before retrying the command. If a
// file system check operation had been started and then aborted,
// use 'fsck -f' to repair the volume and then retry the command.
00513, 0, "unable to obtain ACFS driver version number"
// *Cause: The ACFS driver version number could not be retrieved. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
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 %(1)s %(2)s version \n %(3)s ACFS kernel version"
// *Cause: The command failed because of a mismatch between the loaded
// ACFS driver and the ACFS commands.
// *Action: Use the 'acfsdriverstate version' command to obtain additional
// version information and contact Oracle Support Services.
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"
// *Cause: Too many arguments were entered on the command line.
// *Action: Review the command usage and retry the command providing the
// correct number of arguments.
00520, 0, "%s is not an ADVM volume."
// *Cause: Volume specified was not an ADVM volume.
// *Action: Retry the command specifying 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, "%(1)s is an unsupported drive type %(2)d."
// *Cause: Failed to obtain volume information. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
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 %(1)s is already mounted on %(2)s."
// *Cause: The file system could not be mounted because the specified
// volume was already mounted using a different mount point.
// *Action: Select a different volume and retry the mount operation.
/ Message 00529 removed - do not reuse message number
/ Message 00530 removed - do not reuse message number
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"
// *Cause: The command does not support the specified option.
// *Action: Review the command usage and retry the command providing valid
// options.
00533, 0, "%s requires an argument"
// *Cause: The command did not pass a required argument.
// *Action: Review the command usage and retry the command providing the needed
// argument.
00534, 0, "A valid numeric string is required."
// *Cause: The command was rejected because the specified value was not
// a valid numeric string.
// *Action: Review the command usage and retry the command providing valid
// input.
00535, 0, "insufficient arguments"
// *Cause: The command required additional arguments.
// *Action: Review the command usage and retry the command providing the needed
// argument.
00536, 0, "unknown extra argument: %s"
// *Cause: The command was rejected because the indicated argument was not
// a valid argument for this command.
// *Action: Review the command usage and retry the command providing valid
// options.
/ Message 00537 removed - do not reuse message number
00538, 0, "invalid command or command is not unique: %s"
// *Cause: The command was rejected because the indicated sub-command was
// not supported.
// *Action: Review the command usage and retry the command providing valid
// input.
00539, 0, "missing arguments"
// *Cause: The command was rejected because additional arguments were
// required.
// *Action: Review the command usage and retry the command providing valid
// input.
00540, 0, "incorrect number of arguments"
// *Cause: The command was rejected because an incorrect number of
// arguments were specified.
// *Action: Review the command usage and retry the command providing valid
// input.
00542, 0, "argument is not an integer"
// *Cause: The command was rejected because a string was specified as an
// argument instead of an integer.
// *Action: Review the command usage and retry the command providing valid
// input.
00543, 0, "invalid command"
// *Cause: The command was rejected because an invalid sub-command was
// specified.
// *Action: Review the command usage and retry the command providing valid
// input.
00544, 0, "option spelling is not unique: %s"
// *Cause: An attempt to execute a command specifying an abbreviated option
// name was rejected because there were multiple possible options
// beginning with the specified string.
// *Action: Review the command usage and retry the command providing the
// desired option.
00545, 0, "%(1)s does not support a value: %(2)s=%(3)s"
// *Cause: The command was rejected because an option that does not support
// a value was specified with a value attached.
// *Action: Review the command usage and retry the command providing the
// correct option syntax.
00546, 0, "failed to change on-disk signature"
// *Cause: The command failed to update ACFS metadata on-disk. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
00547, 0, "Both the primary and alternate superblocks are damaged."
// *Cause: The file system metadata was found to be damaged.
// *Action: Run fsck (Unix or Linux) or acfschkdsk.exe (Windows)
// 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"
// *Cause: An attempt to validate the metadata on-disk failed due to
// a metadata inconsistency found in the file system superblocks.
// *Action: Run the ACFS Fixer to resolve the metadata inconsistency
// and then retry the operation.
00551, 0, "unable to process input from the command line"
// *Cause: A failure occurred opening the stdin stream. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
00552, 0, "End-of-file received instead of 'y' or 'n'"
// *Cause: An end-of-file was received while waiting for the answer to a
// question prompt.
// *Action: None.
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]? "
// *Document: NO
00554, 0, "Unable to obtain group name for gid: %ld"
// *Cause: The command failed because the group name could not be
// determined using the supplied group id.
// *Action: Ensure that the required group exists, then re-run the command.
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"
// *Cause: ACFS did not support the specified option.
// *Action: Review the command usage and retry the command providing valid
// options.
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.
/ Message 00574 UNUSED and available
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.
/ Message 00588 UNUSED and available
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"
// *Cause: An attempt to validate the metadata on-disk failed due to
// a metadata inconsistency found in the volume disk header.
// *Action: Run the ACFS Fixer to resolve the metadata inconsistency
// and then retry the operation.
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."
// *Cause: The command did not support the specified option combination.
// *Action: Review the command usage and retry the command providing valid
// options.
00609, 0, "End-of-file received."
// *Cause: An end-of-file was received while waiting for the answer to a
// question prompt.
// *Action: None.

// 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."
// *Document: NO
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.

00621, 0, "Unable to determine privileges"
// *Cause: An error occured retrieving the user credentials.
// *Action: Verify the mount point is an ACFS mount point and it is not offline.
00622, 0, "must provide a base mount point"
// *Cause: A mount point on the base site was not provided.
// *Action: Provide an existing mount point on the base site.
00623, 0, "must provide a target mount point"
// *Cause: A mount point on the target site was not provided.
// *Action: Provide an existing mount point with an empty file system on the
// target site.
00624, 0, "The path specified is too long."
// *Cause: The path specified exceeded the allowed maximum path length.
// *Action: Verify the path was entered correctly, or use a different path.
00625, 0, "%s is not a valid ACFS mount point."
// *Cause: The mount point path specified was not a valid mount point.
// *Action: Provide a valid ACFS mount point.
00626, 0, "Latest timestamp: %lu"
00627, 0, " Accelerator Volumes: %s"
00628, 0, "Device : %s : Mount Point : %s : Options : %s : Nodes : %s : Disk Group: %s : Primary Volume : %s : Accelerator Volumes : %s"
/
/ Messages [00629 - 00998] UNUSED and available
/
00999, 0, "unexpected assert: \"%(1)s\", %(2)s: %(3)s: %(4)d"
// *Cause: An unexpected situation has occurred.
// *Action: Contact Oracle Support Services.
/
/ End generic 00500-00999

/
/ 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"
// *Cause: An error occurred during the generation of a unique
// file system identifier. This message is accompanied by other
// messages providing details on the error.
// *Action: Correct the problem indicated by the other messages. If
// the solution is not clear, contact Oracle Support Services.
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 device '%s'"
// *Cause: Volume device 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"
// *Cause: An attempt to close a volume handle failed. The accompanying
// messages provide detailed information on the failure.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
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"
// *Cause: An attempt to close a file system handle failed. The accompanying
// messages provide detailed information on the failure.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
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 fsck (Unix or Linux) or acfschkdsk.exe (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"
// *Cause: An attempt to write to the volume failed. The accompanying
// messages provide detailed information on the failure.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
/ Message 01016 removed - do not reuse message number
01017, 0, "length of file system name exceeds %u"
// *Cause: An ACFS file system could not be created because the length of the
// file system name exceeded the indicated maximum length.
// *Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on
// Windows) supplying a name with length less than or equal to
// the indicated maximum.
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 exceeds %u"
// *Cause: An ACFS file system could not be created because the length of the
// volume name exceeded the indicated maximum length.
// *Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on
// Windows) supplying a name with length less than or equal to
// the indicated maximum.
01022, 0, "failed to bring ADVM volume %s online"
// *Cause: An ACFS file system could not be created because an error
// occurred while bringing the volume online. This message is
// accompanied by other messages providing details on the error.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
/ Message 1023 removed - do not reuse message number
/ Message 1024 removed - do not reuse message number
01025, 0, "failed to generate a file system id"
// *Cause: An ACFS file system could not be created because an error
// occurred during the generation of a file system identifier.
// This message is accompanied by other messages providing
// details on the error.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
/ Message 01026 UNUSED and available
/ Message 01027 UNUSED and available
/ Message 01028 UNUSED and available
/ Message 01029 UNUSED and available
/ Message 01030 UNUSED and available
/ Message 01031 UNUSED and available
/ Message 01032 UNUSED and available
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.
/ Message 01034 UNUSED and available
/ Message 01035 UNUSED and available
/ Message 01036 UNUSED and available
/ Message 01037 UNUSED and available
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.
/ Message 01039 UNUSED and available
/ Message 01040 UNUSED and available
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.
/ Message 01042 UNUSED and available
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.
/ Message 01048 UNUSED and available
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.
/Obsolete 01056 - see 01060
01056, 0, "Usage: [%sh] [%sv] [%sf] [%sb <blksz>] [%sn <name>]%s <volume> [<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"
/Obsolete 01160 - see 01168
01060, 0, "Usage: [%sh] [%sv] [%sf] [%sn <name>]%s <volume> [<size>]"
/Obsolete 01061 is not used.
01061, 0, " [%sb <blksz>] - Block size used by new file system"
01062, 0, " [%sn <name>] - Name of file system to be created"
01063, 0, " <volume> - 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"
/Obsolete 01068 - see 01161
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"
/Obsolete 01087 - see 01162
01087, 0, "VolLength = %u"
01088, 0, "VolClusterSize = %u"
01089, 0, "VolFETAOffset = %u"
01090, 0, "VolExtentHeaderSize = %u"
01091, 0, "VolEAContainerUnitBlkSize = %u"
01092, 0, "VolExclusiveMount = %d"
/Obsolete 01093 - see 1163
01093, 0, "volume size = %u"
01094, 0, "%s is not an ADVM volume"
// *Cause: Volume specified was not an ADVM volume.
// *Action: Retry the command with an ADVM volume.
01095, 0, "unable to determine current directory"
// *Cause: An ACFS file system could not be created because an attempt
// to determine the current directory failed. This message is
// accompanied by other messages providing details on the error.
// *Action: Correct the problem described in the accompanying messages if
// possible and retry the command. If the solution is not clear,
// contact Oracle Support Services.
01096, 0, "length of volume path exceeds %d"
// *Cause: An ACFS file system could not be created because the length of the
// volume path exceeded the indicated maximum length.
// *Action: Retry the command (mkfs on Unix or Linux or acfsformat.exe on
// Windows) supplying a volume path with length less than or equal
// to the indicated maximum.
/Obsolete 01097 - see 01100.
01097, 0, "Usage: -V acfs [%sv name] [%ss size] [%so [h],[v],[f],[b=blksz]%s] <volume>"
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"
/Obsolete 01100 - see 01101
01100, 0, "Usage: -V acfs [%sv <name>] [%ss <size>] [%so [h],[v],[f]%s] <volume>"
01101, 0, "Usage: -V acfs [%sv <name>] [%ss <size>] [%so [h],[v],[f],[i=<metasize>],[c=<release>]%s] <volume>"
01102, 0, " [i=<metasize>] - Metadata block size"
01103, 0, " [f] - Force file system format, use to overwrite an existing file system"
/Obsolete 01104 is not used.
01104, 0, " [b=<blksz>] - Block size used by new file system"
01105, 0, "MetadataSize = %u"
01106, 0, "Usage: [%so [h],[v],[f]%s,[i=<metasize>],[n=<name>],[a=<volume>],[c=<release>]] <volume> [<size>]"
01107, 0, " [%si=<metasize>] - Metadata block size"
01108, 0, " [c=<release>] - Create ACFS file system compatible with specified release (For example, 12.2.0.0.0)"
/Obsolete 01110 - see 01112.
01110, 0, "Usage: [%so [h],[v],[f],[b=<blksz>]%s,[n=<name>]] <volume> [<size>]"
01111, 0, " [n=<name>] - Name of file system to be created"
/Obsolete 01112 - see 01106
01112, 0, "Usage: [%so [h],[v],[f]%s,[n=<name>]] <volume> [<size>]"
01113, 0, "Block size %s is invalid for metadata."
// *Cause: An attempt to create a file system was rejected because
// the requested metadata block size was invalid.
// *Action: Specify a metadata block size of 4096 or take the default.
// File system creation sets the metadata block size to the
// primary volume's logical sector size by default.
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.
01152, 0, "The length of accelerator volume name exceeds %u."
// *Cause: Accelerator volume name length exceeded the maximum length displayed
// in the message.
// *Action: Select an accelerator volume name with length less than or equal to
// the maximum length displayed in the message and retry the command.
01153, 0, "accelerator volume = %s"
// *Document: NO
01154, 0, "The accelerator volume contains a mounted ACFS file system. The file system must be dismounted with acfsdismount on each node."
// *Cause: The specified volume could not be used as an accelerator volume
// because it was in use by a mounted file system.
// *Action: Dismount the ACFS file system with acfsdismount and retry the
// command.
01155, 0, "The accelerator volume contains a mounted non-ACFS file system. The file system must be dismounted with 'advmutil dismount'."
// *Cause: The specified volume could not be used as an accelerator volume
// because it was in use by a mounted non-ACFS file system.
// *Action: Dismount the non-ACFS file system with 'advmutil dismount' and
// retry the command.
01156, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.1.0.2.0."
// *Cause: An attempt to create a file system with an accelerator volume failed
// because the ADVM compatibility attribute for the disk group was not
// set to 12.1.0.2.0 or higher.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
// statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
01157, 0, "accelerator volume size = %u %s"
// *Document: NO
01158, 0, "On Accelerator Volume:"
// *Document: NO
01159, 0, "The accelerator volume must be different from the volume containing the file system."
// *Cause: The file system could not be created because the same volume was
// specified for both the accelerator and the file system.
// *Action: Choose a different volume for the accelerator and retry the command.
01160, 0, "The specified accelerator volume was smaller than the %.1lf %s required for this file system."
// *Cause: The file system could not be created because the specified
// accelerator volume was below the minimum allowed size reported
// in the message.
// *Action: Select a larger accelerator volume and retry the command.
01161, 0, "volume space used = %d %s"
01162, 0, "VolLength = %u %s"
01163, 0, "volume size = %u %s"
01164, 0, "The specified device '%s' is already in use with a CRS-managed file system."
// *Cause: The file system could not be created because the specified
// device was already registered with CRS (Cluster Ready Services).
// *Action: Select an unused device, or use srvctl to modify the association
// for this device and retry the file system creation.
/Obsolete 01165 - see 01167
01165, 0, "Usage: [%sh] [%sv] [%sf] [%sn <name>] [%sa <volume>]%s <volume> [<size>]"
01166, 0, " [%sa <volume>] - ACFS accelerator volume pathname"
01167, 0, "accelerator volume space used = %d %s"
// *Document: NO
01168, 0, "Usage: [%sh] [%sv] [%sf] [%si <metasize>] [%sn <name>] [%sc <release>]%s <volume> [<size>]"
01169, 0, " [%si <metasize>] - Metadata block size"
01170, 0, "Accelerator volume sector size = %u must match primary volume sector size = %u"
// *Cause: An attempt to create a file system was rejected because the
// logical sector sizes of primary and accelerator volume were
// different, as shown. The sector sizes of the primary and
// accelerator volumes must be the same.
// *Action: Select devices that have the same logical sector size for the
// primary and accelerator volumes or specify the 'i 4096' switch.
01171, 0, "Usage: [%sh] [%sv] [%sf] [%si <metasize>] [%sn <name>] [%sa <volume>] [%sc <release>]%s <volume> [<size>]"
01172, 0, " [%sc <release>] - Create ACFS file system compatible with specified release (For example, 12.2.0.0.0)"
01173, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum 12.2.0.0.0."
// *Cause: An attempt to create a file system failed because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version for either the primary or accelerator volume,
// which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
01174, 0, "file system size = %u %s"
01175, 0, "ACFS compatibility = %d.%d.%d.%d.%d"
01176, 0, "file system format requires volumes with sector size = %u"
// *Cause: An attempt to create a file system was rejected because the
// logical sector size of the primary or accelerator volumes was
// too large for the 512-byte metadata block size format.
// *Action: Select devices with a 512-byte logical sector size when
// creating a file system using the 'i 512' format switch.
// Use the command 'advmutil volstats' to verify that the volume's
// sector size is 512 bytes before formatting the file system.
// Alternatively, format the file system without the 'i 512' switch,
// allowing Oracle ACFS to create a 4096-byte metadata block size
// format.
01177, 0, " [a=<volume>] - ACFS accelerator volume pathname"
01178, 0, "bytes per sector (accelerator volume) = %d"
01179, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than the required minimum %d.%d.%d.%d.%d"
// *Cause: An attempt to create a file system failed because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version for either the primary or accelerator volume,
// which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
01180, 0, "Usage: [%so [h],[v],[f]%s,[i=<metasize>],[n=<name>],[c=<release>]] <volume> [<size>]"
/
/ 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.
02007, 0, "symlink %s supplied as mount point"
02008, 0, "volume: %s, symlink mount point: %s, mount point: %s"
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."
// *Cause: The file system could not be mounted because the specified
// directory was already in use by another file system mount point.
// *Action: Select an unused directory and retry the mount operation.
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"
// *Document: NO
02020, 0, "options length exceeds %d"
// *Cause: An ACFS file system could not be mounted because the length of the
// options provided exceeded the indicated maximum length.
// *Action: Retry the mount operation supplying an option list of length less
// than or equal to the indicated maximum.
02021, 0, "mount path paired with volume %(1)s exceeds %(2)d characters"
// *Cause: An ACFS file system could not be mounted because the total
// length of the mount path plus the volume path exceeded the
// indicated maximum character length.
// *Action: Retry the mount operation supplying a total length less than
// or equal to the indicated maximum.
02022, 0, "no options"
// *Document: NO
02023, 0, "no update /etc/mtab entry option specified"
// *Document: NO
02024, 0, "verbose option specified"
// *Document: NO
02025, 0, "command string: %s."
// *Document: NO
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"
// *Cause: An ACFS file system could not be mounted because an attempt
// to obtain a list of volumes failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02029, 0, "Silently ignoring requested duplicate mount of %s on %s."
// *Document: NO
02030, 0, "Usage: [%so] <mount options> [%sh] [%sv] [%sn] <volume> <directory>"
02031, 0, " [%so] <mount options> - 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> - Volume to mount"
02036, 0, " <directory> - Root of file system on volume"
02037, 0, "File system not created on a %s system. Cannot mount."
// *Cause: An ACFS file system could not be mounted because it was created
// on a different type of system than the current system.
// *Action: Retry the mount on a system that matches the indicated system type.
02038, 0, "File system created on an incompatible system (endianness). Cannot mount."
// *Cause: An ACFS file sytem could not be mounted because it was created
// on a computer which has a different endianness than the current
// system. Little endianness machines (such as the Intel X86 based
// systems) store the Least Significant Bit in the first byte of an
// integer value. Big endianness 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 endianness as the system which created
// the file system.
/ Messages for acfsmountvol
02039, 0, "length of path exceeds %d"
// *Cause: An ACFS file system could not be mounted because the length of the
// path exceeded the indicated maximum length.
// *Action: Retry the mount command (acfsmountvol.exe on Windows)
// supplying a path with length less than or equal to the indicated
// maximum.
02040, 0, "Path must be a valid directory or drive letter."
// *Cause: An ACFS file system could not be mounted because the
// mount point path specified was not a valid mount point.
// *Action: Retry the operation, specifying a valid ACFS mount point.
02041, 0, "length of volume name exceeds %d"
// *Cause: An ACFS file system could not be mounted because the length of the
// volume name exceeded the indicated maximum length.
// *Action: Retry the mount command (acfsmountvol.exe on Windows)
// supplying a volume name with length less than or equal to the
// indicated maximum.
02042, 0, "volume: %s"
// *Document: NO
02043, 0, "volume %s in use by a non-ACFS file system"
// *Cause: The file system could not be mounted because the specified
// volume was already in use by another file system.
// *Action: Select a different volume and retry the mount operation.
02044, 0, "%s does not contain a valid ACFS file system. Verify volume contents using acfschkdsk.exe."
// *Cause: The specified file system could not be mounted due to inconsistent
// file system metadata.
// *Action: Run acfschkdsk.exe as soon as possible to fix the metadata
// inconsistency, and then retry the acfsmountvol.exe command.
02045, 0, "%s is in use by another non-ADVM volume"
// *Cause: The file system could not be mounted because the specified
// mount point was already in use by another file system.
// *Action: Select a different mount point and retry the mount operation.
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"
// *Cause: An ACFS file system could not be mounted because an attempt
// to determine a full path name failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02049, 0, "conversion of reparse data Unicode string to ANSI string failed"
// *Cause: An ACFS file system could not be mounted because an attempt
// to convert a unicode string to an ANSI string failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
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"
// *Cause: An ACFS file system could not be mounted because an attempt
// to create a symbolic link failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02052, 0, "broadcast of new symbolic link %s failed"
// *Cause: An ACFS file system could not be mounted because a system wide
// broadcast of the symbolic link failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02053, 0, "failed to create mount point on directory %s"
// *Cause: An ACFS file system could not be mounted because the supplied
// directory could not be turned into a reparse point. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02054, 0, "unable to retrieve a list of active ACFS file systems"
// *Cause: An attempt to obtain an active list of ACFS file systems failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02055, 0, "Usage: %s [/v] [/all]"
02056, 0, " %s [/v] <path> <volume> "
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, " <path> - Drive letter or mount point"
02063, 0, " <volume> - 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, "Volume %s failed to mount due to a version mismatch. Volume version %d is not supported by the current driver, which supports a maximum volume version of %d."
// *Cause: The volume mount failed because the loaded ACFS driver did not
// support the volume version of the indicated volume.
// *Action: Use the 'acfsdriverstate version' command to obtain the version
// of the loaded ACFS driver and contact Oracle Support Services.
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"
// *Document: NO
02085, 0, "creating drive letter"
// *Document: NO
02086, 0, "creating mount point"
// *Document: NO
02087, 0, "unable to lock volume"
// *Document: NO
02088, 0, "failed to unlock the volume"
// *Cause: An attempt to dismount the ACFS file system failed because the
// volume could not be unlocked. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
02089, 0, "Info: failed to change the volume signature, but continuing with dismount anyway. No action required"
// *Cause: An attempt to modify the ACFS file system metadata failed
// during the dismount. The accompanying messages provide
// detailed failure information.
// *Action: None.
02090, 0, "unable to retrieve ACFS mount information from CRS"
// *Cause: Failed to retrieve mount information the CRS.
// *Action: Analyze the error messages that precede 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] <mount options> <volume> <directory>"
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> - Volume to mount"
02109, 0, " <directory> - Root of file system on volume"
02110, 0, "Unable to mount %s on %s."
02111, 0, " [%so] <mount options> - Standard mount options"
02112, 0, " [%sr] - Mount in read-only mode"
02113, 0, "Usage: [%so] <mount options> <volume> <directory>"
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 <share name>
// /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.
02126, 0, "Volume %s cannot be mounted."
// *Cause: The volume mount failed. This message is accompanied by other
// messages providing details on the error.
// *Action: Correct the problem indicated by the other messages and
// retry the mount command.
02127, 0, "unable to transfer mount data to the ACFS driver"
// *Cause: The mount failed because the transfer of mount data from the
// mount command to the ACFS driver failed. This message is
// accompanied by other messages providing details on the error.
// *Action: Correct the problem identified by the other messages. If the
// cause is unclear, contact Oracle Support Services.
02128, 0, "unable to clean up mount data passed to ACFS driver"
// *Cause: The operation to clean up mount data from a temporary location
/// failed.
// *Action: None. This state will not have any repercussions and it will
// be remedied automatically during the next restart.
02129, 0, "Volume %s cannot be mounted. Volume is out of space."
// *Cause: The volume mount failed because the volume was out of space.
// *Action: Correct the problem by resizing the ADVM volume and then retry
// the mount command.
02130, 0, "Volume %s cannot be mounted. Volume version does not match the ACFS driver version."
// *Cause: The volume mount failed because the loaded ACFS driver does not
// support the volume version.
// *Action: Use 'acfsdriverstate' command to determine the state of the ACFS
// driver and address any issues that are reported. Retry the mount
// command after the installed driver has been verified.
02131, 0, "Volume %s cannot be mounted. Cluster membership is not established."
// *Cause: The volume mount failed because the ACFS driver could not
// communicate with Oracle Clusterware.
// *Action: Verify the online state of Oracle Clusterware using command 'crsctl
// check CRS' and address any issues that are reported. Retry
// the mount command once Oracle Clusterware is fully operational.
02132, 0, "Volume %s cannot be mounted. Insufficient kernel resources to complete the mount."
// *Cause: The volume mount failed due to insufficient kernel resources.
// *Action: Reduce the load activity on the system and retry the mount
// command.
02133, 0, "Volume %s cannot be mounted. Metadata inconsistency found on-disk."
// *Cause: The volume mount failed due to a metadata inconsistency
// found in the volume superblock.
// *Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
// inconsistency and then retry the mount command.
/ Note: 02134 is displayed as part of the Solaris mount usage with 02111-02118
02134, 0, " [%so] rstchown|norstchown [,...]- Allow or disallow restricted chown (Solaris 11 only)"
02135, 0, "Volume %s failed to mount due to a version mismatch. Volume version %d is not supported by the %d.%d.%d.%d.%d release."
// *Cause: The volume mount failed because the loaded ACFS driver did not
// support the volume version of the indicated volume.
// *Action: Use the 'acfsdriverstate version' command to obtain the version
// of the loaded ACFS driver and contact Oracle Support Services.
02136, 0, "Volume %s failed to mount due to a version mismatch. Volume version %d requires that the loaded ACFS drivers be from the %d.%d.%d.%d.%d Oracle Database Appliance release."
// *Cause: The volume mount failed because the loaded ACFS driver did not
// support the volume version of the indicated volume.
// *Action: Use the 'acfsdriverstate version' command to obtain the version
// of the loaded ACFS driver and contact Oracle Support Services.
02137, 0, " [%so] rwonlysnaps [,...] - Mount read-only but allow writes in RW snapshots"
02138, 0, " [%so] nodeleteopen [,...] - Prevent the deletion of open files"

/
/ 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"
// *Cause: An attempt to obtain file system information failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
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 primary volume size below 200MB"
// *Cause: A size request specified a primary volume size less than the
// minimum allowed.
// *Action: Specify a primary volume size of 200MB or more
03005, 0, "unable to resize %s"
// *Cause: An attempt to resize the file system failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03006, 0, "smallest size, without loss of data, is: %(1)u (%(2)uMB)"
// *Cause: A resize request failed because the specified size would result
// in data loss.
// *Action: Select a primary volume size that is greater than the size
// indicated in the message and retry the command.
03007, 0, "insufficient storage - largest size is: %(1)u (%(2)uMB)"
// *Cause: A resize request failed because there was not enough storage to
// accomodate the specified size.
// *Action: Select a primary volume size that is less than the size
// indicated in the message and retry the command.
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."
// *Cause: ADVM or ASM was unable to resize the volume.
// *Action: Try again later. Check the ASM alert log if the issue persists.
03010, 0, "new file system size: %(1)u (%(2)uMB)"
// *Document: NO
03011, 0, "The volume size did not change because space is always rounded to multiples of the ASM resize increment."
// *Document: NO
03012, 0, "length of volume name exceeds %d"
// *Cause: The length of the volume name exceeded the indicated maximum
// length.
// *Action: Select a volume name with length less than or equal to
// the indicated maximum length.
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"
// *Cause: Failed to remove the ACFS file system from the volume. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03015, 0, "invalid IP address: %s"
// *Cause: An attempted 'acfsutil repl' command failed because the
// indicated IP address specification was invalid.
// *Action: Retry the command with a valid IP address.
03016, 0, "ACFS is busy with online fsck. Try again later."
// *Cause: An attempt to resize a volume was rejected because ACFS was running
// online fsck.
// *Action: Retry the resize operation when online fsck is not running.
03017, 0, " Build full version: %s"
//*Document: No
/ Message 03018 UNUSED and available
/ Message 03019 UNUSED and available
/ Message 03020 UNUSED and available
/ Message 03021 UNUSED and available
/ Message 03022 UNUSED and available
/ Message 03023 UNUSED and available
03024, 0, "ioctl failed"
// *Cause: An attempted utility operation failed because an error
// occurred in the underlying ioctl operation. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03025, 0, "ioctl call to panic the system failed"
// *Cause: An attempt to execute the 'acfsutil panic' command failed
// because the ioctl request to panic the system failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
/ Message 03026 UNUSED and available
03027, 0, "Invalid product name. Valid product names are OKS, OFS, and AVD."
// *Cause: An attempt to execute the 'acfsutil log' command failed because it
// was issued with an invalid product name.
// *Action: Retry the command specifying one of OKS, OFS, and AVD.
03028, 0, "Product name not specified. Valid product names are OKS, OFS, and AVD."
// *Cause: An attempt to execute the 'acfsutil log' command failed because
// no product name was specified.
// *Action: Retry the command specifying one of OKS, OFS, and AVD.
03029, 0, "product name requires a debug level or context"
// *Cause: An attempt to execute the 'acfsutil log' command failed because
// the debug level or context required for the specified
// product was not provided.
// *Action: Retry the command specifying the debug level or context.
03030, 0, "unable to get log buffer size"
// *Cause: An attempt to execute the 'acfsutil log' command failed because
// the ioctl to retrieve log buffer size failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03031, 0, "unable to set debug context or level"
// *Cause: An attempt to execute the 'acfsutil log' command failed
// because the ioctl to set the debug context or level failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03032, 0, "unable to retrieve log"
// *Cause: An attempt to execute the 'acfsutil log' command failed
// because the ioctl to retrieve the log failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03033, 0, "unable to open %s"
// *Cause: An attempted utility operation failed because the indicated
// file could not be created and/or opened.
// *Action: If a file exists by the same name as the file specified,
// verify that this is a file that can be overwritten.
03034, 0, "write of log file failed"
// *Cause: An attempt to write to the log file failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03035, 0, "unable to retrieve mount entries"
// *Cause: An attempt to obtain an active list of ACFS file systems failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03036, 0, "no mounted ACFS file systems"
// *Cause: The system did not have any mounted ACFS file systems.
// *Action: None
03037, 0, "not an ACFS file system"
// *Cause: The specified file or directory was not a part of an ACFS
// file system.
// *Action: Retry the command with a file or directory that is part of an
// ACFS file system.
03038, 0, "unable to retrieve list of volumes associated with %s"
// *Cause: An ACFS informational query failed because an attempt
// to obtain a list of volumes failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03039, 0, "ioctl call to unregister the ACFS driver failed"
// *Cause: An ACFS detach command failed because an attempt to unregister
// the driver failed.
// *Action: Verify the ACFS driver is loaded and running and retry the
// command.
03040, 0, "Volumes are still mounted. All ACFS file systems must be dismounted before the ACFS driver can be unregistered."
// *Cause: An ACFS detach command failed to unregister the driver
// because ACFS file systems were still mounted.
// *Action: Dismount all ACFS file systems and retry the command.
03041, 0, "unable to unregister ACFS driver"
// *Cause: An ACFS detach command failed because an attempt to unregister
// the driver failed.
// *Action: Verify the ACFS driver is loaded and running and retry the
// command.
/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"
// *Cause: At attempt to create a snapshot was rejected because the specified
// snapshot name was too long.
// *Action: Issue the command again using a shorter snapshot name.
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"
// *Cause: The specified directory was not an ACFS mount point.
// *Action: Retry the command with an ACFS mount point.
03046, 0, "unable to perform snapshot operation on %s"
// *Cause: An attempt to execute the acfsutil snap command failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03047, 0, "waiting for another snapshot operation to complete"
// *Document: NO
03048, 0, "Snapshot operation could not complete."
// *Cause: An attempt to execute the acfsutil snap command failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
03049, 0, "There are too many snapshots for the file system associated with %s. Reduce the number of snapshots before proceeding."
// *Cause: An attempt to execute the acfsutil snap command failed because
// there were too many snapshots for the file system.
// *Action: Reduce the number of snapshots for the associated file system
// using 'acfsutil snap delete' and then retry the acfsutil snap
// command.
03050, 0, "Cannot create snapshot %s. It already exists."
// *Cause: An attempt to create a snapshot failed because a snapshot
// with the indicated name was found to already exist.
// *Action: Retry the acfsutil snap command specifying a different name.
03051, 0, "Snapshot %s does not exist."
// *Cause: An attempt to execute the acfsutil snap command failed because no
// snapshot could be found with the indicated name.
// *Action: Retry the acfsutil snap command with the correct name.
03052, 0, "unable to delete snapshot %s due to open files"
// *Cause: An attempt to delete a snapshot failed because there were files
// open in the snapshot.
// *Action: Use lsof or a 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."
// *Cause: A snapshot was successfully deleted but some of the disk
// storage could not be freed.
// *Action: Run the ACFS Fixer to free the storage.
03054, 0, "Snapshot %s is not a valid snapshot name."
// *Cause: The acfsutil snap command failed because the indicated name was not
// a valid snapshot name. Possible reasons include:
// 1) The snapshot name exceeded the limit of 255 characters.
// 2) The snapshot name equaled "." or "..".
// 3) The snapshot name contained "/" (Unix or Linux).
// 4) The snapshot name contained "\" or ":" (Windows).
// 5) The snapshot name contained an illegal character for
// NTFS file names (Windows).
// *Action: Retry the acfsutil snap command specifying a valid snapshot name.
03055, 0, "Snapshot operation failed due to an error on another node. Check Alert logs on other nodes for more details."
// *Cause: An attempt to execute the acfsutil snap command failed because of
// an error on another node in the cluster.
// *Action: Examine the Alert logs on the other nodes, resolve the indicated
// problems, and then retry the operation.
03056, 0, "Snapshot operation is complete."
// *Document: NO
03057, 0, " ACFS Version: %(1)u.%(2)u.%(3)u.%(4)u.%(5)u.%(6)u"
03058, 0, " flags: %s"
03059, 0, " primary volume: %s"
03060, 0, " mount time: %s"
03061, 0, " volumes: %u"
/Obsolete: 03062 is superceded by message 03628.
03062, 0, " total size: %u"
/Obsolete: 03063 is superceded by message 03629.
03063, 0, " total free: %u"
03064, 0, " label: %s"
03065, 0, " flags: %s"
03066, 0, " on-disk version: %(1)u.%(2)u"
03067, 0, " allocation unit: %u"
03068, 0, " major, minor: %(1)u, %(2)u"
/Obsolete: 03069 is superceded by message 03630.
03069, 0, " size: %u"
/Obsolete: 03070 is superceded by message 03631.
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"
/Obsolete: 03079 is superceded by message 03632.
03079, 0, " size: %u"
/Obsolete: 03080 is superceded by message 03633.
03080, 0, " allocated: %u"
03081, 0, " hardlinks: %u"
03082, 0, " device index: %u"
03083, 0, " major, minor: %(1)u,%(2)u"
03084, 0, " access time: %s"
03085, 0, " modify time: %s"
03086, 0, " change time: %s"
03087, 0, " extents:"
03088, 0, "%(1)u.%(2)u.%(3)u.%(4)u.%(5)u"
03089, 0, "permission denied"
// *Cause: The command failed because the user did not have the required
// ASM Administrator privilege.
// *Action: Retry the command from an account with the required privilege.
03090, 0, "%s is an invalid %s number"
// *Cause: The specified argument value was not a valid numeric value.
// *Action: Review the command usage and retry the command providing valid
// input.
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"
// *Cause: An attempt to read the tunable parameters from the ACFS
// driver failed. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
03093, 0, "no %s tunables for this platform"
// *Cause: Informational.
// *Action: None.
/ Message 03094 UNUSED and available
03095, 0, "tunable parameter %s not found"
// *Cause: The specified tunable parameter does not exist.
// *Action: Verify the correctness of the parameter name.
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"
// *Cause: An attempt to write to the tunable parameters file failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
03099, 0, "error updating driver tunables"
// *Cause: An attempt to update the kernel version of the tunable
// parameters failed. The accompanying messages provide
// detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
03100, 0, " %*.*soffset ----length | -dev --------offset"
03101, 0, " %*u %10u | %4d %14u"
03102, 0, " %*u %10u | <hole>"
03103, 0, " %*u %10u | %4d %14u <UNKNOWN TYPE %#x>"
03104, 0, " extent count: %d"
/Message 03105 UNUSED and available
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"
// *Cause: A request to add the indicated device and mountpoint to the
// Oracle Registry failed. The accompanying messages provide
// detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation. If another registration is using
// this device or mountpoint, remove the existing registration
// before retrying the operation.
03112, 0, "unable to remove mount point %s from Oracle Registry"
// *Cause: A request to delete the indicated device or mountpoint from the
// Oracle Registry failed. The accompanying messages provide
// detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
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, "Incorrect data format in file '%d'."
// *Cause: The file data was not in the expected format.
// *Action: Contact Oracle Support Services.
03120, 0, "Note: Reported snapshot space usage is inaccurate."
// *Cause: One or more nodes went offline, causing lost snapshot space updates.
// *Action: No action is required. This number is provided for informational
// purposes only. To correct the snapshot space usage,
// dismount the file system on all nodes and run fsck
// (Unix or Linux) or acfschkdsk.exe (Windows).
/ Obsolete 03121 is not used in 12.1.0.2 but it is used in 12.1.0.1
// 03121, 0, "FSCK-NEEDED was just set on the volume due to unexpected storage count."
// *Cause: The snapshot storage calculated was not expected.
// *Action: No action is required. To get a more accurate count,
// dismount the file system on all nodes and run fsck
// (Unix or Linux) or acfschkdsk.exe (Windows).
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.
03130, 0, "Resize request is greater than allowed maximum for ADVM volume."
// *Cause: An attempt to resize an ADVM volume failed because the size
// requested was larger than the maximum allowed ADVM volume size.
// *Action: Check the instance alert log for the maximum size of the
// ADVM volume and retry the resize operation,
// specifying a smaller volume size.
03131, 0, "volume %s already exists in the Oracle Registry as:"
03132, 0, "mount point %s already exists in the Oracle Registry as:"
// *Cause: The indicated mount point was in use in the Oracle Registry.
// *Action: If the new device is meant to replace an old device on this mount
// point, unmount the old device and then retry the command.
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 Cluster Ready Services"
// *Cause: An attempt to access the ACFS mount point failed because the mount
// point information could not be retrieved from CRS.
// *Action: Verify the mount point is registered with CRS using the
// 'acfsutil registry <device>' commands.
03136, 0, "unable to locate volume %s in Cluster Ready Services"
// *Cause: An attempt to access the ASM volume failed because the volume
// information could not be retrieved from CRS.
// *Action: Verify the volume is registered with CRS using the
// 'acfsutil registry <device>' commands.
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 path name is longer than system limit of %d characters"
// *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.
/Obsolete: 03159 is superceded by message 03634.
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"
// *Cause: An attempt to resize an ADVM volume failed because ASM did not have
// enough contiguous free diskgroup storage. This could have been a
// transient condition if ASM rebalance was running, otherwise the
// ASM alert logs may provide detailed failure indications.
// *Action: Check the ASM alert logs, address ASM issues if any, and retry
// the resize. If ASM rebalance is running it may release sufficient
// space by completion to allow a retry of the resize to succeed.
// Monitor V$ASM_DISK.FREE_MB view, if desired, to track free storage
// and retry the resize if sufficient storage becomes available.
// Otherwise, retry the resize after using ASM commands to increase
// the free space or retry, specifying a smaller quantity.
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 creation of a read/write snapshot was rejected because the
// ADVM disk group compatibility had not been upgraded to 11.2.0.3.0
// or higher, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03175, 0, " %u (delete in progress)"
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.
03179, 0, "unable to create snapshot '%s' while cluster is in rolling migration"
// *Cause: The cluster was in rolling migration. Snapshot creations are not
// allowed during rolling migration.
// *Action: Complete the rolling migration and then create the snapshot.
03180, 0, "Unable to obtain ASM volume device information for '%s'"
// *Cause: The operation for retrieval of ASM volume device information 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.
// NLS_DO_NOT_TRANSLATE [3081,3083]
03181, 0, " ----current offset | -cur vol offset -mir --extent %s-device name --------doffset --length -ASMdev"
// *Document: NO
03182, 0, " %12lu |%16lu %1u %8u %s %15lu %8lu %3u"
// *Document: NO
03183, 0, " ACFS file extent | ADVM volume"
// *Document: NO
03184, 0, " -------------------------------------------------------------------------------------------------%s"
// *Document: NO
03185, 0, "Unable to obtain ASM volume extent information for %s"
// *Cause: The operation for retrieval of ASM volume extent information 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.
03186, 0, "Supplied ACFS file offset value exceeded the maximum of the file and allocation sizes of %lu."
// *Cause: The supplied file offset value in bytes exceeded both the file size and allocation size.
// *Action: Specify a file offset within the actual or allocated size of the file.
// Use 'acfsutil info file filename' to see those values.
03187, 0, "Extent %d (mirror %d) is not in use."
// *Cause: Informational
// *Action: None
// NLS_DO_NOT_TRANSLATE [3090,3093]
03190, 0, "offset ----length | -dev --------offset"
// *Document: NO
03191, 0, "%*u %10u | %4d %14u"
// *Document: NO
03192, 0, "%*u %10u | <gap>"
// *Document: NO
03193, 0, "%*u %10u | %4d %14u <unknown type %#x>"
// *Document: NO
03194, 0, " extent count: %d"
// *Document: NO
03195, 0, " owner: %s"
// *Document: NO
03196, 0, " group: %s"
// *Document: NO
03197, 0, "unable to delete snapshot %s while it is configured for use by ACFS replication"
// *Cause: An attempt to delete a snapshot was rejected because it was
// configured for use by ACFS replication.
// *Action: To force deletion of the snapshot, re-try the command with the -R
// option.
03198, 0, "unable to delete snapshot %s as a component of ACFS replication"
// *Cause: An attempt to delete a snapshot was rejected because it was not
/ configured for use by ACFS replication.
// *Action: To delete the snapshot, re-try the command without the -R option.
03199, 0, "unable to convert snapshot %s because it is replication-specific"
// *Cause: An attempt was made to convert a replication-specific snapshot while
// replication was running.
// *Action: Terminate replication and retry the command.
03200, 0, "snapshot name: %s"
03201, 0, "RO snapshot or RW snapshot: %s"
03202, 0, "snapshot creation time: %s"
/Obsolete: 03203 is not used.
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'
03204, 0, "Snapshot '%s' is already read-only."
// *Cause: A request was made to convert a snapshot to be read-only but
// the snapshot was already read-only.
// *Action: None
03205, 0, "Snapshot '%s' is already read-write."
// *Cause: A request was made to convert a snapshot to be read-write but
// the snapshot was already read-write.
// *Action: None
03206, 0, "The ADVM compatibility attribute for the diskgroup was below the required version (%s) for the 'acfsutil snap convert' command."
// *Cause: The 'acfsutil snap convert' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03207, 0, "invalid combination of options"
// *Cause: The 'acfsutil snap convert' command was passed an invalid option
// combination which included both the -r and -w options.
// *Action: Remove either the -r or -w option from the 'acfsutil snap convert'
// command.
03208, 0, "The /r option is not supported on this operating system"
// *Cause: The 'acfsutil snap convert /r' option was specified. This
// functionality requires a minimum operating system version of
// Windows Server 2008 R2.
// *Action: Upgrade operating system to Windows Server 2008 R2 or use the
// 'acfsutil snap create' command to create a read-only snapshot.
03209, 0, "parent name: %s"
03210, 0, "%s %s %s"
03211, 0, "%-24s %s %s"
03212, 0, "There are too many snapshots for the file system associated with %s. Only %u are allowed. Reduce the number of snapshots before proceeding."
// *Cause: An attempt to create more than the maximum allowed number of active snapshots was rejected.
// *Action: Delete a snapshot before creating a new one.
03213, 0, "Creation of a snapshot failed due to presence of snapshots that prevent this functionality."
// *Cause: A snapshot creation which specified a parent snapshot was not
// processed because of compatibility issues with existing snapshots.
// Possible causes include:
// 1) Snapshots of the file system were found that were created before
// ADVM compatibility attribute was set to 12.1.
// 2) Snapshots of the file system were found that were created after
// ADVM compatibility was set to 12.1 but while 11.2 snapshots
// existed.
// *Action: Delete all snapshots associated with the file system and retry
// the command.
03214, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than 12.1."
// *Cause: The creation of a snapshot with a parent snapshot was rejected
// because the ADVM disk group compatibility had not been
// upgraded to version 12.1 or higher, which is required for that
// command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03215, 0, " compatible.advm: %u.%u.%u.%u.%u"
03216, 0, "The ADVM compatibility attribute for the diskgroup was below the required version (%s) for unlimited volume expansions."
// *Cause: A request to resize the ACFS file system failed because the
// volume expansion limit was reached. This limit was in effect
// because the ADVM compatibility attribute associated with the
// disk group had not been upgraded to the indicated version,
// which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03217, 0, "snapshot location: %s"
03218, 0, " Size Count Percent Total Size"
// *Document: NO
03219, 0, " %s %7d %8.2f %13d"
// *Document: NO
03220, 0, "Percentage of free space less than 128K: %.2f%%"
// *Document: NO
/Obsolete: 03221 is superceded by message 03635.
03221, 0, "File system size: %15u"
// *Document: NO
/Obsolete: 03222 is superceded by message 03636.
03222, 0, "Total free: %15u"
// *Document: NO
03223, 0, "File system disk usage by offset:"
// *Document: NO
03224, 0, "Free space allocation:"
// *Document: NO
03225, 0, " file entry table allocation: %u"
// *Document: NO
03226, 0, " accelerator volume: %s"
// *Document: NO
03227, 0, " state: %s"
// *Document: NO
03228, 0, "unable to retrieve metadata statistics for primary volume associated with mount point %s"
// *Cause: An internal ioctl operation to retrieve ACFS metadata
// statistics failed. This message is accompanied by other
// messages providing details on the error.
// *Action: Correct the problem identified by the other messages. If the
// cause is unclear, contact Oracle Support Services.
03229, 0, "unable to retrieve metadata statistics for accelerator volume associated with mount point %s"
// *Cause: An internal ioctl operation to retrieve ACFS metadata
// statistics failed. This message is accompanied by other
// messages providing details on the error.
// *Action: Correct the problem identified by the other messages. If the
// cause is unclear, contact Oracle Support Services.
03230, 0, " metadata read I/O count: %u"
// *Document: NO
03231, 0, " metadata write I/O count: %u"
// *Document: NO
03232, 0, " total metadata bytes read: %u %s"
// *Document: NO
03233, 0, " total metadata bytes written: %u %s"
// *Document: NO
03234, 0, " accelerator version: %u"
// *Document: NO
03235, 0, " allocation success since mount: %u %%"
// *Document: NO
03236, 0, " accelerator volume extent nodes: %d"
// *Document: NO
03237, 0, " primary volume extent nodes: %d"
// *Document: NO
03238, 0, "storage added to snapshot: %u %s\n"
// *Document: NO
03239, 0, "snapshot name: %s (delete in progress)"
// *Document: NO
03240, 0, "snapshot name: %s (delete waiting for last close)"
// *Document: NO
03241, 0, " %u (delete waiting for last close)"
// *Document: NO
03242, 0, " metadata block size: %u"
// *Document: NO
03243, 0, "failed to write Hang Manager entries to the kernel in-memory and persistent logs"
// *Cause: An internal ioctl operation to write Hang Manager data to
// the in-memory and persistent logs failed. This message is
// accompanied by other messages providing details on the error.
// *Action: Correct the problem identified by the other messages. If the
// cause is unclear, contact Oracle Support Services.
03244, 0, "The specified numeric value %s is outside the valid range."
// *Cause: The indicated numeric argument was rejected because it was too long
// to be converted to a 64-bit internal representation.
// *Action: Retry the command specifying a value between -2^63+1 and 2^63-1.
03245, 0, "offset ----length | -dev --------offset | shared"
// *Document: NO
03246, 0, "%*u %10u | %4d %14u | %s"
// *Document: NO
03247, 0, " owned extent count: %d"
// *Document: NO
03248, 0, " shared extent count: %d"
// *Document: NO
03249, 0, "offset ----length | -dev --------offset | inherited"
// *Document: NO
03250, 0, " added extent count: %d"
// *Document: NO
03251, 0, " inherited extent count: %d"
// *Document: NO
03252, 0, "quota: %u %s"
// *Document: NO
03253, 0, "quota usage: %u %s\n"
// *Document: NO
03254, 0, " granularity level: %d"
// *Document: NO
03255, 0, "accelerator volume not replaced"
// *Cause: An attempt to replace the accelerator volume failed. This message
// is accompanied by other messages providing details on the error.
// *Action: Correct the problems indicated by the other messages. If the cause
// of the problems is unclear, contact Oracle Support Services.
03256, 0, "primary volume has no accelerator volume to replace"
// *Cause: An attempt to replace the accelerator volume was rejected because the
// specified volume did not have an accelerator volume associated with
// it.
// *Action: Ensure that the primary volume has an associated accelerator volume
// before attempting replacement.
03257, 0, "the specified primary volume is an accelerator volume. Cannot proceed."
// *Cause: An attempt to replace an accelerator volume was rejected because the
// volume specified as the primary volume was not a primary volume.
// *Action: Ensure that the specified volume is a primary volume with an
// associated accelerator volume before attempting replacement.
03258, 0, "the specified replacement accelerator volume must be at least as large as the accelerator volume it is to replace."
// *Cause: An attempt to replace the accelerator volume was rejected because
// the specified replacement volume was smaller than the current
// accelerator volume.
// *Action: Retry the 'acfsutil accel replace' command specifying a volume at
// least as large as the volume to be replaced.
03259, 0, "primary volume: %s"
// *Document: NO
03260, 0, "old accelerator volume: %s"
// *Document: NO
03261, 0, "new accelerator volume: %s"
// *Document: NO
03262, 0, "Moving to new accelerator volume"
// *Document: NO
03263, 0, "Volume signature indicates that an accelerator operation is in progress."
// *Cause: An attempt to perform a filesystem check could not be completed
// because metadata showed that an accelerator operation was either in
// progress or incomplete on the specified volume.
// *Action: Ensure that an accelerator operation is not being run on another
// node or by another user before attempting to check this file
// system again. If an accelerator change operation had been started
// and then aborted, use 'fsck -f' to repair the volume. If
// the operation was interrupted, run it again with the same arguments.
03264, 0, "'acfsutil accel replace' failed due to a version mismatch. The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than %d.%d.%d.%d.%d."
// *Cause: An attempt to replace an accelerator volume was rejected because the
// ADVM disk group compatibility had not been upgraded to the release
// specified in the message or higher, which is required for the
// operation.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03265, 0, "'acfsutil accel replace' interrupted. Ensure primary volume is accessible then run 'acfsutil accel replace' with the same arguments again to complete the operation."
// *Cause: An event or condition interrupted the execution of the 'acfsutil
// accel replace' command. This message is accompanied by other
// messages providing details on the error.
// *Action: Address errors in the accompanying error messages and run
// 'acfsutil accel replace' with the same arguments on to render the
// primary volume mountable. The accelerator replace operation should
// then be complete.
03266, 0, "The specified new accelerator volume is already the accelerator volume that corresponds to the specified primary volume."
// *Cause: The specified new accelerator volume was the same as the accelerator
// volume it was to replace. This state may occur because another
// operation instructed 'acfsutil accel replace' be run again with the
// same arguments to recover from or complete a failed accelerator
// replacement. This message will also be seen as a result of
// accidentally rerunning the same command.
// *Action: The issued 'acfsutil accel replace' command should have finished an
// incomplete accelerator replace operation if one existed. Otherwise
// the file system should remain unchanged. No further action is
// necessary.
03267, 0, "Volume signature indicates that an accelerator operation is in progress."
// *Cause: An attempt to format a volume could not be completed because an
// accelerator operation was either in progress or incomplete on the
// specified volume.
// *Action: Ensure that an accelerator operation is not being run on another
// node or by another user. If an accelerator operation had been
// started and then aborted, use 'fsck.acfs -f' to repair the
// primary volume. If an accelerator operation was interrupted,
// reissue the command with the same arguments to complete it.
03268, 0, "Cannot use volume %s. It contains an existing ACFS file system or is being used as an accelerator."
// *Cause: An attempt to replace a file system's accelerator volume was
// rejected because the on-disk metadata of the indicated volume showed
// that a valid ACFS file system was located on the volume or that it
// was an existing accelerator.
// *Action: Reissue the request specifying a different volume not containing an
// existing file system or being used as an accelerator. To use the
// indicated volume, evidence of its prior use containing a file system
// or as an accelerator volume must first be removed.
03269, 0, " Accelerator volume moved: %(1)d%%"
03270, 0, "New accelerator volume sector size (%(1)u) must match existing accelerator volume sector size (%(2)u)."
// *Cause: An attempt to execute 'acfsutil accel replace' was rejected because
// the logical sector sizes of the existing and specified new
// accelerator volumes were different, as shown. The sector size of
// the accelerator volume must remain the same as the sector size of
// the associated primary volume.
// *Action: Select a device that has the same logical sector size as the
// existing accelerator volume and retry the operation.
03271, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the diskgroup was below the required version (%s) for the 'acfsutil snap quota' command."
// *Cause: The 'acfsutil snap quota' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03272, 0, "The specified primary volume %s does not appear to contain an ACFS file system."
// *Cause: An attempt to replace a primary volume's accelerator volume failed
// because the on-disk metadata of the indicated primary volume did not
// show that a valid ACFS file system was located on the volume.
// *Action: Reissue the request specifying a different primary volume containing
// an existing ACFS file system that has an accompanying accelerator
// volume.
03273, 0, "Volume signature indicates that an accelerator operation is in progress."
// *Cause: An attempt to mount a file system could not be completed because an
// accelerator operation was either in progress or incomplete on the
// specified volume.
// *Action: Ensure that an accelerator operation is not being run on another
// node or by another user before retrying the mount operation. If an
// accelerator operation had been started and then aborted, use
// 'fsck.acfs -f' to repair the primary volume. If an accelerator
// operation was interrupted, reissue the command with the same
// arguments to complete it.
03274, 0, "Snap quota can not be enabled for this snapshot."
// *Cause: The command 'acfsutil snap quota' was rejected because the snapshot
// was created from a file system whose compatibility level was less
// than 12.2.
// *Action: Use the 'acfsutil snap quota' to set quota for a snapshot created
// from a file system whose compatibility level is at least 12.2.0.0.0
03275, 0, "Updating CRS dependencies for resource '%s'."
// *Cause: Informational.
// *Action: None.
03276, 0, "CRS dependencies were updated successfully."
// *Cause: Informational.
// *Action: None.
03277, 0, "failed to update CRS resource"
// *Cause: An attempt to replace the accelerator failed because an
// error occurred while updating a resource. The accompanying messages
// from CRS provide detailed failure information.
// *Action: Examine the accompanying CRS error messages, address issues
// reported and retry.
03278, 0, "restarting replace operation"
// *Cause: The metadata of the supplied volumes indicated that a previous
// invocation of 'acfsutil accel replace' with the same arguments as
// this one was interrupted before completion. This invocation
// attempted to complete the replace operation.
// *Action: The issued 'acfsutil accel replace' command attempted to complete
// the specified accelerator replace operation. No further action is
// necessary if this message is not accompanied by failure messages.
03279, 0, "The file system on the specified primary volume %s is either in use or has been removed."
// *Cause: An attempt to replace a primary volume's accelerator volume failed
// because the on-disk metadata of the indicated primary volume showed
// that the file system was either in use or had been removed.
// *Action: Reissue the request specifying a different primary volume that
// contains a valid ACFS file system configured with an accompanying
// accelerator volume. Issue 'fsck' on the primary volume for more
// detail on its current state.
/
03280, 0, "failed to increase log size and change log level of in-memory log on all nodes"
// *Cause: An attempt to increase log size and change log level on all nodes
// of the cluster failed because an error occurred while sending the
// request to every node.
// *Action: Retry the operation. Alternatively, issue the following commands on
// each cluster node:
// 'acfsutil log -r 500M; acfsutil log -p ofs -l 5'
// run the workload that caused the problem
// wait for two or three minutes
// 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'
/
03281, 0, "failed to reset log size and log level of in-memory log on all nodes"
// *Cause: An attempt to reset log size and change log level on all nodes
// of the cluster failed because an error occurred while sending the
// request to every node.
// *Action: Retry the operation. Alternatively, issue the command on each
// cluster node:
// 'acfsutil log -r 10M; acfsutil log -p ofs -l 2'
/
03282, 0, "Blocking for %d seconds, reproduce problem now"
/
03283, 0, "invalid combination of -o and -f options"
// *Cause: The 'acfsutil log' command was issued with both the -f and -o
// options. This is a conflict, because the log file names are
// pre-specified for -o and may not be specified using -f.
// *Action: Re-issue the 'acfsutil log' command with only the desired option.
// With -o, the log files will be generated in the persistent log
// directory in the form yymmddhhmmss.log. With -f the specified
// name will be used.
03284, 0, "invalid combination of -o and -n, -T, -c, -s, -q options"
// *Cause: The 'acfsutil log -o' command is incompatible with other options
// included in the commmand line. The -o option can not be combined
// with the -n, -T, -c, -s, or -q options.
// *Action: Re-issue the 'acfsutil log' command with only the desired option.
// With -o, only log file size, log level and product name may be
// specified.
03285, 0, "Dumping log on all nodes"
03286, 0, "failed to find volume resource for device %s"
// *Cause: An attempt to replace an accelerator volume with the command
// 'acfsutil accel replace' failed because the volume
// resource for the indicated device was not found.
// *Action: List the CRS resources to verify that the volume resource for the
// indicated device exists and is online and retry.
03287, 0, "unable to find old accelerator volume resource name"
// *Cause: An attempt to replace an accelerator volume with the command
// 'acfsutil accel replace' failed because the old accelerator
// resource could not be found because the file system resource
// dependencies were not correct.
// *Action: Examine the file system resource attributes, ensure that the
// primary and accelerator resources are correct and retry.
03288, 0, "CRS dependencies already had the requested values."
// *Cause: A request to update the dependencies for a file system resource was
// ignored because the dependencies already had the requested values.
// *Action: No action necessary.
/
03289, 0, "snapshot link: %s"
// *Document: NO
03290, 0, "The Oracle ADVM compatibility level for the disk group is less than the required version 18.0.0.0.0 for snap link."
// *Cause: The 'acfsutil snap link' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade
// the disk group compatibility (COMPATIBLE.ADVM attribute) to the
// specified version and then re-issue the original 'acfsutil
// snap link' command. If the disk group compatibility cannot be
// upgraded, update the ACFS compatibility level using the
// 'acfsutil compat set' command and then re-issue the original
// 'acfsutil snap link' command.
03291, 0, "Only one snaphshot link can be created for this snapshot."
// *Cause: The command 'acfsutil snap link' was rejected because the snapshot
// already had a snapshot link.
// *Action: Use the 'acfsutil snap info' command to see the existing snapshot
// link for this snapshot. Before creating a new snapshot link, use
// the 'acfsutil snap link -d' command to delete the existing link
// for the snapshot.
03292, 0, " create time: %s"
// *Document: NO
03293, 0, "file entry table allocation: %u %s"
// *Document: NO
03294, 0, "Insufficient privileges to perform command. Resource Administrator access is required."
// *Cause: An attempt to execute an acfsutil command was rejected because the
// caller did not have sufficient privileges.
// *Action: Retry the command while logged in as a user with
// resource ACL access.
03295, 0, "Invalid freeze or thaw command."
// *Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected
// because an invalid option was specified. The 'acfsutil thaw'
// command does not accept any options. The 'acfsutil freeze' command
// accepts the '-f' option only.
// *Action: Retry the command, specifying only valid options.
03296, 0, "cannot freeze or thaw file system %s because the Grid Infrastructure has not been upgraded to %s"
// *Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected
// because the Grid Infrastructure had not been upgraded to the
// indicated version.
// *Action: Ensure that the Grid Infrastructure has completed an upgrade to the
// indicated version or higher and then re-issue the command.
03297, 0, "unable to freeze file system %s"
// *Cause: The file system could not be frozen. The accompanying messages
// provide detailed failure information.
// *Action: Read the accompanying messages, correct the issues identified there,
// and then retry the operation.
03298, 0, "unable to thaw file system %s"
// *Cause: The file system could not be thawed from a frozen state. The
// accompanying messages provide detailed failure information.
// *Action: Read the accompanying messages, correct the issues identified there,
// and then retry the operation.
03299, 0, "cannot freeze or thaw file system %s because the cluster is in rolling migration"
// *Cause: An 'acfsutil freeze' or 'acfsutil thaw' command was rejected
// because the cluster was in rolling migration. Freezing or
// thawing a file system during rolling migration was not
// supported.
// *Action: Complete the rolling migration and then retry the command.
/
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 acfsutil command was rejected because the ADVM disk group
// compatibility had not been upgraded to 11.2.0.2.0 or higher,
// which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
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 obsolete - see 3342
03311, 0, " average rate of change since mount: %u KB/s"
// *Document: NO
/ 03312 obsolete - see 3343
03312, 0, " amount of change: %.2f MB rate of change: %u KB/s"
// *Document: NO
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 'acfsutil tag' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03322, 0, "The ADVM compatibility attribute for the diskgroup is below the required version (%s) for the 'acfsutil repl' commands."
// *Cause: The 'acfsutil repl' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
03323, 0, "%(1)sc option requires the %(2)st option"
// *Cause: The 'c' option was specified without the 't' option.
// The 'c' option invokes case insensitive substring
// matching on the tag names specified using the 't' option.
// *Action: To use the 'c' option, add the 't' option to specify a tag.
03324, 0, "Unable to obtain metric data for %s"
// *Cause: An internal ioctl operation to access metric data from ACFS
// file system 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.

03325, 0, " Since mount:"
// *Document: NO
03326, 0, " reads: %lu"
// *Document: NO
03327, 0, " writes: %lu"
// *Document: NO
03328, 0, " read cache hits: %lu"
// *Document: NO
03329, 0, " minimum read size: %u"
// *Document: NO
03330, 0, " minimum write size: %u"
// *Document: NO
03331, 0, " maximum read size: %u"
// *Document: NO
03332, 0, " maximum write size: %u"
// *Document: NO
03333, 0, " During interval:"
// *Document: NO
03336, 0, " bytes read: %lu"
// *Document: NO
03337, 0, " bytes written: %lu"
// *Document: NO
03338, 0, " average reads per second: %.2f"
// *Document: NO
03339, 0, " average writes per second: %.2f"
// *Document: NO
03340, 0, " average bytes read per second: %.2f"
// *Document: NO
03341, 0, " average bytes written per second: %.2f"
// *Document: NO
03342, 0, " average rate of change since mount: %.2f KB/s"
// *Document: NO
03343, 0, " amount of change: %.2f MB rate of change: %.2f KB/s"
// *Document: NO
03344, 0, "Error, %ss option with repetition interval applied to multiple file systems."
// *Cause: A request to report file system statistics periodically was
// rejected because it applied to multiple file systems. A single
// file system must be specified explicitly when supplying the 's'
// option with a time interval.
// *Action: Reissue the request specifying a single file system or omitting
// the repetition interval.
03345, 0, "cannot reduce accelerator volume size below 256MB"
// *Cause: A size request specified an accelerator volume size less than the
// minimum allowed.
// *Action: Specify an accelerator volume size of 256MB or more.
03346, 0, "unable to grow the accelerator volume in support of a request to grow the primary volume"
// *Cause: A size request required growth of the accelerator volume, which
// failed. This message is accompanied by other messages providing
// details on the error.
// *Action: Correct the problem identified by the other messages. If the
// cause is unclear, contact Oracle Support Services.
03347, 0, "Error, %ss option with repetition interval applied to multiple file systems (%s)."
// *Cause: A request to report file system statistics periodically was
// rejected because it applied to multiple file systems. A single
// file system must be specified explicitly when supplying the 's'
// option with a time interval.
// *Action: Reissue the request specifying a single file system or omitting
// the repetition interval.
03348, 0, "cannot display file system statistics and individual items at the same time"
// *Cause: An attempt to display file system statistics was rejected
// because one or more of the -s or -d options were specified
// with the -o option. The display of statistics and the
// display of individual items are mutually exclusive.
// *Action: Retry the command specifying either the -o option for
// individual items or the -s or -s and -d for statistics.
03349, 0, "cannot display detailed file system statistics without specifying the statistics option"
// *Cause: An attempt to display file system statistics was rejected
// because the -d option was specified without the -s option.
// The detail option -d augments the -s option and cannot be
// used alone.
// *Action: Retry the command with both -s and -d options.
03350, 0, "cannot display file system statistics and fragmentation at the same time"
// *Cause: An attempt to display file system statistics was rejected
// because the -s option was specified with the -f option.
// The display of statistics and the display of fragmentation
// are mutually exclusive.
// *Action: Retry the command specifying either the -s option for statistics
// or the -f option for fragmentation.
03351, 0, "cannot display file system fragmentation and individual items at the same time"
// *Cause: An attempt to display file system fragmentation was rejected
// because the -f option was specified with the -o option.
// The display of fragmentation and the display of individual
// items are mutually exclusive.
// *Action: Retry the command specifying either the -f option for
// fragmentation or the -o option for individual items.
03352, 0, "cannot display file system fragmentation without specifying the fragmentation option"
// *Cause: An attempt to display file system fragmentation was rejected
// because the -v option was specified without the -f option.
// The verbose option -v augments the -f option and cannot be
// used alone.
// *Action: Retry the command with both -f and -v options.
03353, 0, "invalid count value supplied"
// *Cause: An attempt to display file system statistics was rejected
// because a zero or negative integer was provided for the count
// argument.
// *Action: Retry the command with a positive integer for the
// statistics count.
03354, 0, "local statistics dump failed"
// *Cause: An attempt to save ACFS file system statistics failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation. If the resolution is not
// clear or the problem persists, contact Oracle Support Services.
03355, 0, "state dump failed"
// *Cause: An attempt to save ACFS binary log data failed.
// The accompanying messages provide detailed failure information.
// *Action: The Oracle Kernel Services (OKS) persistent log provides more
// detailed failure information. Resolve the indicated problems,
// and then retry the operation. If the resolution is not clear or
// the problem persists, contact Oracle Support Services.
03356, 0, "Resize request would cause %.4f TB of data to be moved."
// *Document: NO
03400, 0, "Invalid repl toggle command."
// *Cause: The command was rejected because an invalid sub-command was
// specified.
// *Action: Review the command usage and retry the command providing valid
// input.
03401, 0, "primary replication is %s"
// *Document: NO
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.
03452, 0, "failed to move file or directory from %s to %s"
// *Cause: An attempt to rename a file or directory failed because the target
// was an existing, populated directory or the user permissions were
// insufficient to perform the operation.
// *Action: Retry the operation after removing the target files or correcting
// the permissions.

/ 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 Oracle Kernel Services
// (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 is obsolete - see 3543
03513, 0, "The OKS persistent log configuration settings cannot be queried."
// *Cause: The Oracle Kernel Services (OKS) persistent log was not running.
// *Action: Start the log with 'acfsutil plogconfig -d <gridhome>'.
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"
03528, 0, "failed to determine Oracle Base"
// *Cause: The operation to retrieve the Oracle Base location 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.
/ obsolete, never shipped with a product.
03529, 0, "Warning: The 'd' option was specified with an argument, which is no longer used - argument ignored."
// *Cause: 'acfsutil plogconfig' now gets the log location internally.
// The specified log location was ignored and the command
// continued using the internally derived location.
// *Action: None.
03530, 0, "The 'terminate' option may not be used with any other options."
// *Cause: Conflicting options were specified on the command line.
// *Action: Do not use any other options with the 'terminate' option.
03531, 0, "Snapshot link %s does not exist."
// *Cause: An attempt to execute the acfsutil snap link command failed because
// no snapshot link could be found with the indicated name.
// *Action: Retry the acfsutil snap link command with the correct name.
03532, 0, "The specified string %s is not a valid snapshot link name."
// *Cause: The acfsutil snap link command failed because the indicated name was
// not a valid snapshot link name. Possible reasons include:
// 1) The snapshot link name exceeded the limit of 255 characters.
// 2) The snapshot link name equaled "." or "..".
// 3) The snapshot link name contained "/" (Unix or Linux).
// 4) The snapshot link name contained "\" or ":" (Windows).
// 5) The snapshot link name contained an illegal character for
// NTFS file names (Windows).
// *Action: Retry the acfsutil snap link command specifying a valid snapshot
// link name.
03533, 0, "compression operation failed because the cluster is in rolling migration"
// *Cause: An 'acfsutil compress' command was rejected because the
// cluster was in rolling migration. Compressing files during
// rolling migration was not supported.
// *Action: Complete the rolling migration and then retry the command.
03534, 0, "cannot read from file: %s"
// *Cause: Execution of a requested application failed because it
// encountered an error in attempting to read from the indicated file.
// Additional messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
/ Message 03535-03538 UNUSED and available
03539, 0, "Base time stamp not found in log file."
// *Cause: Informational. The likely cause is that the running Oracle Kernel
// Services (OKS) driver is an older version that does not support
// time stamp conversion.
// *Action: None.
03540, 0, "The specified interval is greater than %d seconds."
// *Cause: An invalid interval value was entered on the command line.
// *Action: Enter an interval value equal to or less than the maximum.
03541, 0, "The symbolic link '%s' to '%s' cannot be created."
// *Cause: An attempt to start Oracle Kernel Services persistent logging was
// not completely successful. Logging was started, but the indicated
// symbolic link could not be created. Most likely the link name was
// non-empty directory.
// *Action: If a symbolic link is desired, delete the link target and
// its contents and reissue the command.
03542, 0, "The specified OKS log directory '%s' is invalid because it is NFS mounted."
// *Cause: The indicated logging directory was NFS mounted.
// *Action: Enter a node local location for the Oracle Kernel Services (OKS)
// log.
03543, 0, "The OKS persistent log is not active."
// *Cause: The Oracle Kernel Services (OKS) persistent log was not running.
// *Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
03544, 0, "Directory '%s' exists as a file."
// *Cause: An Oracle Kernel Services (OKS) persistent log directory could not
// be created because it exists as a file.
// *Action: Either delete the file or choose another directory name.
03545, 0, "The input text is longer than the maximum of %d bytes."
// *Cause: The command failed because input text was too long.
// *Action: Retry the command using a text string shorter than the indicated
// maximum size.
03546, 0, "failed to update the debug levels for the specified binary log"
// *Cause: The 'acfsutil blog' command encountered an error while attempting
// to update the binary log debug levels.
// *Action: Check the Oracle Kernel Services (OKS) log for details, correct
// the error, and retry command.

/ ACFS Plug-in
03600, 0, "Plug-in is enabled on '%s'"
//*Document: NO
03601, 0, "Plug-in is disabled on '%s'"
//*Document: NO
03602, 0, "Plug-in is already enabled on '%s'"
// *Cause: An attempt was made to enable the plug-in when it is already enabled.
// *Action: First disable the plug-in then retry the command.
03603, 0, "Plug-in is not enabled on '%s'"
// *Cause: A plug-in command was attempt when the plug-in is not enabled.
// *Action: Enable the plug-in and then retry the command.
03604, 0, "Unable to perform plug-in operation on '%s'"
// *Cause: The plug-in operation 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.
03605, 0, "Plug-in status: %s"
//*Document: NO
03606, 0, "Metric type: %s%d"
//*Document: NO
03607, 0, "Enabled tags: %s"
//*Document: NO
03608, 0, "Delivery method: %s"
//*Document: NO
03609, 0, "Post interval (seconds): %d"
//*Document: NO
03610, 0, "Invalid plug-in metric type: %s"
// *Cause: An invalid plug-in metric type was specified.
// *Action: Enter a valid metric type from the following list:
// acfsmetric1, acfsmetric2
03611, 0, "Invalid interval specified."
// *Cause: An invalid interval was specified.
// *Action: Enter a valid interval between 1 and 3600 seconds.
03612, 0, "Unable to retrieve list of plug-in enabled tags."
// *Cause: ACFS was unable to retrieve the list of tags for which the plug-in is
// collecting metrics. 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.
03613, 0, "Unable to write plug-in config file."
// *Cause: ACFS was unable to write the plug-in config file to disk.
// *Action: Try the command again. If the problem persists, contact
// Oracle Support Services.
03614, 0, "Plug-in cannot be enabled for more than %d tags."
// *Cause: An attempt was made to enable the plug-in for more than the
// maximum allowed number of tags.
// *Action: Enable plug-in with fewer tags.
03615, 0, "An error occured when copying the list of tags."
// *Cause: This is an internal error.
// *Action: Try the command again. If the problem persists, contact
// Oracle Support Services.
03616, 0, "Kernel:"
//*Document: No
03617, 0, "Commands:"
//*Document: No
03618, 0, " Build version: %s"
//*Document: No
03619, 0, " Build hash: %d"
//*Document: No
03620, 0, " Bug numbers: %s"
//*Document: No
03621, 0, "missing plug-in metric type"
// *Cause: No plug-in metric type was specified.
// *Action: Enter a valid metric type from the following list: "acfsmetric1"
/
03622, 0, "successfully modified ACFS registration for '%s'"
//*Document: No
03623, 0, "unable to modify the ACFS registration for mount point '%s'"
// *Cause: Could not modify the ACFS registration for the specified mount point.
// *Action: Examine the accompanying error messages and respond accordingly. If
// the solution is not clear, contact Oracle Support Services.
03624, 0, "unable to modify registration for ACFS volume '%s'"
// *Cause: Could not modify the ACFS registration for the ACFS volume.
// *Action: Examine the accompanying error messages and respond accordingly. If
// the solution is not clear, contact Oracle Support Services.
/
03625, 0, "Metric types: %s"
// *Document: NO

03626, 0, "invalid combination of -C and -f options"
// *Cause: The 'acfsutil log' command was issued with both the -f and -C
// options. This is a conflict, because the log file names are
// pre-specified for -C and may not be specified using -f.
// *Action: Re-issue the 'acfsutil log' command with only the desired option.
// With -C, the log files will be generated in the persistent log
// directory in the form yymmddhhmmss.log. With -f the specified
// name will be used.
/
03627, 0, "logging behavior change specified with cluster option"
// *Cause: The 'acfsutil log' command was issued with both the -C option and
// and an option that modifies the logging behavior.
// *Action: Re-issue the 'acfsutil log' command without the -C option to modify
// the ACFS logging behavior. To create logs on all cluster nodes,
// issue 'acfsutil log -C' with no other options.
03628, 0, " total size: %u %s"
03629, 0, " total free: %u %s"
03630, 0, " size: %u %s"
03631, 0, " free: %u %s"
03632, 0, " size: %u %s"
03633, 0, " allocated: %u %s"
03634, 0, " snapshot space usage: %u %s"
03635, 0, "File system size: %15u %s"
03636, 0, "Total free: %15u %s"
/
03637, 0, "corruption detected in log file '%s'"
// *Cause: The 'acfsutil logconvert' command detected a corrupted log entry.
// *Action: Examine the log file manually and, if a single line is corrupted,
// remove that line and re-issue the command. For systemic corruption,
// log file recovery may not be possible.
03638, 0, " logical sector size: %u"
03639, 0, " auto-resize increment: %u %s"
03640, 0, " auto-resize maximum: %u %s"
03641, 0, "auto-resize increment below minimum %uG"
// *Cause: An attempt to update auto-resize settings specified an auto-resize
// increment less than the minimum allowed.
// *Action: Retry the command using a bigger auto-resize increment.
03642, 0, "successfully updated auto-resize settings"
03643, 0, "failed to update auto-resize settings"
// *Cause: The ACFS driver was unable to update the auto-resize settings.
// *Action: Ensure that your compatible.advm setting allows auto-resize and
// then re-issue the command.
03644, 0, "No auto-resize increment is currently configured."
// *Cause: An attempt was made to set an auto-resize maximum when no auto-resize
// increment was set.
// *Action: Specify an auto-resize increment when specifying a maximum.
03645, 0, "File system of size %.1f %s requires an accelerator volume of size %.1f %s for best performance, which is larger than the current accelerator volume size %.1f %s."
// *Cause: The file system was resized such that the accelerator volume size
// was then below the minimum size recommended for best performance.
// *Action: Run 'acfsutil size' to shrink the file system to the recommended size, or to increase the accelerator volume size to the recommended size.

03646, 0, " Input device name: %s"
03647, 0, " Log file name: %s"
03648, 0, " Reading configuration information from device %s ..."
03649, 0, " Copying first %d megabytes from device %s ..."
03650, 0, " Continue scanning metadata on device %s ..."
03651, 0, " Scanning: number of gigabytes scanned on device %s ... %d ..."
03652, 0, " End of general metadata scan on device %s ..."
03653, 0, " Copying %s bit map from device %s ..."
03654, 0, "\nacfsutil meta summary:"
03655, 0, "Too many read failures on device %s. Exiting."
// *Cause: An attempt to retrieve the metadata from the indicated device
// was terminated because there were too many read errors. The
// accompanying error messages provide additional failure details.
// *Action: Attempt to correct the issues indicated by the accompanying
// messages and retry. If unable to make progress, contact
// Oracle Support Services.

03656, 0, "invalid compression unit size: %d bytes\n Valid compression unit sizes are %s bytes."
// *Cause: An invalid value for compression unit size was provided.
// *Action: Specify a valid value for compression unit size with the
// -c option and retry.
03657, 0, "Directory %s is not on an ACFS Volume."
// *Cause: The specified output directory was not located on an ACFS Volume.
// *Action: Specify an output directory on an ACFS Volume and retry.
03658, 0, "Too many file names were specified."
// *Cause: There were too many file names for the the options being used.
// *Action: Consult the command inline help or the product documentation for command
// argument details.
03659, 0, "No files to copy were specified."
// *Cause: There were no file names to copy specified.
// *Action: Consult the command inline help or the product documentation for command
// argument details.
03660, 0, "Compression is not enabled on the volume containing directory %s."
// *Cause: The target ACFS volume did not have compression enabled.
// *Action: Enable compression on the volume and retry, or use the -u option.
03661, 0, "changing compression unit size from %s to %s bytes when copying file %s"
03662, 0, "partial write during copy of file %s"
// *Cause: A write to the volume during file copy failed.
// This message is accompanied by other messages providing details
// on the error.
// *Action: Correct the problem indicated by the other messages. If the
// cause of the problem is unclear, contact Oracle Support Services.
03663, 0, "File %s is compressed with compression unit size %d bytes."
03664, 0, "File %s has type %d."
03665, 0, "obtained block size %d from file %s that can be used for compression unit size"
03666, 0, "did not obtain block size from file %s that can be used for compression unit size"
03667, 0, "File %s is a recognized type of file."
03668, 0, "compressing file %s with compression unit size %d bytes"
03669, 0, "not compressing file %s"
03670, 0, "File %s will have type %d."
03671, 0, "failed to set compression information for file %s"
// *Cause: An internal ioctl operation to set compression information for a
// file failed. This message is accompanied by other messages
// providing details on the error.
// *Action: Correct the problem indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
03672, 0, "copying file %s to file %s"
03673, 0, "files successfully copied: %d\n"
03674, 0, "Pathname %s is not a directory."
// *Cause: The pathname following the -r option was not a directory.
// *Action: Specify a directory for a recursive copy and retry.
03675, 0, "File %s is not a recognized type of file."
//*Document: No
03676, 0, "Pathname %s is not a directory or a regular file."
// *Cause: The pathname provided was not a directory or a regular file.
// *Action: Retry the command using only directory or file names on the
// command line.
03677, 0, "no output directory specified"
// *Cause: No output directory was found in the command line.
// *Action: Provide the name of an existing directory and retry.
03678, 0, "too many directories specified"
// *Cause: The parameters provided contain more directories than expected
// for the options used.
// *Action: Consult the command inline help or the product documentation
// for command argument details.
03679, 0, "File %s is a file type that cannot be compressed."
// *Cause: The file specified with the -c option was a type of file that
// cannot be compressed.
// *Action: Retry the command without the -c option.
03680, 0, "File system path %s already exists. Compress copy of file %s will not execute."
// *Cause: An attempt to execute the acfsutil compress copy command failed
// because the indicated destination path name already existed and
// the forced overwrite option was not specified.
// *Action: To overwrite an existing file, specify the -f option.
// Otherwise, specify a file system path that does not exist.
03681, 0, "No files were copied.\n"
// *Cause: An attempt to execute the acfsutil compress copy command failed
// because no files could be copied. This message is accompanied
// by other messages providing detailed failure information.
// *Action: Correct the problems indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
03682, 0, "File system path %s is not a regular file."
// *Cause: The specified path name was not a regular file.
// *Action: Specify the path of a regular file to copy.
03683, 0, "File system path %s is not a directory."
// *Cause: The last path name specified was not a directory.
// *Action: Specify a file system directory for the last command line argument.
03684, 0 ,"File %s with internal block size %s bytes is being compressed with compression unit size %s bytes. It will not be usable by the RDBMS."
// *Cause: The file was copied with a compression unit size that prevents the
// database from using it.
// *Action: If the copy is intended to be used by the database, it must be
// compressed with a compression unit size equal to the internal
// block size. In this case, use the -c option with a value equal
// to the internal block size and retry the command.
03685, 0, "File system path %s cannot be converted to an absolute path."
// *Cause: A path 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 path name in the form of an absolute path.
// On Windows, the absolute path includes the drive letter.
03686, 0, " Output file name: %s"
03687, 0, "File %s is a type of file that will be created with a compression unit size of %s bytes instead of %s bytes."
03688, 0, "File %s is a type of file that will be created with a compression unit size of %s bytes."
03689, 0, " Input accelerator device name: %s"
03690, 0, " Output accelerator file name: %s"
03691, 0, "successful update of mount point '%s' to ACFS compatibility level with %d.%d.%d.%d.%d%s release stream"
// *Cause: Informational.
// *Action: None.
03692, 0, "Failed to update ACFS compatibility level for mount point '%s'. The active ACFS compatibility level (%d.%d.%d.%d.%d%s) is a higher release than the requested release."
// *Cause: The internal ioctl operation to set ACFS compatibility level for a
// mounted file system failed because the active ACFS compatibility
// level is higher than the requested release stream.
// *Action: Select a supported release stream that is higher than the active
// ACFS compatibility level and retry the 'acfsutil compat set'
// command.
03693, 0, "failed to get ACFS compatibility level for mount point '%s'"
// *Cause: An internal ioctl operation to get the ACFS compatibility level for
// a mounted file system failed. This message is accompanied by
// other messages providing details on the error.
// *Action: Correct the problem indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
03694, 0, " ACFS compatibility: %u.%u.%u.%u.%u%s"
03695, 0, "Invalid release supplied. Requested version of %d.%d.%d.%d.%d exceeds the active version of the cluster (%d.%d.%d.%d.%d)."
// *Cause: The release supplied was higher than the active version of
// the cluster.
// *Action: If the cluster is in the proces of a rolling upgrade, verify the
// target version of the upgrade and wait until the upgrade has
// completed to retry the command. If the cluster is not in the
// process of a rolling upgrade, the supplied release will not be
// supported until the cluster has been upgraded to a sufficient
// release.
03696, 0, "Invalid release supplied."
// *Cause: The supplied release was invalid.
// *Action: Verify that the supplied release follows the Oracle version
// syntax (For example, 12.2.0.0.0) and retry the command.
03697, 0, "The ACFS compatibility level must be set to %d.%d.%d.%d.%d or higher to proceed."
// *Cause: The specified ACFS compatibility level was too low to support the
// supplied list of options.
// *Action: Retry the mkfs command with a release passed to the -c
// option that is equal to or exceeds the required version displayed
// in the message.
03698, 0, "Warning: requested ACFS compatibility level exceeds the compatible.advm setting %d.%d.%d.%d.%d"
03699, 0, "Warning: proceeding with ACFS compatibility level upgrade to a version that exceeds the current compatible.advm setting"
03700, 0, "failed to set ACFS compatibility level for mount point '%s'"
// *Cause: An internal ioctl operation to set ACFS compatibility level for a
// mounted file system failed. This message is accompanied by
// other messages providing details on the error.
// *Action: Correct the problem indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
/03701-03750: acfsutil usage messages. Note to translators: Please do not
/ translate keywords in these messages. The keyword is the first
/ term on the left:
/ keyword - <Description>
03701, 0, "The following commands are supported:"
03702, 0, " accel - Manage accelerators"
03703, 0, " audit - Manage Auditing"
03704, 0, " blog - Manage Binary Logs"
03705, 0, " compat - Manage compatibility levels"
03706, 0, " defrag - Defragment a file system"
03707, 0, " detach - Unregister ACFS as a file system type"
03708, 0, " dumpstate - Dump file system state for diagnosis"
03709, 0, " encr - Manage Encryption"
03710, 0, " info - Display file system information"
03711, 0, " log - Manage Kernel Logs"
03712, 0, " meta - Collect file system metadata"
03713, 0, " plugin - Manage plugins"
03714, 0, " registry - Add, delete, or display mount registry entries"
03715, 0, " repl - Manage Replication"
03716, 0, " rmfs - Remove a file system"
03717, 0, " sec - Manage security"
03718, 0, " size - Resize a file system"
03719, 0, " scrub - Check mirror consistency"
03720, 0, " snap - Manage Snapshots"
03721, 0, " tag - Manage Tags"
03722, 0, " tune - Modify or display tunable parameters"
03723, 0, " version - Display version information"
03724, 0, "For more information, run: acfsutil %sh <command>"
03725, 0, "Version %s"
/03726-03728 for acfsutil size
03726, 0, "Resizing file system in steps"
03727, 0, "Resizing file system to %.4f TB"
03728, 0, "Resizing ADVM volume to %.4f TB"

03729, 0, " compress - Manage compression"
03730, 0, " mount sequence number: %u"

03731, 0, "The Oracle ADVM compatibility level for the disk group is less than the required version 12.2 for auto-resize."
// *Cause: An attempt to enable auto-resize was rejected because the ADVM
// disk group compatibility level had not been upgraded to the
// indicated version, which is required for that command.
// *Action: Ensure that the compatible.advm setting is at least 12.2.0.0.0 and
// then re-issue the command.
03732, 0, "Skipping invalid or non-numeric -o entry %s."
// *Cause: An attempt to copy an item from the additional offset list (-o)
// encountered the indicated non-numeric or invalid entry. The
// indicated invalid entry was skipped.
// *Action: If the invalid entry was required, re-issue the command with the
// correct value. Otherwise no further action is required.
03733, 0, "Too many -o arguments. Ignoring entries beyond %d."
// *Cause: The command 'acfsutil meta' was not executed for all offset list
// (-o) entries because the number of -o entries exceeded the
// indicated limit. Entries beyond that limit were ignored.
// *Action: If the additional entries are required, re-issue the command,
// specifying a different output file along with the -o arguments that
// were previously ignored. Otherwise no further action is required.
03734, 0, " freeze - Suspend file system updates"
03735, 0, " thaw - Resume file system updates"
03736, 0, " remote - Manage ACFS remote files"
03737, 0, " lockstats - Print lock contention statistics"
/03738-03750 reserved for acfsutil usage
03751, 0, "Unable to modify the set of nodes where this ACFS file system is running."
// *Cause: An attempt to modify the set of nodes where this ACFS file system
// was running was rejected because that operation was not supported
// by the command 'acfsutil registry'.
// *Action: Delete and re-add the ACFS file system using the command 'acfsutil
// registry'. Use the node option to specify the nodes on which this
// file system should run.
03752, 0, "\nDiskgroup: %s (%d%s free)"
03753, 0, " total disk space: %s"
03754, 0, " total free space: %s"
03755, 0, " usable after reservation: %s"
03756, 0, " redundancy type: %s"
03760, 0, "\n Total space used by ASM non-volume files:"
03761, 0, " used: %s"
03762, 0, " mirror used: %s"
03763, 0, "\n volume: %s"
03764, 0, " total: %s"
03765, 0, " free: %s"
03766, 0, " redundancy type: %s"
03767, 0, " file system: %s %s"
03768, 0, " auto-resize increment: %s"
03769, 0, " auto-resize maximum: %s"
03770, 0, "\nDiskgroup: %s (Not Available)"
03771, 0, " snapshot: %s (%s)"
03772, 0, " quota limit: %s"
/ Note to translators: 03773 is a column header with fixed spacing in the
/ rows beneath. Please preserve alignment.
03773, 0, "Diskgroup Consumer Space Size With Mirroring Usable Free %sFree Path"
03774, 0, " net free with mirroring: %s"
03775, 0, " ASM file space: %s"
03776, 0, " used: %s"
03777, 0, "no connection to Oracle ASM"
// *Cause: A requested operation that required services from Oracle
// Automatic Storage Management (ASM) failed because it could not
// connect to an ASM instance.
// *Action: Start an Oracle ASM instance and retry the command. If the
// problem persists, contact Oracle Support Services.
/
03778, 0, "unable to perform remote operation '%(1)s' for file %(2)s"
// *Cause: An attempt to issue the indicated remote command on the indicated
// file failed. The Oracle Kernel Services (OKS) persistent log
// provides more detailed failure information.
// *Action: Examine the messages in the OKS persistent log, resolve the
// indicated problems, and retry the operation.
/
03779, 0, "Expand: %(1)s"
//*Document: No
/
03780, 0, "'acfsutil meta' metadata file had an unknown file format:\n %(1)s expected\n %(2)s found"
// *Cause: An attempt to expand an ACFS metadata file was rejected because the
// metadata file had an unknown format, possibly because it was not
// created by the command 'acfsutil meta', or it was created by an
// incompatible version of that command.
// *Action: Retry the operation, specifying a valid 'acfsutil meta' file.
/
03781, 0, "unit of measurement: %s"
//*Document: No
/ Note to translators: 03782 is a column header with fixed spacing in the
/ rows beneath. Please preserve alignment.
03782, 0, " Consumer Space Size With Mirroring Usable Free %sFree Path"
03783, 0, "unable to determine the cluster type"
// *Cause: An 'acfsutil' command failed to determine the type of cluster
// that contained the local server. The accompanying messages
// provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and retry the operation.
3784, 0, "Minimum scan size is %dMB."
// *Cause: An attempt to perform a limited file system scan was rejected
// because the scan size was smaller than the indicated minimum.
// *Action: Retry the command using a valid scan size.

3785, 0, "| Lock Type | Acquires | Max Wait | Total Wait |"
3786, 0, "+-------------------------------------+--------------+------------+------------+"
3787, 0, "| %-35s | %12d | %10d | %10d |"
3788, 0, "| Acquires | Converts | Max Wait | Total Wait | [LK ID 1][LK ID 2] |"
3789, 0, "+--------------+--------------+------------+------------+----------------------+"
3790, 0, "| %12u | %12u | %10u | %10u | [%-19s]--[%-14s | %s]"
3791, 0, "--------------------------------------------------------------------------------"
3792, 0, "[%-19s]--[%-14s | %s]"
3793, 0, " Maximum Wait Time = %u"
3794, 0, " Total Wait Time = %u"
3795, 0, " | | Acquires | Converts |"
3796, 0, " +------------+--------------+--------------+"
3797, 0, " | Granted | %12u | %12u |"
3798, 0, " | Waited | %12u | %12u |"
3799, 0, " | Not Queued | %12u | %12u |"
3800, 0, " | Cancelled | NA | %12u |"
3801, 0, " Total grants without waiting = %u\n"
3802, 0, "unable to obtain lock statistics"
// *Cause: An error occurred while fetching lock statistics. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
3803, 0, "no lock statistics to report"
// *Document: NO
3804, 0, "invalid sort column: %s"
// *Cause: An attempt to get lock statistics was rejected because an invalid
// value was provided for the sort option.
// *Action: Retry the operation, providing a valid value for the sort option.
// Valid sort option values can be displayed by running the command
// with the 'h' (help) option.
3805, 0, "command failed due to an internal error"
// *Cause: An attempt to get lock statistics failed due to an internal error.
// *Action: Contact Oracle Support Services.
3806, 0, "lock statistics are turned off"
// *Document: NO
3807, 0, "unknown sort column: %d"
// *Cause: An internal sort function was called with an unknown sort column.
// This was an internal error.
// *Action: Contact Oracle Support Services.
3808, 0, "command cannot accept the 'b' and 'e' options simultaneously"
// *Cause: An 'acfsutil lockstats' command was rejected because of an invalid
// option combination. 'acfsutil lockstats' cannot take both the
// 'b' option (turn on lock statistics) and the 'e' option (turn off
// lock statistics) simultaneously.
// *Action: Rerun the command with either the 'b' option or the 'e' option,
// but not both.
3809, 0, "invalid value for option 't': '%s'"
// *Cause: An 'acfsutil lockstats' command was rejected because a value that was
// not a positive integer was provided for the 't' option.
// *Action: Rerun the command, providing a positive integer value for the
// option 't'.
3810, 0, "Lock statistics are already turned on."
// *Document: NO
3811, 0, "Lock statistics are already turned off."
// *Document: NO
3812, 0, "\nThe following statistics were collected the last time lock statistics were turned on."
// *Document: NO

/ 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"
// *Cause: The file system could not be dismounted because the specified
// volume was in use by another non-ACFS file system.
// *Action: Select a different volume and retry the dismount operation.
04004, 0, "error removing symbolic link for %s"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to remove a symbolic link failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04005, 0, "error removing DOS definition for %s"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to remove a DOS definition failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04006, 0, "unable to remove the reparse point on %s"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to remove the associated reparse point failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04007, 0, "dismount failed due to open files on the volume"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to lock the associated volume failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04008, 0, "failed to unlock the volume"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to unlock the associated volume failed. The accompanying
// messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04009, 0, "unable to retrieve the volume name associated with %s"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to retrieve the volume associated with the supplied mount
// point failed. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
04010, 0, "conversion of reparse data Unicode string to ANSI string failed"
// *Cause: An ACFS file system could not be dismounted because an attempt
// to convert a unicode string to an ANSI string failed. The
// accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and then retry the operation.
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] <path>"
04022, 0, " %s [/v] [/P] <path>"
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, " <path> - 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 <share name> /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 <share name> /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 <share name> /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.
04038, 0, "Volume %s is still mounted. Dismount will complete as soon as activity ceases on the file system."
// *Cause: At the conclusion of the file system dismount request, the
// file system was still mounted. This could be a result of
// open files on the mount point. The dismount will finish
// as soon as activity ceases on the file system.
// *Action: To force dismount to complete, terminate
// any processes or applications that are using the file system.

/
/ Messages for umount on Linux
04050, 0, "Usage: [%sh] [%sv] [%sn] [%sl] [%sr] <mount point>"
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, " <mount point> - 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 umount on Solaris
04100, 0, "Usage: [%sh] <mount_point | volume>"
04101, 0, " [%sh] - Prints out this usage message"
04102, 0, " <mount_point | volume> - Directory/volume to unmount"

/
/ Messages for umount on AIX
04150, 0, "unable to retrieve mount point information from the ACFS driver"
// *Cause: During unmount processing, an attempt to retrieve
// mount point information from the ACFS driver failed.
// *Action: Verify the mount point is a valid ACFS file system before
// retrying the unmount command. If the problem persists, contact
// Oracle Support Services.
04151, 0, "unmount of mount point %s failed"
// *Cause: The file system unmount 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.

/
/ 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 <standby mount point>/.
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: An attempt to initialize replication was rejected because the file
// system was in a state incompatible with replication. Possible
// causes include:
// 1. The file system was not formatted with 512-byte metadata blocks,
// or the file system was compressed.
// 2. The file system was frozen.
// *Action: If the file system was frozen, run 'acfsutil thaw <mount-point>' and
// then retry the operation. Otherwise, migration to newer replication
// infrastructure must be performed. Refer to the Oracle Product
// Documentation for more information.
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 %d 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 %dGB 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: %d"
// *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 %dGB per active node, actual free space left: %dGB"
// *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: %d of %d Online"
05096, 0, "Log compression: %s"
05097, 0, "Debug log level: %d"
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: %d"
05113, 0, "Number of Files Enabled: %d"
05114, 0, "Number of Files Remaining: %d"
05115, 0, "Percentage Complete: %d"
05116, 0, "Event: Standby Site Initialization Progress"
05117, 0, "Number of Files Enabled: %d"
05118, 0, "Number of Files Initialized: %d"
05119, 0, "Percentage Complete: %d"
05120, 0, "Event: Initialization Files Complete"
05121, 0, "Cord Number: %d"
05122, 0, "Initialized Files in Cord: %d"
05123, 0, "Event: Error"
05124, 0, "Severity: %d"
05125, 0, "Message: %s"
05126, 0, "Event: Transmitted Log"
05127, 0, "Cord Number: %d"
05128, 0, "Capture Time: %s"
05129, 0, "Acknowledged Time: %s"
05130, 0, "Event: Applied Log"
05131, 0, "Cord Number: %d"
05132, 0, "Log Create Time: %s"
05133, 0, "Log Apply Complete Time: %s"
05134, 0, "Event: Retransmitted Log"
05135, 0, "Cord Number: %d"
05136, 0, "Node Number: %d"
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-%d"
05152, 0, " %d%% complete"
05153, 0, "Number of Events: %u"
05154, 0, "Events Log: %s"
05155, 0, " Scanning directories: %d found"
05156, 0, " Initializing directories"
//*Document: No
05157, 0, " Initializing files"
//*Document: No
05158, 0, "Replication background processes are not running"
// *Cause: Replication background processes were stopped.
// *Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication
// background processes.
//*Document: No
05159, 0, "Last sync time with primary: %s"
// *Cause: Informational
// *Action: None
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.
05172, 0, "Replication cannot be terminated because background processes are not running."
// *Cause: Replication background processes were stopped and cannot finish
// processing replication data.
// *Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication
// background processes and complete the apply of existing replication
// data, or run 'acfsutil repl terminate standby immediate
// <mountpoint>' to terminate replication immediately without applying
// the remaining replication data.

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
05205, 0, "Failed to initialize replication because ACFS Security is in use on the standby file system '%s'."
// *Cause: ACFS replication initialization failed on the standby file system because
// ACFS Security was in use on the file system.
// *Action: If you are sure you want to use the indicated file system as standby,
// reformat the standby file system and retry the command.
05206, 0, "Failed to initialize replication on ACFS Security enabled file system '%s' because ACFS Security is not initialized on the standby site."
// *Cause: Replication initialization failed on ACFS Security enabled primary file
// system because ACFS Security was not initialized on the standby site.
// *Action: There are two possible options based on user's preference.
// 1. If ACFS Security is desired on primary and standby file systems,
// follow the below mentioned steps in sequence:
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Initialize ACFS Security on standby site by executing
// 'acfsutil sec init' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
// 2. If ACFS Security is not desired on primary and standby file systems,
// follow the below mentioned steps in sequence:
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Remove ACFS Security on primary file system by using
// 'acfsutil sec prepare' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
05207, 0, "A request to initialize replication failed because the primary replication file system is enabled for ACFS Security and standby site is not initialized for ACFS Security."
// *Cause: A request to initialize replication failed because the primary
// replication file system was enabled for ACFS Security
// and standby site was not initialized for ACFS Security.
// *Action: There are two possible options based on user's preference.
// 1. If ACFS Security is desired on primary and standby file systems,
// follow the below mentioned steps in sequence:
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Initialize ACFS Security on standby site by executing
// 'acfsutil sec init' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
// 2. If ACFS Security is not desired on primary and standby file systems,
// follow below mentioned steps in sequence:
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Remove ACFS Security on primary file system by using
// 'acfsutil sec prepare' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
05208, 0, "A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and standby site has PKCS wallet."
// *Cause: Replication initialization failed because the use of PKCS wallet
// for an ACFS Replication standby site is not supported.
// *Action: There are two possible options based on user's preference.
// 1. If ACFS Encryption is desired on primary and standby file systems
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Convert the PKCS wallet to SSO wallet on standby by executing
// 'acfsutil keystore migrate' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
// 2. If ACFS Encryption is not desired on primary and standby file systems
// a. Terminate replication on stanby filesystem by executing
// 'acfsutil repl terminate' command.
// b. Remove ACFS Encryption on primary filesystem by using
// 'acfsutil encr set' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
05209, 0, "A request to initialize replication failed because the primary replication file system is enabled for ACFS Encryption and an error occurred in accessing OCR at standby site."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
05210, 0, "Failed to initialize replication because ACFS Encryption is in use on the standby file system '%s'."
// *Cause: ACFS replication initialization failed on the standby file system because
// ACFS Encryption was in use on the file system.
// *Action: If you are sure you want to use the indicated file system as standby,
// reformat the standby file system to remove encryption and retry
// the command.
05211, 0, "Failed to initialize replication on ACFS Encryption enabled file system '%s' because PKCS wallet existed on standby site."
// *Cause: Replication initialization failed because the use of PKCS wallet
// for an ACFS Replication standby site is not supported.
// *Action: There are two possible options based on user's preference.
// 1. If ACFS Encryption is desired on primary and standby file systems
// a. Terminate replication on standby file system by executing
// 'acfsutil repl terminate' command.
// b. Convert the PKCS wallet to SSO wallet on standby by executing
// 'acfsutil keystore migrate' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
// 2. If ACFS Encryption is not desired on primary and standby file systems
// a. Terminate replication on stanby filesystem by executing
// 'acfsutil repl terminate' command.
// b. Remove ACFS Encryption on primary filesystem by using
// 'acfsutil encr set' command.
// c. Reinitialize replication on standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
05212, 0, "Failed to initialize replication on ACFS Encryption enabled file system '%s' because an error occurred in accessing the OCR at standby site."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
05213, 0, "Checking for standby site's ACFS Security initialization status ..."
// *Document: NO
05214, 0, "Failed to prepare ACFS Security on replication enabled file system '%s' because ACFS Security is not initialized on the standby site."
// *Cause: An attempt to prepare ACFS Security on replication enabled
// file system failed because ACFS Security was not initialized on
// the standby site.
// *Action: Initialize ACFS Security on the standby site by executing
// the 'acfsutil sec init' command and retry the operation.
05215, 0, "Checking wallet type on standby site..."
// *Document: NO
05216, 0, "Failed to set ACFS encryption on a replication enabled file system '%s' because PKCS wallet is not supported as ACFS encryption key store on standby site."
// *Cause: An attempt to set ACFS encryption on replication enabled
// file system failed because the standby site was having a PKCS wallet
// as ACFS encryption key store.
// *Action: If ACFS encryption is desired on primary and standby file systems
// follow the steps mentioned below in sequence:
// a. Convert the PKCS wallet to SSO wallet on standby site by
// executing the 'acfsutil keystore migrate' command.
// b. Retry the 'acfsutil encr set' command.
//
05217, 0, "Failed to set ACFS Encryption on replication enabled file system '%s' because an error occurred accessing the OCR at standby site."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
05218, 0, "Cannot proceed because another conflicting 'acfsutil' command is in progress."
// *Cause: The command could not proceed because one of the following 'acfsutil'
// commands was in progress in the cluster.
// a. 'acfsutil repl init'
// b. 'acfsutil sec prepare'
// c. 'acfsutil encr set'
// d. 'acfsutil audit enable'
// *Action: Retry the command after some time.
05219, 0, "Cannot proceed because CRS stack is not up."
// *Cause: The command could not proceed because CRS stack was not up.
// *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
// or the CSS is not running, check with the CRS administrator to
// bring it up. If it does not resolve the problem,
// contact Oracle Support Services.
05220, 0, "Cannot proceed because ACFS replication initialization is in progress."
// *Cause: The command could not proceed because ACFS replication
// initialization was in progress.
// *Action: Verify that the ACFS replication initialization is complete
// by executing 'acfsutil repl info' and retry.
05221, 0, "Failed to prepare ACFS Security on a replication enabled file system '%s' because ACFS audit is not initialized on the standby site."
// *Cause: An attempt to prepare ACFS Security on a replication enabled
// file system failed because ACFS Audit was not initialized on
// the standby site.
// *Action: Initialize ACFS Audit on the standby site by executing
// the 'acfsutil audit init' command and retry the operation.
05222, 0, "Failed to initialize replication on ACFS Audit prepared filesystem %s because ACFS Audit is not initialized on the standby site."
// *Cause: Replication initialization failed on an ACFS Audit prepared primary
// file system because ACFS Audit was not initialized on the
// standby site.
// *Action: If ACFS Audit is desired on primary and the standby file systems,
// follow the steps mentioned below in sequence:
// a. Terminate replication on the standby file system by executing
// 'acfsutil repl terminate' command.
// b. Initialize ACFS Audit on the standby site by executing
// 'acfsutil audit init' command.
// c. Reinitialize replication on the standby file system by executing
// 'acfsutil repl init' command.
// d. Retry 'acfsutil repl init' command on the primary file system.
05223, 0, "Failed to prepare ACFS Audit on replication enabled file system '%s' because ACFS audit is not initialized on the standby site."
// *Cause: An attempt to prepare ACFS Audit on a replication enabled
// file system failed because ACFS Audit was not initialized on
// the standby site.
// *Action: Initialize ACFS Audit on the standby site by executing
// the 'acfsutil audit init' command and retry the operation.
05224, 0, "Failed to prepare ACFS Audit on replication enabled file system '%s' because an error occurred accessing the OCR at standby site."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
05225, 0, "Checking ACFS Audit state on standby site..."
// *Document: No
05226, 0, "Failed to set ACFS Encryption on a replication enabled file system '%s' because ACFS audit is not initialized on the standby site; moreover, PKCS wallet is not supported as ACFS Encryption key store on the standby site."
// *Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption
// on replication enabled filesystem failed because standby site is
// not ACFS audit initailized and PKCS wallet is not supported as
// ACFS Encryption key store on the standby site.
// *Action: follow the steps mentioned below in sequence.
// a. Initialize ACFS Audit on the standby site by executing
// 'acfsutil audit init' command.
// b. Convert the PKCS wallet to SSO wallet on standby by executing
// 'acfsutil keystore migrate' command.
// c. Retry command 'acfsutil repl init' on the primary site.
05227, 0, "Failed to set ACFS Security on a replication enabled file system '%s' because ACFS Security is not initialized on the standby site; moreover, ACFS Audit is not initialized on standby site."
// *Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS
// Security on a replication enabled filesystem failed because the
// standby site was neither Audit initialized nor Security initialized.
// *Action: follow the steps mentioned below in sequence.
// a. Initialize ACFS Audit on the standby site by executing
// 'acfsutil audit init' command.
// b. Initialize ACFS Security on the standby site by executing
// 'acfsutil sec init' command.
// c. Retry command 'acfsutil repl init' on the primary site.
05228, 0, "Failed to set ACFS Encryption on a replication enabled file system '%s' because ACFS audit is not initialized on the standby site."
// *Cause: An attempt to set ACFS Encryption on a replication enabled
// file system failed because ACFS Audit was not initialized on
// the standby site.
// *Action: Initialize ACFS Audit on the standby site by executing
// the 'acfsutil audit init' command and retry the operation.
05229, 0, "Failed to prepare ACFS Security on replication enabled file system '%s' because an error occurred accessing the OCR at the standby site."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
05230, 0, "Failed to get standby site's encryption state."
// *Cause: An attempt to get standby site's encryption status failed because standby site was unreachable.
// *Action: Verify the status of remote site and retry the command.
05231, 0, "Failed to get standby site's security state."
// *Cause: An attempt to get standby site's security status failed because standby site was unreachable.
// *Action: Verify the status of remote site and retry the command.
05232, 0, "Failed to get standby site's audit state."
// *Cause: An attempt to get standby site's audit status failed because standby site was unreachable.
// *Action: Verify the status of remote site and retry the command.
05233, 0, "Cannot prepare a file system for ACFS Security while the cluster is in rolling migration."
// *Cause: An attempt to prepare a file system for ACFS Security was
// rejected because the cluster was in rolling migration.
// ACFS Security prepare operation is not allowed during rolling
// migration.
// *Action: Complete the rolling migration and retry the command.
05234, 0, "Cannot set ACFS Encryption parameters while the cluster is in rolling migration."
// *Cause: An attempt to set ACFS Encryption parameters was rejected because the
// cluster was in rolling migration. ACFS Encryption set operation is
// not allowed during rolling migration.
// *Action: Complete the rolling migration and retry the command.
05235, 0, "Cannot enable ACFS Audit while the cluster is in rolling migration."
// *Cause: An attempt to enable ACFS Audit was rejected because the
// cluster was in rolling migration. ACFS Audit enable operation is
// not allowed during rolling migration.
// *Action: Complete the rolling migration and retry the command.
05236, 0, "Snapshot cannot serve as replication standby for primary with security enabled."
// *Cause: An attempt to initialize ACFS replication was rejected because a
// snapshot was specified as the replication standby site for a
// primary file system with ACFS security enabled.
// *Action: Retry initializing ACFS replication either:
// 1. specifying a file system (not a snapshot) as the standby site, or
// 2. after first disabling ACFS security on the primary file system.
05237, 0, "Snapshot cannot serve as replication standby for primary with encryption enabled."
// *Cause: An attempt to initialize ACFS replication was rejected because a
// snapshot was specified as the replication standby site for a
// primary file system with ACFS encryption enabled.
// *Action: Retry initializing ACFS replication either:
// 1. specifying a file system (not a snapshot) as the standby site, or
// 2. after first disabling ACFS encryption on the primary file system.
05238, 0, "Snapshot cannot serve as replication standby for primary with audit enabled."
// *Cause: An attempt to initialize ACFS replication was rejected because a
// snapshot was specified as the replication standby site for a
// primary file system with ACFS audit enabled.
// *Action: Retry initializing ACFS replication either:
// 1. specifying a file system (not a snapshot) as the standby site, or
// 2. after first disabling ACFS audit on the primary file system.
05239, 0, "Failed to prepare ACFS Security on replication enabled file system '%s'."
// *Cause: An attempt to prepare security on replication enabled file system
// because ACFS security is not supported on primary file systems
// when the standby site is a snapshot.
// *Action: Retry the command after reinitializing replication using a file
// system (not a snapshot) as the standby site.
05240, 0, "Failed to set ACFS Encryption on replication enabled file system '%s'."
// *Cause: An attempt to set encryption on the indicated replication enabled
// file system because ACFS encryption was not supported where the
// standby site is a snapshot.
// *Action: Retry the command after reinitializing replication using a
// file system (not a snapshot) as the standby site.
05241, 0, "Failed to enable ACFS Audit on replication enabled file system '%s'."
// *Cause: An attempt to enable ACFS audit on replication enabled file system
// because ACFS Audit was not supported where the standby site is a
// snapshot.
// *Action: Retry the command after reinitializing replication using a file
// system (not a snapshot) as the standby site.
05242, 0, "Snapshot creation failed for file system with ACFS Security enabled."
// *Cause: An attempt to create a snapshot using the command 'snap dup create'
// was rejected because the file system had ACFS Security enabled.
// Snapshots were not supported for file systems with security
// enabled.
// *Action: Retry after disabling ACFS Security using 'sec prepare -u' on the
// file system.
05243, 0, "Snapshot creation failed for file system with ACFS Encryption enabled."
// *Cause: An attempt to create a snapshot using the command 'snap dup create'
// was rejected because the file system had ACFS Encryption enabled.
// Snapshots were not supported for file systems with encryption
// enabled.
// *Action: Retry after disabling ACFS Encryption using 'encr set -u' on the
// file system.

/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: %d"
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 %d:"
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: %d"
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.
05523, 0, "The replication relationship for mount point '%s' must be restarted or upgraded."
// *Cause: ACFS replication activity determined that the indicated mount
// point was using outdated replication infrastructure. Release 12.2
// introduced new ACFS replication infrastructure, and migration
// to the new infrastructure was required.
// *Action: The new replication infrastructure supports current and future
// functional and performance improvements. While replication
// continues to function for the indicated mount point, migration
// to the new infrastructure must be performed as soon as possible.
// One option is to terminate and restart replication. The other
// option is to use the 'acfsutil repl upgrade' suite of commands
// to migrate this use of replication without disturbing it. Refer
// to the Oracle product documentation for more information.
05524, 0, "The replication relationship just initiated must be restarted or upgraded."
// *Cause: A replication relationship was initiated specifically using an
// outdated replication infrastructure. Release 12.2 introduced new
// ACFS replication infrastructure, and migration to the new
// infrastructure was required.
// *Action: The new replication infrastructure supports current and future
// functional and performance improvements. While replication
// will function for the relationship just initiated, migration to
// the new infrastructure must be performed as soon as possible. One
// option is to terminate and restart replication. The other
// option is to use the 'acfsutil repl upgrade' suite of commands
// to migrate this use of replication without disturbing it. Refer
// to the Oracle product documentation for more information.
//
/ 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 first tree (<<<) to second tree (>>>):"
// *Cause: Informational
// *Action: None
05702, 0, "Testing for extra files in the second tree.\nSecond tree (<<<) to first tree (>>>):"
// *Cause: Informational
// *Action: None
05703, 0, "Results for file comparison of first tree to second tree:"
// *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 in the second tree:"
// *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 first tree is actively being modified or an
// internal error occurred.
// *Action: If possible, ensure the first tree 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 found in the second tree.
// *Action: None
05715, 0, "Found: %s"
// *Cause: The specified file is an extra file in the second tree.
// *Action: None
05716, 0, "<<< Tag names exist on file %s\n>>> No tag names exist on file %s"
// *Cause: The file in the first tree has tag names but the file in the
// second tree 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 while comparing the first tree to the second tree. Continuing. Affected files: %s %s"
// *Cause: An unexpected result occurred while comparing the first tree to the
// second tree.
// *Action: None. The file was skipped.
05719, 0, "An unexpected result occurred while comparing the second tree to the first tree. Continuing. Affected files: %s %s"
// *Cause: An unexpected result occurred while comparing the second tree to the
// first tree.
// *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 first tree was modified or an internal error occurred.
// *Action: If possible, do not modify files in the first tree when
// running this tool.
05722, 0, "A file read failed during a checksum operation: %s "
// *Cause: Either the first tree was modified or an internal error occurred.
// *Action: If possible, do not modify files in the first tree 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.
/ Message 05725 UNUSED and available
/ Message 05726 UNUSED and available
/ Message 05727 UNUSED and available
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 second tree does not exist: \"%s\" ."
// *Cause: Failed to access the specified second tree.
// *Action: Use a networked file system to provide access to the second tree
// on the primary node where the 'acfsutil repl compare' will be
// performed.
05733, 0, "Successfully compared: %s %s"
// *Cause: Informational.
// *Action: None.
05734, 0, "Successfully verified existence: %s %s"
// *Cause: Informational.
// *Action: None.
/ Message 05735 UNUSED and available
/ Message 05736 UNUSED and available
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.
05747, 0, "Directory '%s' is a nested ACFS reparse point and was not included in the file system comparison."
// *Cause: Informational.
// *Action: None.
05748, 0, "The '%ss' option requires either the '%sa' option or '%st' option."
// *Cause: An incorrect combination of options was specified.
// *Action: Combine the 's' option with either the 'a' option or 't' option.
5749, 0, "The specified trees are the same and will not be compared."
// *Cause: The provided first and second trees resolved to the same
// location.
// *Action: Rerun the command specifying unique trees.

/ Replication messages for free space warnings
05801, 0, "The primary replication file system %s is at least %u%% full."
// *Cause: Free space in the primary replication file system fell below a monitored threshold.
// *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 %s 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 %s has 2GB or less space available per active node. Replication is being 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 per active node.
05804, 0, "The standby replication file system %s 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 that the network connectivity between the primary and standby
// replication systems is functional.
05805, 0, "The standby replication file system %s 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 made
// more than 60 minutes ago. The standby is at least 60 minutes out of sync with the primary.
// *Action: Check that the network connectivity between the primary and standby
// replication systems is functional.
05806, 0, "The primary replication file system %s has reached an appropriate free space level."
// *Cause: A previously-reported free space shortage in the primary replication file system was relieved.
// *Action: None.
05807, 0, "The standby file system %s is less than 15 minutes out of sync now."
// *Cause: A previously-reported out of sync time difference between the standby replication file system
// and the primary reached an appropriate out of sync time for replication to run efficiently.
// *Action: None.
05808, 0, "The primary replication file system %s had an unrecoverable error and replication has been terminated for that file system."
// *Cause: The primary file system encountered an unrecoverable error in the
// kernel that has caused replication for this file system to be
// terminated. The cause will be in the Oracle Kernel Services (OKS)
// persistent log.
// *Action: Replication must be restarted. To do this, terminate replication
// on the standby file system, run mkfs (Unix or Linux) or
// acfsformat.exe (Windows) on the volume for the standby
// file system, remount that volume, and then restart replication for
// both file systems.
05809, 0, "invalid query of replication apply events on the standby site"
// *Cause: An attempt was made to query the replication apply events on the
// standby site which failed because the information is available only
// on the primary site.
// *Action: Query the replication apply events from the primary site.
05810, 0, "invalid query of replication transport events on the standby site"
// *Cause: An attempt was made to query the replication transport events on
// the standby site which failed because the information is available
// only on the primary site.
// *Action: Query the replication transport events from the primary site.
05811, 0, "ACFS replication initialization failed in Oracle Restart environment."
// *Cause: Initialization failed because the system was configured with Oracle
// Restart. ACFS replication is not supported for Oracle Restart
// configurations.
// *Action: Initialize ACFS replication in an environment that is configured
// with single or multi-node RAC.

/ Replication Configuration Information Messages for v2
05812, 0, "Primary hostname: %s"
05813, 0, "Primary path: %s%s%s"
05814, 0, "Background Resources: %s"
05815, 0, "Standby connect string: %s@%s"
05816, 0, "Standby path: %s%s%s"
05817, 0, "Replication interval: %d days, %d hours, %d minutes, %d seconds"
05818, 0, "Sending primary as of: %s"
05819, 0, "Receiving primary as of: %s"
05820, 0, "Status: %s"
/ Message 05821 UNUSED and available
05822, 0, "Retries made: %d"
05823, 0, "Last send started at: %s"
05824, 0, "Last receive started at: %s"
05825, 0, "Last send completed at: %s"
05826, 0, "Last receive completed at: %s"
05827, 0, "Elapsed time for last send: %d days, %d hours, %d minutes, %d seconds"
05828, 0, "Elapsed time for last receive: %d days, %d hours, %d minutes, %d seconds"
05829, 0, "Next send starts at: %s"
05830, 0, "Data transfer compression: %s"
05831, 0, "Event: Clone created"
05832, 0, "Event: Clone applied"
05833, 0, "Session started at: %s"
05834, 0, "Session ended at: %s"
05835, 0, "Number of bytes transmitted: %ld"
05836, 0, "Number of bytes applied: %ld"
05837, 0, "Transfer started at: %s"
05838, 0, "Transfer completed at: %s"
05839, 0, "Transfer status: %d"
05840, 0, "Apply started at: %s"
05841, 0, "Apply completed at: %s"
05842, 0, "Event: Replication configuration updated"
05843, 0, "Configuration update time: %s"
05844, 0, "ssh command path: %s"
05845, 0, "Create started at: %s"
05846, 0, "Create completed at: %s"
05847, 0, "Create status: %d"
05848, 0, "Prepared for upgrade"
05849, 0, "ssh strict host key checking: %s"
05850, 0, "Replication ID: 0x%x"
05851, 0, "Primary reversal started at: %s"
05852, 0, "Primary reversal completed at: %s"
05853, 0, "Standby reversal started at: %s"
05854, 0, "Standby reversal completed at: %s"
05855, 0, "Reversal status: %d"
/ 05849-05886 were allocated for custom defined "Status details:" not in errno.h
/ They may be reused since "Status details:" has been removed from
/ 'repl info -c' output.

05887, 0, "cannot cleanup snapshot directories"
// *Cause: The 'acfsutil repl terminate' command failed to cleanup from a
// previous replication instantiation.
// *Action: Verify user permissions, that the snapshot directory is available,
// and then retry the command.
05888, 0, "ACFS replication requires reinitialization of mount point %s."
// *Cause: This file system has already been initialized with a different
// version of ACFS replication.
// *Action: Run 'acfsutil repl terminate' and retry the initialization.
05889, 0, "a username and VIP name or username and hostname to the standby replication site was not provided"
// *Cause: The username and VIP name or username and hostname used to connect
// to the standby replication site were not specified.
// *Action: Provide the username and VIP name or hostname to connect to the
// standby replication site.
05890, 0, "a username for the standby replication site was not provided"
// *Cause: The username on the standby replication site with which the
// primary replication site will connect and apply changes was not
// specified.
// *Action: Provide the username for connecting and applying changes to the
// standby replication site using the -u option.
05891, 0, "username %s used to connect to the standby site was rejected"
// *Cause: The username specified on the command line was not found in the
// password database on the standby site.
// *Action: Verify the username is correct when connecting to the standby site.
05892, 0, "Cannot terminate replication. Pending operations are unable to complete because the replication primary file system is full."
// *Cause: The primary replication file system was full and replication could
// not complete sending data before terminating.
// *Action: Resize the primary file system, or delete snapshots from the primary
// file system if they exist, and retry 'acfsutil repl terminate'.
05893, 0, "cannot update the standby replication site"
// *Cause: An attempt to update the standby replication site failed because an
// apply operation was in progress.
// *Action: Pause replication or stop the replication resource and try to update
// the standby replication site again.
05894, 0, "invalid zero or negative integer replication interval"
// *Cause: The value specified with the 'i' option was not an integer greater
// than zero.
// *Action: Specify the 'i' option with an integer value greater than zero.
05895, 0, "missing time unit on interval ('%si') option"
// *Cause: A unit of time was not specified with the interval that was provided
// with the 'i' option.
// *Action: Append a unit from the set W (weeks), D (days), H (hours),
// M (minutes), S (seconds) to the interval specified.
05896, 0, "invalid time unit in replication interval"
// *Cause: An unrecognized unit was used following the interval length given
// with the 'i' option.
// *Action: Append a unit of time from the set W (weeks), D (days), H (hours),
// M (minutes), S (seconds) to the interval specified.
05897, 0, "missing interval ('%si') option"
// *Cause: The 'acfsutil repl init primary' command was incomplete because a
// replication interval was not specified.
// *Action: Provide an interval when the primary is initialized. An interval
// can be set implicitly through the use of the '-C' option or
// explicitly through the argument passed to the '-i' option.

/Replication Statistics for v2
05898, 0, "Average time to apply snapshot duplicate stream: %s"
05899, 0, "Minimum time to apply snapshot duplicate stream: %s"
05900, 0, "Maximum time to apply snapshot duplicate stream: %s"

05901, 0, "The specified tag name list exceeds the maximum of %u characters."
// *Cause: The specified tag name list was too long.
// *Action: Remove some tag names and try the command again.
05902, 0, "Snapshot %s is read-only and cannot be modified."
// *Cause: A request to write to a snapshot was rejected because the snapshot
// was configured as read-only.
// *Action: Convert the snapshot to be read-write and retry.
05903, 0, "unable to cleanup old snapshots"
// *Cause: Informational.
// *Action: None.
05904, 0, "The base and target operating systems are not compatible."
// *Cause: An attempt to apply changes from a base file system to a target file
// system was rejected because one system was Unix or Linux and the
// other system was Windows.
// *Action: Ensure both systems are Unix or Linux or both systems are Windows.
05905, 0, "Target file system or snapshot has been altered since the last 'snap duplicate apply'."
// *Cause: An attempt to apply changes from a base file system or snapshot
// to a target file system or snapshot was rejected because the
// target had previously been modified and was no longer in sync with
// the base file system or snapshot.
// *Action: Run the 'acfsutil snap remaster' command with the snap duplicate
// backup snapshot for the target file system or snapshot, in order
// to re-base the target to the backup snapshot contents.
05906, 0, "The system containing the base or primary file system disconnected prematurely."
// *Cause: An attempt to apply changes from the base or primary file system to
// the target or standby file system could not be completed because
// connectivity to the system containing the base or primary file
// system was lost.
// *Action: Reestablish connectivity to the system containing the base or
// primary file system and then retry.
05907, 0, "The ACFS file system mounted at path %s is already running the latest version of replication."
// *Cause: A request to prepare an ACFS file system for replication upgrade
// was rejected because the file system is already running the latest
// version of replication.
// *Action: If the indicated ACFS file system was not the intended target for
// upgrade, reissue the command specifying the correct file system.
05908, 0, "The replication upgrade control file %s cannot be opened."
// *Cause: An attempt to open the replication upgrade control file failed.
// *Action: Run the 'acfsutil repl upgrade prepare' command to prepare the file
// system to be upgraded.
05909, 0, "Snapshot %s is not read only."
// *Cause: An attempt to use the 'snap duplicate create' command failed because
// the snapshot was writable.
// *Action: Re-create the snapshot as read only and retry the command.
05910, 0, "The snapshot specified as the old snapshot by the %si option is not older than the snapshot specified as the new snapshot."
// *Cause: An attempt to create a snap duplicate failed because the snapshot
// specified as the old snapshot by the 'i' option is not older than the
// snapshot specified as the new snapshot.
// *Action: Reverse the order of the two snapshot names or specify a different
// new or old snapshot and retry the command.
05911, 0, "Target file system or snapshot has been altered since the start of the current 'snap duplicate apply'."
// *Cause: An attempt to apply changes from a base file system or snapshot
// to a target file system or snapshot was rejected because the
// target was modified while the apply attempt was in progress,
// and was no longer in sync with the base file system or snapshot.
// *Action: Run the 'acfsutil snap remaster' command with the snap duplicate
// backup snapshot for the target file system or snapshot, in order
// to re-base the target to the backup snapshot contents.
05912, 0, "unable to perform 'snap duplicate' operation because ACFS replication is initialized on the file system"
// *Cause: An attempt to use the 'acfsutil snap duplicate' command was rejected
// because ACFS replication was initialized on the file system.
// *Action: Terminate replication on the file system if appropriate by executing
// the 'acfsutil repl terminate' command and then retry the 'acfsutil
// snap duplicate' command.
05913, 0, "unable to contact the standby node %s"
// *Cause: An attempt to use the ping utility to contact a standby node failed.
// *Action: Ensure that the correct host name or IP address was specified for
// the standby node, and that the standby node is operating normally.
// Then reissue the 'acfsutil repl init primary' command.
05914, 0, "user %s on node %s unable to log in via 'ssh' to the standby node %s as user %s"
// *Cause: An attempt by 'acfsutil repl init primary' or 'acfsutil repl update' to use the ssh utility to log in to a standby node failed.
// *Action: Ensure that the correct user name and address were specified for
// the standby node, and that the standby cluster is operating
// normally. If need be, verify network connectivity to the standby
// cluster, and refer to the product documentation to verify ssh
// configuration details. Then reissue the 'acfsutil repl init
// primary' or 'acfsutil repl update' command.
05915, 0, "invalid use of '-t ALL' option"
// *Cause: An attempt to execute the 'acfsutil repl compare' command was
// rejected because the '-t ALL' option was specified on the command
// line, but no tag names had been specified when the primary was
// initialized.
// *Action: Reissue the 'acfsutil repl compare' command without the '-t ALL'
// option.
05916, 0, "path %s not found"
// *Cause: The ssh utility was not found at the indicated path.
// *Action: Ensure that the path to the ssh utility is correct and retry.
05917, 0, "user 'root' on node %s unable to continue logging in via 'ssh' to the standby node %s as user '%s'"
// *Cause: A periodic attempt by ACFS replication to use the ssh utility to
// continue logging in to a standby node failed.
// *Action: Ensure that the standby cluster is operating normally. If need
// be, verify network connectivity to the standby cluster, and refer
// to the product documentation to verify ssh configuration details.
05918, 0, "Replication initialization on primary site cannot confirm replication initialized on standby mount point '%s'."
// *Cause: The 'acfsutil repl init primary' command failed on the primary
// replication site because it could not confirm that replication
// has been initialized on the standby replication site.
// *Action: Ensure that the correct user name and address were specified
// for the standby node, and run the 'acfsutil repl info -c'
// command on the standby site to confirm that replication has
// been initialized there for the mount point named. Then retry
// the 'acfsutil repl init primary' command.
05919, 0, "Replication failed because it was unable to create a backup snapshot for mount point '%s' on standby node '%s'."
// *Cause: The 'acfsutil snap dup apply' operation, as used by ACFS
// replication, was unable to create a backup snapshot at the
// end of an apply operation on the standby node named. As a
// result, replication cannot proceed.
// *Action: Check the standby cluster for conditions that would prevent
// snapshot creation, such as lack of storage or having too
// many snapshots present. Replication will resume automatically
// once backup snapshots can again be created.
05920, 0, "ssh cipher option \"%s\" is invalid for replication"
// *Cause: An attempt to configure replication on the primary file system
// was rejected because the indicated value was specified for the
// 'sshCipher' option. Replication does not support unencrypted
// ssh connections.
// *Action: Retry the command with a supported ssh cipher option.
05921, 0, "One or more files under mount point '%s' was not transferred because its path name exceeded %d characters. The first such file was in directory '%s' and had name '%s'."
// *Cause: The command 'acfsutil snap duplicate create' did not complete
// correctly because one or more files located under the indicated
// mount point had an absolute path name longer than the indicated
// limit. Any files with path names exceeding the limit were not
// processed by 'acfsutil'. The directory and basename of the
// first such file found are shown in the message, but there may
// be many others.
// *Action: Rename the problematic files so that their absolute path names
// are shorter than the limit, and retry the command.
05922, 0, "One or more files under primary mount point '%s' was not replicated because its path name exceeded %d characters. The first such file was in directory '%s' and had name '%s'."
// *Cause: ACFS replication did not replicate the primary correctly
// because one or more files located under the indicated mount
// point had an absolute path name longer than the indicated
// limit. Any files with path names exceeding the limit were not
// replicated. The directory and basename of the first such file
// found are shown in the message, but there may be many others.
// *Action: Rename the problematic files so that their absolute path names
// are shorter than the limit. Once each file has been renamed,
// the next later replication operation will automatically
// transfer the file.
05923, 0, "unable to apply the incremental snapshot duplication stream because no initial snapshot duplication stream has been applied"
// *Cause: An attempt to apply an incremental snapshot duplication stream failed
// because no preceding initial snapshot duplication stream has been applied to
// the snapshot duplication target.
// *Action: Apply an initial snapshot duplication stream to the target using 'acfsutil
// snapshot duplicate create' without the -i option to create the initial
// snapshot duplication stream.
05924, 0, "unable to apply the incremental snapshot duplication stream because its starting snapshot does not match the final snapshot used to create the most recently applied snapshot duplication stream"
// *Cause: The incremental snapshot duplication stream could not be applied because
// its starting snapshot did not match the final snapshot of the last
// stream applied.
// *Action: Apply all the intermediate incremental data streams in the correct
// order leading up to failed snap duplication stream and then rerun
// the apply operation.
05925, 0, "unable to re-apply the initial snapshot duplication stream because its starting snapshot does not match the snapshot used to create the partially applied duplication stream"
// *Cause: An attempt to apply an initial snapshot duplication stream was
// interrupted. An attempt was then made to re-apply the initial
// snapshot duplication stream. The re-apply failed because its
// starting snapshot did not match the snapshot of the last,
// partially applied snapshot duplication stream.
// *Action: Re-apply the correct initial snapshot duplication stream using the
// -r option of the command 'acfsutil snap duplicate create'.
05926, 0, "The snapshot duplication stream cannot be applied because a previous duplication stream was interrupted."
// *Cause: Snapshot duplication failed because a previously interrupted
// snapshot duplication stream was detected.
// *Action: Generate a snapshot duplication stream using the -r option of the
// command 'acfsutil snap duplicate create', and apply it.
//
05927, 0, "cannot synchronize the primary and standby replication sites"
// *Cause: A request to synchronize the primary and standby replication sites
// was rejected because the primary replication site was paused.
// *Action: Resume replication on the primary replication site and try to
// synchronize the primary and standby replication sites again.
05928, 0, "The ADVM compatibility attribute for the diskgroup is below the required version (%s) for the 'acfsutil snap duplicate' commands."
// *Cause: The command 'acfsutil snap duplicate' was rejected because the ADVM
// disk group compatibility attribute had not been upgraded to the
// indicated version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM) attribute to the specified
// version and then re-issue the original command. If the disk
// group compatibility attribute cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
05929, 0, "Replication could not proceed because it was unable to delete a directory in mount point '%s' on standby node '%s'."
// *Cause: The 'acfsutil snap dup apply' operation, as used by ACFS
// replication, could not proceed because it was unable to delete a
// directory in the indicated mount point on the standby replication
// site shown.
// *Action: Check the alert log for message ACFS-05027 which includes the name
// of the directory being deleted. Check the standby cluster for
// conditions that would prevent the directory from being deleted,
// such as its being in use. Replication will resume automatically
// once the directory can be removed.
05930, 0, "A valid 'ssh' connection was detected for standby node %s as user %s."
05931, 0, "The standby replication ACFS file system mounted at path %s at site %s is not running a compatible version of replication."
// *Cause: A request to upgrade a primary replication ACFS file system
// was rejected because the standby file system is not running a
// compatible version of replication.
// *Action: Ensure that the cluster where the standby replication ACFS file
// system is located is running a version of Clusterware that supports
// the version of ACFS replication to which upgrade was attempted.
// Upgrade the standby replication ACFS file system, and then reissue
// the command to upgrade the primary ACFS replication file system.
// Refer to Oracle product documentation for details regarding
// Clusterware and ACFS replication version compatibility.
05932, 0, "cannot upgrade the existing ACFS replication environment"
// *Cause: A request to upgrade the existing ACFS replication environment to
// snapshot-based replication was rejected because the existing tag
// name list exceeded the limit of 4096 characters imposed by
// snapshot-based replication.
// *Action: Terminate the existing replication environment and reconfigure using
// snapshot-based replication. Refer to Oracle product documentation
// for details regarding upgrading to ACFS snapshot-based replication.
05933, 0, "invalid, out-of-date option given for 'acfsutil repl init'"
// *Cause: An attempt to invoke a 'acfsutil repl init' command was rejected
// because it specified an option specific to an earlier version
// of ACFS replication.
// *Action: Ensure that you are using 'acfsutil repl init' as required
// by the current version of ACFS replication. Refer to the
// Oracle product documentation for details about running current
// replication.
05934, 0, "ACFS replication could not start an apply operation for mount point '%s' due to an existing apply operation."
// *Cause: This message may indicate a problem with networking or storage
// access that is preventing the existing apply operation from making
// progress. Alternatively, this message may indicate an internal
// error.
// *Action: Contact Oracle Support Services.
05935, 0, "The ACFS replication primary is mounted on more than one node."
// *Cause: A request to prepare ACFS replication for upgrade was rejected
// because the file system was mounted on more than one node.
// *Action: Unmount the ACFS replication primary on all but one node and retry
// the command.
05936, 0, "The new snapshot and the old snapshot do not have the same parent."
// *Cause: An attempt to create a snap duplicate stream failed because the
// snapshot specified as the old snapshot by the -i option did not
// have the same parent as the snapshot specified as the new snapshot.
// *Action: Reissue the command with the correct snapshot names.
05937, 0, "The new snapshot is not a child of the parent snapshot."
// *Cause: An attempt to create a snap duplicate stream failed because the
// snapshot specified as the new snapshot was not a child of the
// parent snap specified by the -p option.
// *Action: Reissue the command with the correct snapshot names.
05938, 0, "The new snapshot is not a child of the mount point."
// *Cause: An attempt to create a snap duplicate stream failed because the
// snapshot specified as the new snapshot was not a child of the
// specified mount point.
// *Action: Reissue the command with the correct snapshot names.
05939, 0, "The parent snapshot must be writable."
// *Cause: An attempt to create a snap duplicate stream failed because the
// snapshot specified as the parent snapshot by the -p option was not
// writable.
// *Action: Reissue the command specifying a writable parent snapshot.
05940, 0, "The ACFS file system mounted at path %s is not prepared for replication upgrade."
// *Cause: A request to undo replication upgrade preparation on an ACFS file
// system was rejected because the file system had not been prepared
// for replication upgrade.
// *Action: If the indicated ACFS file system was not the intended target for
// upgrade, reissue the command specifying the correct file system.
// Otherwise no further action is necessary.
05941, 0, "The ACFS file system mounted at path %s may not be unprepared for replication upgrade."
// *Cause: A request to undo replication upgrade preparation on an Oracle ACFS
// file system was rejected because its standby file system had already
// been upgraded.
// *Action: If the indicated Oracle ACFS file system was not the intended target
// for upgrade, reissue the command specifying the correct file system.
// Otherwise no further action is necessary.
05942, 0, "unable to apply updates to standby mount point '%s' due to user mismatch"
// *Cause: An apply update operation on the indicated mount point was
// rejected because the replication user for the primary mount
// point and the indicated standby mount point did not match. This
// could occur if the command 'acfsutil repl update' had been used
// to change the replication user for one mount point and not the
// other.
// *Action: Run the 'acfsutil repl update' command for the mount point where
// the intended replication user is not currently configured to
// ensure that both mount points have the intended user configured.
05943, 0, "The replication user '%s' may lack needed privileges -- confirm the user's group memberships."
// *Cause: The 'acfsutil repl init standby' command completed correctly and
// registered the indicated user as specified by the -u option.
// However additional validation by the command determined that the
// indicated user was not a member of one or more groups presumed
// necessary for subsequent correct functioning of replication.
// *Action: If the intended replication user was correctly specified, ensure
// that that user is a member of the necessary groups, as specified
// in the Oracle documentation, before continuing to initiate
// replication. If the indicated user is not the intended
// replication user, then re-initialize the standby using the command
// 'acfsutil repl terminate standby' and then 'acfsutil repl init
// standby' naming the intended user.
05944, 0, "The old and new snapshots are not properly related."
// *Cause: An attempt to create a snap duplicate stream failed because the
// specified new snapshot was not properly related to the old
// snapshot specified with -i. The new snapshot must either be a
// child of the old snapshot or be a child of the same parent as the
// old snapshot.
// *Action: Reissue the command specifying old and new snapshots with the
// required relationship.
05945, 0, "Clusterware at site %s must be upgraded to support the standby replication ACFS file system mounted at path %s."
// *Cause: Following an upgrade of the Oracle Clusterware on the cluster
// where a primary replication ACFS file system was located, an
// attempt to do an automatic update of the standby failed,
// because the cluster where the standby replication ACFS file system
// was located was not running the same version of Clusterware.
// *Action: Upgrade the Oracle Clusterware on the cluster where the standby
// file system is located to ensure that the cluster is running the
// same version of Clusterware as the cluster where the primary file
// system is located.
05946, 0, "The replication subcommand (%s) is not supported by the version of replication configured on the file system or snapshot."
// *Cause: An attempt to execute the indicated replication sub-command was
// rejected because it was not supported by the configured replication
// version.
// *Action: None.
05947, 0, "Snapshot %s must be writable."
// *Cause: An attempt to initialize replication on a snapshot failed because
// the snapshot specified was not writable.
// *Action: Reissue the command specifying a writable snapshot.
05948, 0, "The named standby is already in use by a different primary."
// *Cause: An attempt to initialize replication failed because the
// standby specified was already paired with a different primary.
// *Action: Reissue the command specifying a standby that is not in use.
//
05949, 0, "The standby replication ACFS file system mounted at path %s at site %s is not running a compatible version of replication."
// *Cause: A request to initiate replication of an ACFS file system was
// rejected because the indicated standby file system was running an
// incompatible version of replication.
// *Action: Ensure that the cluster where the standby replication ACFS file
// system is located is running a version of Clusterware that supports
// the version of ACFS replication which was being initialized.
// Initialize the standby replication ACFS file system, and then
// reissue the command to initialize the primary ACFS replication file
// system. Refer to Oracle product documentation for details
// regarding Clusterware and ACFS replication version compatibility.
05950, 0, "cannot reverse replication during a rolling upgrade"
// *Cause: An attempt to reverse the replication role at a site was rejected
// because the cluster was in a rolling upgrade. Replication site
// reversal is not allowed during a rolling upgrade.
// *Action: Complete the rolling upgrade and then reverse the replication site.
05951, 0, "snapshot creation is blocked while ACFS replication is updating the standby"
// *Cause: An attempt to create a snapshot could not complete immediately
// because the replication standby was currently being updated
// by ACFS replication.
// *Action: If the command has completed in the meantime, no action is
// required. Otherwise, if no action is taken, snapshot creation
// will be retried periodically and complete once the ACFS
// replication update has completed. To complete the snapshot
// creation immediately, interrupt the replication update and
// reissue the command. Terminiate the 'acfsutil snap create',
// run 'acfsutil repl pause' on the replication primary to pause
// the update, and then reissue 'acfsutil snap create'. Finally,
// run 'acfsutil repl resume' on the primary to resume the
// replication update.
05952, 0, "A replication standby site cannot be reversed before the primary site is reversed."
// *Cause: An attempt to reverse a replication standby site was rejected
// because the corresponding replication primary site had not been
// reversed before the attempted standby reversal.
// *Action: Reverse the replication primary site, then retry the operation.

/ 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 <volume>"
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 <volume>"
07011, 0, " %(1)sr - Read-only mode"
07012, 0, " %(1)sl - Process metadata log files"
07013, 0, " %(1)svv - Very verbose mode"
/ Message 7014 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 <volume>"
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 primary volume size: %(2)s\nfor structure:\n%(3)s"
// *Cause: An I/O request was made for data that exceeded the size of the
// primary volume.
// *Action: If the ACFS Fixer is currently running, then no further action 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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.
/ Message 07056 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.
/ Message 07059 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.
/ Message 07067 removed - do not reuse message number
/ Message 07068 removed - do not reuse message number
/ Message 07069 removed - do not reuse message number
/ Message 07070 removed - do not reuse message number
/ Message 07071 removed - do not reuse message number
/ Message 07072 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.
/ Message 07093 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: %(2)s 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.
/ Message 07153 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.
/ Message 07166 removed - do not reuse message number
07167, 0, "Functionality may be limited due to problems accessing the accelerator volume: %(1)s."
// *Cause: An attempt to open the accelerator volume failed. Refer to the
// accompanying messages for more information on the problem.
// *Action: Correct the problems described in the accompanying messages if
// possible and rerun the command.
/ 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ 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.
/ Message 07173 removed - do not reuse message number
/ Message 07174 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.
/ 7180 is displayed with 7185
07180, 0, "There is an inconsistency between the ACFS Map_File and the ACFS Log_File."
// *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.
/ Message 07181 removed - do not reuse message number
/ Message 07182 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, "The 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.
/ Message 07194 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.
/ Message 07198 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, "duplicate _SnapFetaFenum: %(1)s found for the following snapshots:\n"
// *Cause: The _SnapFetaFenum property of the indicated snapshots had the
// same value. _SnapFetaFenum values must be unique.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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)u, but expected to find: %(2)u\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, "results for Snap_Map data may be limited or incorrect due to inconsistencies with Snap_Map metadata"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
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, "functionality may be limited due to File_Entry_Table metadata inconsistency"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
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, "functionality related to snapshots disabled due to problems accessing Snap_Map file"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
/ 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.
/ Message 07210 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.
/ Message 07213 removed - do not reuse message number
/ Message 07214 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, %(5)s or %(6)s\nfor structure:\n%(7)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, "cannot process command due to Snap_Map File metadata inconsistency"
// *Cause: An acfsdbg command was not executed due to a metadata inconsistency.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
/ 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 %(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, "missing snapshot name or identifier"
// *Cause: A snapshot name or identifier was not entered as required for
// this command.
// *Action: Re-enter the command with a valid snapshot name or snapshot
// identifier.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07238 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, "Invalid Security_Metadata_File"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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.
/ Message 07244 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.
/ Message 07253 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, "unable to process request for volume %(1)s; volume is not open"
// *Cause: An attempt to read metadata failed because the volume was not open.
// Refer to the accompanying messages for more information on the
// problem.
// *Action: Correct the problem described in the accompanying messages if
// possible and rerun the acfsdbg utility.
07258, 0, "unable to reset context to snapshot %(1)s due to File_Entry_Table metadata inconsistency"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
// Services.
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, "unable to reset context to snapshot %(1)s due to Snap_Map file metadata inconsistency"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
07262, 0, "unable to reset context to snapshot %(1)s because it no longer exists"
// *Cause: The identified snapshot no longer exists due to on-disk metadata
// changes that are allowed whenever the acfsdbg utility is operating
// in read-only mode.
// *Action: Enter the 'primary' or 'snap <snapshot name>' command to set
// context.
/ 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.
/ Message 07269 removed - do not reuse message number
/ Message 07270 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07273 removed - do not reuse message number
07274, 0, "missing or invalid snapshot name"
// *Cause: No snapshot name was provided or the name entered was not valid.
// *Action: Re-enter the command with a valid snapshot name.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows). 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
/ Message 07278 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.
/ Message 07281 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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, "snapshot: %(1)s (identifier: %(2)u) has invalid File_Entry_Table identifier: %(3)s that exceeds the maximum value for this file system: %(4)s"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
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, "cannot convert file identifier: '%(1)s' to numeric value"
// *Cause: The format entered for the file identifier was invalid.
// *Action: Use the acfsdbg utility help (-h) option for a list of commands
// and format options for entering data.
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.
/ Message 07307 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07323 removed - do not reuse message number
/ Message 07324 removed - do not reuse message number
/ Message 07325 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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.
/ Message 07328 removed - do not reuse message number
/ Message 07329 removed - do not reuse message number
/ Message 07330 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07332, 0, "cannot convert snapshot identifier: '%(1)s' to numeric value"
// *Cause: The format entered for the snapshot identifier was invalid.
// *Action: Use the acfsdbg utility help (-h) option for a list of commands
// and format options for entering data.
07333, 0, "invalid snapshot identifier entered: %(1)s\n minimum: 1 maximum: %(2)u"
// *Cause: The snapshot identifier entered was not within the valid range
// for this file system.
// *Action: Re-enter the command with a snapshot identifier that is within
// the valid range described in the message.
07334, 0, "invalid snapshot name '%(1)s' entered"
// *Cause: The snapshot name entered did not exist.
// *Action: Re-enter the command with the name or identifier of a valid
// snapshot.
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, "starting disk offset %(1)s exceeds ending disk offset %(2)s"
// *Cause: The starting storage map offset was greater than the ending
// offset.
// *Action: Re-enter the command with valid disk offsets.
/ 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'"
/ Message 07349 removed - do not reuse message number
07350, 0, "command disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap' to set context"
// *Cause: The acfsdbg utility could not process the request because the
// File_Entry_Table context was not set. The acfsdbg utility requires
// a valid File_Entry_Table context to locate on-disk metadata
// structures.
// *Action: Enter 'primary' or 'snap <snapshot name>' command to set
// context.
07351, 0, "requested Snap_Info_Entry structure not available due to inconsistencies with Snap_Map metadata"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
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.
/ Message 07353 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, "Cannot fix orphaned files because the lost+found directory is damaged."
// *Cause: Fsck could not move the orphan files because there was an
// inconsistency with the lost+found directory. Files that do not
// have a valid parent directory are considered to be orphan files
// and are moved to the lost+found 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.
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.
/ Message 07357 removed - do not reuse message number
/ Message 07358 removed - do not reuse message number
/ Message 07359 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, "Volume_Disk_Header has invalid _VolFeatureFlag values.\n found: %(1)s\n, but expected to find: %(2)s or %(3)s\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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, "Volume_Disk_Header has invalid _VolStateFlag values for accelerator volume: %(1)s\n found: %(2)s,\n but expected to find: %(3)s \nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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.
/ Message 07371 removed - do not reuse message number
/ Message 07372 removed - do not reuse message number
/ Message 07373 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.
/ Message 07380 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, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapIncarnationNumber\n found: 0, but expected to find: > 0\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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.
/ Message 07387 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.
/ Message 07390 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.
/ Message 07393 removed - do not reuse message number
/ Message 07394 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07397 removed - do not reuse message number
/ Message 07398 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, "mismatch between _NOLSTXPTR feature and _NOUPHDRPTR feature\n _NOLSTXPTR: %(1)s _NOUPHDRPTR: %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07401 removed - do not reuse message number
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.
/ Message 07403 removed - do not reuse message number
/ Message 07404 removed - do not reuse message number
/ Message 07405 removed - do not reuse message number
/ Message 07406 removed - do not reuse message number
07407, 0, "Snap_Map_Header contains invalid _SnapCreatePending field\nfound: 0, but expected to find: > 0\nfor structure:\n%(1)s"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
07408, 0, "Snap_Map_Header contains invalid _SnapDeletePending field\nfound: 0, but expected to find: > 0\nfor structure:\n%(1)s"
// *Cause: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
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, "Accelerator Volume_Disk_Header has invalid _VolSignature value\n found: '%(1)s'\n, expected: %(2)s\nfor structure: \n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07414, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid snap_map_tuples for file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07415, 0, "invalid snap_map_tuple: ( %(1)s, %(2)s ) for disk offset: %(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07416, 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.
// *Action: If the ACFS Fixer is currently running, then no further action 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.
/ Message 07422 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 value: %(1)s) 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.
/ Message 07428 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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.
/ Message 07433 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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, "snapshot: %(1)s (identifier: %(2)u)\n"
// *Document: NO
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, "Global_BitMap has invalid value for next offset to search\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s"
// *Cause: The Global_BitMap property that indicates the next offset to search
// for available bits to allocate 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.
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, "invalid snap_map_tuple for disk offset: %(1)s\n found: ( 0, 0 ), but expected non-zero values\nfor file:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07448, 0, "invalid snap_map_tuple for disk offset: %(1)s\n found: ( 0, 0 ), but expected non-zero values"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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\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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07456, 0, "Global_Metadata_Directory structure has incorrect _accelerator_GBM_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07457 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, "Global_Metadata_Directory structure has incorrect _accelerator_snap_map_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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\n expected: %(2)s\nfor file:\n%(3)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.
/ Message 07472 removed - do not reuse message number
/ Message 07473 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"
// *Cause: The file system checker was unable to use the more efficient memory
// allocation facility, so the file system checker attempted to
// continue with the standard memory allocation facility.
// *Action: None.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07482, 0, "snapshot %(1)s with _snapid value: %(2)s has invalid parent snapshot with _snapid value: %(3)s"
// *Cause: The indicated snapshot does not have a valid parent.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07483, 0, "snapshot with _snapid value: %(1)s has invalid ancestor snapshot"
// *Cause: The indicated snapshot has an invalid ancestor 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.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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, "Metadata structure has non-zero values for various fields\nfor structure:\n%(1)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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\n disk offset: %(4)s\n volume identifier: %(5)s"
// *Document: NO
07494, 0, "ACFS Internal File: %(1)s%(2)s\n file identifier: %(3)s\n disk offset: %(4)s\n volume identifier: %(5)s"
// *Document: NO
07495, 0, "ACFS Internal Structure: %(1)s%(2)s\n file identifier: %(3)s\n disk offset: %(4)s\n volume identifier: %(5)s"
// *Document: NO
07496, 0, "Parent Directory: %(1)s%(2)s\n file identifier: %(3)s\n disk offset: %(4)s\n volume identifier: %(5)s"
// *Document: NO
07497, 0, "Parent Structure: %(1)s%(2)s\n file identifier: %(3)s\n disk offset: %(4)s\n volume identifier: %(5)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, "snapshot with _snapid value: %(1)s has invalid ancestor snapshot (_cycle)"
// *Cause: The indicated snapshot has an invalid ancestor 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.
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, 0, "Snap_Map_Header structure has invalid _SnapConvertPending value\n found: %(1)u, but expected to find: less than %(2)u\nfor structure:\n%(3)s"
// *Cause: The _SnapConvertPending property of the indicated Snap_Map_Header
// metadata structure was incorrect. The _SnapConvertPending 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.
07520, 0, "Snap_Map_Info structure has invalid _SnapInfoFlags value\n found: %(1)s\nfor structure:\n%(2)s"
// *Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info
// metadata structure 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.
07521, 0, "Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: %(1)s\nfor structure:\n%(2)s"
// *Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
// metadata structure 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.
07522, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapParentId: %(3)u, parent snapshot does not exist"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07523, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapParentId value\n found: %(3)u, but expected to find: 0\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07524, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapAncestorIncarn value\n found: %(3)u, but expected to find: 0\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07525, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapAncestorIncarn value\n found: %(3)u, must be less than _SnapIncarnationNumber: %(4)u\nfor structure:\n%(5)s"
// *Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
// metadata structure 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.
07526, 0, "Volume_Disk_Header has invalid _VolStateFlag values.\n found: %(1)s,\n but expected to find: %(2)s \nfor structure:\n%(3)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.
07527, 0, "Volume Disk Header has invalid VolFeatureFlag values \n found: %(1)s \n%(2)s but expected to find: %(3)s \n%(4)sfor structure:\n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07528, 0, "found partially created snapshot: %(1)s (identifier: %(2)u)"
// *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.
07529, 0, "found partially deleted snapshot: %(1)s (identifier: %(2)u)"
// *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.
07530, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid file identifier\n found: %(3)s maximum: %(4)s\nfor structure:\n%(5)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.
07531, 0, "snapshot: (identifier: %(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.
07532, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid _SnapVisibility value found: %(3)u, but expected to find: %(4)u, %(5)u or %(6)u\for structure:\n%(7)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.
07533, 0, "duplicate _SnapIncarnationNumber: %(1)u found for the following snapshots:\n"
// *Cause: The _SnapIncarnationNumber property of the indicated snapshots
// had the same value. _SnapIncarnationNumber values must be unique.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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, 0, "checking snapshot: %(1)s (identifier: %(2)u), %(3)u of %(4)u snapshots"
07536, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid parent snapshot identifier: %(3)u, maximum: %(4)u\nstructure:\n%(5)s"
// *Cause: The indicated snapshot does not have a valid parent.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07537, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid ancestor snapshot: %(3)s (identifier: %(4)u)"
// *Cause: The indicated snapshot has an invalid ancestor 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.
07538, 0, "snapshot: %(1)s (identifier: %(2)u) has invalid ancestor snapshot (_cycle)"
// *Cause: The indicated snapshot has an invalid ancestor 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.
07539, 0, "Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n found: %(1)u\nfor structure:\n%(2)s"
// *Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
// metadata structure 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.
07540, 0, "deleting snapshot: %(1)s (identifier: %(2)u) 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: No further action is needed.
07541, 0, "Snap_Map_header has invalid value for SnapMapFlags\n found: %(1)s\n %(2)s\n but expected to find: %(3)s\n %(4)s\nfor structure: %(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07542, 0, "Snapshot %(1)s (identifier %(2)u) has invalid _SnapStorageCount value found: %(3)u, but expected to find: %(4)u, for structure: \n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07543, 0, "snapshot %(1)s (identifier %(2)u) has invalid _SnapStorageCount value found: %(3)u, but it should not be greater than the total amount of the storage all snapshots have %(4)u, for structure: \n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07544, 0, "Compressed file:\n%(2)s\n has an incorrect value %(1)u\nfor the _compression_unit_size_index property of the _FileEntry\nand cannot be used."
// *Cause: The _FileEntry indicated that compression was enabled but
// the _compression_unit_size_index property was not set to a valid value.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will delete this file. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07545, 0, "Compressed file:\n%(2)s\nhas an incorrect value %(1)u\nfor the compression algorithm and cannot be used."
// *Cause: The file entry indicated that compression was enabled but
// the compression algorithm was not set to a valid value.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will delete this file. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07546, 0, "extent[%(1)u] has invalid _FileOffset value\n found: %(2)s, but expected to find multiple of: %(3)s\nfor compressed file:\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's compression unit size, for compressed 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.
07547, 0, "Compressed file has extents that overlap.\n_FileOffset: %(1)s and\n_FileOffset: %(2)s\nfor file:\n%(3)s"
// *Cause: Two file extents with the _FileOffset values shown, were found
// to use the same disk storage incorrectly.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07548, 0, "Compressed file extent is in an inconsistent state.\n_FileOffset: %(1)s\nfor file:\n%(2)s"
// *Cause: A file extent with the _FileOffset value shown was found to be using
// disk storage incorrectly.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07549, 0, "File has _attributes value indicating compression but this is inconsistent with the volume header.\n found: %(1)s\nFile:\n%(2)s\nshould not be compressed"
// *Cause: The volume header indicated that compression was never enabled but
// a file entry indicating compression was 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.
07550, 0, "The default compression algorithm value %(1)s for the volume is incorrect."
// *Cause: The volume header indicated that compression was enabled but
// the default compression algorithm was not set as expected.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07551, 0, "The Volume_Disk_Header indicates that this file system has an accelerator volume, but the Global_Metadata_Directory structure does not contain an accelerator volume name."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the file system has an accelerator volume associated with it
// then this problem may not be recoverable. The file system will
// have to be restored from a backup copy if the the problem cannot
// be resolved.
07552, 0, "Global_Metadata_Directory structure has no value for _accelerator_device, but contains a non-zero value for _accelerator_GBM_fileid or _accelerator_snap_map_fileid\n _accelerator_GBM_fileid: %(1)s\n _accelerator_snap_map_fileid: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07553 removed - do not reuse message number
07554, 0, "unable to close volume: %(1)s"
// *Cause: An attempt to close a volume failed. Refer to the accompanying
// messages for more information on the error.
// *Action: Correct the problem described in the accompanying messages if
// possible and rerun the command.
07555, 0, "unable to close file: %(1)s"
// *Cause: An attempt to close a file failed. Refer to the accompanying
// messages for more information on the error.
// *Action: Correct the problem described in the accompanying messages if
// possible and rerun the command
07556, 0, "I/O request for (disk offset + size): %(1)s exceeds accelerator volume size: %(2)s\nfor structure:\n%(3)s"
// *Cause: An I/O request was made for data that exceeded the size of the
// accelerator volume.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07557, 0, "found accelerator volume: %(1)s associated with this file system,\nbut accelerator volumes are not supported on this operating system: %(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07558, 0, "unable to process SnapMap metadata on the accelerator volume due to a problem with the primary volume's SnapMap metadata"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07559, 0, "The _FileEntry metadata structure for the accelerator volume storage SnapMap is invalid."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07560, 0, "\nextent[%(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\n _VolId: %(6)s\n _ExtFlags: %(7)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07561, 0, "for file:\n%(1)s\n"
// *Document: NO
07562, 0, "for structure:\n%(1)s\n"
// *Document: NO
07563, 0, "volume: %(1)s had an unsupported logical sector size\n found: %(2)u, but only %(3)u or %(4)u are supported\n"
// *Cause: File system check has identified the metadata inconsistency
// reported in the message.
// *Action: Copy the file system to a volume with a supported sector size
// of 512 or 4096 and rerun fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07564, 0, "Snap_Clone_ID structure has an invalid Version value\n found: %(1)s\nfor structure:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07565, 0, "Snap_Clone_ID structure has an invalid Flags value\n found: %(1)s\nfor structure:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07566, 0, "extent[%(1)u] at _FileOffset value %(2)s has invalid _PhysicalDiskOffset value \n found: %(3)s, but expected to find multiple of: %(4)s\nfor structure:\n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07567, 0, "extent[%(1)u] at _FileOffset value %(2)s has invalid _PhysicalDiskOffset value \n found: %(3)s, but expected to find multiple of: %(4)s\nfor compressed file:\n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07568, 0, "Volume_Disk_Header has incorrect metadata size value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: The MetadataSize property of the indicated Volume_Disk_Header did
// not match supported values.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07569 removed - do not reuse message number
07570, 0, "snap_map_tuple for disk offset: %(1)s conflicts with primary file system\n found: ( %(2)s, %(3)s )\n expected: ( 0, 0 )"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07571, 0, "snap_map_tuple for disk offset: %(1)s not set in Global BitMap\n snap_map_tuple: ( %(2)s, %(3)s )"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07572, 0, "invalid snap_map_tuple found for for disk offset %(1)s,\nfirst value must be less than or equal to second value\n snap_map_tuple: ( %(2)s, %(3)s )"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07573, 0, "orphan snap_map_tuple found for for disk offset %(1)s\n snap_map_tuple: ( %(2)s, %(3)s )"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07574, 0, "snapshot marked for delete: %(1)s (identifier: %(2)u) was still present"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message. A snapshot was marked for delete, but did
// not get deleted due to open files in the snapshot. There are two
// possible causes why the snapshot was not deleted.
// 1. The volume went offline while there were still open files in the
// snapshot.
// 2. The system was unexpectedly shutdown while there were still
// open files in the snapshot.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07575, 0, "command takes no arguments"
// *Cause: The command entered does not take any arguments.
// *Action: Reenter the command with no arguments.
07576, 0, "Compressed file:\n%(2)s\nhas an incorrect value %(1)u\nfor the _range_size value and cannot be used."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07577, 0, "extent structure has incorrect _NextDataExtent value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07578, 0, "extent structure has incorrect _NextDataExtentVolId value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07579, 0, "HEADER extent structure found in _NextDataExtent list for file that does not support range locking\nfor file:\n%(1)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07580 UNUSED and available
07581, 0, "disk storage used %(1)s greater than sum of extents allocation size %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07582, 0, "file _DiskUsage value not equal to disk storage used by DATA extents\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07583, 0, "invalid file entry number found in deferred release file at offset: %(1)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/Translation comment: Do not translate "Remap_Bitmap" for message #07584
7584, 0, "found a %(1)d in the Remap_Bitmap for offset %(2)s where a %(3)d was expected"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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 of size %(2)s bytes failed at disk offset: %(1)s.\n Can not read beyond end of primary volume, size: %(3)s."
// *Cause: An attempt to read metadata failed because the data requested was
// beyond the size of the primary volume for this file system.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07589, 0, "Metadata write at disk offset: %(1)s size: %(2)s bytes"
// *Document: NO
07590, 0, "Metadata write of size %(2)s bytes failed at disk offset: %(1)s.\n Can not write beyond end of primary volume, size: %(3)s."
// *Cause: An attempt to write metadata failed because the write location was
// beyond the size of size of the primary volume for this file system.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07591 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.
/ Message 07593 removed - do not reuse message number
/ Message 07594 removed - do not reuse message number
/ Message 07595 removed - do not reuse message number
/ Message 07596 removed - do not reuse message number
/ Message 07597 removed - do not reuse message number
07598, 0, "Metadata read of size %(2)s bytes failed at disk offset: %(1)s.\n Can not read beyond end of accelerator volume, size: %(3)s."
// *Cause: An attempt to read metadata failed because the data requested was
// beyond the size of the accelerator volume for this file system.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Message 07599 removed - do not reuse message number
07600, 0, "Metadata write of size %(2)s bytes failed at disk offset: %(1)s.\n Can not write beyond end of accelerator volume, size: %(3)s."
// *Cause: An attempt to write metadata failed because the write location was
// beyond the size of size of the accelerator volume for this file
// system.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07605 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/Translation comment: Do not translate "Remap_Bitmap" for message #07608
7608, 0, "found %(1)d incorrectly set bits in the Remap_Bitmap"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/Translation comment: Do not translate "Remap_Bitmap" for message #07609
7609, 0, "found %(1)d incorrectly unset bits in the Remap_Bitmap"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ 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
/ Message 07621 UNUSED and available
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07626 UNUSED and available
/ Message 07627 UNUSED and available
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, 0, "file has invalid _oracle_file_type value\n found: %(1)u\nfor file:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07631, 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: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07632, 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: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07633, 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: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07634, 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: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07635, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find: %(3)s\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07636, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find: %(3)s\nfor file:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07637, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find less than: %(3)s\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07638, 0, "extent[%(1)u] has invalid _Length value\n found: %(2)s, but expected to find less than: %(3)s\nfor file:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Messages [07639 - 07646] UNUSED and available
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
/ Message 07651 UNUSED and available
/ 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.
/ Message 07654 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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
07661, 0, "metadata lookup by file identifier is disabled due to lack of File_Entry_Table context; enter 'primary' or 'snap <snapshot name>' 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 <snapshot name>' 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.
/ Message 07665 UNUSED and available
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: The acfsdbg utility has identified the metadata inconsistency
// reported in the accompanying message.
// *Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
// inconsistencies may point to internal errors. In this case,
// contact Oracle Support Services.
/ Messages [07670 - 07681] UNUSED and available
07682, 0, "file system check has been cancelled"
// *Cause: File system checking was terminated because a signal was received,
// such as Control-C.
// *Action: None
/ Message 07683 UNUSED and available
/ Message 07684 UNUSED and available
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.
/ Message 07686 UNUSED and available
/ Message 07687 UNUSED and available
/ Message 07688 UNUSED and available
/ Message 07689 UNUSED and available
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.
/ Message 07699 UNUSED and available
/ Message 07700 UNUSED and available
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).
/ Message 07702 UNUSED and available
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
/ Messages 7705-7707 removed - do not reuse message numbers
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 fsck (Unix or Linux) or acfschkdsk.exe
// (Windows).
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.
/ Message 07712 UNUSED and available
/ Message 07713 UNUSED and available
/ Message 07714 UNUSED and available
/ Message 07715 UNUSED and available
/ Message 07716 UNUSED and available
/ Message 07717 removed - do not reuse message number
/ Message 07718 UNUSED and available
/ Message 07719 UNUSED and available
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.
/ Message 07730 UNUSED and available
/ Message 07731 UNUSED and available
/ Message 07732 UNUSED and available
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)s maximum: %(2)s\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)s maximum: %(2)s\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)u 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)u 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)u 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)u 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)u 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)u 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)u 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, 0, "directory _Private structure has invalid _dir_bitmap_start value\n found: %(1)s maximum: %(2)s\nfor structure:\n%(3)s"
// *Cause: The _dir_bitmap_start 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.
07762, 0, "Directory contains invalid bitmap block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s"
// *Cause: A bitmap block of the indicated directory file was found in
// the wrong location. Directory bitmap blocks must be located
// contiguously after the first bitmap block.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07763, 0, "Directory bitmap is not contiguous from block %(1)u to block %(2)u at disk offset: %(3)s\nfor file:\n%(4)s"
// *Cause: A discontinuity was seen in the directory bitmap. Directory bitmap
// blocks must be located contiguously after the first bitmap block.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07764, 0, "Directory bitmap has incorrect last block\n found: %(1)u expected: %(2)u\nfor file:\n%(3)s"
// *Cause: The directory bitmap does not end where expected.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07765, 0, "Version 11.2.0.3 or earlier directory contains bitmap block %(1)u at disk offset: %(2)s\nfor file:\n%(3)s"
// *Cause: The directory _Private structure indicates that the directory does
// not have a bitmap, yet a bitmap block was found in 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.
07766, 0, "Directory bitmap does not match state of block %(1)u\n bitmap: %(2)s block: %(3)s\nfor file:\n%(4)s"
// *Cause: The directory bitmap indicates an incorrect state for the directory block.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07767, 0, "Directory bitmap contains non-zero value for bit %(1)u mapping beyond end of directory:\n%(2)s"
// *Cause: The directory bitmap contains a non-zero bit in the range mapping
// blocks beyond the end of 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.
07768, 0, "Directory _Private structure has invalid _dir_bitmap_size value\n found: %(1)s minimum: %(2)s\nfor structure:\n%(3)s"
// *Cause: The _dir_bitmap_size property of the indicated _Private
// directory structure was invalid. Its value did not meet the minimum
// 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.
07769, 0, "Number of bitmap blocks found does not match value of _dir_bitmap_size in directory _Private structure\n found: %(1)s expected: %(2)s\nfor structure:\n%(3)s"
// *Cause: The number of bitmap blocks in the directory does not match the
// number of blocks that were expected.
// *Action: If the ACFS Fixer is currently running, then no further action is
// needed. The ACFS Fixer will resolve the problem. If the ACFS
// Checker is running, then run the ACFS Fixer to resolve the problem.
07770, 0, "System directory _Private structure has invalid on-disk version\n found: %(1)s expected: %(2)s\nfor structure:\n%(3)s"
// *Cause: The on-disk version of the indicated _Private directory structure
// 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.
07771, 0, "directory _Private structure has invalid directory bitmap end value\n found: %(1)s maximum: %(2)s\nfor structure:\n%(3)s"
// *Cause: The calculated end of the directory bitmap 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.
07772, 0, "snapshot '%(1)s' has invalid _SnapLinkParentFenum value\n found: %(2)u maximum: %(3)u\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07773, 0, "snapshot link to non-existent snapshot"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07774, 0, "Global_Metadata_Directory structure has incorrect _remap_table_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07775, 0, "Global_Metadata_Directory structure has incorrect _remap_bitmap_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07776, 0, "Global_Metadata_Directory structure has incorrect _accelerator_remap_table_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07777, 0, "Global_Metadata_Directory structure has incorrect _accelerator_remap_bitmap_fileid value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/ Messages [07778 - 07863] UNUSED and available
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.
/ Messages [07865 - 07899] UNUSED and available
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] <volume>"
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] <volume>"
/ Message 07919 UNUSED and available
07920, 0, "Usage: [%sn|%sN|%sy|%sY] [%so h,v,[a|f]%s] <volume>"
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],x=<filename>%s] <volume>"
07928, 0, "Plug-in configuration file has invalid _FileSize value\n found: %(1)s, but expected to find: %(2)s\nfor file:\n%(3)s"
// *Cause: The _FileSize property of the indicated plug-in configuration 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.
07929, 0, "The %(1)s command is unable to open the storage accelerator volume %(2)s that is associated with this file system."
// *Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the
// specified storage accelerator volume. This could be because the
// ASM disk group containing the storage accelerator volume is
// not mounted.
// *Action: Verify that the ASM disk group containing the storage accelerator
// volume is mounted. Then rerun fsck (Unix or Linux) or
// acfschkdsk.exe (Windows).
07930, 0, "Continuing will result in the storage accelerator volume being removed from the file system, which could leave the file system in an inconsistent and possibly unusable state if critical system metadata is stored on the storage accelerator volume."
// *Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the
// specified storage accelerator volume. This could be because the
// ASM disk group containing the storage accelerator volume is
// not mounted.
// *Action: If the accelerator volume has no known problems, verify that the
// ASM disk group containing the storage accelerator
// volume is mounted. Then rerun fsck (Unix or Linux) or
// acfschkdsk.exe (Windows). Or, if the accelerator volume is
// known to have problems such as disk corruption and you wish
// to have fsck (Unix of Linux) or acfschkdsk.exe (Windows)
// disassociate the accelerator volume from the file system,
// allow it to continue.
07931, 0, "Discontinuing %(1)s as requested"
// *Document: NO
07932, 0, "Volume %s does not contain a valid ACFS storage accelerator."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07933, 0, "Accelerator volume %s is associated with a different file system."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07934, 0, "The file identifier for the accelerator volume storage bitmap is invalid.\n found: %s maximum: %s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07935, 0, "The _FileEntry metadata structure for the accelerator volume storage bitmap is invalid."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07936, 0, "Extent structure has incorrect _VolId value.\n found: %(1)s\nfor structure:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07937, 0, "File extent exceeds accelerator volume size.\n %(1)s\nextent: _FileOffset: %(2)s _Length: %(3)s _PhysicalDiskOffset: %(4)s\nfor file:\n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07938, 0, "Accelerator Global_BitMap has invalid value for number of bits set.\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07939, 0, "Accelerator 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: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07940, 0, "Accelerator Global_BitMap has invalid value for next offset to search.\n found: %(1)s maximum: %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07941, 0, "mismatch between temporary Global_BitMap and on-disk accelerator Global_BitMap"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07942, 0, "Accelerator Global_BitMap has bits incorrectly set for storage beyond the file system size for file:\n%(1)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07943, 0, "The specified volume is an accelerator volume. Cannot proceed."
// *Cause: The volume specified on the command line was an accelerator
// volume. The command requires the primary file system volume.
// *Action: Rerun the command specifying the primary file system volume.
/
07944, 0, "could not set up _VolDiskHdr STRUCT_INFO"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/
07945, 0, "found _DirNode in block: %(1)u at disk offset: %(2)s\nfor directory:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/
07946, 0, "%s has an invalid extent node at disk offset %s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/
07947, 0, "Mount point directory '%(1)s' was specified when device name expected."
// *Cause: The ACFS Checker rejected the mount point because a file system
// device name was expected.
// *Action: Specify the device containing the file system.
/
07948, 0, " %(1)sx <filename> - For accelerator data collected by 'acfsutil meta'"
07949, 0, "Usage: [%(1)sh] [%(2)sr] [%(3)sl] %(4)s [%(5)sx <filename>] <volume>"
07950, 0, "Usage: [%(1)sh] [%(2)sa | %(3)sf] [%(4)sv] [%(5)sy | %(6)sn] [%(7)svv] %(8)s [%(9)sx <filename>] <volume>"
/
07951, 0, "signal %(1)d received"
// *Cause: The ACFS Checker received the indicated interrupt signal.
// *Action: If this was not an operator-initiated abort of the ACFS Checker,
// then correct the problem indicated by the accompanying error
// messages. If the solution is not clear, contact Oracle Support
// Services.
/
07952, 0, "File has _SynchFlags value indicating range locking which is not supported on this file system.\n found: %(1)s\nFile:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07953, 0, "File has invalid _range_size value.\n found: %(1)u expected: %(2)u\nFile:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer will resolve the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07954, 0, "The specified volume is an accelerator volume so cannot be made mountable."
// *Cause: An attempt to force a volume into a mountable state using
// 'fsck.acfs -f' was rejected because the supplied volume was an
// accelerator. An accelerator can only be used in conjunction with
// its primary volume.
// *Action: Reissue the 'fsck.acfs -f' command with the primary volume that
// corresponds to the supplied accelerator volume. If the primary
// volume no longer exists, the accelerator volume cannot be made
// usable.
07955, 0, "read of global directory file entry failed"
// *Cause: A read of the volume metadata during an invocation of 'fsck.acfs -f'
// failed. Accompanying messages provide failure details.
// *Action: Correct the problem indicated by the other messages. If the
// cause of the problem is unclear, contact Oracle Support Services.
/
/ The following message is paired with ACFS-07488 that suggests the file
/ system check as described in the Action of ACFS-07956
/
07956, 0, "accelerator volume found and restored"
// *Cause: During an invocation of 'fsck.acfs -f', the supplied primary
// volume's metadata showed that it had made use of an accelerator
// volume. Both the primary and accelerator volumes have been
// restored, but the metadata has not been verified.
// *Action: The ACFS Fixer has restored the file system, but its metadata must
// be verified using 'fsck.acfs' before attempting to mount it. If the
// accelerator had been repurposed, the file system associated with the
// primary volume cannot be mounted, which will be reported by
// 'fsck.acfs'.
07957, 0, "unable to mount removed file system %s"
// *Cause: An attempt to mount the indicated file system was rejected because
// it had been removed via the acfsutil rmfs utility.
// *Action: To render this file system mountable, run 'fsck.acfs -f'.
07958, 0, " [x=filename] - For accelerator data collected by 'acfsutil meta'"
07959, 0, " [x=filename] - For accelerator data collected by 'acfsutil meta'"
/
07960, 0, "acfsdbg cannot find the ACFS storage accelerator volume"
// *Cause: An attempt to locate the ACFS storage accelartor volume failed.
// Either:
// - the file system did not have an ACFS storage accelerator, or
// - the metadata for locating the ACFS storage accelerator was
// corrupt, or
// - the 'acfsdbg' command was being used to analyze the output of
// the 'acfsutil meta' command, and the sparse copy of the
// ACFS storage accelerator volume was not provided.
// *Action: Retry the 'acfsdbg' command using the '-x' option to specify the
// location of the ACFS storage accelerator volume.
07961, 0, "GBM Lookup Table is corrupt and must be removed."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07962, 0, "GBM Lookup Table has the wrong size.\n found: %(1)u expected: %(2)u"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07963, 0, "GBM Lookup Table is not a multiple of the block size.\n found: %(1)u expected: %(2)u"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07964, 0, "mismatch between GBM Lookup Table block and temporary GBM Lookup Table block for disk offset: %(1)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07965, 0, "Global_Metadata_Directory structure has incorrect _glut_fenum value\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07966, 0, "GBM Lookup Table file entry is not initialized."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/
07967, 0, "'acfsutil meta' files and ACFS file system devices cannot be processed at the same time: %(1)s"
// *Cause: An ACFS Checker attempt was rejected because a mix of 'acfsutil
// meta' metadata collector files and physical ACFS file system
// devices were specified on the command line.
// *Action: Either specify the physical ACFS file system device or the the
// primary and accelerator 'acfsutil meta' files on the command line.
07968, 0, "Remap_BitMap bit set for disk offset %(1)s has no corresponding remapped offset."
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07969, 0, "Remap_Table has incorrect _VolVolumeSize value.\n found: %(1)s, but expected to find: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
07970, 0, "communication error with ACFS kernel driver encountered during setup for online fsck"
// *Cause: An attempt to run online fsck failed due to a communication error
// with the ACFS kernel driver. The accompanying messages provide
// detailed failure information.
// *Action: Correct the problems indicated by the accompanying messages and
// retry the online fsck operation. If the solution is not clear,
// contact Oracle Support Services.
07971, 0, "communication error with ACFS kernel driver encountered during cleanup for online fsck"
// *Cause: An execution of online fsck did not completely correctly because
// a communication error with the ACFS kernel driver occurred during
// cleanup processing. The accompanying messages provided detailed
// failure information. As a result, cleanup of online fsck may be
// incomplete, which may cause failures in other ACFS operations.
// Manual cleanup of online fsck should undertaken as soon as possible
// to ensure continued correct operation.
// *Action: Correct the problems indicated by the accompanying messages and
// remount the ACFS file system on all nodes to complete cleanup of
// online fsck.
07972, 0, "unable to unlink online fsck Copy-On-Write (COW) file: %(1)s"
// *Cause: An execution of online fsck did not complete correctly because
// unlinking the online fsck COW file failed. The accompanying
// messages provide detailed failure information.
// *Action: Manually unlink the indicated online fsck COW file to reclaim
// file system storage and make the online fsck COW file path
// available to subsequent online fsck operations.
07973, 0, "online fsck Copy-On-Write (COW) file %(1)s not accessible on all nodes"
// *Cause: An attempt to run online fsck for an ACFS file system failed
// because one or more nodes with the ACFS file system mounted were
// unable to access the indicated online fsck COW file.
// *Action: Retry the online fsck operation after verifying that all nodes with
// the ACFS file system mounted can access the indicated online fsck
// COW file.
07974, 0, "online fsck already active on the specified ACFS file system"
// *Cause: An attempt to run online fsck for an ACFS file system was rejected
// because it appeared an instance of online fsck was already active
// on the ACFS file system.
// *Action: Retry the online fsck operation after waiting for the other
// instance of online fsck to complete. If there was no other instance
// of online fsck active on the ACFS file system, the ACFS file system
// should be remounted on all nodes to clear this state.
07975, 0, "online fsck already active on another ACFS file system"
// *Cause: An attempt to run online fsck for an ACFS file system was rejected
// because it appeared an instance of online fsck was already active
// on another ACFS file system within the same cluster. More than one
// instance of online fsck is not allowed within the same cluster.
// *Action: Retry the online fsck operation after waiting for the other
// instance of online fsck to complete. If there was no other instance
// of online fsck active within the cluster, the prior ACFS file
// system checked by online fsck should be remounted on all nodes to
// clear this state.
07976, 0, "network communication error encountered during setup for online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system failed
// because a network communication error was encountered between the
// nodes that have the ACFS file system mounted.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for network and membership errors and correct any
// errors. Then retry the online fsck operation after verifying that
// network connectivity exists between all nodes that have the ACFS
// file system mounted and that the ACFS file system is online on all
// of those nodes.
07977, 0, "network communication error encountered during cleanup for online fsck"
// *Cause: An execution of online fsck did not complete correctly because
// a network communication error occurred during cleanup processing
// between the nodes that have the ACFS file system mounted. As a
// result, cleanup of online fsck may be incomplete, which may cause
// failures in other ACFS operations. Manual cleanup of online fsck
// should be undertaken as soon as possible to ensure continued
// correct operation.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for network and membership errors and correct any
// errors. Verify that network connectivity exists between all nodes
// that have the ACFS file system mounted and remount the ACFS file
// system on all nodes to complete cleanup of online fsck.
07978, 0, "I/O error encountered accessing online fsck Copy-On-Write (COW) file"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because online fsck encountered an I/O error while accessing the
// online fsck COW file.
// *Action: Ensure that the ACFS file system containing the online fsck COW
// file is mounted and online on exactly those nodes on which the ACFS
// file system specified for online fsck is mounted. Examine the
// Oracle Kernel Services (OKS) persistent logs on all nodes for
// errors, correct any errors, and then retry the online fsck
// operation.
07979, 0, "unexpected error from ACFS kernel driver encountered during setup for online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system failed
// because of an unexpected error reported from the ACFS kernel
// driver.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for errors, correct any errors if possible, and
// then retry the online fsck operation. If the solution is not
// clear, contact Oracle Support Services.
07980, 0, "unexpected error from ACFS kernel driver encountered during cleanup for online fsck"
// *Cause: An execution of online fsck did not complete correctly because
// an unexpected error during cleanup processing was reported from the
// ACFS kernel driver. As a result, cleanup of online fsck may be
// incomplete, which may cause failures in other ACFS operations.
// Manual cleanup of online fsck should be undertaken as soon as soon
// as possible to ensure continued correct operation.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for errors and correct any errors. Remount the
// ACFS file system on all nodes to complete cleanup of online fsck.
07981, 0, "failed to copy global ACFS metadata to online fsck Copy-On-Write (COW) file"
// *Cause: An attempt to run online fsck for an ACFS file system failed
// because online fsck could not copy global ACFS metadata to the
// online fsck COW file.
// *Action: Examine the Oracle Kernel Services (OKS) persistent logs on all
// nodes. If metadata validation errors are seen in the OKS
// persistent logs, it may not be possible to run online fsck on the
// specified ACFS file system, offline fsck may be required instead.
// If metadata validation errors are not seen in the OKS persistent
// logs, resolve any errors indicated in the OKS persistent logs, and
// then retry the online fsck operation.
07982, 0, "incorrect kernel state for online fsck encountered during setup for online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system failed
// because the state data for online fsck maintained in the ACFS
// kernel driver was inconsistent. This is an internal error.
// *Action: Contact Oracle Support Services.
07983, 0, "incorrect kernel state for online fsck encountered during cleanup for online fsck"
// *Cause: An execution of online fsck did not complete correctly because
// the state data for online fsck maintained in the ACFS kernel driver
// was inconsistent during cleanup processing. This is an internal
// error.
// *Action: Contact Oracle Support Services.
07984, 0, "online fsck aborted because file system mounted on a new node"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because the ACFS file system was mounted on a new node while online
// fsck was running.
// *Action: Retry the online fsck operation.
07985, 0, "communication error with ACFS kernel driver encountered while querying runtime status for online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because a query to the ACFS kernel driver for the runtime status
// for online fsck encountered a communcation error. The accompanying
// messages provide detailed failure information.
// *Action: Correct the problems indicated by the accompanying messages and
// retry the online fsck operation. If the solution is not clear,
// contact Oracle Support Services.
07986, 0, "online fsck Copy-On-Write (COW) file is full"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because the online fsck COW file ran out of space.
// *Action: Retry the online fsck operation with a larger COW file size.
07987, 0, "unknown runtime error encountered during online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because an unknown runtime error was encountered.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for online fsck errors. These online fsck errors
// will indicate whether further action is required. Then retry the
// online fsck operation. If the error persists, contact Oracle
// Support Services.
07988, 0, "network communication error encountered during online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because a network communication error was encountered between the
// nodes that have ACFS file ssytem mounted.
// *Action: Examine the alert logs and Oracle Kernel Services (OKS) persistent
// logs on all nodes for network and membership errors and correct any
// errors. Then retry the online fsck operation after verifying that
// network connectivity exists between all nodes that have the ACFS
// file system mounted and that the ACFS file system is online on all
// of those nodes.
07989, 0, "online fsck used %(1)d bytes of Copy-On-Write (COW) file"
07990, 0, "unexpected non-empty volume logs encountered during online fsck"
// *Cause: An attempt to run online fsck for an ACFS file system was aborted
// because non-empty volume logs were encountered unexpectedly.
// *Action: Retry the online fsck operation. If the error persists, contact
// Oracle Support Services.
07991, 0, "The length of the online fsck Copy-On-Write (COW) file path exceeds %u."
// *Cause: An attempt to run online fsck was rejected because the specified
// online fsck COW file path exceeded the maximum length displayed in
// the message.
// *Action: Retry the online fsck operation specifing a COW file whose path
// name is less than the maximum length displayed in the message.
07992, 0, ""
07993, 0, "Validate a mounted ACFS file system"
07994, 0, "Usage: [%(1)sh] [%(2)sv] [%(3)svv] %(4)s %(5)sO %(6)sC <COW file path> %(7)sS <COW file size> <mountpoint>"
07995, 0, " %(1)sO - Perform online fsck for mounted ACFS file system"
07996, 0, " %(1)sC <COW file path> - Path to online fsck Copy-On-Write (COW) file"
07997, 0, " %(1)sS <COW file size> - Size of online fsck Copy-On-Write (COW) file"
07998, 0, " mountpoint - ACFS mountpoint path"
07999, 0, "unexpected ACFS Checker/Fixer assert: \"%(1)s\", %(2)s: %(3)s: %(4)d"
// *Cause: An unexpected situation has occurred.
// *Action: Contact Oracle Support Services.
08000, 0, "unable to create online fsck Copy-On-Write (COW) file: %(1)s"
// *Cause: An attempt to run online fsck was rejected because an error occurred
// while creating the indicated COW file. The accompanying messages
// provide detailed failure information.
// *Action: Correct the problems indicated by the accompanying messages and
// retry the online fsck operation. If the solution is not clear,
// contact Oracle Support Services.
08001, 0, "unable to determine ACFS mountpoint for online fsck Copy-On-Write (COW) file: %(1)s"
// *Cause: An attempt to run online fsck was rejected because the indicated
// online fsck COW file was not located within an ACFS file system.
// *Action: Retry the online fsck operation specifying an online fsck COW file
// located within an ACFS file system.
08002, 0, "_NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that is not valid\n _NextDeferredListLink: %(1)s\n snapshot: %(2)s (identifier: %(3)u)\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08003, 0, "Deferred_Delete_Storage_List has invalid file identifier for _PrevDeferredListLink:\n found: %(1)s expected: %(2)s\nfor structure:\n %(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08004, 0, "unable to process Deferred_Delete_Storage_List data for structure:\n%(1)"
// *Cause: File system checking has identified metadata inconsistencies.
// The accompanying messages provide further details.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08005, 0, "Deferred_Delete_Storage_List incorrectly contains an entry for a read only snapshot:\n file identifier: %(1)s\n snapshot: %(2)s (identifier: %(3)u)\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08006, 0, "_NextDeferredListLink on Deferred_Delete_Storage_List references a file identifier that exceeds the maximum value supported for this file system\n _NextDeferredListLink: %(1)s\n file identifier: %(2)s maximum: %(3)s\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08007, 0, "%(1)s has determined that there is a loop within a Deferred_Delete_Storage_List\nfor file:\n%(2)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08008, 0, "Deferred_Delete_Storage_List structure for accelerator volume has invalid values:\n _PrevDeferredListLink: %(1)s\n _NextDeferredListLink: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08009, 0, "Deferred_Delete_Storage_List for snapshot: %(1)s (identifier: %(2)u) incorrectly contains an entry for a File_Entry_Table: %(3)s\nfor structure:\n%(4)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08010, 0, "Deferred_Delete_Storage_List entry contains an invalid _DRSLSequenceNumber\n found: %(1)s\n maximum: %(2)s\nfor file:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08011, 0, "_NextDeferredListLink on Deferred_Delete_Storage_List references a snapshot that does not exist\n _NextDeferredListLink: %(1)s\n snapshot identifier: %(2)u\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08012, 0, "Deferred_Delete_Storage_List has invalid file identifier for_NextDeferredListLink: %(1)s\n snapshot identifier: %(2)u\n found: %(3)s minimum: %(4)s\nfor structure:\n%(5)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08013, 0, "Deferred_Delete_Storage_List contains an entry that was previously referenced by a directory or other ACFS structure\n _NextDeferredListLink: %(1)s\n file identifier: %(2)s\nfor structure:\n%(3)s"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
/
08014, 0, "Usage: [%sn|%sN|%sy|%sY] [%so h,v,vv,[a|f]%s] <volume>"

08015, 0, "snap name: %(1)s snap id: %(2)d current snap: %(3)d snaps to check: %(4)d snapAUsCount: %(5)s"
// *Document: NO

08016, 0, "multiple invalid snap_map_tuples found; number found: %d"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message. The number of instances is indicated here
// in lieu of flooding the output by displaying message ACFS-07414
// for each occurrence.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08017, 0, "multiple snap_map_tuples with (0,0) found where a non-zero value was expected; number found: %d"
// *Cause: File system checking has identified the metadata inconsistency
// reported in the message. The number of instances is indicated here
// in lieu of flooding the output by displaying message ACFS-07448
// for each occurrence.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem. If the
// message was generated by the ACFS Checker, then run the ACFS Fixer
// to resolve the problem. Frequent metadata inconsistencies may
// point to internal errors. In this case, contact Oracle Support
// Services.
08018, 0, "allocated but unused storage of %d MB found"
// *Cause: File system checking has identified unreferenced snapshot storage
// that could be freed.
// *Action: If the message was generated by the ACFS Fixer, then no further
// action is needed. The ACFS Fixer has resolved the problem and freed
// the indicated storage. If the message was generated by the ACFS
// Checker, then run the ACFS Fixer to free the storage.

/ Messages [8019 - 08999] UNUSED and available
/
/ End fsck.acfs/acfschkdsk 07000-08999
/

/ Messages for advmutil

/ Messages 9000 to 9039 are Windows specific and are used to mount, dismount,
/ and list *NON* ACFS file systems ONLY.

/ Messages tagged "*Document: NO" are OFSMSG_INFO in the code and so no
/ message number is displayed to the user.

09000, 0, "Invalid drive letter specification: %s"
// *Document: NO
09001, 0, "Error reading ORACLE_HOME environmental variable"
// *Document: NO
09002, 0, "NOTE: The volume %s contains an ACFS filesystem"
// *Document: NO
09003, 0, "Executing: %s"
// *Document: NO
09004, 0, "CreateProcess of acfsmountvol failed, %s"
// *Cause: The 'advmutil mount' command failed because a required process
// could not be created. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09005, 0, "Error running %s"
// *Cause: The 'advmutil mount' command failed because a required process
// could not be executed. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09006, 0, "Error opening volume %s"
// *Cause: The advmutil command failed because the indicated file could not
// be created. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
/ Message 9007 removed - do not reuse message number
/ Message 9008 removed - do not reuse message number
09009, 0, "Error closing volume %s"
// *Cause: The 'advmutil mount' or 'advmutil list' command encountered an error
/ while attempting to close the indicated file.
// *Action: None. The command completed successfully. The
// indicated file was closed by the operating system.
09010, 0, "Error locking volume %s"
// *Cause: The 'advmutil dismount' command failed while attempting to lock
// the indicated volume. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09011, 0, "Error dismounting file system on volume %s"
// *Cause: The 'advmutil dismount' command failed. The accompanying messages
// provide detailed failure information.
// *Action: Ensure that the indicated file system is not in use. Examine the
// accompanying messages, resolve the indicated problems, and then
// retry the operation.
09012, 0, "Error opening the Windows Registry"
// *Cause: The 'advmutil list' command failed while opening the Windows
// Registry. This is an internal error.
// *Action: Contact Oracle Support Services.
09013, 0, "Error reading the Windows Registry"
// *Cause: The 'advmutil list' command failed while reading the Windows
// Registry. This is an internal error.
// *Action: Contact Oracle Support Services.
09014, 0, "Drive Letter ASM Volume\n====================================================="
// *Document: NO
09015, 0, "The volume %s was not found. Verify the diskgroup is mounted and the volume is enabled."
// *Cause: The 'advmutil mount' command failed because the indicated ADVM
// volume was not found.
// *Action: Run the command 'asmcmd volinfo --all'. If the indicated volume is
// listed as 'DISABLED', run the command 'asmcmd volenable' and then
// retry the mount operation. If the indicated volume is not listed,
// verify the ASM setup, and then create and mount the ADVM volume.
09016, 0, "Error mounting volume %s on drive %s"
// *Cause: The 'advmutil mount' command failed to mount the specified volume.
// The accompanying messages provide detailed failure information.
// *Action: Ensure that the user issuing the mount command has write
// permissions on the drive. Examine the accompanying messages,
// resolve the indicated problems, and then retry the operation.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09017, 0, "ASM volume %s mounted on %s"
// *Document: NO
09018, 0, "Error broadcasting mount of volume %s on drive %s"
// *Cause: The 'advmutil mount' command failed because it was unable to
// broadcast device change information to other devices in
// the system. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09019, 0, "Error opening volume on %s"
// *Cause: The 'advmutil dismount' command failed to open the indicated file.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09020, 0, "Error dismounting %s"
// *Cause: An 'advmutil dismount' operation failed to remove a symbolic link.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09021, 0, "Error broadcasting dismount of %s"
// *Cause: The 'advmutil dismount' command failed because it was unable to
// broadcast device change information to other devices in
// the system. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09022, 0, "ASM volume dismounted from %s"
// *Document: NO
09023, 0, "Volume %s is currently assigned to drive %s"
// *Document: NO
09024, 0, "Drive letter %s is currently assigned to volume %s"
// *Document: NO
09025, 0, "Failed to update the Windows Registry for volume %s on drive %s"
// *Cause: An attempt to store data in the Windows registry failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09026, 0, "Drive letter %s assigned to %s"
// *Document: NO
09027, 0, "Error deleting the drive letter assignment %s"
// *Cause: An 'advmutil dismount' command failed because the specified drive
// letter could not be removed from a volume assignment.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09028, 0, "Assignment for drive letter %s not found"
// *Cause: An 'advmutil dismount' command failed because the indicated drive
// letter could not be found.
// *Action: Retry the 'advmutil dismount' command specifying the correct drive
// letter.
09029, 0, "Drive letter %s unassigned from %s"
// *Document: NO
09030, 0, "Error unassigning drive letter %s from volume %s"
// *Cause: An advmutil dismount failed because it could not unassign a drive
// letter. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09031, 0, "The volume %s contains an ACFS filesystem. Use acfsmountvol, or use acfsutil rmfs to remove the ACFS file system"
// *Document: NO
/ Message 9032 removed - do not reuse message number
/ Message 9033 removed - do not reuse message number
09034, 0, "Error taking %s offline"
// *Cause: An 'advmutil dismount' command failed to offline the specified
// mount point.
// *Action: Verify that the mount point is online via the 'asmcmd volinfo'
// command. If it is, contact Oracle Support Services. If the mount
// point is already offline, no further action is required.
09035, 0, "Error unlocking %s"
// *Cause: An 'advmutil dismount' command failed because it could not unlock
// the specified file system. The accompanying messages provide
// detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09036, 0, "Error bringing %s online"
// *Cause: An 'advmutil mount' command failed because it could not bring the
// specified file system online. The accompanying messages provide
// detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09037, 0, "Error reading reparse point %s"
// *Cause: An 'advmutil dismount' command failed because it could not read the
// specified reparse point. The accompanying messages provide detailed
// failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
09038, 0, "Volume %s contains an ACFS filesystem and must be dismounted with acfsdismount"
// *Document: NO
09039, 0, "Mount point %s is already in use"
// *Document: NO
/
/ 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 obsolete
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"
/ WPTG: Do not translate "compatible.advm" in the following message.
09061, 0, "Device: %s, 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 <name> - list named tunable parameter"
09079, 0, "tune <name>=<val> - set named tunable parameter to <val>\n (root/admin access required)"
09080, 0, "volinfo [<volume>] - print ADVM volume information\n (one descriptor per line format)"
/ 09081 obsolete - see 09090
09081, 0, "volinfo [%sL] [<volume>] - print ADVM volume information\n (colon separated format)"
09082, 0, "mount /all - mount all registered ADVM volumes"
09083, 0, "mount [/register] {<drive_letter> | <mount_point>} - mount volume\n and optionally enter it into\n the system registry"
09084, 0, "mount /dg=<disk group> - mount all volumes in the diskgroup"
09085, 0, "dismount [/unregister] /all - dismount all registered volumes and\n optionally unregister them"
09086, 0, "dismount [/unregister] {<drive_letter> | <mount_point>} - dismount\n volume and optionally unregister it"
09087, 0, "dismount [/unregister] /dg=<disk group> - dismount all volumes\n in the specified disk group"
09088, 0, "list /registry - list all registered ADVM volumes"
09089, 0, "canonical <volume> - print operating system standard name\n for ADVM volume."
09090, 0, "volinfo [%sl] [<volume>] - print ADVM volume information\n (colon separated format with labels)"

09091, 0, "volinfo [%sL] [<volume>] - print ADVM volume information\n (space separated format - no labels)"
09092, 0, "Current volume stage: %s"

/
/ 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, "Driver %s 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, "Driver %s failed to unload."
// *Cause: An unknown error has occurred when trying to unload the driver.
// *Action: Check system specific logs (/var/log/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 <options>'. 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 does not exist."
// *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: Syntax error or help [-h] option was passed.
// *Action: Use syntax as specified in the 'Usage' message.
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.
09168, 0, "The CRS query \"%s\" cannot be parsed."
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
09169, 0, "The CRS attribute value specification \"%s\" is invalid."
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
09170, 0, "The file system's CRS resource name \"%s\" is invalid."
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
09171, 0, "The CRS resource for the file system on device %s cannot be retrieved"
// *Cause: Informational
// *Action: Analyze the error messages that precede this message.
09172, 0, "The CRS resource for the file system on device %s cannot be registered"
// *Cause: Informational
// *Action: Analyze the error messages that precede this message.
09173, 0, "The srvctl command line \"%s\" failed to execute. (%d)"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
09174, 0, "unable to communicate with CRS"
// *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.
09175, 0, "Invalid trace level. Valid values for trace level are 0, 1 or 2."
// *Cause: An invalid trace level was provided.
// *Action: Use a supported trace level: 0, 1, or 2.
09176, 0, "Entering '%s'"
// *Cause: Informational.
// *Action: None.
09177, 0, "Return from '%s'"
// *Cause: Informational.
// *Action: None.
09178, 0, "Return code = %s"
// *Cause: Informational.
// *Action: None.
09179, 0, "Command executed: '%s', output = '%s'"
// *Cause: Informational.
// *Action: None.
09180, 0, "Sub-command is '%s'"
// *Cause: Informational.
// *Action: None.
09181, 0, "Kernel version is '%s'"
// *Cause: Informational.
// *Action: None.
09182, 0, "Variable '%s' has value '%s'"
// *Cause: Informational.
// *Action: None.
09183, 0, "Query = '%s'"
// *Cause: Informational.
// *Action: None.
09184, 0, " %s [-h] [-s | -v | -t <0,1,2>]"
// *Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09185, 0, " %s [-h] [-s | -v | -t <0,1,2>] [-l <directory>]"
// *Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09186, 0, " Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]"
// *Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09187, 0, " Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l <location>]"
// *Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09188, 0, "cannot use the trace option with the silent or verbose options"
// *Cause: Conflicting options were specified.
// *Action: Specify only one of -s, -v, and -t.
09189, 0, " [-t <0,1,2> ] - trace level"
// *Cause: Either a syntax error or unknown option was specified, or the help (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09190, 0, "User group '%s' does not exist."
// *Cause: The group name is required to create ADVM/ACFS devices with
// the correct attributes. The group name could not be found in the
// /etc/group file nor in the various remote services like
// LDAP, AD, NIS/Yellow Pages, DNS, etc.
// *Action: Ensure that the required group exists, then re-run the command.
09191, 0, " Usage: acfsroot version_check [-h] [-t <0,1,2>]"
// *Cause: Either a syntax error or unknown option was specified, or the help
// (-h) option was specified.
// *Action: Use syntax as specified in the 'Usage' message.
09192, 0, "unknown installation mode: %s"
// *Cause: An attempt to execute the 'acfsroot install' command failed because
// an unknown mode was specified.
// *Action: Consult the documentation and reissue the command specifying a
// supported installation mode.
09193, 0, "Use of the -m flag is not supported in this OS."
// *Cause: An attempt was made to install ACFS with the -m flag in an
// operating system that did not support Oracle Database Appliance
// modes.
// *Action: Installation of ACFS cannot proceed with the -m flag in the current
// operating system. Reissue the command without the -m flag.
/ acfsdriverstate
09194, 0, "unable to query the WMI service to identify the Windows OS Version"
// *Cause: A requested management operation failed because an attempt to obtain
// the current Windows OS version from the Windows Managment
// Instrumentation (WMI) Service in order to determine whether
// ACFS/ADVM drivers were supported was not successful.
// *Action: Use the Windows Task Manager to verify the status of the WMI service
// (winmgmt). After the WMI service is verified to be enabled and
// running, retry the command.
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.
/ Message 09202 UNUSED and available
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, "usage: %s [-h] [-orahome <home_path>] {installed | loaded | version | supported | validate} [-s]"
// *Cause: Syntax error or help [-h] option was passed.
// *Action: Use syntax as specified in the 'Usage' message.
/Obsolete: 09206 is superseded by message 09205
09206, 0, "usage: %s [-orahome <ORACLE_HOME>] {installed | loaded | version | supported} [-s]"
// *Cause: Syntax error.
// *Action: Use syntax as specified in the 'Usage' message.
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.
09210, 0, "The ADVM/ACFS drivers are supported but have not been verified on this Operating System version."
// *Cause: The drivers have not been explicitly tested on this operating system
// version but are expected to work properly.
// *Action: This message is informational.
09211, 0, "usage: %s [-h] [-orahome <home_path>] {installed | loaded | version [-v]| supported [-v]} [-s]"
// *Cause: Syntax error or help [-h] option was passed.
// *Action: Use syntax as specified in the 'Usage' message.
09212, 0, " Driver build version = %s."
09213, 0, "Configuration file '%s' in the /boot directory does not exist or cannot be read."
// *Cause: An attempt to check for compatible kernel was unable to read required /boot
// configuration data.
// *Action: Verify user permissions, that the configuration file is accessible,
// and then retry the command.
09214, 0, " -v: Verbose"
/
/ acfsload
09225, 0, "Failed to start OKS persistent logging."
// *Cause: The drivers were successfully loaded but Oracle Kernel Services
// (OKS) persistent logging failed to start.
// *Action: run "acfsutil plogconfig -d <GridHome>" 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 <options>" to install the correct drivers.
/ Message 09227 UNUSED and available
09228, 0, "usage: %s [-h] {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 ('srvctl status 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.<diskgroup>.<volume>.acfs"
09268, 0, " _ORA_VOLUME_DEVICE <ADVM_device_name>"
09269, 0, " _ORA_MOUNTPOINT_PATH <mount_point_name>"
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.
/ Messages 9276 - 9288 UNUSED and available
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.
09291, 0, "Waiting for the Windows 'sc stop %s' command to complete."
// *Cause: Informational. System activity is preventing the driver from stopping.
// *Action: If the driver does not unload, a node reboot may be necessary
09292, 0, "Warning: A newer version of ACFS software is available in Oracle home %s."
// *Cause: A version check prompted by user request or a maintenance operation
// determined that updated software is available in the indicated
// Oracle home.
// *Action: To ensure the benefits of the latest fixes and performance
// improvements, the available drivers should be installed at the next
// maintenance opportunity. Use the command 'rootcrs.pl -updatedriver'
// to update all drivers on the system.
09293, 0, "Kernel and command versions do not match."
// *Cause: A requested version check or a system monitor has found that the
// installed tools are out of sync with the installed kernel modules.
// This may cause interoperability issues.
// *Action: To ensure the benefits of the latest fixes and performance
// improvements, and to remove potential interoperability issues,
// the installed software should be updated as soon as possible. Use
// the command 'rootcrs.pl -updatedriver' to update all driver software
// on the system, or use 'acfsroot install' to update just ACFS.
09294, 0, "updating file %s"
09295, 0, "failed to open file %s"
// *Cause: A requested action failed to complete because the indicated
// file could not be opened.
// *Action: Verify the file exists and is accessible by the current user,
// examine previous error messages, address issues, and retry
// the command.

/
/ 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.
/ Message 09302 UNUSED and available
09303, 0, "No installation files found for OS kernel version %s."
// *Cause: If '-l' (distribution directory) was specified, the directory
// may not be valid.
// *Action: Choose a proper distribution location version.
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 <options>'.
// 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 build number = %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 <directory>]"
09332, 0, " [-l <directory>] - location of the installation directory"
09333, 0, " (if not the default location)"
09334, 0, " (comma separated if more than one location specified)"
09335, 0, " [-k <version>] - install kernel version number"
09336, 0, " (if not the current kernel version)"
/ Message 09337 is obsolete and used in earlier releases.
09337, 0, "Usage: acfsroot <install|uninstall|version_check|enable|disable> [arguments]"
/ Message 09338 is obsolete and used in earlier releases.
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 <location>]"
// *Cause: Syntax error or help [-h] option was passed.
// *Action: Use syntax as specified in the 'Usage' message.
/ Message 09386 obsolete is not available.
09386, 0, " For more information, use acfsroot <command> -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.
09389, 0, "ORACLE_HOME is not set to the location of the Grid Infrastructure home."
// *Cause: The ORACLE_HOME environment variable was not set correctly.
// *Action: Make sure that the ORACLE_HOME environment variable is set to the
// location of the Grid Infrastructure home and that it is properly
// exported.
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 <file_name>"
// and then retry the operation.
09427, 0, "Failed to unload ADVM/ACFS drivers. A system reboot is recommended."
// *Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due
// to an unanticipated condition or configuration. The operating
// system state did not allow the driver to be unloaded successfully.
// *Action: Reboot the system to reestablish the operating system environment.
09428, 0, "Failed to load ADVM/ACFS drivers. A system reboot is recommended."
// *Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due
// to an unanticipated condition or configuration. The operating
// system state did not allow the driver to be unloaded successfully.
// *Action: Reboot the system to reestablish the operating system environment.
09429, 0, "Failed to install ADVM/ACFS files."
// *Cause: An unexpected condition has been detected. The files were previously
// verified to exist.
// *Action: Check the file permissions. Contact Oracle Support if the problem
// cannot be resolved.
09430, 0, "ADVM/ACFS is not supported on this OS configuration: '%s'"
// *Cause: Attempting to install or configure ADVM/ACFS failed because
// ADVM/ACFS device drivers have not been ported to this OS
// configuration.
// *Action: For supported configurations, refer to MOS note (Doc ID 1369107.1):
// ACFS Support On OS Platforms (Certification Matrix).
/09431 - 09439 AVAILABLE
09440, 0, "Usage: %s {/i | /u} {/a | /o | /l} [<path>]"
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 Oracle Kernel Services (OKS) driver"
// *Cause: Syntax error.
// *Action: Use syntax as specified in the 'Usage' message.
09446, 0, "<path> 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: Attempting to install or configure ADVM/ACFS failed because
// ADVM/ACFS device drivers have not been ported to this OS
// version.
// *Action: For supported versions, refer to MOS note (Doc ID 1369107.1)
// ACFS Support On OS Platforms (Certification Matrix).
09460, 0, "Missing symbols: '%s'"
// *Cause: Informational.
// *Action: None.

/
/
/ acfsroot
09500, 0, "Location of Oracle Home is '%s' as determined from the internal configuration data"
// *Cause: Informational.
// *Action: None.
09501, 0, "Location of Oracle Home is '%s' as determined from the ORACLE_HOME environment variable"
// *Cause: Informational.
// *Action: None.
09502, 0, "Location of Oracle Home is '%s' as determined from the location of the Oracle library files"
// *Cause: Informational.
// *Action: None.
09503, 0, "ADVM and ACFS driver media location is '%s'"
// *Cause: Informational.
// *Action: None.
09504, 0, "Copying file '%s' to the path '%s'"
// *Cause: Informational.
// *Action: None.
09505, 0, "Using acfsutil executable from location: '%s'"
// *Cause: Informational.
// *Action: None.
09506, 0, "The files '%s' and '%s' are the same, not copying."
// *Cause: Informational. The file was not copied because the target and
// source point to the same file.
// *Action: None.
09507, 0, "Searching the alternative location: '%s'"
// *Cause: Informational.
// The installation files were not found in the specified location.
// A likely path containing that location will be searched.
// *Action: None.
09508, 0, "ACFS installation aborted (component %s)."
// *Cause: Installation was aborted due to an error.
// *Action: See preceding error message for more information.

/ acfsutil compression
09520, 0, " compression status: ENABLED"
09521, 0, " compression status: DISABLED (volume may contain compressed files)"
09522, 0, "invalid compression operation %s"
// *Cause: An attempted compression operation was rejected because the
// specified command syntax was invalid.
// *Action: Refer to the command usage displayed with the message and resissue
// the command with correct syntax.
09523, 0, "Invalid compression algorithm specified. The only valid choice is 'lzo'. "
// *Cause: An attempted compression operation was rejected because the
// specification of the compression algorithm was invalid. The only
// algorithm currently supported is 'lzo'.
// *Action: Retry the command specifying the compression algorithm 'lzo'.
09524, 0, "unable to modify volume compression configuration on the local node"
// *Cause: A request to modify the compression configuration of the volume
// failed. This message is accompanied by other messages providing
// details on the error.
// *Action: Examine the accompanying messages, correct the indicated problems
// and retry. If unable to proceed, contact Oracle Support Services.
09525, 0, "Only regular files may be compressed."
// *Cause: An attempted compression operation was rejected because the
// specified pathname did not specify a regular file.
// *Action: Retry the command specifying the pathname of a regular file.
09526, 0, "unable to obtain file compression information"
// *Cause: An attempt to read the compression information for the file
// failed. This message is accompanied by other messages providing
// details on the error.
// *Action: Examine the accompanying messages, correct the indicated problems
// and retry. If unable to proceed, contact Oracle Support Services.
09527, 0, "Compression Unit size: %u"
09528, 0, "The file %s is not compressed."
09529, 0, "Storage used is %u%% of what the uncompressed file would use."
09530, 0, "Storage used is the same as what the uncompressed file would use."
09531, 0, "Disk storage saved: %s"
09532, 0, "File is empty."
09533, 0, "Disk storage used: %s"
09534, 0, " compression status: DISABLED"
09535, 0, "The requested compression configuration operation failed on a remote node."
// *Cause: An attempt to change the compression configuration for the
// volume failed on a remote node in the cluster. The probable cause
// is a lack of necessary OS resources.
// *Action: Retry the command. If unable to proceed, contact Oracle Support
// Services.
09536, 0, "The Oracle ADVM compatibility attribute for the disk group is less than the required version 12.2 for 'acfsutil compress' commands."
// *Cause: The 'acfsutil compress' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Ensure that your compatible.advm setting is at least 12.2.0.0.0 and
// then re-issue the command.
09537, 0, "Entire file is compressed."
09538, 0, "File byte range %u to %u will be compressed asynchronously."
09539, 0, "'acfsutil compress' commands are not supported on this OS configuration: '%s'"
// *Cause: The 'acfsutil compress' command was rejected because the current
// version of the OS does not support compression.
// *Action: For supported versions, refer to MOS note (Doc ID 1369107.1)
// ACFS Support On OS Platforms (Certification Matrix).
09540, 0, "Option '%s' is not currently supported for compressed files."
09541, 0, "File is not scheduled for asynchronous compression."
09542, 0, "The command was not attempted because asynchronous compression is very active on file '%s' ."
// *Cause: The 'acfsutil defrag file' command was unable to make progress
// because the file was busy being modified by the asynchronous
// compression mechanism.
// *Action: Wait until the file is no longer being modified by the
// asynchronous compression mechanism and re-issue the command. Use
// 'acfsutil compress info' to see if asynchronous compression is
// active on a compressed file.
09543, 0, "Another 'defrag file' command is already active for file '%s'."
09544, 0, "Invalid files or directories found: '%s'"
// *Cause: During verification of the directory from which ACFS installs
// kernel modules (usm), unexpected files or directories were found.
// *Action: Remove the invalid files or directories, and then retry the
// operation.
09545, 0, "Verification error: kernel module '%(1)s' is incompatible with the installed kernel version '%(3)s'. It is compatible with kernel version '%(2)s'."
// *Cause: An attempted command failed because of kernel module
// incompatibility. The version of the indicated kernel
// module is not compatible with the installed kernel.
// *Action: Revert any manual modifications to the usm install directories,
// and then retry the operation. If a problem is still reported,
// re-install any applied patches or the base software.
09546, 0, "Incorrect permissions for file '%(1)s'. Expected: (user=%(2)s, group=%(3)s, mode=%(4)s), Found: (user=%(5)s, group=%(6)s, mode=%(7)s)"
// *Cause: An attempt to install ACFS drivers failed because the indicated
// permissions were incorrect on the indicated file.
// *Action: Correct the permissions as indicated and retry the operation.
09547, 0, " Driver available build number = %s."
09548, 0, " Driver available build version = %s."
09549, 0, " Kernel and command versions."
09550, 0, " An error occurred while retrieving the kernel and command versions."
// *Cause: An attempt to retrieve the ACFS driver version information failed
// because an error occurred when acfsdriverstate command invoked the
// command 'acfsutil version -v'.
// *Action: Execute the command 'acfsutil version -v' on its own, and if it
// succeeds, retry the command 'acfsdriverstate version -v'.
09551, 0, "Command file '/sbin/weak-modules' does not exist or it is not an executable."
// *Cause: An attempt to check Kernel Application Binary Interface (KABI)
// compatibility failed because the command '/sbin/weak-modules' could
// not be found, or the current user did not have permission to execute
// it. This indicates a problem with the Linux installation.
// *Action: Resolve the Linux installation problem, ensuring that the command
// '/sbin/weak-modules' is installed, and that the file has the
// appropriate permissions, and then retry the operation.
09552, 0, "Command '/sbin/weak-modules' returned a potential compatibility issue. For more details execute the command '%s'."
// *Cause: The command '/sbin/weak-modules' found incompatibilities between the
// running kernel and the ACFS/ADVM drivers.
// *Action: Run the indicated command for details. Contact Oracle Support
// Services to determine whether updated ACFS/ADVM drivers are
// available for the current operating system and architecture.
09553, 0, "Operating System: %s"
// *Cause: Informational.
// *Action: None.
09554, 0, "Machine Architecture: %s"
// *Cause: Informational.
// *Action: None.
09555, 0, "Operating system name and information: %s"
// *Cause: Informational.
// *Action: None.
09556, 0, "Release package: %s"
// *Cause: Informational.
// *Action: None.
09557, 0, "Version: %s"
// *Cause: Informational.
// *Action: None.
09558, 0, "Variable _ORA_USM_NOT_SUPPORTED is defined: %s"
// *Cause: Informational.
// *Action: None.
09559, 0, "Running in a local container: %s"
// *Cause: Informational.
// *Action: None.
09560, 0, "Configuration file %s in the /boot directory is accessible."
// *Cause: Informational.
// *Action: None.
09561, 0, "USM Drivers are KABI Compatible."
// *Cause: Informational.
// *Action: None.
09562, 0, "Install Path: %s"
// *Cause: Informational.
// *Action: None.

/ acfshanfs command
09600, 0, "Usage: %s [-h] {-nfsv4lock} {-volume <enabled_volume_device>} [-force]"
// *Cause: Informational.
// *Action: None.
09601, 0, "Usage: %s [-h] {-nfsv4lock}"
// *Cause: Informational.
// *Action: None.
09602, 0, "Installation cannot proceed: path '%s' is mounted or it is a symlink."
// *Cause: An attempt to validate the path found that the indicated path
// was mounted or was a symlink.
// *Action: Unmount the file system or remove the symlink.
09603, 0, "The script will do the following actions:"
// *Cause: Informational.
// *Action: None.
09604, 0, " - Update the operating system startup procedure so that NFS does not automatically start."
// *Cause: Informational.
// *Action: None.
09605, 0, " Management of the NFS daemons will be moved to Oracle Clusterware."
// *Cause: Informational.
// *Action: None.
09606, 0, " - Format the volume: %s."
// *Cause: Informational.
// *Action: None.
09607, 0, " - Create an ACFS resource for the file system."
// *Cause: Informational.
// *Action: None.
09608, 0, " - Mount the ACFS file system on '%s'."
// *Cause: Informational.
// *Action: None.
09609, 0, " Continue the installation? [1=yes,2=no]:"
// *Cause: Informational.
// *Action: None.
09610, 0, "Error - the ACFS resource for the specified file system is already in use."
// *Cause: An attempt to use the specified volume found that it was in use by
// an ACFS file system resource.
// *Action: Specify a volume that is not in use, or remove the conflicting
// ACFS resource.
09611, 0, "Starting NFS Service."
// *Cause: Informational.
// *Action: None.
09612, 0, "Stopping NFS Service."
// *Cause: Informational.
// *Action: None.
09613, 0, "Restarting NFS Service."
// *Cause: Informational.
// *Action: None.
09614, 0, "Formatting the volume device."
// *Cause: Informational.
// *Action: None.
09615, 0, "NFS_PATH is not supported."
// *Cause: Informational.
// *Action: None

/ acfsutil scrub
09620, 0, "'acfsutil scrub' is not implemented."
// *Cause: An attempt to invoke the command 'acfsutil scrub' was rejected
// because the version of acfsutil that was used did not include
// 'scrub' functionality.
// *Action: Upgrade the Grid Infrastructure software to a version that
// supports the ACFS scrubber, and retry the operation.
09621, 0, "ACFS Scrubber has started"
09622, 0, "Start Time : %s"
09623, 0, "Scrubbing Path: %s"
09624, 0, "Summary File : %s"
09625, 0, "Trace File : %s"
09626, 0, "Power Level : %d"
09627, 0, "Trace Level : %d"

09629, 0, "+---------------------+---------+---------+---------+---------+---------+"
/ Translation note: Please keep location of 'Time' column separators | as is.
/ Remove white space if translation is longer than English.
/ Add white space if translation is shorter.
09631, 0, "| Time | R_MBD | B_MDB | F_MDB | R_UDB | B_UDB |"
09632, 0, "+---------------------+---------+---------+---------+---------+---------+"
09633, 0, "|%s | %04s| %04s| %04s| %04s| %04s|"
09634, 0, "Scrubber detected more than %u inconsistencies, exiting early."

09635, 0, "R_MDB = Read metadata blocks"
09636, 0, "B_MDB = Bad metadata blocks"
09637, 0, "F_MDB = Fixed metadata blocks"
09638, 0, "R_UDB = Read userdata bytes"
09639, 0, "B_UDB = Bad user data bytes"

09640, 0, "ACFS Scrubber has completed. Final statistics:"
09641, 0, "Finish Time: %s"
09642, 0, "Metadata Statistics:"
09643, 0, "\t# Directories Cached, not scrubbed : %u"
09644, 0, "\t# Directories Consistent : %u"
09645, 0, "\t# Directories Inconsistent : %u"
09646, 0, "\t# Directories Unable to be processed : %u"
09647, 0, "\t# Files Cached, not scrubbed : %u"
09648, 0, "\t# Files Consistent : %u"
09649, 0, "\t# Files Inconsistent : %u"
09650, 0, "\t# Files Unable to be processed : %u"
09651, 0, "User Data Statistics:"
09652, 0, "\t# Files Consistent : %u"
09653, 0, "\t# Files Inconsistent : %u"
09654, 0, "\t# Files Unable to be processed : %u"
09655, 0, "\t# Bytes Consistent : %u"
09656, 0, "\t# Bytes Inconsistent : %u"
09657, 0, "\t# Bytes Unable to be processed : %u"

09658, 0, "\t# Files with lost data (BADFDA7A) : %u"
09659, 0, "\t# Bytes Lost (BADFDA7A) : %u"
09660, 0, "Data has been lost in the filesystem."
// *Cause: The ACFS Scrubber determined that data has been lost in one or more
// files in the file system being scrubbed. This may result in ACFS
// data needing to be restored from backup. This could be the result of
// a storage problem, a configuration issue or a software bug.
// *Action: Check the alert log for the result of the recovery attempt. Run
// fsck to verify the file system state. If unsuccessful, contact
// Oracle Support Services with the incident information.

09670, 0, "Failure to initialize the ACFS Scrubber."
// *Cause: An attempt to initialize the ACFS scrubber resulted in an
// internal error.
// *Action: Contact Oracle Support Services.
09671, 0, "Invalid trace value specified. Must be between %d (terse) and %d (verbose)."
// *Cause: An attempt to initialize the trace level failed because an
// invalid value was specified.
// *Action: Retry the command using a value within the range indicated.
09672, 0, "Invalid I/O load specified. Must be between %d (lowest) and %d (highest)."
// *Cause: An attempt to initialize the I/O load failed because an
// invalid value was specified.
// *Action: Retry the command using a value within the range indicated.
09673, 0, "Invalid file extent logging value specified. Must be between 0 and 3."
// *Cause: An attempt to initialize the file extent logging level failed
// because an invalid value was specified.
// *Action: Retry the command using a value within the range specified.
09674, 0, "The filesystem is offline."
// *Cause: An attempt to scrub the contents of the filesystem was unsuccessful
// because the filesystem was offline.
// *Action: Retry the command when the filesystem is online.
09675, 0, "The ACFS Scrubber was interrupted."
// *Cause: An interrupt signal was received by the Scrubber to abort scrubbing.
// *Action: None.

/ Translation note: Please keep location of column separators | as is.
/ Remove white space if translation is longer than English.
/ Add white space if translation is shorter.
09676, 0, "| NO DATA |"
// *Cause: No data is being printed in this field because the ACFS Scrubber
// is running as a background job.
// *Action: None.

/ advmutil openProgress
09700, 0, "Usage: advmutil [%sh] info progress [%sv] %sd <device_path>"
09701, 0, " [%sh] - show this help and exit"
09702, 0, " [%sv] - Verbose mode"
09703, 0, " %sd <device_path> - Device to query"

09707, 0, "Querying volume: %s"
09708, 0, "Failed to query the device"

09710, 0, "NOT an ADVM volume"
09711, 0, "Opening root volume"
09712, 0, "DGUSE"
09713, 0, "Loading disks"
09714, 0, "Loading extents"
09715, 0, "Open restarted"
09716, 0, "Volume fully opened"
09717, 0, "Volume being closed"
09718, 0, "Not opening"
/
/ ACFS Remote messages
/
/ Header for the acfsutil cluster credential command.
09800, 0, "NAME\t\t\tVERSION\t\tGUID"
09801, 0, "Failure to access Oracle Cluster Registry (OCR)."
// *Cause: An attempt to access the Oracle Cluster Registry encountered an
// internal error.
// *Action: Contact Oracle Support Services.
09802, 0, "Failure to initialize the credentials context."
// *Cause: An attempt to initialize the Oracle Cluster Registry credentials
// context encountered an internal error.
// *Action: Contact Oracle Support Services.
09803, 0, "Failure to initialize the credentials domain for the '%s' cluster."
// *Cause: An attempt to create the Oracle Cluster Registry credentials domain
// for the indicated cluster encountered an internal error.
// *Action: Contact Oracle Support Services.
09804, 0, "Failure to create the credentials for the '%s' cluster."
// *Cause: An attempt to create the credentials for the indicated cluster
// encountered an internal error.
// *Action: Contact Oracle Support Services.
09805, 0, "Failure to export the credentials for the '%s' cluster."
// *Cause: Unable to export the credentials for the indicated cluster to the
// specified Cluster Manifest File.
// *Action: Ensure that the current user has write permissions to the specified
// Cluster Manifest File, and retry the operation.
/ List entry for the cluster credential list command
09806, 0, "%s\t\t%s\t%s"
09807, 0, "Could not find the '%s' credential domain."
// *Cause: The ACFSREMOTE credential domain was not found in the Oracle Cluster
// Registry (OCR).
// *Action: Verify ACFSREMOTE credentials already exist in the Oracle Cluster
// Registry (OCR). Run the 'acfsutil cluster credential -s <Grid
// Infrastructure User>' command if the ACFSREMOTE credentials domain
// is not present.
09809, 0, "No Member Clusters have been registered."
// *Cause: An attempt to list the registered clusters returned no results
// because no Member Clusters have been registered.
// *Action: None.
09810, 0, "No credentials were found for the '%s' cluster name."
// *Cause: An attempt to list the credentials for the indicated cluster failed
// as it does not exist in the ACFSREMOTE domain.
// *Action: Verify the indicated cluster name is already registered. If
// necessary, register it using the 'acfsutil cluster credential -g
// <cluster name> -o <Cluster Manifest File>' command.
09812, 0, "Unable to obtain the credential set for the '%s' cluster."
// *Cause: At attempt to get the credential set for the specified cluster
// encountered an internal error.
// *Action: Contact Oracle Support Services.
09813, 0, "Unable to add a new credential pair to the credential set of the '%s' cluster."
// *Cause: An attempt to add the new credentials for the specified cluster
// encountered an internal error.
// *Action: Contact Oracle Support Services.
09814, 0, "Unable to set the member cluster version."
// *Cause: An attempt to write the cluster version to the Oracle Cluster
// Registry (OCR) encountered an internal error.
// *Action: Contact Oracle Support Services.
09816, 0, "Unable to determine the version of member cluster '%s'."
// *Cause: An attempt to read the cluster version for the indicated cluster
// from the Oracle Cluster Registry (OCR) encountered an internal
// error.
// *Action: Contact Oracle Support Services.
/ The next 3 messages are 'summary' messages which will be displayed if any
/ error is found during the creation, listing or deletion of credentials.
/ Another error from among the above messages will have also been displayed,
/ where the cause and action to take are specified.
09818, 0, "Unable to add an already existing cluster '%s'. Exporting the existing credentials."
09819, 0, "Unable to remove the '%s' cluster. It does not exist."
09820, 0, "Failed to register the '%s' cluster."
09821, 0, "Unable to access the specified Cluster Manifest File."
// *Cause: An attempt to read the Cluster Manifest File provided failed.
// ACFS Remote Member Cluster registration requires a Cluster Manifest
// File with valid ASM credentials.
// *Action: Make sure the specified Cluster Manifest File has read and write
// permissions. Verify the input Cluster Manifest file was generated
// via 'asmcmd mkcc --asm' (or a flagless 'asmcmd mkcc').
// If the Member Cluster has already been registed for ASM use,
// execute 'asmcmd mkcc --acfs' with the Cluster Manifest File
// previously generated.
09822, 0, "The provided cluster name '%(1)s' does not match the name of the Cluster Manifest File's cluster source '%(2)s'."
// *Cause: There was a mismatch in the name provided and the name of the
// cluster in the Cluster Manifest File.
// *Action: Make sure you spelled the name correctly or register the specified
// cluster as a new one.
09823, 0, "Unable to find the ASM attributes section in the provided Cluster Manifest File."
// *Cause: The ASM_attributes section was not found in the Cluster Manifest File
// provided.
// *Action: Provide the Cluster Manifest File generated during execution of
// 'asmcmd mkcc <options>' command.
09824, 0, "Unable to find the cluster global unique ID in the provided Cluster Manifest File."
// *Cause: The cluster global unique ID for the specified cluster was not
// found in the Cluster Manifest File provided.
// *Action: Provide the Cluster Manifest File generated during execution
// of 'asmcmd mkcc <options>' command.
09825, 0, "Unable to find the cluster name in the provided Cluster Manifest File."
// *Cause: The cluster name for the specified cluster was not found in the
// Cluster Manifest File provided.
// *Action: Provide the Cluster Manifest File generated during execution
// of 'asmcmd mkcc <options>' command.
09826, 0, "Unable to import the credentials from the specified file."
// *Cause: An attempt to import the credentials from the Member Cluster Data
// File failed.
// *Action: Provide the Cluster Manifest File generated during execution
// of 'asmcmd mkcc <options>' command.
09827, 0, "ACFS Remote credentials were not found in the provided Cluster Manifest File."
// *Cause: The ACFS Remote section was not found in the provided Cluster
// Manifest File.
// *Action: Retry the Member Cluster registration command 'asmcmd mkcc <cluster
// name> <Cluster Manifest File> <options>', appending '--acfs' to the
// options specified.

09828, 0, "Command not permitted on cluster class '%s'."
// *Cause: An attempt to execute the command 'acfsutil cluster credential' with
// the specified options was rejected because the local cluster was of
// the indicated class. With the options specified this command may be
// executed only from a node in a Domain Services Cluster.
// *Action: Retry the command on a member node of the Domain Services Cluster.
09829, 0, "unable to retrieve the current cluster class"
// *Cause: An attempt to execute 'acfsutil cluster credential' failed because
// the cluster class could not be obtained from the OCR. Possibly the
// OCR is unavailable or this may be an internal error.
// *Action: Verify the OCR is available and retry. If retry does not succeed,
// contact Oracle Support Services.
09830, 0, "The version string provided is invalid."
// *Cause: The expected version string input was not of a valid format.
// *Action: Retry the command with a valid version format. The expected format
// is X.X[.X.X.X] where the 2 first numbers are mandatory and the
// last 3 are optional.

09837, 0, " --trace <level>: Trace level"
09838, 0, " --member: Member Cluster check"
09839, 0, " --domain: Domain Services Cluster check"

09840, 0, "ACFS Remote supported: %s"
09841, 0, "iSCSI supported: %s"
09842, 0, "xen blkfrnt/blkback supported: %s"

09843, 0, "ACFS Remote installed: %s"
09844, 0, "iSCSI installed: %s"
09845, 0, "xen blkfrnt/blkback installed: %s"

09846, 0, "ACFS Remote loaded: %s"
09847, 0, "iSCSI loaded: %s"
09848, 0, "xen blkfrnt/blkback loaded: %s"

09850, 0, "acfsremote transport_config: Configure ACFS Remote transport."
09851, 0, "acfsremote transport_list: List ACFS Remote transports."
09852, 0, "acfsremote transport_change: Modify transport configuration."
/ Translation note: Do not translate the words before the ':' because those
/ are arguments of a command. This applies to messages 9853-9858.
09853, 0, " --rescan <transport>: Rescan for new transports"
09854, 0, " --refresh <transport>: Refresh existing transports"
09855, 0, " --add --dsf=<dsf> --transid=<id>: Add the node ID to the ACL of the specified DSF target"
09856, 0, " --remove --dsf=<dsf> --transid=<id>: Remove the node ID from the ACL of the specified DSF target"
09857, 0, " --export --dsf=<dsf> --guid=<guid>: Setup the specified DSF in the transport"
09858, 0, " --rmexport --dsf=<dsf> --guid=<guid>: Delete the target for the DSF"

09860, 0, "Configuring ACFS Remote"
09861, 0, "Retrieving active sessions"
09862, 0, "Scanning iSCSI devices in Domain Services Cluster %s"
09863, 0, "Logging in target %s"

09864, 0, " --dsf: Path to Device Special File"
09865, 0, " --guid: Cluster Global Unique Identifier (GUID)"
09866, 0, " --transid: Transport ID"

/ Translation note: in the following 3 messages, the initial
/ ???acfsremote <keyword>??? are literal command strings and should not
/ be translated.
09867, 0, "acfsremote supported: Check if ACFS Remote is supported."
09868, 0, "acfsremote installed: Check if ACFS Remote is installed."
09869, 0, "acfsremote loaded: Check if ACFS Remote is loaded."

/ advmutil OCR messages
09890, 0, "Unable to delete Oracle Cluster Registry subkey '%s' error: %s"
// *Cause: An attempt to delete an advmutil transport or session failed
// because an attempt to delete the indicated Oracle Cluster Registry
// subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09891, 0, "Unable to open Oracle Cluster Registry subkey '%s' error: %s"
// *Cause: An attempt to open an advmutil transport or session failed
// because an attempt to open the indicated Oracle Cluster Registry
// subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09892, 0, "Unable to set Oracle Cluster Registry subkey '%s' in '%s' error: %s"
// *Cause: An attempt to set an advmutil transport or session failed
// because an attempt to set the indicated Oracle Cluster Registry
// subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09893, 0, "Unable to enumerate Oracle Cluster Registry subkey '%s' error: %s"
// subkey failed.
// *Cause: An attempt to enumerate an advmutil transport or session failed
// because an attempt to enumerate the indicated Oracle Cluster
// Registry subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09894, 0, "Invalid Oracle Cluster Registry subkey '%s' in path '%s. error: %s'"
// *Cause: An attempt to access an advmutil transport or session failed
// because an attempt to access the indicated Oracle Cluster Registry
// subkey failed with the indicated error.
// *Action: Contact Oracle support service.
09895, 0, "Unable to create Oracle Cluster Registry subkey '%s' error: %s"
// *Cause: An attempt to create an advmutil transport or session failed
// because an attempt to create the indicated Oracle Cluster Registry
// subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09896, 0, "Unable to retrieve Oracle Cluster Registry subkey value '%s' error: %s"
// *Cause: An attempt to retrieve an advmutil transport or session failed
// because an attempt to retrieve the indicated Oracle Cluster
// Registry subkey failed with the indicated error.
// *Action: Contact Oracle Support Services.
09897, 0, "unable to retrieve the ASM Administrator name"
// *Cause: An attempt to retrieve the ASM Administrator name from the
// ADVM control device failed.
// *Action: Verify that the Oracle stack is up and that ADVM driver is loaded.
// If not, bring up the Oracle stack, ensure that the ADVM driver
// is loaded, and retry the command.

/
/ 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 1023 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 <mount_point> -n'.
10154, 0, "Failed to create realm '%s' on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10181, 0, "Failed to get groups for realm '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10182, 0, "Failed to get users for realm '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10183, 0, "Failed to get filters for realm '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10184, 0, "Failed to get realm encryption attributes of realm '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10190, 0, "Updated attributes of realm '%s'."
// *Cause: Updated realm attributes.
// *Action: None.
/10191, 0, "Message removed - do not reuse message number"
/10192, 0, "Message removed - do not reuse message number"
/10193, 0, "Message removed - do not reuse message number"
/10194, 0, "Message removed - do not reuse message number"
10195, 0, "None of the options -a, -d, are specified with the edit command."
// *Cause: An attempt to execute the command 'ruleset edit' was rejected
// because specifying one of -a or -d was mandatory.
// *Action: Retry the operation, specifying either -a or -d.
/10196, 0, "Message removed - do not reuse message number"
/10197, 0, "Message removed - do not reuse message number"
/10198, 0, "Message removed - do not reuse message number"
/10199, 0, "Message removed - do not reuse message number"
/10200, 0, "Message removed - do not reuse message number"
/10201, 0, "Message removed - do not reuse message number"
/10202, 0, "Message removed - do not reuse message number"
/10203, 0, "Message removed - do not reuse message number"
10204, 0, "The rule '%s' will not be added or deleted."
// *Cause: An attempt to execute the command 'ruleset edit' was rejected
// because the indicated rule name was specified with both the -a
// and the -d option.
// *Action: Retry the command, specifying the indicated rule name in either
// the -a or the -d option, but not both.
10205, 0, "The option -f should be specified at the end after all other options."
// *Cause: An attempt to edit the realm was rejected because -f was not
// supplied as the last argument of the command.
// *Action: Retry the command, specifying -f as the last argument.
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 <user_name>
//* - application <application_name>
//* - time <start_time>,<end_time>
//* - hostname <host_name>
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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 <mnt> -l <rule-name>'.
10230, 0, "Failed to perform rule edit operation on '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10239, 0, "Failed to get information for rule '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10253, 0, "Failed to get list of command rules."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 <ruleset-name>'.
10257, 0, "Failed to get all rule sets on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10258, 0, "Failed to get information for rule set '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10259, 0, "Invalid command rule '%s'."
// *Cause: Invalid command rule was specified.
// *Action: Execute 'acfsutil sec info -m <mount_point> -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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10274, 0, "Failed to update rule set option."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10275, 0, "Failed to get rule sets for mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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.
10356, 0, "waiting for the operation to complete..."
// *Cause: Informational.
// *Action: None.
10357, 0, "System realm 'SYSTEM_Audit' created."
// *Cause: Informational.
// *Action: None.
10358, 0, "Keystore: %s"
// *Document: NO
10359, 0, "Failed to create system realm '%s'"
// *Cause: An attempt to create a realm with the specified name was rejected
// because the specified name was a system realm name. System realms
// get created as the result of some ACFS Security operations and
// cannot be explicitly created by the ACFS Security Administrator.
// *Action: Rerun the command with a different realm name.
10360, 0, "Failed to create system ruleset '%s'"
// *Cause: An attempt to create a ruleset with the specified name was rejected
// because the specified name was a system ruleset name. System rulesets
// get created as the result of some ACFS Security operations and cannot
// be explicitly created by the ACFS Security Administrator.
// *Action: Rerun the command with a different ruleset name.
10361, 0, "Failed to create system rule '%s'"
// *Cause: An attempt to create a rule with the specified name was rejected
// because the specified name was a system rule name. System rules get
// created as the result of some ACFS Security operations and cannot be
// explicitly created by the ACFS Security Administrator.
// *Action: Rerun the command with a different rule name.

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 '<mount_point>/.Security/encryption/logs/encr-<host_name>.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 '<mount_point>/.Security/encryption/logs/encr-<host_name>.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 '<mount_point>/.Security/encryption/logs/encr-<host_name>.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 '<mount_point>/.Security/encryption/logs/encr-<host_name>.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.
10423, 0, "This encryption operation is not allowed on a standby file system."
// *Cause: An encryption operation that is not allowed on a standby file system was attempted. The following acfsutil encryption commands are not allowed on a standby file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
// *Action: None.
10424, 0, "This ACFS Security operation is not allowed on a standby file system."
// *Cause: An ACFS Security operation that is not allowed on a standby
// file system was attempted.
// The following acfsutil security commands are not allowed on a
// standby file system:
// 'sec prepare', 'sec save/load/enable/disable',
// 'sec realm create/destroy/clone/add/delete',
// 'sec rule create/destroy/clone/edit', and
// 'sec ruleset create/destroy/clone/edit'
// *Action: None.

/
/ 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.
10463, 0, "Skipping file '%s' because it does not belong to the file system mounted on '%s'"
// *Cause: The file does not belong to the specified mounted ACFS file system.
// *Action: None.
10464, 0, "ACFS Encryption operations are not allowed on files of this type."
// *Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of
// the following Oracle file types: data, control, online redo log,
// archive log, backup, incremental backup, or flashback.
// *Action: None.
10465, 0, "FS-level encryption parameters have been set to:"
// *Cause: Informational.
//*Action: None.
10466, 0, "Using user-provided parameters: algorithm %s, key length %d bytes"
//*Cause: Informational.
//*Action: None.
10467, 0, "Using FS-level parameters: algorithm %s, key length %d bytes"
//*Cause: Informational.
//*Action: None.
10468, 0, "Encryption has been enabled on mount point '%s'."
//*Cause: Informational.
//*Action: None.
10469, 0, "Rekeying file/directory '%s'..."
//*Cause: Informational.
//*Action: None.
10470, 0, "Encrypting file/directory '%s'... "
//*Cause: Informational.
//*Action: None.
10471, 0, "Path: %s"
//*Cause: Informational.
//*Action: None.
10472, 0, "Re-encrypting FEK for mount point '%s'... "
//*Cause: Informational.
//*Action: None.
10473, 0, "Re-encrypting FEK for file/directory '%s'... "
//*Cause: Informational.
//*Action: None.
10475, 0, "Failed to rekey file/directory '%s'."
// *Cause: An unexpected error occured while attempting to rekey the indicated
// file. This is an internal error.
// *Action: Contact Oracle Support Services.
10476, 0, "Algorithm AES %d-bit, Key length %d bytes"
//*Cause: Informational.
//*Action: None.
10477, 0, "Decrypting file/directory '%s'... "
//*Cause: Informational.
//*Action: None.
10478, 0, "Encryption has been disabled on mount point '%s'."
//*Cause: Informational.
//*Action: None.
10479, 0, "File is larger than 128M, cannot encrypt, decrypt or rekey."
// *Cause: An attempt was made to encrypt, decrypt or rekey a file larger than
// 128M in size.
// *Action: If an encryption operation was attempted, create a new file of size
// zero, encrypt it using desired encryption parameters, and copy the
// original file into the newly created file. Then rename the newly
// created file to the original file name if required.
// If a decryption operation was attempted, create an unencrypted new
// file of size zero, and copy the original encrypted file into the
// new file. Then rename the newly created file to the original file
// name if required.
// If a rekey operation was attempted, create a new file of size zero,
// encrypt it using desired (after rekey) encryption parameters, and
// copy the original file into the newly created file. Then rename the
// newly created file to the original file name if required.

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]."
// *Cause: An attempt to create the indicated wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
10542, 0, "Wallet '%s' save failed [error : %d %s]."
// *Cause: An attempt to save the indicated wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
10543, 0, "Wallet '%s' open failed [error : %d %s]."
// *Cause: An attempt to open the indicated wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
/10544, 0, "Message removed - do not reuse message number"
/10545, 0, "Message removed - do not reuse message number"
/10546, 0, "Message removed - do not reuse message number"
/10547, 0, "Message removed - do not reuse message number"
10548, 0, "Wallet initialization failed [error : %d %s]."
// *Cause: An attempt to initialize the wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
10549, 0, "Wallet termination failed [error : %d %s]."
// *Cause: An attempt to terminate the wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.

/
/ More of security messages
/
10550, 0, "Security wallet created."
// *Cause: Security wallet was created.
// *Action: None.
10551, 0, "Security wallet creation failed."
// *Cause: An attempt to create the security wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
10552, 0, "Security wallet save failed."
// *Cause: An attempt to save the security wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
10553, 0, "Security wallet open failed."
// *Cause: An attempt to open the security wallet failed with the indicated
// error. This is an internal error.
// *Action: Contact Oracle Support Services.
/10554, 0, "Message removed - do not reuse message number"
/10555, 0, "Message removed - do not reuse message number"
/10556, 0, "Message removed - do not reuse message number"
10557, 0, "Security wallet could not be owned by '%s'."
// *Cause: An attempt to change the ownership of the security wallet failed.
// This is an internal error.
// *Action: Contact Oracle Support Services.
/10558, 0, "Message removed - do not reuse message number"
10559, 0, "Insufficient privileges to switch to %0!s '%1!s'."
// *Cause: An attempt to change the user or group membership privilege for
// a process failed because the user who was executing the command
// did not have sufficient privileges.
// *Action: Retry the command as a system administrator.
/10563, 0, "Message removed - do not reuse message number"
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: An attempt to create the encryption key store failed with the
// indicated error. This is an internal error.
// *Action: Refer to encryption log in
// '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
10567, 0, "Encryption key store save failed."
// *Cause: An attempt to save the encryption key store failed. This is an
// internal error.
// *Action: Contact Oracle Support Services.
10568, 0, "Encryption key store open failed."
// *Cause: An attempt to open the encryption key store failed. This is an
// internal error.
// *Action: Contact Oracle Support Services.
10569, 0, "Encryption key store delete succeeded."
// *Cause: Encryption key store was deleted.
// *Action: None.
/10570, 0, "Message removed - do not reuse message number"
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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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]."
// *Cause: Internal error occurred.
// *Action: Contact Oracle Support Services.
10581, 0, "Internal API error : [%s]."
// *Cause: Internal error occurred.
// *Action: Contact Oracle Support Services.
10582, 0, "Internal API error : [%d : %s %s]."
// *Cause: Internal error occurred.
// *Action: Contact Oracle Support Services.
10583, 0, "Internal API error : [%s, %d]."
// *Cause: Internal error occurred.
// *Action: Contact Oracle support service.
10585, 0, "Ioctl '%s' failed in '%s' with error %d."
// *Cause: Internal error occurred.
// *Action: Contact Oracle Support Services.
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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10601, 0, "Failed to update first security administrator '%s' information."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10612, 0, "Failed to remove user '%s' from security administrator(s) list."
// *Cause: Internal error
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10635, 0, "Failed to get security administrator group."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10640, 0, "Failed to create log directory on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10641, 0, "Failed to create backup directory on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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 '<mount_point>/.Security/realm/logs/sec-<host_name>.log'.
10656, 0, "Failed to get timestamp."
// *Cause: Internal error.
// *Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_name>.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.
10691, 0, "Changed ACFS Security administrator password for current user."
// *Cause: Informational.
// *Action: None.

10700, 0, "Failed to store volume encryption key."
// *Cause: Internal error.
// *Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.log'.
10701, 0, "Failed to get volume encryption key."
// *Cause: Internal error.
// *Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr-<host_name>.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.
10708, 0, "An earlier key store migrate operation did not complete. Provide the same password as the one used in the previous attempt."
// *Cause : An earlier run of 'acfsutil keystore migrate' command did not complete.
// *Action: When prompted for a password (ACFS-10349), provide the same password as the one used in the previous attempt.
10709, 0, "Existing ACFS encryption key store is already password-protected."
// *Cause : Informational.
// *Action: None.
10710, 0, "Existing ACFS encryption key store is already not password-protected."
// *Cause : Informational.
// *Action: None.
10711, 0, "Recovery of ACFS encryption key store completed successfully."
// *Cause : Informational.
// *Action: None.
10712, 0, "ACFS encryption key store migration to password-protected key store completed successfully."
// *Cause : Informational.
// *Action: None.
10713, 0, "ACFS encryption key store migration to password-free key store completed successfully."
// *Cause : Informational.
// *Action: None.
10714, 0, "The environment variable OKV_HOME is not set."
// *Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV_HOME environment variable was not set.
// *Action: Set the environment variable OKV_HOME and retry the command.
10715, 0, "failed to find the PKCS library in path '%s'"
// *Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.
// *Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
10716, 0, "failed to load the PKCS library"
// *Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV PKCS library could not be loaded from '$OKV_HOME/lib'.
// *Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the PKCS library. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
10717, 0, "failed to find Oracle Key Vault (OKV) client configuration file"
// *Cause: The attempt to access the Oracle key vault server to obtain the volume encryption keys failed because the OKV client configuration file, okvclient.ora, was not found in '$OKV_HOME/conf'.
// *Action: Ensure that the OKV_HOME environment variable is set to point to the path that contains OKV client data, including the OKV client configuration file, okvclient.ora. If not, set OKV_HOME and retry the command. If the problem persists, contact Oracle Support Services.
10718, 0, "failed to login to OKV server"
// *Cause: A login attempt to Oracle Key Vault (OKV) server failed.
// *Action: Ensure that correct password is provided, verify okvclient.ora file entries for servers, verify both the servers are still running, and then retry. If the problem persists, contact Oracle Support Services.
10719, 0, "failed to store encryption keys in file system wallet"
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10720, 0, "Key store must be either SSO, PKCS, or OKV."
// *Cause: An attempt to store an encryption key was rejected because the specified key store was not one of: SSO, PKCS or OKV.
// *Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
10721, 0, "failed to save encryption keys, file system wallet already exists in directory '%s'"
// *Cause: An attempt to create a new wallet and save encryption keys in it failed because the wallet already existed in the said location.
// *Action: Delete or move the wallet and retry the command.

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 '<mount_point>/.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 '<mount_point>/.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 '<CRS_HOME>/log/<host_name>/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 '<mount_point>/.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 '<mount_point>/.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 '<CRS_HOME>/log/<host_name>/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.
/ Message 10754 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.
/ Message 10763 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.
10767, 0, "Realm_Metadata File Private structure has invalid _freeDataList value\n found: %(1)u maximum: %(2)u\nfor file:\n%(3)s"
// *Cause: The _freeDataList property of the _Private structure of the
// indicated Realm_Metadata file was incorrect. The _freeDataList
// value exceeded the maximum value for this Realm_Metadata
// file.
// *Action: If the ACFS Fixer was running, the problem would have been
// resolved. If only the ACFS Checker was 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 <mount_point> -u' as security
// administrator and retry.
10781, 0, "could not undo ACFS security or encryption for the file system mounted on path '%s' because of existing snapshots"
// *Cause: An attempt to undo ACFS security or encryption for the indicated
// file system failed because there were existing snapshots (created
// by user or created as part of replication V2 being active) for the
// file system. ACFS security and encryption can only be undone for a
// file system with no snapshots. This message may be displayed before
// or after all files have been decrypted using the command 'acfsutil
// encr set -u'. In either case, the file system retains its encryption
// 'prepared' state and files can be encrypted without running
// 'acfsutil encr set' again.
// *Action: Remove all snapshots by executing 'acfsutil snap delete', and also
// check if replication V2 is active, terminate replication on the
// file system 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 same as 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.
10800, 0, "Failed to complete ACFS Security undo operation on mount point '%s'."
// *Cause: ACFS Security undo operation did not complete because some
// rules, rulesets, or realms exist for the given file system.
// *Action: Retry the operation after making sure that no other
// 'acfsutil sec' commands are running for the given file system.
10801, 0, "failed to acquire a lock on ACFS security wallet"
// *Cause: The ACFS security wallet could not be initialized because the lock
// on the wallet could not be obtained.
// *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 this does not
// resolve the problem contact Oracle Support Services.
10802, 0, "unable to release the lock being held on the ACFS security wallet"
// *Cause: After security initialization, the lock on ACFS security wallet could not be 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 this does not
// resolve the problem contact Oracle Support Services.
10803, 0, "cannot proceed because another instance of 'acfsutil' command is updating the ACFS security wallet"
// *Cause: An attempt to update the ACFS security wallet failed because the
// ACFS security wallet was locked by another instance of the acfsutil
// command.
// *Action: Retry the command later.

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 <mount_point> -S <snapshot_name> -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 '<mount_point>/.Security/realm/logs/sec-<host_name>.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 <mount_point> -S <snapshot_name> -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 <mount_point> -S <snapshot_name> -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.

10936, 0, "ACFS Security is now disabled in snapshot '%s' of mount point '%s'."
// *Cause: Informational.
// *Action: None.

10937, 0, "ACFS Security is now enabled on realm '%s' in snapshot '%s' of mount point '%s'."
// *Cause: Informational.
// *Action: None.

10938, 0, "ACFS Security is now disabled on realm '%s' in snapshot '%s' of mount point '%s'."
// *Cause: Informational.
// *Action: None.

10939, 0, "ACFS Security is now enabled on realm '%s' in mount point '%s'."
// *Cause: Informational.
// *Action: None.

10940, 0, "ACFS Security is now disabled on realm '%s' in mount point '%s'."
// *Cause: Informational.
// *Action: None.

10941, 0, "Failed to create '%s' file on mount point '%s'"
// *Cause: An attempt to create a file on the indicated mount point failed,
// most likely because the user lacked the requisite permission.
// *Action: Ensure that the user has the required permission and retry.
// Otherwise, contact Oracle Support Services.

10942, 0, "Insufficient disk space on mount point '%s'"
// *Cause: The requested operation failed because the file system was full.
// *Action: Resize the file system and retry.

/
/ Audit vault integration with sec/encr related messages
/

10945, 0, "ACFS Auditing source '%s' is already enabled on mount point '%s'."
// *Cause:Informational.
// *Action: None.
10946, 0, "ACFS Auditing source '%s' is already disabled on mount point '%s'."
// *Cause:Informational.
// *Action: None.
10947, 0, "Audit trail on mount point '%s' is marked as read."
// *Cause:Informational.
// *Action: None.
10948, 0, "Audit trail on mount point '%s' is archived."
// *Cause: Informational.
// *Action: None.
10949, 0, "ACFS Auditing has been initialized on the cluster with '%s' as the Oracle ACFS auditor OS group and '%s' as the Oracle ACFS audit manager OS group."
// *Cause: Informational.
// *Action: None.
10950, 0, "Audit trail archive for mount point '%s' is purged."
// *Cause: Informational.
// *Action: None.
10951, 0, "Current user does not have system administrative privileges to initialize auditing."
// *Cause: The user was not part of system administrators group.
// *Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
10952, 0, "Auditing already initialized; cannot reinitialize."
// *Cause: An attempt was made to initialize auditing after it was already initialized.
// *Action: None.
10953, 0, "Auditing is not initialized."
// *Cause: A command was issued which requires auditing to be intialized for the cluster, but auditing has not been initialized.
// *Action: Initialize auditing by reissuing 'acfsutil audit init' command.
10954, 0, "Failed to enable auditing on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
10955, 0, "Failed to disable auditing on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
10956, 0, "Failed to enable auditing for realm '%s' on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
10957, 0, "Failed to disable auditing for realm '%s' on mount point '%s'."
// *Cause: Internal error.
// *Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
10958, 0, "Current user does not have privileges to run audit commands."
// *Cause: An attempt to execute an audit command was rejected because the
// attempting user was not a member of the audit managers group or
// the auditors group.
// *Action: Retry the command as a user who is part of the audit managers group
// (for all audit commands except 'audit read') or the auditors group
// (for 'audit read').
10960, 0, "Failed to get audit information for the mount point '%s'."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10961, 0, "Failed to get audit manager OS group."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10962, 0, "Failed to get auditor OS group."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10963, 0, "Auditing is not enabled on mount point '%s'."
// *Cause: A command was issued that requires auditing to be enabled at the file system level, but it is not enabled.
// *Action: Run 'acfsutil audit enable', and retry the command.
10964, 0, "Failed to archive audit trail on mount point '%s'."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10965, 0, "Failed to mark audit trail on mount point '%s' as read"
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10966, 0, "Audit trail on mount point '%s' is already marked as read."
// *Cause: Audit trail was already marked as read on mount point.
// *Action: None.
10967, 0, "Audit trail on mount point '%s' not found."
// *Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.
// *Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then reissue the original command.
10968, 0, "Failed to create audit trail XML file '%s' for mount point %s."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10969, 0, "Failed to purge audit trail archive file for mount point '%s'."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10970, 0, "Failed to purge audit trail archive because it is not marked 'read' for mount point '%s'."
// *Cause: Audit trail was not yet marked as 'read' on mount point.
// *Action: Run 'acfsutil audit read' and retry the command.
10971, 0, "Current user does not have privileges to run this audit command."
// *Cause: Command was executed as user who is not part of audit manager OS group.
// *Action: Run command as user who is part of audit manager OS group.
10972, 0, "Failed to update audit managers and auditors group information in the driver; some of the subsequent audit related commands may fail."
// *Cause: Audit Managers and Auditors information was not communicated to the ACFS driver during mount. The mount command was successful but the subsequent audit commands will not work on this host until the problem is corrected.
// *Action: Contact Oracle Support Services.
10973, 0, "The ADVM compatibility attribute for the diskgroup must be set to version '%s' to enable auditing on mount point '%s'."
// *Cause: A security adminstrator or audit manager or administrator attempted to enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not been upgraded to a supported version.
// *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the
// COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
10974, 0, "Auditing cannot be enabled on mount point '%s', because ADVM compatibility is lower than '%s'."
//*Cause: A security adminstrator or system administrator attempted to enable auditing as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing could not be enabled because the 'compatible.advm attribute had not been upgraded to a supported version.
// *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade the
// COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit enable' command.
10975, 0, "Failed to get audit information for realm '%s' on mount point '%s'."
// *Cause: Internal error.
// *Action: Contact Oracle Support Services.
10976, 0, "Failed to create audit trail XML file because the old audit trail XML file exists for mount point '%s'."
// *Cause: A request to archive the audit trail found an existing audit trail XML file.
// *Action: Run 'acfsutil audit purge' and retry the command.
10977, 0, "Auditing is enabled for realm '%s' on mount point '%s'."
// *Cause: Informational.
// *Action: None.
10978, 0, "Auditing is disabled for realm '%s' on mount point '%s'."
// *Cause: Informational.
// *Action: None.
10979, 0, "Cannot proceed because file system is not prepared for ACFS Security."
// *Cause: An attempt to enable or disable audit on Security source failed
// because the file system was not prepare for ACFS Security.
// *Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the
// file system and retry 'acfsutil audit' command.
10980, 0, "Cannot proceed because file system is not set for ACFS Encryption."
// *Cause: An attempt to enable or disable audit on Encryption source failed
// because the file system was not set for ACFS Encryption.
// *Action: Execute 'acfsutil encr set' to set ACFS Encryption on the
// file system and retry 'acfsutil audit' command.

10981, 0, "Auditing information for mount point '%s':"
// *Document: NO
10982, 0, "Maximum Audit trail size : %d MB"
// *Document: NO
10983, 0, "Archive file : '%s'"
// *Document: NO
10984, 0, "Automatic purging : '%s'"
// *Document: NO
10985, 0, "Failure action : '%s'"
// *Document: NO
10986, 0, "Audit sources:"
// *Document: NO
10987, 0, "\t Security : '%s'"
// *Document: NO
10988, 0, "\t Encryption : '%s'"
// *Document: NO
10989, 0, "Audit manager OS group : '%s'"
// *Document: NO
10990, 0, "Auditor OS group : '%s'"
// *Document: NO
10991, 0, "Auditing is enabled on mount point '%s'."
// *Document: NO
10992, 0, "Auditing is disabled on mount point '%s'."
// *Document: NO
10993, 0, "\nCommand rule auditing information for realm '%s' on mount point '%s':\n"
// *Document: NO
10994, 0, "Realm authorizations : %s"
// *Document: NO
10995, 0, "Realm violations for all users : %s"
// *Document: NO
10996, 0, "Realm violations for only realm users : %s"
// *Document: NO
10997, 0, "Command rule auditing is not enabled for realm '%s' on mount point '%s'."
// *Document: NO
10998, 0, "ACFS Audit not initialized"
// *Cause: ACFS Audit was not initilized.
// *Action: Run 'acfsutil audit init' command.
10999, 0, "Audit trail archive file on mount point '%s' was not found."
// *Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did not exist.
// *Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges, then reissue the original command.
11000, 0, "ACFS Auditing is already initialized with different Audit Managers and Auditors group."
// *Cause: Values provided on the command line did not match those with which ACFS Auditing was initialized earlier.
// *Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors group provided for the previous initialization.

/
/ 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, "No operation was performed because device state is %s instead of DEFINED."
// *Cause: The method expected a DEFINED device state.
// *Action: AIX ODM internal error - contact Oracle Customer Support.
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.
11070, 0, "Node Count: %u"
11071, 0, "Rebuild Master: %s"
11072, 0, "Local Node: %s"
11073, 0, "Current Incarnation: %s"
11074, 0, "ACFS DLM Interfaces: %s"
11075, 0, "Cluster State: %s"
11076, 0, "Nodes:"
11077, 0, " Node %u - IP %s %s"
11078, 0, "unable to obtain cluster information for local node"
// *Cause: An internal ioctl operation to access cluster information failed.
// This message is accompanied by other messages providing
// details on the error.
// *Action: Correct the problem indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
//
//
/ This message will print the different available modes:
/ UNKNOWN, NONAPP, ODA, EXADATA, DOMU
11079, 0, "Oracle Appliance: [%s]"
11080, 0, "[ True ]"
11081, 0, "[ False ]"
11082, 0, "defragmenting file %s ..."
11083, 0, "insufficient OS kernel resources to defragment file %s"
// *Cause: An attempted defragment operation failed due to insufficient kernel resources.
// *Action: Reduce the load activity on the system and retry the defragment.
11084, 0, "no space left on the file system"
// *Cause: A defragment request failed because the file system was full.
// *Action: Delete unnecessary files from the file system to free up space,
// resize the file system, or delete snapshots from the file system
// if any exist.
11085, 0, "insufficient privileges to defragment file %s"
// *Cause: The caller does not have sufficient privileges to perform
// the defragment command on the indicated file.
// Write access is required for 'acfsutil defrag file'.
// Read access is required for 'acfsutil defrag file -i'.
// *Action: Obtain the required access rights for the indicated file.
11086, 0, "The specified path %s is not a regular file."
// *Cause: An attempted defragment operation was rejected because the
// specified pathname was not a regular file.
// *Action: Retry the command specifying the pathname of a regular file.
11087, 0, "The specified path %s is not a directory."
// *Cause: An attempted defragment operation was rejected because the
// specified pathname was not a directory.
// *Action: Retry the command specifying a directory path.
11088, 0, "caught interrupt; stop defragmenting file %s"
// *Cause: Informational.
// *Action: None.
11089, 0, "failed to read from or write to file %s"
// *Cause: During defragmentation processing for the indicated file,
// an attempt to read or write data to disk failed.
// *Action: Verify that the file system is online and retry the command.
// If the command still fails, run fsck (Unix or Linux) or
// acfschkdsk.exe (Windows), before retrying the command.
11090, 0, "failed to defragment file %s"
// *Cause: During defragmentation processing for the indicated file, an
// internal ioctl request failed.
// This message is accompanied by other messages providing
// details on the error.
// *Action: Correct the problem indicated by the other messages. If the cause
// of the problem is unclear, contact Oracle Support Services.
11091, 0, "unable to rename snapshot %s because it is replication-specific"
// *Cause: An attempt to rename a snapshot failed because it specified a
// replication-specific snapshot.
// *Action: Reconsider the need for the request, or specifiy a snapshot that
// is not associated with replication.
11092, 0, "Snapshot name %s already exists."
// *Cause: The snapshot rename operation failed because the newly
// designated snapshot name was in use by another snapshot.
// *Action: Rename or delete the conflicting snapshot and then re-issue the
// original 'acfsutil snap rename' command.
11093, 0, " number of fragmented extents: %u"
11094, 0, " size of fragmented extents: %u %s"
11095, 0, "'acfsutil defrag' command is not supported for the current ADVM compatibility version. Version %s is required."
// *Cause: The 'acfsutil defrag' command was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade
// the disk group compatibility (COMPATIBLE.ADVM attribute) to the
// specified version and then re-issue the original 'acfsutil
// defrag' command. If the disk group compatibility cannot be
// upgraded, update the ACFS compatibility level using the
// 'acfsutil compat set' command and then re-issue the original
// 'acfsutil defrag' command.
11096, 0, "ACFS Remote mode: [%s]"
11097, 0, "ASM Storage mode: [%s]"
11098, 0, "OKS DLM Interfaces: %s"
11099, 0, "Oracle Restart mode: [ON]"
11100, 0, " successfully set the %s flag"
11101, 0, " successfully cleared the %s flag"
11102, 0, " flag %s is set"
11103, 0, " flag %s is not set"
11104, 0, "insufficient OS kernel resources to perform the command %s"
// *Cause: An attempt to execute the command 'acfsutil volstate' failed
// due to insufficient kernel resources.
// *Action: Reduce the load on the system and retry the command.
11105, 0, "insufficient privileges to perform the command %s"
// *Cause: The caller does not have sufficient privileges to perform
// the command on the indicated mountpoint.
// Write access is required for 'acfsutil volstate -s'.
// Write access is required for 'acfsutil volstate -c'.
// *Action: Obtain the required access rights for the indicated mountpoint
// and retry the command.
11106, 0, "failed to perform the command %s"
// *Cause: While accessing the volume, an internal ioctl request failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.

/
/
/
/ ACFS catch-all message
11111, 0, "%s"
// *Cause: None
// *Action: None

/
/ ______________________________________________________________________
/ [12000 - 12999] Snap Remaster error/warning/information/usage messages.
/
/ ____________________________________________________
/ [12000 - 12099] Snap Remaster Informational messages.
/
12000, 0, "\nRemastering snapshot '%(1)s' as the master file system,\n deleting the current master file system,\n and deleting all the other snapshots.\n\n If you continue, 'snap remaster' must run to completion.\n"
// *Document: NO
/
12001, 0, "Do you want to continue? [0=no,1=yes]: "
// *Document: NO
/
12002, 0, "reclaiming snap remaster released storage"
// *Cause: The 'acfsutil snap remaster' command has replaced the master file
// system with the remastered snapshot, releasing all the master's
// unique storage. In addition, any other snapshots that existed on
// the volume have also been removed, releasing all their unique
// storage. This storage was being marked as available in the
// Global_BitMap.
// *Action: None.
/
12003, 0, " 'snap remaster' phase: %(1)d\n"
// *Cause: The indicated 'snap remaster' conversion phase has started.
// *Action: None.
/
12004, 0, "\ninvoking ACFS Checker, which will check the remastered snapshot file system, and ACFS Fixer, which will reclaim released storage\n"
// *Cause: The ACFS Checker and the ACFS Fixer were reclaiming the storage
// released when the original master file system and other snapshots
// were deleted.
// *Action: None.
/
12005, 0, "\nSnapshot '%(1)s' has been remastered as the master file system.\n"
// *Cause: The specified snapshot has been remastered as the master file
// system. The original master file system and all the other
// snapshots have been deleted.
// *Action: None.
/
/ Messages [12006 - 12099] UNUSED and available
/ ----------------------------
/
/
/ _________________________________________________________
/ [12100 - 12199] Reserved for Snap Remaster usage messages.
/
12100, 0, "Usage: [%(1)sh] %(2)so remaster_snapshot:<name> <volume>"
// *Document: NO
/
12101, 0, " %(1)so remaster_snapshot:<name>\n - Remaster snapshot <name> to the\n master file system."
// *Document: NO
/
12102, 0, " %(1)so remaster_continue\n - Continue an interrupted snapshot remastering."
// *Document: NO
/
12103, 0, " %(1)so remaster_force\n - Skip confirmation prompt."
// *Document: NO
/
12104, 0, " %(1)so remaster_show_fixup\n - Show ACFS Checker fixup messages."
// *Document: NO
/
12105, 0, " %(1)sv - ACFS Checker Verbose mode"
// *Document: NO
/
12106, 0, " %(1)svv - ACFS Checker Very Verbose mode"
// *Document: NO
/
/ Messages [12107 - 12199] UNUSED and available Snap Remaster usages messages."
/ ----------------------------------------------------------
/
/
/ _________________________________________________________
/ [12200 - 12999] More Snap Remaster error/warning messages.
/
12200, 0, "missing required snapshot name"
// *Cause: A 'snap remaster' command was issued without a required argument.
// *Action: Specify the name of the snapshot to remaster.
/
12201, 0, "Volume signature '%(1)s' is invalid for snap remastering."
// *Cause: The volume signature indicated the volume was not in a state where
// 'snap remaster' can be performed.
// *Action: Make sure the volume is unmounted and that ACFS Checker has run
// successfully.
/
12202, 0, "Volume signature indicates 'snap remaster' in progress.\n Signature: '%(1)s'\n Use 'acfsutil snap remaster %(2)sc %(3)s'\n to complete the 'snap remaster'."
// *Cause: The volume signature indicated that 'snap remaster' was being run
// on this volume.
// *Action: Make sure 'snap remaster' is not being run on another node or by
// another user. If 'snap remaster' was started and then aborted,
// use the 'acfsutil snap remaster -c <device>' command to continue
// interrupted snapshot remastering.
/
12203, 0, "Volume signature '%(1)s' indicates 'snap remaster' can be performed.\n However, on-disk 'snap remaster' phase (%(2)d) indicates 'snap remaster' is in progress."
// *Cause: The requested 'snap remaster' failed to run because the on-disk
// information indicated that another 'snap remaster' was in progress.
// *Action: Make sure 'snap remaster' is not being run on another node or by
// another user. If 'snap remaster' was started and then aborted,
// use the ACFS Fixer to restore the file system to a good starting
// point.
/
12204, 0, "The snap remastering phase '%(1)d' is invalid.\n Valid phase range from %(2)d to %(3)d."
// *Cause: The on-disk snap remastering conversion phase had an invalid value.
// *Action: Use the ACFS Fixer to restore the file system to a good starting
// point. Report this error to Oracle Support Services.
/
12205, 0, "Snap remaster request for snapshot '%(1)s' declined.\n\n"
// *Cause: The user responded negatively when prompted to confirm the snapshot
// remastering.
// *Action: None.
/
12206, 0, "failed to fetch the ACFS Global metadata directory"
// *Cause: Snap remaster failed to read the file system's ACFS Global
// metadata directory. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12207, 0, "failed to access the remastered snapshot '%(1)s' File Entry Table"
// *Cause: The File Entry Table for the snapshot being remastered could not
// be read. Refer to accompanying messages for more information on
// the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12208, 0, "failed to copy the current '%(1)s' file entry into the remastered snapshot '%(2)s' File Entry Table"
// *Cause: Snap remaster failed to copy the indicated file entry into the
// remastered snapshot File Entry Table. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12209, 0, "failed to access on-disk structure '%(1)s'"
// *Cause: Snap remaster failed to access the indicated on-disk structure.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12210, 0, "failed to copy remastered snapshot '%(1)s' current File Entry Table file entry to the beginning of the remastered snapshot File Entry Table"
// *Cause: Snap remaster failed to copy the snapshot to be remastered's
// file entry into the snapshots File Entry Table. Refer to
// accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12211, 0, "failed to snapshot metadata from the snapshot information table"
// *Cause: Snap remaster failed to zero the snapshot metadata for all the
// other snapshots from the snapshot information table. Refer to
// accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12212, 0, "failed to reset the snapshot map header to indicate %(1)d active snapshots"
// *Cause: Snap remaster failed to set the snapshot map header to the
// indicated number of active snapshots. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12213, 0, "failed to erase the snapshot entries from the '.ACFS%(1)ssnaps%(2)s' directory"
// *Cause: Snap remaster failed to remove the deleted snapshot names from
// the indicated directory. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12214, 0, "failed to remove the remastered snapshot metadata from the snapshot information table"
// *Cause: Snap remaster failed to snapsnot information table metadata for the
// snapshot being remastered. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12215, 0, "failed to clear the snapshot storage allocation map"
// *Cause: Snap remaster failed to remove the storage allocations for the
// deleted snapshots. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12216, 0, "failed to save the current per-node local directory metadata entries for reuse"
// *Cause: Snap remaster failed to obtain the local directory metadata entries
// for each cluster node, so that this information could be used in
// the remastered snapshot. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12217, 0, "failed to initialize the locator block metadata and local directory block metadata inside the remastered snapshot"
// *Cause: Snap remaster failed to initialize the remastered snapshot locator
// block metadata and the local directory block metadata using data
// from the original master. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12218, 0, "failed to initialize the global directory block inside the remastered snapshot"
// *Cause: Snap remaster failed to initialize the remastered snapshot global
// directory block for the remastered snapshot. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12219, 0, "remastering snapshot '%(1)s' failed"
// *Cause: A 'snap remaster' command failed.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12220, 0, "The continue option failed because there was no incomplete remastered snapshot."
// *Cause: The snapshot remastering continue option was specified for a file
// system that was not an interrupted snapshot remastering.
// *Action: None.
/
12221, 0, "failed to allocate a %(1)u byte '%(2)s' buffer"
// *Cause: There was insufficient memory to allocate working structures.
// *Action: Contact Oracle Support Services.
/
12222, 0, "failed to read '%(1)s' from disk\n offset %(2)s size %(3)u"
// *Cause: Snap remaster failed to read the indicated data structure from the
// file system. Refer to accompanying messages for more information
// on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12223, 0, "failed to read '%(1)s' file entry %(2)d from disk\n offset %(3)s size %(4)u"
// *Cause: Snap remaster failed to read the indicated file entry metadata from
// the file system. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12224, 0, "Failed to change the on-disk File Entry Table starting location (_VolFETALPosition)."
// *Cause: Snap remaster failed to write the new File Entry Table starting
// offset to the remastered file system. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12225, 0, "failed to initialize extent 'Up Header' offsets and mark deleted snapshot file entries as free"
// *Cause: Snap remaster failed to change the file extent 'Up Header' offsets
// so they are pointing to the remastered File Entry Table and to
// change the state of deleted snapshot file entries to available for
// allocation as new files. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12226, 0, "failed to read the file entry for the master file system File Entry Table"
// *Cause: Snap remaster failed to read the file entry for the master File
// Entry Table. Refer to accompanying messages for more information
// on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12227, 0, "unexpected mode %(1)s in %(2)s"
// *Cause: The reported function detected the wrong mode.
// *Action: Contact Oracle Support Services.
/
12228, 0, "The Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility attribute for the disk group is less than %(1)u.%(2)u."
// *Cause: The snapshot remaster operation was rejected because the ADVM
// disk group compatibility had not been upgraded to the indicated
// version, which is required for that command.
// *Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the
// SQL ALTER DISKGROUP statement to upgrade the disk group
// compatibility (COMPATIBLE.ADVM attribute) to the specified
// version and then re-issue the original command. If the disk
// group compatibility cannot be upgraded, update the ACFS
// compatibility using the 'acfsutil compat set' command and then
// re-issue the original command.
/
12229, 0, "Replication must be terminated before the volume can be remastered."
// *Cause: A 'snap remaster' command was issued for a volume that was being
// replicated.
// *Action: 'snap remaster' cannot be performed on a file system that is being
// replicated. If appropriate, terminate replication on this file
// system with the command 'acfsutil repl terminate primary
// <mountpoint>'.
/
12230, 0, "failed to find the snapshot '%(1)s'"
// *Cause: The specified snapshot was not found.
// *Action: Make sure the snapshot name is correct.
/
12231, 0, "failed to initialize file ID %(1)u for access"
// *Cause: Snap remaster failed to initialize data structures allowing access
// to the indicated file ID.
// *Action: Run the ACFS Fixer.
/
12232, 0, "failed to create a file access structure for file ID %(1)u"
// *Cause: Snap remaster failed to create a structure for accessing the
// indicated file ID. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12233, 0, "failed to access the remastered File Entry Table using file ID %(1)u"
// *Cause: Snap remaster failed to read the File Entry Table for the
// remastered snapshot. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12234, 0, "failed to access the Snap Map file entry at file ID: %(1)u"
// *Cause: Snap remaster failed to read the file entry for the Snap Map using
// the indicated file ID. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12235, 0, "failed to access the '%(1)s' file entry at file ID: %(2)u"
// *Cause: Snap remaster failed read the file entry for the indicated metadata
// using the indicated file ID. Refer to accompanying messages for
// more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12236, 0, "failed to access the Global BitMap file entry at file ID: %(1)u"
// *Cause: Snap remaster failed to read the file entry for the Global BitMap
// using the indicated file ID. Refer to accompanying messages for
// more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12237, 0, "failed to read the file extent map for file ID %(1)u"
// *Cause: Snap remaster failed to read file storage allocation information
// for the file ID indicated file. Refer to accompanying messages for
// more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12238, 0, "metadata write failed\n offset %(1)s size %(2)u file ID %(3)u"
// *Cause: An attempt to write metadata of the indicated file ID failed.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12239, 0, "metadata copy failed\n file offset %(1)s size %(2)u file ID %(3)u"
// *Cause: An attempt to write copied metadata to the indicated file ID
// failed. Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12240, 0, "initializing metadata failed\n file offset %(1)s size %(2)u file ID %(3)u"
// *Cause: An attempt to write initialized metadata to the indicated file ID
// failed. Refer to accompanying messages for more information on
// the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12241, 0, "updating metadata failed\n file offset %(1)s size %(2)u file ID %(3)u"
// *Cause: An attempt to write updated metadata to the indicated file ID
// failed. Refer to accompanying messages for more information on
// the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12242, 0, "failed to update the extent headers with the new file ID %(1)u for the moved file entry"
// *Cause: An error occurred while attempting to update the file extent
// headers with the new file ID after the file's file entry was moved
// to the remastered File Entry Table. Refer to accompanying messages
// for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12243, 0, "failed to access the Accelerator Global BitMap file entry at file ID: %(1)u"
// *Cause: Snap remaster failed to read the indicated file entry for the
// Accelerator Global BitMap. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12244, 0, "failed to read the snap map using file ID %(1)u"
// *Cause: Snap remaster failed to initialize the snap entry table with snap
// map entries from the indicated file ID. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12245, 0, "failed to update the file extent parent pointers for file ID: %(1)u"
// *Cause: An error occurred while attempting to update the file extent
// parent pointer after the file's file entry was moved to the
// remastered File Entry Table. Refer to accompanying messages for
// more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12246, 0, "failed to release file ID %(1)u file entry"
// *Cause: An error occurred while releasing the indicated file entry.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12247, 0, "failed to fetch the remastered snapshot Global directory metadata: file ID %(1)u"
// *Cause: Snap remaster failed to read the Global directory metadata using
// the indicated file ID from the remastered File Entry Table.
// Refer to accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12248, 0, "failed to rebuild directory '%(1)s': file ID %(2)u"
// *Cause: Snap remaster failed to reconstruct the indicated file system
// directory after deleted files were removed. Refer to accompanying
// messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12249, 0, "failed to allocate storage from the Global BitMap file ID: %(1)u"
// *Cause: Snap remaster failed to find free storage in the Global BitMap.
// Refer to accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12250, 0, "failed to find an expected %(1)s data structure on an in-memory linked list"
// *Cause: Snap remaster failed to find the indicated data structure.
// *Action: Contact Oracle Support Services.
/
12251, 0, "failed to add file ID %(1)u to the File Entry Table free list"
// *Cause: Snap remaster failed to add the indicated file ID to the remastered
// File Entry Table list of available for reuse file entries. Refer
// to accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12252, 0, "failed to add file ID %(1)u to the in-memory file entry cache"
// *Cause: Snap remaster failed to read the indicated file ID and add it to
// the file entry cache for reuse in the remastered snapshot. Refer
// to accompanying messages for more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12253, 0, "failed to update file ID %(1)u storage"
// *Cause: An error occurred while updating the indicated file entry's storage.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12254, 0, "failed to remove the file ID %(1)u storage"
// *Cause: An error occurred while removing the indicated file entry's storage.
// Refer to accompanying messages for more information on the
// problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12255, 0, "failed to delete file names from directory '%(1)s'"
// *Cause: Snap remaster failed to delete the files in the indicated
// directory. Refer to accompanying messages for more information on
// the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12256, 0, "failed to delete all the .ACFS%(1)srepl%(2)s subdirectories"
// *Cause: Snap remaster failed to delete all the subdirectories in the
// indicated directory. Refer to accompanying messages for more
// information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12257, 0, "Snapshot '%(1)s' replication must be terminated before the volume can be remastered."
// *Cause: A 'snap remaster' command was issued for a volume that was was
// replicating snapshots.
// *Action: 'snap remaster' cannot be performed on a file system that is being
// replicated. Terminate replication on this file system with the
// command 'acfsutil repl terminate primary <mountpoint>'.
/
12258, 0, "cannot find the ACFS Checker and Fixer utility: %(1)s"
// *Cause: The 'snap remaster' back-end utility (the ACFS Checker and Fixer)
// could not be found.
// *Action: Make sure ACFS has been properly installed. If the solution is not
// clear, contact Oracle Support Services.
/
12259, 0, "ACFS Checker and Fixer returned an error."
// *Cause: The 'snap remaster' back-end utility (ACFS Checker and Fixer)
// returned an error. Refer to accompanying messages for
// more information on the problem.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12260, 0, "ACFS Checker and Fixer failed to perform the 'snap remaster'\n command: %(1)s"
// *Cause: The indicated ACFS Checker and Fixer command failed.
// *Action: Correct the problem indicated by the other messages. If the
// solution is not clear, contact Oracle Support Services.
/
12261, 0, "Volume signature indicates 'snap remaster' was in progress.\n Signature: '%(1)s'\n Use\n 'acfsutil snap remaster %(2)sc %(3)s'\n to complete the 'snap remaster'.\n Or to reformat the volume, reissue %(4)s with the %(5)sf option."
// *Cause: The volume signature indicates that 'snap remaster' was being run on
// this volume.
// *Action: Make sure 'snap remaster' is not being run on another node or by
// another user. If 'snap remaster' had been started and then aborted,
// use the 'acfsutil snap remaster -c <device>' command to continue
// the interrupted snapshot remastering.
/
12262, 0, "'snap remaster' rejected because this file system uses an accelerator volume."
// *Cause: 'snap remaster' command was issued for a file system with an
// accelerator volume.
// *Action: None.
/
12263, 0, "ACFS Plugins must be disabled before the file system can be remastered."
// *Cause: An 'acfsutil snap remaster' command was rejected because the
// specified file system had Oracle ACFS plug-ins enabled.
// *Action: If appropriate, disable ACFS Plug-ins with the command
// 'acfsutil plugin disable <mountpoint>' and retry the operation.
/
12264, 0, "ACFS Plugins are enabled on node: %(1)s."
// *Cause: An 'acfsutil snap remaster' command was rejected because the
// specified file system had Oracle ACFS plug-ins enabled on the
// indicated node.
// *Action: If appropriate, disable ACFS Plug-ins with the command
// 'acfsutil plugin disable <mountpoint>' and retry the operation.
/
12265, 0, "'snap remaster' cannot be used on a file system with ACFS security."
// *Cause: An 'acfsutil snap remaster' command was rejected because the
// specified file system had Oracle ACFS security enabled.
// *Action: None.
/
12266, 0, "'snap remaster' cannot be used on a file system with ACFS encryption."
// *Cause: An 'acfsutil snap remaster' command was rejected because the
// specified file system had Oracle ACFS encryption enabled.
// *Action: None.
/
12267, 0, "failed to clean the .ACFS directory tree"
// *Cause: An attempt to remaster an Oracle ACFS snapshot failed to clean the
// .ACFS directory tree. The accompanying messages provide detailed
// failure information.
// *Action: Correct the problem indicated by the other error messages.
// Use the 'acfsutil snap remaster -c <device>' command to continue
// the interrupted snapshot remastering.
/
12268, 0, "failed to copy the .ACFS directory tree to the snapshot"
// *Cause: An attempt to remaster an Oracle ACFS snapshot failed to copy the
// .ACFS directory tree to the snapshot. The accompanying messages
// provide detailed failure information.
// *Action: Correct the problem indicated by the other error messages.
// Use the 'acfsutil snap remaster -c <device>' command to continue
// the interrupted snapshot remastering.
/
12269, 0, "failed to update directory %(1)s"
// *Cause: An attempt to remaster an Oracle ACFS snapshot failed to update the
// indicated directory. The accompanying messages provide detailed
// failure information.
// *Action: Correct the problem indicated by the other error messages.
// Use the 'acfsutil snap remaster -c <device>' command to continue
// the interrupted snapshot remastering.
/
12270, 0, "failed due to remapped metadata files from a prior file system shrink"
// *Cause: An attempt to remaster an Oracle ACFS snapshot failed because the
// specified snapshot contains metadata files that were remapped
// as part of a prior file system shrink. Such files would prevent
// the remastered file system from mounting.
// *Action: Retry the operation, selecting a different snapshot to remaster.
/
/
/ Messages [12271 - 12999] UNUSED and available
/ ----------------------------

// advmutil remote (export, transport, and session)
//
/ export_gateway errors
13000, 0, "unable to determine the cluster type"
// *Cause: An 'advmutil' command failed to determine the type of cluster
// that contained the local server. The accompanying messages
// provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated
// problems, and retry the operation.
13001, 0, "insufficient privileges - ASM administrator group access required"
// *Cause: A requested 'advmutil' command failed because the user
// did not have the required ASM Administrator privilege.
// *Action: Retry the command from an account with the required privilege.
13002, 0, "Command is not supported on a cluster of the current type."
// *Cause: A requested 'advmutil export' or 'advmutil transport' command failed
// because the command could only be run on a Domain Services Cluster.
// *Action: Verify that this command is the correct command to execute,
// and if so, retry the command on a Domain Services Cluster.
/ advmutil export mapping usage
13015, 0, "export mapping %(1)sc <clusterName> [%(2)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
/13031, 0, " %(1)sh - help/usage information"

/ advmutil export mapping errors
13016, 0, "A failure occurred while updating the currently active export list for cluster '%(1)s'."
// *Cause: An 'advmutil export create' or 'advmutil export mapping' command
// failed because an error occurred when attempting to modify the
// currently active configuration for the indicated cluster.
// Accompanying messages provide further failure details.
// *Action: Examine the accompanying messages, address any issues raised
// and retry the original request.

/ advmutil export create usage
13025, 0, "export create %(1)sn <exportName> %(2)sc <clusterName> %(3)sp <storageRepo> {%(4)ss <size> | %(5)sf} [%(6)sh]"
13026, 0, " %sn <exportName> - name of the export"
13027, 0, " %(1)sc <clusterName> - member cluster name"
13028, 0, " %sp <storageRepo> - location of the storage repository in which the backing file will be stored"
13029, 0, " %(1)ss <fileSize> - file size - <num>{'K'|'M'|'G'|'T'|'P'|'E'}"
13030, 0, " %(1)sf - reuse an existing storage repository"
13031, 0, " %(1)sh - help/usage information"

/ export create error messages/informational
13032, 0, "invalid combination of 'fileSize' and 'force' options"
// *Cause: The 'advmutil export create' command was rejected because the
// 'fileSize' and 'force' options were both used on the command line.
// *Action: To create an export where the backing store does not exist, execute
// the 'advmutil export create' command specifying the required
// 'fileSize' option, which will create the backing store. To reuse an
// existing backing store, execute the 'export create' with the
// 'force' option.
13033, 0, "The 'force' option cannot be used if the backing store does not exist."
// *Cause: The 'advmutil export create' command was rejected because the
// 'force' option was specified and the backing store did not exist.
// *Action: To create an export where the backing store does not exist, execute
// the 'advmutil export create' command specifying the required
// 'fileSize' option to create the backing store at the same time.
13034, 0, "insufficient file space - requested: %(1)s available: %(2)s"
// *Cause: An 'advmutil export' or 'advmutil resize' command failed because
// writing the file required the indicated additional space when only
// the indicated space was available.
// *Action: Use a requested file size that fits in the storage repository's
// free space, or create additional space within the storage
// repository.
13035, 0, "missing <exportName>"
// *Cause: An 'advmutil export' command was rejected because the <exportName>
// argument was not specified.
// *Action: Reissue the command, specifying the <exportName> on the command
// line.
13036, 0, "The location '%s' exists but is not a directory."
// *Cause: An advmutil export command failed because the indicated
// location for the storage repository existed on disk and was not a
// directory.
// *Action: To use the indicated location, remove the conflicting object and
// retry the command. Otherwise, retry the command specifying a
// location that was a directory or that does not exist.
13037, 0, "missing <storageRepo>"
// *Cause: An advmutil export command was rejected because the <storageRepo>
// argument was not specified.
// *Action: Reissue the command, specifying the <storageRepo> on the command
// line.
13038, 0, "The specified '<exportName>' is longer than the maximum length %(1)d."
// *Cause: An advmutil export command was rejected because the <exportName>
// exceeded the indicated maximum length.
// *Action: Retry the command, specifying an <exportName> with a length
// less than or equal to the indicated maximum length.
13039, 0, "The <storageRepo>/<exportName> '%(1)s' exists but is not a file."
// *Cause: An 'advmutil export create' or advmutil transport create' command
// failed because it expected the location pointed to by the specified
// <storageRepo> and <exportName> to be a file or not to exist. The
// path pointed to an existing, on-disk, object that was not a file.
// *Action: To use the indicated location, remove the conflicting object and
// retry the command. Otherwise, retry the command specifying a
// location that is a file or that does not exist.
13040, 0, "missing <clusterName>"
// *Cause: An 'advmutil export', 'advmutil transport', or 'advmutil resize'
// command was rejected because the <clusterName> was not specified.
// *Action: Retry the command, specifying the <clusterName> on the command
// line.
13041, 0, "The export '%(1)s' for cluster '%(2)s' already exists as file path '%(3)s'."
// *Cause: An 'advmutil export create' command failed because a file
// already existed on disk at the indicated location.
// *Action: To continue using this file, rerun the advmutil export create
// command with the [-f <force>]
// option. Otherwise, remove the existing export using the command
// 'advmutil export delete' and retry the command
// 'advmutil export create' using the specified name.
13042, 0, "unable to create file '%(1)s'"
// *Cause: An 'advmutil export create' or 'advmutil export resize' command
// failed to create or resize the indicated file in the specified
// storage repository.
// *Action: Examine the accompanying messages, address issues, and retry.
13043, 0, "missing <size> option"
// *Cause: An 'advmutil export create' or 'advmutil export resize' command
// was rejected because the <size> argument was not specified.
// *Action: Reissue the command, specifying the <size> on the command line.
13044, 0, "Unable to determine the GUID for cluster '%(1)s'."
// *Cause: The requested advmutil command failed because it was
// unable to determine the Globally Unique Identifier (GUID) for the
// indicated cluster name. The accompanying messages provide further
// failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
13045, 0, "Export and backing store for volume '%(1)s' for cluster '%(2)s' created."
// *Document: NO
13046, 0, "Export for volume '%(1)s' for cluster '%(2)s' created, backing store reused."
// *Document: NO
13047, 0, "Invalid file size %(1)s is smaller than the minimum supported file size %(2)s."
// *Cause: An 'advmutil export create' or 'advmutil export resize' was
// rejected because the indicated size is smaller than the indicated
// supported minimum file size.
// *Action: Retry the command, specifying a file size larger than the indicated
// minimum.
13048, 0, "The file path for export name '%(1)s' is longer than the maximum allowed '%(2)d' characters."
// *Cause: An 'advmutil export create' command was rejected because the provided
// arguments for <storageRepo>, <clusterName>, and <exportName>
// resulted in a file path <storageRepo>/<clusterGUID>/<exportName>
// that was longer than the indicated maximum path length.
// *Action: Retry the command, specifying a smaller <storageRepo> and
// <exportName> so that the combined length is less than the indicated
// maximum.
13049, 0, "The location '%(1)s' is not a mounted ACFS file system."
// *Cause: An 'advmutil export create' command failed because the indicated
// location, specified as <storageRepo>, was not an ACFS file system.
// *Action: Retry the command, ensuring that the location specified for
// <storageRepo> is an ACFS file system.
13050, 0, "File '%(1)s' does not exist."
// *Cause: An 'advmutil export resize' or 'advmutil transport create' command
// failed because the indicated file did not exist.
// *Action: Retry the command, ensuring the arguments specifying <fileName>,
// <clusterName>, and <storageRepo> used to create the path name
// are correct.
/ Message 13051 UNUSED and available
13052, 0, "Failed to create export '%(1)s' for cluster '%(2)s'."
// *Cause: An 'advmutil export create' command failed because the specified
// export could not be created. The accompanying messages provide
// further failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
13053, 0, "Creating File Backed Volume."
//*Document: No
13054, 0, "The specified export already exists in the Oracle Cluster Registry (OCR)."
// *Cause: An 'advmutil export create' was rejected because the export already
// existed in the Oracle Cluster Registry (OCR).
// *Action: To recreate an existing export with a new File Backed Volume, first
// remove the export using 'advmutil export remove' and retry the
// 'advmutil export create' command. Otherwise, use the existing
// export or create a new one using a different name.

/ advmutil export remove usage
13055, 0, "export remove %(1)sc <clusterName> [%(2)sp <storageRepo> %(3)sn <exportName>] [%(4)sf] [%(5)sb] [%(6)sy] [%(7)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
/13028, 0, " %(1)sp <storageRepo> - location of the storage repository in which the backing file will be stored"
/13026, 0, " %(1)sn <exportName> - name of the export"
13056, 0, " %(1)sf - force removal even if export mapping is active"
13057, 0, " %(1)sb - remove the backing file for this map"
13058, 0, " %(1)sy - Do not prompt when removing the backing file for cluster"
/13031, 0, " %(1)sh - help/usage information"

/ advmutil export remove errors and queries
13061, 0, "missing <exportName> or <storageRepo>"
// *Cause: An 'advmutil export remove' command was rejected because both
// <exportName> and <storageRepo> must be specified on the command
// line, and one of them was not specified.
// *Action: Retry the command specifying <storageRepo> and <exportName>.
13062, 0, "File '%(1)s' does not exist."
// *Cause: An 'advmutil export remove' or 'advmutil export list' command
// expected to find the indicated file, which did not exist.
// *Action: None. The command will complete normally.
13063, 0, "Continue to remove all exports for cluster '%(1)s'?"
// *Document: NO
13064, 0, "[y/n]: "
// *Document: NO
/ Message 13065 UNUSED and available
13066, 0, "Removed export '%(1)s' from cluster '%(2)s'."
// *Document: NO
13067, 0, "Unable to remove export '%(1)s' from cluster '%(2)s'."
// *Cause: An 'advmutil export remove' command failed because it could not
// remove the indicated export from the indicated cluster.
// The accompanying messages provide further failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
13068, 0, "unable to clear ACFS remote usage attribute for file '%(1)s'"
// *Cause: An attempt to remove the indicated file from usage in a specified
// storage repository failed because the ACFS Remote attribute could
// not be cleared. If the ACFS remote usage attribute is set, the
// file will not be deleted and its storage will not be removed as
// part of the export remove.
// *Action: Check that the indicated file exists and if so, use
// 'acfsutil remote clear' to clear the ACFS remote attribute
// explicitly before manually deleting the file. If unable to delete
// the indicated file, then contact Oracle Support Services.
13069, 0, "unable to open backing store file '%s(1)'"
// *Cause: An attempt to remove the indicated ACFS remote backing storage
// file from usage in a specified storage repository failed because
// the file could not be opened to clear the ACFS remote attribute.
// Additional messages provide detailed failure information.
// *Action: Check that the file exists and if so, use 'acfsutil remote clear'
// to clear the ACFS remote attribute explicitly before manually
// deleting the file. If unable to delete the existing file, contact
// Oracle Support Services.

/ advmutil export list usage
13070, 0, "export list [%(1)sc <clusterName>] [%(2)so <options>] [%(3)sg <groupType>] [%(4)sa] [%(5)sn] [%(6)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
/13167, 0, " %(1)sa - display only active exports"
13071, 0, " %(1)sn - do not print column headers"
13072, 0, " %(1)so - options, comma separated, no spaces: '%(2)s'"
13073, 0, " %(1)sg <groupType> - group by 'clusterName', 'clusterGUID', or 'storageRepo'"
/13031, 0, " %(1)sh - help/usage information"
/
/ export list errors/informational
13076, 0, "Invalid options '%(1)s' specified. Valid options are '%(2)s'."
// *Cause: An 'advmutil export list' command was rejected because the indicated
// option was not valid.
// *Action: Retry the command specifying a list of valid, comma-separated
// options.
13077, 0, "invalid group type '%(1)s' specified"
// *Cause: An 'advmutil export list' command was rejected because the
// specified group type was not a valid group type. Valid groups are
// 'clusterName', 'clusterGUID', and 'storageRepo'.
// *Action: Retry the command specifying a valid group type.
13078, 0, "unable to find the cluster name for the GUID '%(1)s'"
// *Cause: An 'advmutil export list' command failed because it was unable to
// determine the cluster name from the Globally Unique Identifier
// (GUID). The accompanying messages provide further failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
/ bug 24455356 - in discussion with dev.
13079,0, "more options specified than the maximum allowed: %(1)d"
// *Cause: An 'advmutil export list command' was rejected because more options
// were specified than the indicated maximum.
// *Action: Retry command specifying fewer options than the indicated maximum.
13080, 0, "Listing active exports."
// *Document: NO
13081, 0, "Export list failed."
// *Cause: An advmutil export list' command failed because the system call to
// retrieve the export information failed. The accompanying messages
// provide further failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
13082, 0, "Removed '%(1)d' exports, failed '%(2)d'."
// *Document: NO
13083, 0, "unable to mark file '%(1)s' for ACFS remote usage"
// *Cause: An operation to mark the indicated file for ACFS Remote usage in a
// specified storage repository failed. This will not affect normal
// usage as a ACFS remote backing store, however with the ACFS remote
// attribute not set the file will not be protected from local
// modification.
// *Action: The export will be created and operate normally. Run
// 'acfsutil remote set' on the indicated file to mark the indicated
// file for ACFS remote usage.

/ advmutil export resize usage
13090, 0, "export resize %(1)sc <clusterName> %(2)sp <storageRepo> %(3)sn <exportName> %(4)ss <size> [%(5)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
/13028, 0, " %(1)sp <storageRepo> - location of the storage repository in which the backing file will be stored"
/13026, 0, " %(1)sn <exportName> - name of the export"
13091, 0, " %(1)ss <fileSize> - file size - [+]<num>{'K'|'M'|'G'|'T'|'P'|'E'}"
/13031, 0, " %(1)sh - help/usage information"
/
/ export resize errors/informational
13092, 0, "invalid file size or file size increment specified"
// *Cause: An 'advmutil export size' command was rejected because an invalid
// file size or file size increment was specified.
// *Action: Retry the command, specifying a file size greater than the current
// file size or a file size increment equal to or greater than 1MB.
// Shrinking File Backed Volume (FBV) files can only be done on a
// Member Cluster using the command 'acfsutil size'.
/ Message 13093 UNUSED and available
13094, 0, "File was resized from '%(1)s 'to '%(2)s'."
// *Document: NO

/
/ transport create usage
13100, 0, "transport create %(1)sc <clusterName> [%(1)sb <binding> [%(3)sn <netNum>]] | [%(4)si <resourceID>] [%(5)sf] [%(6)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
13101, 0, " %(1)sb <binding> - transport VIP (host name or network address)"
13102, 0, " %(1)sn <netNum> - optional network number (default = 1)"
13103, 0, " %(1)si <resourceID> - alternate (existing) resource identifier"
13104, 0, " %(1)sf - force acceptance of specified preexisting binding"
/13031, 0, " %(1)sh - help/usage information"

/ transport create errors/informational
13107, 0, "no available sequence number"
// *Cause: An 'advmutil transport create' command failed because all
// of the available transport sequence numbers for the specified
// transport type were in use.
// *Action: Use the 'advmutil transport remove' command to delete an existing
// transport that is not in use. Then retry the
// 'advmutil transport create' command.
13108, 0, "transportId '%(1)s.%(2)s' created for cluster '%(3)s'"
// *Document: NO
13109, 0, "Transport resource '%(1)s' is in use by other transports."
// *Cause: An 'advmutil transport create' command was rejected because the
// indicated resource existed and was in use by other transports.
// *Action: To reuse an existing transport resource, retry the command,
// specifying the 'resourceID' option for that resource. The
// 'resourceID' is the resource name minus the leading 'ora.' and
// the trailing '.transport_vip'.
13110, 0, "Transport '%(1)s' already exists on cluster '%(2)s'."
// *Cause: An 'advmutil export create' command was rejected because the
// indicated transport already existed on the indicated cluster.
// *Action: Retry the command, specifying a different resourceID.
/
/ transport remove usage
13112, 0, "transport remove %(1)sc <clusterName> %(2)si <transportID> [%(3)sh]"
/13027,0, " %(1)sc <clusterName> - member cluster name"
13113, 0, " %(1)si <transportID> - '<transportType>.<sequenceNum>'"
/13031, 0," %(1)sh - help/usage information"

/ transport remove errors/informational
13115, 0, "missing <transportID>"
// *Cause: An 'advmutil transport remove' command was rejected because the
// <transportID> argument was not specified."
// *Action: Retry the command, specifying the <transportID> on the command line.
/ bug 24455356 - in discussion with dev.
13116, 0, "invalid transport ID '%(1)s'"
// *Cause: An 'advmutil transport remove' command was rejected because
// the indicated transport identifier was not specified in the form
// '<transportType>.<sequenceNumber>'.
// *Action: Retry the command, specifying the <transportID> using the correct
// format.
13117, 0, "The transport '%(1)s.%(2)s' does not exist for cluster '%(3)s'."
// *Cause: An 'advmutil transport remove' command failed because the
// transport did not exist for the indicated cluster name.
// *Action: Verify the available <transportIDs> for this cluster by using the
// 'advmutil transport list' command. Retry the command, specifying
// a valid <transportID>. Alternatively, retry the command
// specifying a different cluster name for which the specified
// <transportID> is valid.
13118, 0, "Transport '%(1)s.%(2)s' for cluster name '%(3)s' was removed."
// *Document: NO
/ bug 24455356 - in discussion with dev.
13119, 0, "No eligible exports were found."
// *Cause: No exports existed for the specified input criteria.
// *Action: Informational.
/
/ transport list usage
13125, 0, "transport list [%(1)sc <clusterName> | %(2)sg <clusterGUID>] [[%(3)si <transportID>] [%(4)sv]] [%(5)sh]"
/13027, 0, " %(1)sc <clusterName> - member cluster name"
13126, 0, " %(1)sg <clusterGUID> - cluster Globally Unique IDentifier (GUID)"
/13111, 0, " %(1)si <TransportID> - <transportType>.<sequenceNum>"
13128, 0, " %(1)sv - verbose output including XML data"
/13031, 0, " %(1)sh - help/usage information"

/ transport list errors/informational
13130, 0, "Both <clusterName> and <clusterGUID> were specified on the command line."
// *Cause: An 'advmutil transport list' command was rejected because both the
// <clusterName> and the <clusterGUID> were specified on the command
// line.
// *Action: Retry the command, specifying either a <clusterName>,
// a <clusterGUID>, or neither.
13131, 0, "missing <clusterName> or <clusterGUID>"
// *Cause: An 'advmutil transport list' command was rejected because a
// <transportID> was specified without also specifying a
// <clusterGUID> or a <clusterName> on the command line.
// *Action: Retry the command, specifying either a <clusterName> or a
// <clusterGUID> when specifying a <transportID>.
13132, 0, "missing <transportID> argument"
// *Cause: An 'advmutil transport list' command was rejected because the
// verbose option was specified without specifying a <transportID>.
// *Action: Retry the command, specify either a <transportID> and the verbose
// option, or removing the verbose option.
13133, 0, "No eligible transports were found."
// *Cause: No transports existed for the specified input criteria.
// *Action: Informational

/ Export/Transport Ioctl errors (preceded by a command specific failure message)
/
13150, 0, "unknown system call failure - 'ASDO_E_FAILURE'"
// *Cause: The requested operation failed because of an unhandled kernel
// ioctl error.
// The accompanying messages provide further failure details.
// *Action: Contact Oracle Support Services.
13151, 0, "invalid user address passed to the 'oracleadvm' driver -'ASDO_E_FAULT'"
// *Cause: The requested operation failed because the oracleadvm driver
// attempted to access an invalid user memory address.
// *Action: Contact Oracle Support Services.
13152, 0, "GUID for the cluster name not found - 'ASDO_E_GUID_NOT_FOUND'"
// *Cause: The requested operation failed because it could not determine the
// Globally Unique IDentifier. Additional messages may accompany this
// to provide further failure details.
// *Action: Examine any additional messages, address any issues raised, and
// retry the original command.
// Additionally, verify the cluster name is valid, and retry the
// command specifying a valid
// cluster name. Finally, contact Oracle Support Services.
13153, 0, "invalid argument - 'ASDO_E_INVAL_ARG'"
// *Cause: The requested operation failed because an invalid argument was
// passed to a system call.
// *Action: Contact Oracle Support Services.
13154, 0, "invalid system call opcode - 'ASDO_E_INVAL_TYPE'"
// *Cause: The requested operation failed because an invalid opcode was
// passed to a system call.
// *Action: Contact Oracle Support Services.
13155, 0, "specified storage repository not mounted - 'ASDO_E_REPOMOUNT_NOT_FOUND'"
// *Cause: The requested operation failed because the storage repository was
// not mounted.
// *Action: Verify that the specified storage repository is a valid ACFS file
// system.
// Use 'advmutil export list' to determine if the storage repository
// is listed as a valid storage repository.
// Retry the command, specifying a valid storage repository.
13156, 0, "required file path not found - 'ASDO_E_PATH_NOT_FOUND'"
// *Cause: The requested operation failed because the kernel could not find the
// required path.
// *Action: Contact Oracle Support Services.
13157, 0, "repository directory not found - 'ASDO_E_REPOPATH_NOT_FOUND'"
// *Cause: The requested operation failed because the required repository
// directory was not found.
// *Action: Contact Oracle Support Services.
13158, 0, "insufficient memory - 'ASDO_E_NOMEM'"
// *Cause: The operation failed because the 'oracleadvm' driver could not
// allocate sufficient kernel memory to perform the operation.
// *Action: Terminate un-needed processes that may be consuming kernel memory.
// Retry the command.

/ advmutil export lsof usage
13165, 0, "export lsof [%(1)sp <path>] [%(2)sa] [%(3)sh]"
13166, 0, " %(1)sp <path> - location of the directory or file"
13167, 0, " %(1)sa - display only active exports"
/13031, 0, " %(1)sh - help/usage information"

13170, 0, "export lsof ioctl failed"
// *Cause: An 'advmutil export lsof' command failed because the system call to
// retrieve the export information failed. The accompanying messages
// provide further failure details.
// *Action: Examine the accompanying messages, address any issues raised and
// retry the original request.
13171, 0, "getCurNumExports ioctl failed"
// *Cause: An 'advmutil export lsof' command failed because the system call to
// retrieve the export information failed. The accompanying messages
// provide detailed failure information.
// *Action: Contact Oracle Support Services.

/advmutil session list usage
13180, 0, "session list [%(1)sn <nodeName>] [[%(2)si <transportID>] [%(3)sv]] [%(4)sh]"
13181, 0, " %(1)sn <nodeName> - node name"
/13111, 0, " %(1)si <transportID> - '<transportType>.<sequenceNum>'"
/13128, 0, " %(1)sv - verbose output including XML data"
/13031, 0, " %(1)sh - help/usage information"

/advmutil session list errors/informational
13190, 0, "Command is not supported on a cluster of the current type."
// *Cause: An 'advmutil session list' command failed because the command
// could only be run on a Member Cluster.
// *Action: Verify that this command is the correct command to execute, and if
// so, retry the command on a Member Cluster.
/ Message 13191 UNUSED and available
13192, 0, "invalid sequence number %(1)d"
// *Cause: An 'advmutil session list' command was rejected because the
// indicated sequence number was out-of-range.
// *Action: Retry the command, specifying a sequence number between 0 - 999
// (inclusive).
13193, 0, "Node '%(1)s' does not exist on this cluster."
// *Cause: An 'advmutil session list' command failed because the specified
// node was not a member of this cluster.
// *Action: Retry the command, specifying a node that is a member of this
// cluster.
13194, 0, "invalid transport type '%(1)s' specified"
// *Cause: An 'advmutil session list' command was rejected because the
// indicated transport type specified on the command line was invalid.
// *Action: Refer to the documentation for valid transport types.
// Retry the command, specifying a valid transport type.
13195, 0, "No eligible sessions were found."
// *Cause: No sessions exist for the specified input criteria.
// *Action: Informational.
/
/ advmutil transport create resource messages
/
13250, 0, "The resource name '%(1)s)' specified by resource id '%(2)s' does not exist."
// *Cause: An 'advmutil transport create' command was rejected because
// the indicated resource identifier did not resolve to an existing
// transport resource.
// *Action: If the intent is to re-use an existing transport resource,
// reissue the 'advmutil transport create' command, specifying the
// resource identifier of an existing resource.
13251, 0, "Resource ID may not be specified together with network number or host binding."
// *Cause: An 'advmutil transport create' command was rejected because
// the resource ID option was specified with the network number or
// host binding option (or both) on the command line.
// *Action: If the intent is to reuse an existing transport resource,
// reissue the 'advmutil transport create' command specifying the
// the resource ID of an existing resource and omitting
// the options for network number or host binding.
13252, 0, "cannot create a CRS resource ('%(1)s') that already exists"
// *Cause: An 'advmutil transport create' command failed because the command
// attempted to create a Cluster Ready Services (CRS) resource that
// already existed. This is an internal error.
// *Action: Contact Oracle Support Services.
13253, 0, "The 'bind' option must be specified on the command line."
// *Cause: An 'advmutil transport create' command was rejected because
// the 'bind' option was not specified on the command line.
// *Action: Retry the 'advmutil transport create' command, specifying a
// valid 'bind' option.
13254, 0, "The binding VIP '%(1)s' does not exist in the Domain Name System (DNS)."
// *Cause: An 'advmutil transport create' command was rejected because the
// indicated binding VIP (host name or network address) was unknown.
// *Action: Retry the 'advmutil transport create' command specifying a DNS
// resolveable host name or network address.
13255, 0, "The supplied network number '%(1)s' is invalid."
// *Cause: An 'advmutil transport create' command was rejected because
// the specified network number was not a positive digit.
// *Action: Retry the 'advmutil transport create' command, specifying a valid
// network number.
13256, 0, "Entries specified on the command line already exist in the OCR."
// *Cause: An 'advmutil transport create' command was rejected because the
// bind host name or network address are already in the Oracle
// Cluster Registry (OCR).
// *Action: Retry the 'advmutil transport create' command specifying an unused
// host name or network address. Alternatively, use the 'force' option
// on the command line to allow the re-use of this binding.
13257, 0, "The specified network number '%(1)s' does not exist in the Oracle Cluster Ready Services (CRS)."
// *Cause: An 'advmutil transport create' command was rejected because an
// invalid network number was specified on the command line.
// *Action: Retry the 'advmutil transport create' command using a valid
// network number.
13258, 0, "Failed to retrieve '%(1)s' for resource '%(2)s': error %(3)d"
// *Cause: An 'advmutil transport create' command failed because it could not
// retrieve the indicated item from the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation. If unable to resolve the issues,
// contact Oracle Support Services.

/ ACFSR CRS messages
/
/ In nearly every error below, a CRS subroutine failed and specific error
/ messages accompany the error reported below.
/
13300, 0, "Cannot query Cluster Ready Services (CRS) resource '%(1)s'."
// *Cause: An 'advmutil transport' or 'advmutil export' command failed because
// it could not query the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13301, 0, "Invalid CRS attribute format detected in resource '%(1)s'."
// *Cause: An Cluster Ready Services (CRS) resource start or stop dependency
// format error was detected. This is an internal error.
// *Action: Contact Oracle Support Services.
13302, 0, "Failed to get ACFS mount points from Cluster Ready Services (CRS)."
// *Cause: An 'advmutil export create' or 'advmutil export remove' command
// failed because it could not query ACFS mount points.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13303, 0, "The Cluster Ready Services (CRS) cannot be initialized."
// *Cause: An 'advmutil transport' or 'advmutil export' command failed because
// the initialization of the Cluster Ready Services (CRS) failed.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13304, 0, "The bind host name or network address '%(1)s' is already in use in the network."
// *Cause: An 'advmutil transport create' command was rejected because the
// indicated host name or network address specified on the command
// line was in use in the network and was therefore not generally
// available for the transport.
// *Action: Retry the 'advmutil transport create', specifying a host name
// or network address that is DNS resolvable but not in use.
// Alternatively, use the 'force' option on the command line to allow
// the re-use of the specified host name or network address.
13305, 0, "Failed to start Cluster Ready Services (CRS) resource '%(1)s'."
// *Cause: "An 'advmutil transport create' failed because the indicated Cluster
// Ready Services (CRS) resource failed to start.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13306, 0, "The Cluster Ready Services (CRS) resource '%(1)s' cannot be updated."
// *Cause: An 'advmutil transport create' command failed because it was unable
// to update the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13307, 0, "Failed to retrieve the resource '%(1)s' error '%(2)d'."
// *Cause: An 'advmutil transport create' failed to cause it could not retrieve
// the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13308, 0, "Failed to retrieve the start/stop dependencies or state for resource '%(1)s': error %(2)d"
// *Cause: An 'advmutil transport create', 'advmutil export create', or
// 'advmutil export remove' command failed because it could not
// retrieve the current start or stop dependency or the resource state
// for the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation. If unable to resolve the issues,
// contact Oracle Support Services.
13309, 0, "Failed to set the '%(1)s' resource attribute for resource '%(2)s': error %(3)d"
// *Cause: An 'advmutil transport create' failed because it could not set
// the start and stop dependencies for the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13310, 0, "Failed to stop Oracle Ready Services (CRS) resource '%(1)s'."
// *Cause: An 'advmutil transport remove' command failed because the indicated
// resource could not be stopped.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13311, 0, "Failed to delete Oracle Ready Services (CRS) resource '%(1)s'."
// *Cause: An 'advmutil transport remove' command failed because the indicated
// resource could not be deleted.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13312, 0, "The Cluster Ready Services (CRS) resource '%(1)s' does not exist."
// *Cause: An 'advmutil transport remove' command detected that an expected
// CRS resource did not exist.
// *Action: None. This is a warning only. The command completed normally.
13313, 0, "The transport identifier '%(1)s' was not found in the Oracle Cluster Registry (OCR)."
// *Cause: An 'advmutil export create' command failed because it could not
// find a transport identifier in the Oracle Cluster Registry (OCR).
/ This is an internal error.
// *Action: Contact Oracle Support Services.
13314, 0, "Failed to add start and stop dependencies to Cluster Ready Services (CRS) resource '%(1)s'."
// *Cause: An 'advmutil transport create' command failed because it could not
// add start and stop dependencies to the indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13315, 0, "Failed to remove Cluster Ready Services (CRS) resource '%(1)s."
// *Cause: An 'advmutil export remove' command failed to remove the indicated
// start and stop dependency from the applicable transport resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13316, 0, "failed to add cluster Ready Services (CRS) resource '%(1)s'"
// *Cause: An 'advmutil export create' command failed to add the indicated
// resource to the Cluster Ready Resources (CRS).
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13317, 0, "Failed to create Cluster Ready Services (CRS) resource '%(1)s': error '%(2)d'."
// *Cause: An 'advmutil transport create' command failed to create the
// indicated resource.
// The accompanying messages provide detailed failure information.
// *Action: Examine the accompanying messages, resolve the indicated problems,
// and then retry the operation.
13318, 0, "failed to find the file system resource name for the storage repository mount point '%(1)s' for cluster '%(2)s'"
// *Cause: An 'advmutil export create' command failed because it could not
// find the resource name for the mount point of the
// indicated storage repository for the indicated cluster.
// *Action: Examine the ACFS file system resources (ora.acfs.type). Ensure that
// The ACFS file system for the storage repository is listed and is
// ONLINE for the cluster in Cluster Ready Services (CRS).

/ Misc ACFSR messages (ran out of space in export_create)
13375, 0, "The export name '%(1)s' contains non-alphanumeric characters."
// *Cause: An advmutil export command was rejected because the indicated export
// name contained non-alphanumeric characters.
// *Action: Retry the command, specifying an export name containing only
// alphanumeric characters.
13376, 0, "invalid size specification '%(1)s'"
// *Cause: An 'advmutil export create' or 'advmutil export resize' command
// was rejected because the indicated size specification was invalid.
// A valid size consists of a numeric value followed by
// 'K', 'M', 'G', 'T', 'P', or 'E'.
// *Action: Retry the command, specifying a valid size specification.
13377, 0, "The storage repository '%(1)s' is compressed or has compressed files."
// *Cause: An 'advmutil export create' command was rejected because the
// indicated storage repository was compressed or contained
// compressed files.
// *Action: Retry the command, specifying an uncompressed storage repository.

/
/ vim: ts=4 expandtab textwidth=0 wrapmargin=0

OHA YOOOO