Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Disk File Optimizer Error

SOLVED
Go to solution
Lisa Collins
Advisor

Disk File Optimizer Error

Yesterday, I used the DFO software to attempt to defrag a disk that showed 84% fragmented. When the software finished processing, the disk was then 98% fragmented, more fragmented than before using the software. I was going to attempt to run the procedure again today but I am having problems. I enter this command.

defrag file NEOMN2$DRA1:[000000...]*.*;*

I get a response

Disk File Optimizer for OpenVMS DFG V2.9
© Copyright 2005 Hewlett-Packard Development Company,L.P.
%DFG-S-CREATED, DFG$SCRIPT1A created

But then the defragging never really starts. When I look at the log file, I see this error

Defragmentation process for script DFG$SCRIPT21 has completed
Completion time was 2-MAR-2006 15:03:38.39
%DFG-W-UNRECOVERR, unrecoverable error
Target volume was NEOMN2$DRA1 (_NEOMN2$DRA1:)

Can someone help me understand what might be causing the error?

Thank You,
Lisa
52 REPLIES
Duncan Morris
Honored Contributor
Solution

Re: Disk File Optimizer Error

Sounds like some condition caused DFO to exit before it finished processing.

If you have DFU available then use

DFU> VERIFY NEOMN2$DRA1 /DIR

otherwise

$ ANAL/DISK NEOMN2$DRA1

There may well be problems on the drive which need to be attended to before proceeding (perhaps a temporary file left over from DFO??)
Lisa Collins
Advisor

Re: Disk File Optimizer Error

