[Info-vax] Problems detected with analyze/disk

[Richard B. Gilbert]

VAXman- @SendSpamHere.ORG wrote:
> In article <mailman.31.1258928922.9279.info-vax_rbnsn.com at rbnsn.com>, "Peter Weaver" <info-vax at weaverconsulting.ca> writes:
>>> The problem in this case seems to get rid of files with "unprintable"
>>> characters
>>> in their names, with just access to the file-id. With a full file spec
>>> I could have
>>> used the recommended procedure to copy all multiple allocated files
>>> and delete
>>> all but one, then repair the disk. Just don't know how to do it fith
>>> only file-id's.
>> Since you have V8.3 and ODS5 you can do the following;
>>
>> $ DELETE/CONFIRM/LOG SYS$SYSDEVICE:[0000000...]~[708146,53,0]
>> $ DELETE/CONFIRM/LOG SYS$SYSDEVICE:[0000000...]~[156375,23,0]
>>
>> If the files are not on SYS$SYSDEVICE then substitute your disk name, the
>> "~" character is needed and you do not need any "*" characters in the
>> command. The confirm message will show you the device, directory, filename
>> followed by the FID in square brackets then the extension and version
>> number.
> 
> I'd be leary of deleting files on a device/volume with reports of multiply
> allocated blocks.  You may not like the results.
> 
> I'd be looking for a _cause_ of these mulitply allocated blocks before I'd
> begin zapping away files reported with them.
> 
> I've asked about 3rd party software but the original poster hasn't replied
> with any further details.
> 
> 

I'd be inclined to suspect that some application or DCL script is 
playing fast and loose with the rules.  This sort of thing is quite rare 
on most systems.  If I WANTED to multiply allocate blocks I'd really 
have to work at it.