- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Disk Space
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 02:44 AM
тАО12-10-2008 02:44 AM
The free space reported is 12883675.
But, when issued the following command it shows :
SYSTEM1$:> dir $1$DGA100:[000000...]/siz=all/grand
Grand total of 1227 directories, 61283 files, 35996727/38823505 blocks.
Can anyone please let me know why this is reported wrongly ?
Analyse/disk can resolve this problem?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 03:04 AM
тАО12-10-2008 03:04 AM
SolutionMost common instance of this is the sys$common directory on a system disk.
I believe this is covered in the VMS FAQ.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 03:40 AM
тАО12-10-2008 03:40 AM
Re: Disk Space
Doing a quick scan of the OpenVMS FAQ (at http://hoffmanlabs.org/vmsfaq/vmsfaq.html ) I did not find this described, although I agree with Jon, the most likely cause is multiple processing of files due to aliases.
FILES-11 (all levels), unlike the *IX and Windows file structures, allows files (including directories) to be entered at multiple points in the directory tree. This is harmless to disk accounting, as most disk structure accounting is actually done by processing the Index File, not directories.
This feature is most commonly noted on system disks, where [VMS$COMMON] is entered as [SYSCOMMON] under each system root (e.g., [SYS0}, [SYS1], ... [SYS597]). Thus, having multiple OpenVMS roots on one disk only incurs the space cost of files that are particular to each instance, not a complete copy of OpenVMS for each instance sharing a system disk.
This feature of the structure predates OpenVMS, having been part of the original FILES-11 Level 1 specification for RSX-11D. It is not the same as hard/soft links, which are later additions.
Thus, when a [...] enumeration of files on the disk is done, there is the possibility that directories (and files) that are entered multiple times will be added to the total multiple times. ANALYZE/DISK_STRUCTURE (see the online HELP text) will the actual space in use by auditing the index file and storage bitmap.
- Bob Gezelter, http://www.rlgsc.com
P.S. Hoff, perhaps this should be an item in the FAQ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 04:40 AM
тАО12-10-2008 04:40 AM
Re: Disk Space
DFU
Need I say more?
DFU REPORT $1$DGA100:
Still not clear?
http://www.digiater.nl/dfu
That should do it.
Regards,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 05:10 AM
тАО12-10-2008 05:10 AM
Re: Disk Space
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-10-2008 05:45 AM
тАО12-10-2008 05:45 AM
Re: Disk Space
http://www.google.com/search?hl=en&q=openvms+%22directory+%2Fsize%22+%22show+device%22+blocks
That's a search for
OpenVMS "directory /size" "show device" blocks
Which seems a pretty reasonable Google search to try to find the answer here, right?
This particular DCL detail is in the OpenVMS FAQ, in the section on DIRECTORY /SIZE and disk quotas. Certainly not as obviously placed as it should be, but a search for DIRECTORY or /SIZE through the FAQ text file or FAQ PDF will find it. Certainly not as obvious a placement given particularly that fewer and fewer sites are using disk quotas these days. But it's the same basic underlying difference in what the various commands are displaying.
Please do lob a documentation enhancement request at HP for whatever documentation you looked at. I checked DIRECTORY /SIZE here and didn't see this caveat listed, but I don't know what other documentation you reviewed before you posted this. You're far the first to encounter this confusion, as that Google search will indicate - hence it might well be good to see the DIRECTORY /SIZE documentation (and whatever else you looked at) updated.
And why the assumption that something is "wrong" or a "problem"? This can appear inconsistent, confusing, unexpected and surprising, yes. But wrong? A problem? No. Assuming an understanding in the face of an inconsistency is not an assumption that is particularly safe in the generic case. Best to figure out why first, rather than assuming an error. This approach comes to the fore as you move forward toward system and application debugging, too.