Re: archive logs ended up in lost+found directories

I've been doing HP-UX admin for about 5 years, and Oracle DBA stuff for about a year. I don't have any personal experience with your problem, but I always had the same impression about the lost+found directory that you did - that files ended up there if they became "lost" due to inode problems. I suppose there is some possibility of corruption if the file was open at the time,
 but I think that I would probably take that risk and go ahead and apply them.

Sue B

At 12:20 PM 1/26/96 -0700, you wrote:
>This is a question more applicatble to the HP-UX admin list, but any UNIX
>SA/Oracle DBA's on this list who can share their experiences would be much
>appreciated. Plus, this is my own personal tale that I'm sharing with y'all
>;-).
>We had a hardware crash that caused several archived redo log files to end up
>in the lost+found directory. Of course, Murphy was around ;-) and we just
>happened to be in online backup mode and had to do recovery (still running
V7.1)
>My understanding of the lost+found directory is this :- files end up there if
>there is inode inconsistency, and the file handle is lost. There is something
>I've just learnt from HP and Oracle Support, that is cause for concern - they
>say that the integrity of files that end up in lost+found is suspect, meaning
>that we should not attempt to apply these archived logs in a recovery
>scenario. The point of it being that we are forced into a cancel based
>recovery scenario, with all its consequences. Anyone heard about lost+found
>files being suspect???
>
>thx/h
>
>
Received on Wed Jan 31 1996 - 13:52:38 CST