unable to create file on the disk

[Hein van den Heuvel]

>> canâ  t install DFU since it point to same logical disk at indext.sys.

Megat,

Have you tried cleaning up some files already?
Maybe some netserver.log file? Maybe some operator.log versions? maybe even a bruteforce: $delete/log/before= [*...]*.log.*
Or: $purge/keep=3 [*...]*.*
Or a DCL script to find files with F$FILE(name,"ALQ).EQ.0 ?

Hein.

[Ian Miller.]

you could install DFU on another system and then get DFU.EXE and copy it to any disk on the system

[Jon Pinkley]

megat,

Please find and delete some of those empty files that are using your files headers. The problem isn't that your disk is full, it is that there are no available files headers, which are used to store the meta-data about files, i.e. the stuff that is displayed in the output of dump/header/block=count:0.

I gave the command to find files with zero blocks allocated. If you don't want to create a listing file, you can do the following to have it show a page at a time.

$ directory/size=alloc/sel=size:max:0 dsa1:[000000...]/page/date/exclude=([000000]*.sys)

This will get you a list of files that are good candidates for removal. In your note from Mar 28, 2008 03:13:54 GMT you had what claimed to be output from DIRECTORY/FULL DSA1:[000000]INDEXF.SYS but appeared to be the tail of the output of

$ directory/size=alloc/sel=size:max:0 dsa1:[000000...]

Right at the top of what was shown was the following:

Total of 483404 files, 0 blocks.

To me this looks like you have a directory on DSA1: that had 483404 empty files in it (and possibly some non-empty files that were not included due to the /select criterion).

We don't know what that directory is. You will need to determine what it is, and what is creating all these empty files. By including /date, it will also display the date/time these files were created, as that may be a useful indication of what created them.

Good luck,

Jon