- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: BAD file version on file LMIATRN.DAT;429496729
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
тАО04-23-2009 11:40 AM
тАО04-23-2009 11:40 AM
BAD file version on file LMIATRN.DAT;429496729
A developer mistakenly placed a file with an extension of ;429496729
Now, I can not delete it and can not seem to view other files after it...??
Can not delete it, copy it, rename it, etc.
Some of the errors are:
RENAME LMIATRN.DAT;4294967295 LMIATRN.DAT;456
%RENAME-E-SEARCHFAIL, error searching for LMIATRN.DAT;4294967295
-RMS-F-VER, error in version number
AND
dir lmiat*
Directory [BANJOBS.GURJOBS.PROD]
LMIATRN.DAT;272 1KB 21-APR-2009 17:10:39.90 (RWED,RWED,RE,)
LMIATRN.DAT;271 20KB 20-APR-2009 17:20:22.85 (RWED,RWED,RE,)
LMIATRN.DAT;270 19KB 17-APR-2009 18:16:18.15 (RWED,RWED,RE,)
LMIATRN.DAT;269 28KB 16-APR-2009 17:18:09.51 (RWED,RWED,RE,)
LMIATRN.DAT;4294967295
no such file
%DIRECT-E-OPENIN, error opening MUPPET_USERS:[BANJOBS.GURJOBS.PROD]LMIAT*.*;* as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-W-BADIRECTORY, bad directory file forma
Any help is appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 12:09 PM
тАО04-23-2009 12:09 PM
Re: BAD file version on file LMIATRN.DAT;429496729
$ ANALYZE/DISK MUPPET_USERS:
reports and then, depending upon what sort of issues the volume has, a /REPAIR on the same command (at a time when file operations are unlikely) might help. If you're not familiar with the like of this then post the output of the ANALYZE here and wait for advice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 12:13 PM
тАО04-23-2009 12:13 PM
Re: BAD file version on file LMIATRN.DAT;429496729
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 12:30 PM
тАО04-23-2009 12:30 PM
Re: BAD file version on file LMIATRN.DAT;429496729
Why? It's exceedingly difficult to get into this state in the file system without a directory corruption, a disk corruption, or a developer that has done something very, very, very bad.
If this file was explicitly created by a developer, I'd be resolving that matter first.
And yes, ANALYZE /DISK /REPAIR and similar such can usually clear these cases.
Also ensure your disk not throwing errors, and you have a good archive of your data, and consider (if you're not shadowed) RAID or host-based volume shadowing. Also confirm your ECOs are current for whatever OpeNVMS version is in use here.
But if you have developers that are somehow creating corruptions such as this one, then your whole storage environment is at risk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 01:22 PM
тАО04-23-2009 01:22 PM
Re: BAD file version on file LMIATRN.DAT;429496729
It would be interesting to know how it got there of course.
A couple of renames should square this away.
You may want to rename away the 'good' ones first, due to the place in the list it is.
Silly example:
$ dir/file [.tmp]
A.TMP;3 (14911,21,0)
A.TMP;2 (14910,54,0)
A.TMP;1 (14822,81,0)
$ open/read/write tmp tmp.dir
$ read tmp rec
$ bad = (5 + f$cvui(3*8,8,rec)).and.-2 ! Name length + offset + round-up to word
$ write sys$output f$cvui(bad*8,2*8,rec) ! Ready?
3
$ rec[bad*8,2*8]=-1 ! Aim
$ write/update tmp rec ! Fire
$ close tmp
$ dir/file [.tmp]
A.TMP;4294967295 (14911,21,0)
A.TMP;2 (14910,54,0)
A.TMP;1 (14822,81,0)
$ set def [.tmp]
$ rena a.tmp; x.tmp;1 /log
%RENAME-I-RENAMED, A.TMP;-1 renamed to X.TMP;1
$ renam x.tmp a.tmp/log
%RENAME-I-RENAMED, X.TMP;1 renamed to A.TMP;3
$ dir/file
A.TMP;3 (14911,21,0)
A.TMP;2 (14910,54,0)
A.TMP;1 (14822,81,0)
Enjoy,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 01:31 PM
тАО04-23-2009 01:31 PM
Re: BAD file version on file LMIATRN.DAT;429496729
If you wanted to repair that record, then you can use a technique simlir to the one I used to fix it.
Find the record number:
$sea/num/form=non prod.dir LMIATRN.DAT) --> x
The look at it:
$DUMP/REC=(COU=1,STA=x) to visualize the record in question.
Look for the 272,271,270.. as 0110,010F,010E...
Is the corrupted element the last?
Then you can address it with:
$ open/read/write/share=write tmp prod.dir
$ read tmp rec ! Repeat until on target.
$ rec[f$len(rec)-8)*8,16] = 268
$ write /update/symbol tmp rec
$ close tmp
Or just count down the offset from the dump.
Hein.