- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: analyze/disk/usage 1 block off in allocated si...
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
тАО03-05-2009 07:15 AM
тАО03-05-2009 07:15 AM
analyze/disk/usage 1 block off in allocated size
Did anyone ever notice that in the output of anlyze/disk/usage the allocated block count is always 1 higher than what e.g. directory gives with a dir/size=all?
The minimum space allocated according to this utility is 1 block, never 0.
The workaround is simple: subtract 1 off the allocated size.
The used block count does not suffer from this peculiar offset of 1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2009 07:18 AM
тАО03-05-2009 07:18 AM
Re: analyze/disk/usage 1 block off in allocated size
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2009 07:39 AM
тАО03-05-2009 07:39 AM
Re: analyze/disk/usage 1 block off in allocated size
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2009 07:49 AM
тАО03-05-2009 07:49 AM
Re: analyze/disk/usage 1 block off in allocated size
As you know, heavily fragmented, or heavily ACLed files may need more than 1 header.
Cheers,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2009 06:31 AM
тАО03-13-2009 06:31 AM
Re: analyze/disk/usage 1 block off in allocated size
Maybe the test was with just 1 file?
Hein.
(stuur eens een Email?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2009 07:50 AM
тАО07-21-2009 07:50 AM
Re: analyze/disk/usage 1 block off in allocated size
Yes, the file header was the culprit, mainly to accommodate for disk quota to function properly. For 'entered' files as found on the system disk this gives interesting results, as there you have multiple file headers but only one allocated size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2009 11:33 AM
тАО07-21-2009 11:33 AM
Re: analyze/disk/usage 1 block off in allocated size
Nitpicking...
'Entered' files (SET FILE/ENTER) have additional DIRECTORY ENTRIES, but they all have the same File-ID pointing to one and the same file header.
Of course the directory _might_ grow a block as a new file is entered.
Hein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2009 05:31 AM
тАО07-22-2009 05:31 AM
Re: analyze/disk/usage 1 block off in allocated size
The little project I wanted to use this for (making a treemap a la Sequoia (Google) of a VMS disk ) proved to have performance issues on the graphical side anyway. Without tweaking more than I wanted to there was hardly a satisfying user experience, to coin a phrase.
I am closing this thread. Thanks everyone!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2009 05:31 AM
тАО07-22-2009 05:31 AM