I used the anaylze disk and I see this

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
%ANALDISK-W-DELHEADER, file (145,4,0) INETDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (161,4,0) MULTINET_SOCKET_LIBRARY.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (162,4,0) MULTINET_TOPS_LIBRARY.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (167,3,0) NTYDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (170,2,0) INETDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (171,1,0) INETDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (181,4,0) MULTINET_VMS_SHAREABLE.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (186,2,0) MULTINET_SOCKET_LIBRARY.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (187,1,0) MULTINET_SOCKET_LIBRARY.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (188,1,0) MULTINET_TOPS_LIBRARY.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (192,2,0) NTYDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (193,1,0) NTYDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (198,4,0) UCXDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (199,4,0) LAVDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (200,4,0) RMTDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (201,4,0) RCDDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (202,4,0) PWIPDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (203,4,0) LOADABLE_NOT_ASSIST.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (205,1,0) MULTINET_VMS_SHAREABLE.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (215,2,0) UCXDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (217,1,0) UCXDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (218,1,0) LAVDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (219,1,0) RMTDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (220,1,0) RCDDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (221,1,0) PWIPDRIVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (222,1,0) LOADABLE_NOT_ASSIST.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (234,4,0) SERVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (235,4,0) MULTINET_DPC_SHR.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (243,2,0) SERVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (244,1,0) SERVER.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (245,1,0) MULTINET_DPC_SHR.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (254,2,0) MULTINET_TOPS_LIBRARY.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (271,4,0) LOADABLE_R_SERVICES.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (275,2,0) LOADABLE_R_SERVICES.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (276,1,0) LOADABLE_R_SERVICES.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (308,2,0) UCX$IPC_SHR.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (309,1,0) UCX$IPC_SHR.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (325,1,0) LOADABLE_BIND.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (326,2,0) LOADABLE_NAMED_CONTROL.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (328,4,0) LOADABLE_NAMED_CONTROL.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (329,4,0) NAMED.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (339,2,0) LOADABLE_KERBEROS_TELNET.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (340,1,0) LOADABLE_KERBEROS_TELNET.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (341,1,0) LOADABLE_SNMP_AGENT.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (347,4,0) LOADABLE_KERBEROS_TELNET.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (356,2,0) NAMED_CONTROL.COM;1
marked for delete
%ANALDISK-W-DELHEADER, file (378,3,0) NAMED_CONTROL.COM;1
marked for delete
%ANALDISK-W-DELHEADER, file (426,1,0) NETWORK_DATABASE.;2
marked for delete
%ANALDISK-W-DELHEADER, file (454,1,0) MULTINET_VMS_SHAREABLE.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (456,1,0) LAVDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (457,1,0) RMTDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (458,1,0) RCDDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (459,1,0) PWIPDRIVER.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (460,1,0) LOADABLE_NOT_ASSIST.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (464,1,0) MULTINET_DPC_SHR.EXE;2
marked for delete
%ANALDISK-W-DELHEADER, file (473,1,0) NAMED.EXE;1
marked for delete
%ANALDISK-W-DELHEADER, file (476,1,0) LOADABLE_SNMP_AGENT.EXE;2
marked for delete
%ANALDISK-W-FUTCREDAT, file (2040,660,0) [SOPHOS]SYSBDR-G.IDE;1
creation date is in the future
%ANALDISK-W-DELHEADER, file (3153,9072,0) .;
marked for delete
%ANALDISK-W-DELHEADER, file (3963,1,0) NETWORK_DATABASE.;1
marked for delete
%ANALDISK-W-DELHEADER, file (3964,1,0) HOSTTBLUK.DAT;3
marked for delete
%ANALDISK-W-DELHEADER, file (5070,2386,0) ZZ01L0ZWK714Y600I6TE.00;1
marked for delete
%ANALDISK-W-DELHEADER, file (5111,4260,0) QUEUE_CACHE.OLD;416
marked for delete
%ANALDISK-W-DELHEADER, file (15831,373,0) VS-01KD2AVZTJTC0080SI.LIS;1
marked for delete
%ANALDISK-W-DELHEADER, file (32306,8591,0) ZZ01KVC9C2JPW40168CC.00;1
marked for delete
%ANALDISK-W-DELHEADER, file (33745,1108,0) .;
marked for delete
%ANALDISK-W-DELHEADER, file (33750,2249,0) .;
marked for delete
%ANALDISK-W-DELHEADER, file (33752,2000,0) .;
marked for delete
%ANALDISK-W-DELHEADER, file (33757,2596,0) .;
marked for delete
%ANALDISK-W-DELHEADER, file (33860,3600,0) VS-01KTFXUZIHDC003Q1I.LIS;1
marked for delete
%ANALDISK-W-LOSTHEADER, file (1613,493,0) SCAN_OUTBOUND.LOG;28993
not found in a directory
%ANALDISK-W-LOSTHEADER, file (5492,155,0) MAIL.LIS;
not found in a directory

This looks problematic...what do I need to do?

Thanks,
Lisa
Phillip Thayer
Esteemed Contributor

Re: Disk File Optimizer Error

Lisa,

I would do an ANALYZE/DISK NEOMN2$DRA1: and see if there are any errors reported. If so then do an ANALYZE/DISK/REPAIR NEOMN2$DRA1:. When doing the /REPAIR option the disk drive will be locked.

After doing the /REPAIR option then do the DFU command and see if you get the same thing.

Phil
Once it's in production it's all bugs after that.
Duncan Morris
Honored Contributor

Re: Disk File Optimizer Error

Hi Lisa, first of all make sure that you have a backup of this drive!

Most of the DELHEADER items look as though they came from software upgrades/patches.

Run ANAL/DISK/REPAIR to "fix" the errors, and then ANAL/DISK again to see if there are still any furhter problems.

Check your free disk space before and after the repair. You will probably find that you get back a number of blocks.

Ian Miller.
Honored Contributor

Re: Disk File Optimizer Error

your disk errors do not look too bad but worth fixing. Can you post the result of

DEFRAG SHOW */FULL

Also check help or manual for DFO to see if you should be doing
DEFRAG VOLUME NEOMN2$DRA1:
____________________
Purely Personal Opinion
Phillip Thayer
Esteemed Contributor

