- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problem with DFU 3.2 and /over_allocated
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
тАО02-04-2009 04:33 AM
тАО02-04-2009 04:33 AM
Disk exhibiting the problem is 48GB with cluster 137 and is the 32nd shadow set on san HSV200.
Other files, other DFU options and other disks after 32nd seem OK.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 04:56 AM
тАО02-04-2009 04:56 AM
Re: Problem with DFU 3.2 and /over_allocated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 05:00 AM
тАО02-04-2009 05:00 AM
Re: Problem with DFU 3.2 and /over_allocated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 05:01 AM
тАО02-04-2009 05:01 AM
Re: Problem with DFU 3.2 and /over_allocated
(http://www.digiater.nl/dfu)
Please collect the following information and ATTACH as a plain TXT file to a future reply:
- verbatim DFU command and output reduced to header, and example file or two and trailer.
- DIR/FULL for an example file
- SHOW DEV/FULL for the device holding the example
- DUMP/HEAD/BLOC=COUN=0 for an example file.
and maybe
- DUMP/HEAD/BLOCK=COUNT=1 for [000000]INDEXF.SYS
While the OS details are likley irrelevant, please indicate the exact OpenVMS version, platform and patch level. (CD, update X00, ...)
Hope this will help a little bit,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 05:16 AM
тАО02-04-2009 05:16 AM
Re: Problem with DFU 3.2 and /over_allocated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 05:36 AM
тАО02-04-2009 05:36 AM
Re: Problem with DFU 3.2 and /over_allocated
In all seriousness (and with all respect intended), we also see HP-UX and Windows questions here, too.
Jur may well need access to the boxes here and/or to enable any latent diagnostics on the boxes. Not everybody has a configuration sufficient to replicate this.
I don't know that he has a bug tracking system here. (There really isn't one of those typically used for most Freeware, though. I don't have one of those up for the Freeware I've released. But I digress...)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 06:12 AM
тАО02-04-2009 06:12 AM
Re: Problem with DFU 3.2 and /over_allocated
Well, I DO have a bug-tracking system and that's called email :-). As long as the volume is low it works just fine.
I'll look into this problem soon.
Jur.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 06:40 AM
тАО02-04-2009 06:40 AM
SolutionSEPTEMBER_2008.OLME;1 File ID: (1025,3,0)
Size: 156865/156865 Owner: [COMPUTER,WADE]
...
File organization: Indexed, Prolog: 3, Using 1 key
and the dump of the file header:
Header area
...
VAX-11 RMS attributes
Record type: Variable
File organization: Indexed
Record attributes: Implied carriage control
Record size: 0
Highest block: 156865
End of file block: 0
End of file byte: 0
Bucket size: 2
Well, I would say that DIRECTORY is lying. The end of file pointer is really 0 and that's what DFU displays. But this file is an indexed file, and for indexed files the end of file pointer is meaningless. RMS will set it to a value such that the display looks okay, but for some reason that has not been done on this file.
DIRECTORY takes the file organisation into account and show the highest allocated block as the filesize.
So in my opinion neither DIRECTORY nor DFU has a bug. The unusual thing is that an application has created an indexed file where the end of file pointer is zero.
Jur.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 06:47 AM
тАО02-04-2009 06:47 AM
Re: Problem with DFU 3.2 and /over_allocated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 07:07 AM
тАО02-04-2009 07:07 AM