Error trying to remove file on POSIX shell (239 Views)
Reply
Occasional Visitor
Kuldeepak Sharma
Posts: 3
Registered: ‎02-11-2010
Message 1 of 7 (239 Views)

Error trying to remove file on POSIX shell

Hi all,

I have faced the following error on a MPE machine, while trying remove a file on the POSIX shell.

===========================================
:sh
########################################################################

MPE/iX Shell and Utilities (A.50.02)
COPYRIGHT (c) Hewlett-Packard Company 1992, All Rights Reserved.

########################################################################

shell/iX> cd /SYS/BACKUP/store2
shell/iX> ls
EUMD.D.20100106.4.1
shell/iX> rm EUMD.D.20100106.4.1
rm: cannot unlink entry "EUMD.D.20100106.4.1": System call error
shell/iX> ll
ls: ./EUMD.D.20100106.4.1: System call error
total 0
shell/iX> ls -i
0 EUMD.D.20100106.4.1
============================================

There are a couple questions I have regarding the above situation.
1) Primarily, how to REMOVE this file?

2) Usually, in the shell a file /A/B/C corresponds to the file in MPE as C.B.A; but in this case the group BACKUP does not exist under the account SYS.
Furthermore, the fact that we have sub-directories into the BACKUP directory is confusing.
How can i find this file /SYS/BACKUP/store2/EUMD.D.20100106.4.1 in MPE?

Please help urgently, as this file is huge in size, as is taking up valuable disc space which we need for another activity.

Thanks in advance.

Regards,
Kuldeepak SHARMA
Please use plain text.
Respected Contributor
Stan Sieler
Posts: 321
Registered: ‎10-16-1996
Message 2 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

Hi,

There are several possible reasons that
could explain why you can't remove the
file from the shell. If you can
execute the following command and post the
result, it will probably tell us most
of what we might need to know:

(from the CI, not the shell)

listfile /SYS/BACKUP/store2/EUMD.D.20100106.4.1 , 3

That should produce about 20 lines of output.

My guess is that the file is marked "priv"
which would prevent rm/unlink from opening it for purging.

You might also do:

listfile /SYS/BACKUP/store2/EUMD.D.201001@ , 3

so we can see if there are related files (similar names).

Stan
sieler@allegro.com
Please use plain text.
Occasional Visitor
Kuldeepak Sharma
Posts: 3
Registered: ‎02-11-2010
Message 3 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

Hi Stan,

Thanks for the reply.
I see where you're coming from. Elsewere on the internet, I had found such discussions as well, where file could not be removed from the shell, as it was marked "priv"/ has a lockword.

But here, the scenario is quite different. This file is one of seven backup files created on 26/01; all those files were removed, except for this one.

My suspicion is that, probably this file was being accessed by some process ( maybe STORE), which led to this situation.

Anyways, here is the output from the CI, as requested:

:listfile /SYS/BACKUP/store2/EUMD.D.201001@, 3
Bad UFID for the file /SYS/BACKUP/store2/EUMD.D.20100106.4.1 (CIWARN 9165)

What does this output mean, can you suggest any other cause looking at this?

Thanks again,

Regards,
Kuldeepak SHARMA
Please use plain text.
Respected Contributor
Stan Sieler
Posts: 321
Registered: ‎10-16-1996
Message 4 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

Re:

:listfile /SYS/BACKUP/store2/EUMD.D.201001@, 3
Bad UFID for the file /SYS/BACKUP/store2/EUMD.D.20100106.4.1 (CIWARN 9165)


Ah...that's a different kettle of fish entirely.

Your problem is not one of permissions, priv level, or lockword ... unfortunately.

The file has a corrupted file label (or
a corrupted directory entry) ... so you
can't open (or semi-open) the file.

(PURGE and rm require the ability to open
the file.)

When the system is completely idle, try:

(logon as MANAGER.SYS)

:fcheck.mpexl.telesup

ca all

and see what problems get reported.
(On a typical system, we'll see a number
of entries about files of the form @.OUT.HPSPOOL and/or @.IN.HPSPOOL ...
most such are not serious problems.)

We're mostly interested in the output relating to the EUMD.D.20100106.4.1 file.

Assuming it gets reported by FSCHECK, the
fix may be obvious (and FSCHECK may offer
to do it for you).

Please post the relevant FSCHECK output.

thanks,
Stan
Please use plain text.
Occasional Visitor
Kuldeepak Sharma
Posts: 3
Registered: ‎02-11-2010
Message 5 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

Hi Stan,

Thanks for the followup on the question.
I couldn't get the time to work on this till today.
Here is the relevant part of the output of command "ca all", as requested:

========================================
Checking file labels on volume: V_BACKUP:MASTER22

Checking the free list

C*WARNING:@ FILE LABEL CORRUPTION DETECTED FOR: $slough. (153,-26)
File label virtual address of corrupted file is $00000073.$00005100.

=========================================

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/store2/EUMD.D.20100106.4.1
MISSING VOLUME FOR UFID 05690004 4B906AF0 00061BDC 030438B1 31F62F3A

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/tmp/EXP.D.20100107.390_OK
MISSING VOLUME FOR UFID 05690004 4B906AF0 000636DC 04011C18 7C251188

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/tmp/EXP.W.20091121.TIMES
MISSING VOLUME FOR UFID 05690004 4B906AF0 000618DA A30338C9 17C4EB44

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/tmp/SYMD.D.20091215.390_OK
MISSING VOLUME FOR UFID 05690004 4B906AF0 000486DA AF003047 51914820

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/tmp/SYMD.W.20091219.290_OK
MISSING VOLUME FOR UFID 05690004 4B906AF0 000471DA B1040034 4480B3C2

===========================================

Please have a look, there are these errors.
Now that we have identified the problem, I am very eager to know the solution.

Waiting eagerly to hear from you.

Regards,
Kuldeepak SHARMA
Please use plain text.
Respected Contributor
Stan Sieler
Posts: 321
Registered: ‎10-16-1996
Message 6 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

First, Don't reboot.

The file label corruption for the "slough"
file worries me ... twice I've encountered
systems that couldn't be booted up, because
they had corruption of the "slough" file.
(In both cases, I had to use an external
disk editor to resolve the problem,
which was quite difficult.)

C*WARNING:@ FILE LABEL CORRUPTION DETECTED FOR: $slough. (153,-26)
File label virtual address of corrupted file is $00000073.$00005100.

(The two times I encountered the problem,
I have no idea what fscheck would have said
because it had not been run ... so I don't
know for certain that there's a relationship
between the error FSCHECK is reporting
on your system and the error I've seen
that prevents bootup.)

We'll address this later.

Let's look at the UFID problems for the HFS
files:

ENCOUNTERED POSIX FILENAME :/SYS/BACKUP/store2/EUMD.D.20100106.4.1
MISSING VOLUME FOR UFID 05690004 4B906AF0 00061BDC 030438B1 31F62F3A
...

MISSING VOLUME FOR UFID 05690004 4B906AF0 000636DC 04011C18 7C251188
...
MISSING VOLUME FOR UFID 05690004 4B906AF0 000618DA A30338C9 17C4EB44
...
(and similar for a few other files)

This may imply that the fourth volume of
the MPEXL_SYSTEM_VOLUME_SET is missing.

What does a "DSTAT ALL" command show?

Stan
Please use plain text.
Respected Contributor
Stan Sieler
Posts: 321
Registered: ‎10-16-1996
Message 7 of 7 (239 Views)

Re: Error trying to remove file on POSIX shell

Er, make that "the fourth volume of V_BACKUP" may be missing.
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation