- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Allocation Error
Operating System - OpenVMS
1748073
Members
5179
Online
108758
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
09-05-2008 01:13 PM
09-05-2008 01:13 PM
Re: Allocation Error
After more testing, it appears that rename does not fix the backlink, even when renaming to a different name or different directory. My guess is that this is expected behavior, since it is not consisdered the primary link. I.e. the directory pointed to by the backlink does not have an entry with the filename and fileid of the file. So the backlink is not updated.
Analyze disk/repair treats the file as a lost file and puts an entry in [syslost], which doesn't seem to be the correct thing to do, but to avoid that would require that every directory on the disk be searched for an entry with the file id of the file in it.
There doesn't seem to be an easy way to fix the problem using standard utilities. What does work: analyze/disk/repair; set file /remove from target directory, rename from [syslost] to target directory (this updates the backlink because the [syslost] is now the primary entry.
Bottom line: this is a shortcut to avoid if correct backlinks are important to you.
On the other hand, if you are trying to hide files and wnat them to be hard to find, it may be useful.
Jon
Analyze disk/repair treats the file as a lost file and puts an entry in [syslost], which doesn't seem to be the correct thing to do, but to avoid that would require that every directory on the disk be searched for an entry with the file id of the file in it.
There doesn't seem to be an easy way to fix the problem using standard utilities. What does work: analyze/disk/repair; set file /remove from target directory, rename from [syslost] to target directory (this updates the backlink because the [syslost] is now the primary entry.
Bottom line: this is a shortcut to avoid if correct backlinks are important to you.
On the other hand, if you are trying to hide files and wnat them to be hard to find, it may be useful.
Jon
it depends
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2008 07:12 AM
09-06-2008 07:12 AM
Re: Allocation Error
Odwillia,
I'm sure you heard more than enough.
There are more, and older discussion on this:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1165943
Just get more space, or use DFU or use an old 'comdir' or such if you can find it.
Jon,
Good catch on the potential backlink issue.
That changes savvy to silly.
The most likely place where folks would actually suffer from a broken backlink is probably
$SHOW ENTRY/FULL
It use the FID -> Name and would fail.
It might report a file as:
_$10$MDA0:[14,4,0]X.COM;1
While this IS a valid DID abbreviated file spec, it will fail because that DID no longer is there.
http://h71000.www7.hp.com/doc/731FINAL/4506/4506pro_019.html#index_x_1071
The FID abbreviated name does not provide an alternative as it (un-necesarilly so?!) requires the correct directory even though the FID is unique already. Oddly it does not require a valid leading name character such as the doc implies:
$ dir/nohead/notrail/file/wid=file=40 _$10$MDA0:[a.test]y~[13,3,0].com
_$10$MDA0:[A.TEST]X[13,3,0].COM;1 (13,3,0)
$ dir/nohead/notrail/file/wid=file=40 _$10$MDA0:[a]y~[13,3,0].com
%DIRECT-W-NOFILES, no files found
Anyway... if someone wanted to use this savvy/silly shortcut instead of a proper tool, then the better way to so is:
$create/dir device:[temp]
$set file/enter=[temp] device:[data]*.*;*
$set file/nodir device:[000000]temp.dir
$copy/over device:[000000]temp.dir data.dir !!!
$delete device:[000000]temp.dir;
That is quick and preserves the FID for data.dir.
Yuck...
:-)
Hein.
I'm sure you heard more than enough.
There are more, and older discussion on this:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1165943
Just get more space, or use DFU or use an old 'comdir' or such if you can find it.
Jon,
Good catch on the potential backlink issue.
That changes savvy to silly.
The most likely place where folks would actually suffer from a broken backlink is probably
$SHOW ENTRY/FULL
It use the FID -> Name and would fail.
It might report a file as:
_$10$MDA0:[14,4,0]X.COM;1
While this IS a valid DID abbreviated file spec, it will fail because that DID no longer is there.
http://h71000.www7.hp.com/doc/731FINAL/4506/4506pro_019.html#index_x_1071
The FID abbreviated name does not provide an alternative as it (un-necesarilly so?!) requires the correct directory even though the FID is unique already. Oddly it does not require a valid leading name character such as the doc implies:
$ dir/nohead/notrail/file/wid=file=40 _$10$MDA0:[a.test]y~[13,3,0].com
_$10$MDA0:[A.TEST]X[13,3,0].COM;1 (13,3,0)
$ dir/nohead/notrail/file/wid=file=40 _$10$MDA0:[a]y~[13,3,0].com
%DIRECT-W-NOFILES, no files found
Anyway... if someone wanted to use this savvy/silly shortcut instead of a proper tool, then the better way to so is:
$create/dir device:[temp]
$set file/enter=[temp] device:[data]*.*;*
$set file/nodir device:[000000]temp.dir
$copy/over device:[000000]temp.dir data.dir !!!
$delete device:[000000]temp.dir;
That is quick and preserves the FID for data.dir.
Yuck...
:-)
Hein.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP