From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Fri Mar 21 2003 - 05:29:51 EST
I would guess that the problem might have been a corrupt filesystem.
Perhaps a directory entry but no actual file?
If you come across something similar in future you might try using an
exclude file to bypass the affected directory and confirm that the rest of
the system backs up OK. You could then use backup, perhaps, to verify the
identity of the particular file. (I suggest this as it would be quicker
than running a full mksysb; you could just do a particular directory and its
contents.)
Simon Green
Altria ITSC Europe s.a.r.l.
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will seldom be appreciated.
> -----Original Message-----
> From: Bill Verzal [mailto:Bill_Verzal@BCBSIL.COM]
> Sent: 20 March 2003 21:39
> To: aix-l@Princeton.EDU
> Subject: mksysb failing
>
>
> I have since rebuilt the SP node as it was in test mode. So I cannot
> reproduce the problem.
>
> I ran a mksysb -v yesterday and it was complaining about a file
> /var/adm/SPlogs/cs as not being present. I trapped the temp files and
> looked at what the next files were. Everything in the mksysb
> data files
> was present. I ran fsck in single-user mode. I was really
> stumped on this
> one.
>
> I probably should have not rebuilt the node so I could have done more
> testing. If I do this load test again, I'll let you know if
> I run across
> it again. The return code was "3".
>
> Dang - I should not have rebuilt the node (Bill makes a
> letter "L" with his
> fingers and places it upon his forehead)
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:41 EDT