Re: Disk File Optimizer Error

Lisa,

Sorry, I didn't see the output of the ANALYZE.DISK before my last post. It might not be a bad idea to do a reboot of this system also. there seem to be a lot of files that have been deleted while they were installed as known images on the system. This is where you get the "marked for delete" error most of the times. The best way to clear this is to reboot.

Phil
Once it's in production it's all bugs after that.
Lisa Collins
Advisor

Re: Disk File Optimizer Error

I did the repair command. It seems to cleared up most everything. Now I only see this

Analyze/Disk_Structure for _NEOMN2$DRA1: started on 2-MAR-2006 16:36:59.03

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file

But I'm still seeing this error when trying to run the Optimizer:

Defragmentation process for script DFG$SCRIPT24 has completed
Completion time was 2-MAR-2006 16:50:55.50
%DFG-W-UNRECOVERR, unrecoverable error
Target volume was NEOMN2$DRA1 (_NEOMN2$DRA1:)

My Defrag Report looks like this


D1 2-MAR-2006 16:47:54.23

The fragmentation index is 96.2
1 - 20.9 is excellent
21 - 40.9 is good
41 - 60.9 is fair
61 - 80.9 is poor
81 - 100 indicates a badly fragmented disk
Approximately 76.2 (out of 80.0 possible) is due to file fragmentation
Approximately 20.0 (out of 20.0 possible) is due to freespace fragmentation


Freespace Summary:
Total free space: 9598320 blocks
Percentage free: 54 (rounded)
Total free extents: 23640
Maximum free extent: 15354 blocks, LBN: 9782244
Minimum free extent: 18 blocks, LBN: 6567120
Average free extent: 406 blocks
Median free extent: 126 blocks


File Fragmentation Summary:
Number of files (with some allocation): 12028
Total file extents on the disk: 43204
Average number of file extents per file: 3.591952
Median number of file extents per file: 1

Most Fragmented File:
[CSWS.APACHE.SPECIFIC.NEOMN2.NEOMIN.ORG.LOGS]SSL_ENGINE_LOG.;1 (22233 ex
tents)


F i l e F r a g m e n t a t i o n H i s t o g r a m

Extent
Count
------
|
8 To 22233 | (32)
7 | (1)
6 | (10)
5 | (5)
4 | (18)
3 | (22)
2 | (26)
1 | ************************ (11914)
+---------------------------------
Number of files with a given number of extents
Each * corresponds to 500 files



V o l u m e F r e e s p a c e H i s t o g r a m

Freespace
Size
(LBNs)
---------
|
14310 To 15354 | (3)
5166 To 14202 | * (50)
4590 To 5148 | * (50)
4248 To 4572 | * (56)
3906 To 4230 | * (52)
3636 To 3888 | * (50)
3402 To 3618 | * (54)
3240 To 3384 | * (50)
3096 To 3222 | * (52)
2970 To 3078 | * (50)
2826 To 2952 | * (53)
2718 To 2808 | * (50)
2592 To 2700 | * (57)
2484 To 2574 | * (58)
2394 To 2466 | * (55)
2304 To 2376 | * (59)
2232 To 2286 | * (53)
2142 To 2214 | * (60)
2070 To 2124 | * (56)
1998 To 2052 | * (56)
1944 To 1980 | * (58)
1890 To 1926 | * (58)
1836 To 1872 | * (57)
1782 To 1818 | * (59)
1728 To 1764 | * (58)
1674 To 1710 | * (69)
1620 To 1656 | * (72)
1584 To 1602 | * (51)
1548 To 1566 | * (56)
1494 To 1530 | * (83)
1458 To 1476 | * (56)
1422 To 1440 | * (59)
1386 To 1404 | * (52)
1350 To 1368 | * (64)
1314 To 1332 | * (77)
1278 To 1296 | * (53)
1242 To 1260 | * (73)
1206 To 1224 | * (83)
1170 To 1188 | * (72)
1134 To 1152 | * (89)
1098 To 1116 | * (82)
1062 To 1080 | * (98)
1026 To 1044 | * (91)
990 To 1008 | * (110)
972 | * (61)
954 | * (58)
936 | * (61)
918 | * (65)
900 | * (59)
882 | * (63)
864 | * (64)
846 | * (71)
828 | * (78)
810 | * (76)
792 | * (74)
774 | * (75)
756 | * (80)
738 | * (67)
720 | * (83)
702 | * (90)
684 | * (89)
666 | * (119)
648 | * (89)
630 | * (103)
612 | * (113)
594 | * (109)
576 | * (125)
558 | * (128)
540 | * (134)
522 | ** (169)
504 | * (147)
486 | ** (150)
468 | ** (172)
450 | ** (163)
432 | ** (170)
414 | ** (179)
396 | ** (208)
378 | ** (238)
360 | ** (237)
342 | ** (248)
324 | *** (254)
306 | *** (255)
288 | *** (312)
270 | *** (326)
252 | *** (327)
234 | **** (387)
216 | **** (436)
198 | ***** (487)
180 | ***** (530)
162 | ****** (602)
144 | ****** (637)
126 | ******** (751)
108 | ******** (797)
90 | ********* (872)
72 | *********** (1093)
54 | *************** (1478)
36 | ************************ (2354)
18 | ************************************************ (4823)
+--------------------------------------------------------
Number of freespace extents of a given size
Each * corresponds to 100 freespace extents
Phillip Thayer
Esteemed Contributor

Re: Disk File Optimizer Error

Lisa,

Ian is right, I was wondering why you were doing a DEFRAG FILE instead of DEFRAG VOLUME.

Ian, If she does a DEFRAG FILE would it try to read the directories on the disk and possubly have the problem she is experiencing where if she did a DEFRAG VOLUME would it use the INDEXF.SYS file to get the file names and not have the problem?

Phil
Once it's in production it's all bugs after that.
Lisa Collins
Advisor

Re: Disk File Optimizer Error

I've also tried DEFRAG VOLUME NEOMN2$DRA1: and I get the same error.
Phillip Thayer
Esteemed Contributor

Re: Disk File Optimizer Error

Lisa,

Then maybe it is a good idea to do an Image backup of the disk, boot from a CD and re-initialize the disk and rebuild the disk from the image backup. It may be that your disk is just too fragmented for DFO to do anything with it.

If you cannot do that then possibly try doing a defrag file on each file listed as the Most Fragmeneted File on the defrag report. So you would start with a defrag file on [CSWS.APACHE.SPECIFIC.NEOMN2.NEOMIN.ORG.LOGS]SSL_ENGINE_LOG.;1 and then try to defrag the volume. If it doesn't work, do a defrag report and repeat the process.

Best bet would be to rebuild from an image backup though.

Phil
Once it's in production it's all bugs after that.
Duncan Morris
Honored Contributor

Re: Disk File Optimizer Error

Phillip, I concur with an image backup/restore to eliminate the fragmentation.

Lisa, look at the options with defrag volume such as /consolidate to consolidate the free space into as large a piece as possible. Doing a simple defrag just defragments the files as best as possible, but can lead to terribly fragmented free space.

Also look at the docs/release notes for qualifiers to increase various quotas for defrag. I am away from my docs at the moment, but I recollect having to increase some quotas to handle very large or very fragmented disks.
Lisa Collins
Advisor

Re: Disk File Optimizer Error

That was a good idea to try the defrag one file at a time......but unfortunately it didn't work. We will reboot the server before the users come in tomorrow and see if that helps. I'll let you know. Thanks for the suggestions!
Volker Halle
Honored Contributor

Re: Disk File Optimizer Error

Lisa,

please have a look at the following article in Ask Compaq:

[DFO] How To Obtain More Info. On DFO Script Failure, DFG-W-UNRECOVERR

