It looks like there’s some corruption in the file system directory
structure. This might explain why the orbit restore aborted in the first
place.
I believe that some of the commands within FSCHECK have the ability to check
and/or fix problems with the file system, so this might be worth
investigation. Before trying it I'd recommend running BULDACCT and also
having a good full backup of the system, preferably two (belt and braces
approach). I also believe the system has to be quiet before attempting a fix.
Jason Kettley
ORBiT Software Group Technical Support.
On Wed, 2 Dec 2009 13:30:02 -0800, Craig Lalley <[log in to unmask]> wrote:
>--- On Wed, 12/2/09, Jeff Kubler <[log in to unmask]> wrote:
>Craig, and all,
>Now we have a group that is stuck in limbo....
>Will PURGEFILE have an equivalance in FSCHECK to PURGEGROUP?
>
>If worse comes to worse you can always VSCLOSE the volume set, scratch the
luns, and rebuild the volume set.
>
>Nothing like a sledge hammer.
>
>-Craig
>
>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|