Integrity Servers
1830936 Members
1959 Online
110017 Solutions
New Discussion

DiskInfo: Error (FreeSize)

 
steffany
Occasional Contributor

DiskInfo: Error (FreeSize)

Hi

There is a warning showing 0 freedisk and then back again with the memory. (HDD is plenty of memory)

I got a log from my device device HPE integrity rx2800 i6

 

11:20:01.797, [DEBUG] Cmd:cmd /c "rsh user123 -l user_manager write sys$output f$getdvi(\"dsa0\", \"freeblocks\")"
11:20:02.642, [DEBUG] Ret:
11:20:02.642, [DEBUG] Get User345 DiskInfo: Error (FreeSize)

3 REPLIES 3
shiva_jr
HPE Pro

Re: DiskInfo: Error (FreeSize)

Hi @steffany,
    I have not worked on Open VMS. But I found some light on your issue.  Post1 and post2 may help you. Along with posts, please refer this Open vms document (Page no.50).
First, you can try with analyzing the disk without repair. so that get the proper detail and error. After that, you can analyze with repair. 

Regards,
Shiva_jr


 



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Steven Schweda
Honored Contributor

Re: DiskInfo: Error (FreeSize)

> There is a warning [...]

   This warning comes from what, exactly?

> [...] showing 0 freedisk and then back again with the memory. (HDD is
> plenty of memory)

   I don't know what any of that means. Disk storage and memory (RAM)
are two different things.

> I got a log from my device [...]

   What, exactly, produces this log?

> 11:20:01.797, [DEBUG] Cmd:cmd /c "rsh user123 -l user_manager write
> sys$output f$getdvi(\"dsa0\", \"freeblocks\")"

   So, someone/something on a different system is using "rsh" to run
commands on the (remote) VMS system?


> 11:20:02.642, [DEBUG] Get User345 DiskInfo: Error (FreeSize)

   I don't know what that means.  Did the "rsh" connection or command
fail, or did the remote command return a result of zero free blocks, or
what?

   I'd try to eliminate the middleman, and log into the VMS system
interactively. Then you should be able to run your command directly,
and see its results:

      write sys$output f$getdvi("dsa0", "freeblocks")

Or, for more info on that disk device:

      show device /full dsa0

Some general info on the system might be interesting, too:

      tcpip show version

   If the disk really is full, then you might need to delete some files
to get more free space.

support_s
System Recommended

Query: DiskInfo: Error (FreeSize)

Hello,

 

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

 

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".


Accept or Kudo