http://h18000.www1.hp.com/support/asktima/operating_systems/CHAMP_SRC000608003514.html

Volker.
VMS Support
Frequent Advisor

Re: Disk File Optimizer Error

I'm just about to implement DFO V2.9 onto our production servers as a replacement for perfect disk.
Should I be worried that DFO is not as robust as I have been told/sold ?
A defrag of production disks only has to go bad once!
John Abbott_2
Esteemed Contributor

Re: Disk File Optimizer Error

@VMS SUPPORT
>I'm just about to implement DFO V2.9 onto >our production servers as a replacement for .perfect disk.
>Should I be worried that DFO is not as >robust as I have been told/sold ?
>A defrag of production disks only has to go bad once!

In Production, we've been running 2.9 under vms 7.3-2 since 7-JAN (2.8 from 9-APR-05), running various levels of volume defrags every weekend without any failures (accvio or %DFG-WEF- errors) or problems detected afterwards (from using anal/disk)

We defrag ALL of our non-DB volumes.

...But then our disks are never allowed to get as fragmented as Lisa's!

John.
Don't do what Donny Dont does
Karl Rohwedder
Honored Contributor

Re: Disk File Optimizer Error

Dito, running V2.9 on several systems without problems.

regards Kalle
Jansen_8
Regular Advisor

Re: Disk File Optimizer Error

I had problems giving the same error message (which tells you nothing). For me the solution was to increase the pagefile-quota for the DFRAG processes. It appears that by default they are too low.
To change them edit : SYS$COMMON:[SYS$STARTUP]DFG$STARTUP.COM and add or uncomennt the line containing:

$ CALL DEFINE_LOGICAL DFG$PGFLQUOTA 1500000

HP-support advised me to set it to 1500000. Ofcourse the account running the DFG processes should be able to access this ammount of pagefile-quota and you should have enough memory/pagefile space on your machine.

Jouk Jansen
Volker Halle
Honored Contributor

Re: Disk File Optimizer Error

To all,

please consider looking into the script's log file for the real error message, when you receive the %DFG-W-UNRECOVERR

See the TIMA article mentioned in my previous reply. Once you see the real error message, there should be less room for 'speculation' !

OpenVMS and it's utilities are usually VERY GOOD at providing full details for errors. And DFG does not seem to be an exception to this rule. You just need to following the correct troubleshooting steps...

Volker.
Phillip Thayer
Esteemed Contributor

Re: Disk File Optimizer Error

Lisa,

Can you post a copy of the log file from the defrag that is failing? I know you referenced in your original post that the log file showed "%DFG-W-UNRECOVERR, unrecoverable error" but did it show anything else? Use the prodecure in the article referenced by the link in post by Volker and post that log file for us.

Phil
Once it's in production it's all bugs after that.
Lisa Collins
Advisor

Re: Disk File Optimizer Error

I did what the document showed and this is what I see

DFO>sh DFG$SCRIPT32

File script DFG$SCRIPT32 is ENABLED, LEVEL=1, device: NEOMN2$DRA1
No defragmentation process is executing
Scheduler queue contains no pending operations
File list for DEFRAGMENT FILE:
[CSWS.APACHE.SPECIFIC.NEOMN2.NEOMIN.ORG.LOGS]*.*;*
Do not consolidate freespace
Minimum Priority: 3
Default Priority: 4
Script may operate on any available node
No log file specified
No prologue file specified
No epilogue file specified
Mail notification is OFF
OPCOM notification is ON
Special file handling:
Exclude all specifically placed files

DFO>

It does not include a log like the example showed in the document.


We rebooted the server this morning and things seemed fine for 45 minutes. Then the server rebooted itself. I don't know if anyone can make heads or tales out of my dump file but I'll post it just incase



$ ANALYZE/CRASH_DUMP SYS$SYSTEM:SYSDUMP.DMP

OpenVMS (TM) Alpha system dump analyzer
...analyzing a compressed selective memory dump...

Dump taken on 3-MAR-2006 07:26:28.09
CPUSPINWAIT, CPU spinwait timer expired

SDA> sh process

Process index: 0140 Name: PMDFF9 pmas Extended PID: 00000540
--------------------------------------------------------------------
Process status: 00040001 RES,PHDRES
status2: 00000001 QUANTUM_RESCHED

PCB address 8170AF80 JIB address 81705BC0
PHD address 85E28000 Swapfile disk address 00000000
KTB vector address 8170B26C HWPCB address FFFFFFFF.85E28080
Callback vector address 00000000 Termination mailbox 001D
Master internal PID 00010140 Subprocess count 0
Creator extended PID 00000000 Creator internal PID 00000000
Previous CPU Id 00000000 Current CPU Id 00000001
Previous ASNSEQ 000000000000034A Previous ASN 0000000000000011
Initial process priority 4 # open files remaining 193/200
Delete pending count 0 Direct I/O count/limit 200/200
UIC [00001,000004] Buffered I/O count/limit 10000/10000
Abs time of last event 00025111 BUFIO byte count/limit 98528/98528
# of threads 1 ASTs remaining 248/250
Swapped copy of LEFC0 00000000 Timer entries remaining 199/200
Swapped copy of LEFC1 00000000 Active page table count 0
Global cluster 2 pointer 00000000 Process WS page count 526

Press RETURN for more.
SDA>

Process index: 0140 Name: PMDFF9 pmas Extended PID: 00000540
--------------------------------------------------------------------
Global cluster 3 pointer 00000000 Global WS page count 168
PCB Specific Spinlock 81709AC0


Press RETURN for more.
SDA>

Process index: 0140 Name: PMDFF9 pmas Extended PID: 00000540
--------------------------------------------------------------------

Thread index: 0000
------------------
Current capabilities: System: 0000000C QUORUM,RUN
User: 00000000
Permanent capabilities: System: 0000000C QUORUM,RUN
User: 00000000
Current affinities: 00000000
Permanent affinities: 00000000
Thread status: 00040001
status2: 00000001

KTB address 8170AF80 HWPCB address FFFFFFFF.85E28080
PKTA address 7FFEFF98 Callback vector address 00000000
Internal PID 00010140 Callback error 00000000
Extended PID 00000540 Current CPU id 00000001
State CUR 01 Flags 00000000
Base priority 4 Current priority 4
Waiting EF cluster 4 Event flag wait mask 8100C100

Press RETURN for more.
SDA>

Process index: 0140 Name: PMDFF9 pmas Extended PID: 00000540
--------------------------------------------------------------------
CPU since last quantum FFF7 Mutex count 0
ASTs active NONE
Volker Halle
Honored Contributor

Re: Disk File Optimizer Error

Lisa,

you would have to specify a logfile for the script to receive more detailled error messages.

To be able to help you regarding the CPUSPINWAIT system crash, please attach the CLUE file from CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS from today as a .TXT attachment.

Volker.
Ian Miller.
Honored Contributor

Re: Disk File Optimizer Error

What version of VMS are you running?

Is there a file in SYS$ERRORLOG or SYS$MANAGER with a name starting with CLUE dated when the system crashed ? If so can you post it as an attachment.
____________________
Purely Personal Opinion
Lisa Collins
Advisor

Re: Disk File Optimizer Error

This is our system

AlphaServer DS20 500 MHz running OpenVMS Alpha V7.3-1
Zeni B. Schleter
Regular Advisor

Re: Disk File Optimizer Error

As of OpenVMS v7.1 there were references in patches about spinwait Bugchecks. Prior to patches, a workaround was setting the SMP_SPINWAIT to 300000 on those systems with multiple CPUs. We never set the SMP_SPINWAIT back down but we have not seen any problems with SPINWAIT crashes either.

The v7.1 Driv08 patch specifically referred to setting the SMP_SPINWAIT to 300000.