First,
thank you to all who responded.
Second, there was a typo in the posting that was NOT in the vfstab, the
vfstab was correct, and the problem was real.
Interesting solution to the problem, and a new learning experience for me.
The disks were all partitioned with slice 0 at 30Mb, slice 1 at 100Mb,
slice 2 covering the entire disk, and slice 6 everything left after the
130 Mb came out from above.
I was about to throw in the towel, run newfs on all four disks, and restore
from the 6 week old backups, when I tried to mount the other partitions
just for grins. I mounted slice 0, and I saw the data that was supposed
to be there. hmm... I tried to mount slice 1, and had teh same
filesystem not of this type error message, very interesting.
I tried to mount slice 2 (the whole disk), and it mounted! All the data was
there.
It appears that whoever set up the disks originally, ran newfs on the whole
disk partition slice 2, not on slice 6. Is this legitimate? It certainly
stumped me for a while.
I ran backups of all four disks, ran newfs on slice 6 of each of them, and
restored the data to them. All is well, and no data was lost. I certainly
would not have guessed that this would have been done this way.
-chuck
--
ACCEL Services, Inc.| Specialists in Gravity, Magnetics | 1(713)993-0671 ph.
1980 Post Oak Blvd. | and Integrated Interpretation | 1(713)960-1157 fax
Suite 2050 | |
Houston, TX, 77056 | Chuck Campbell | campbell@neosoft.com
| President & Senior Geoscientist |
"Integration means more than having all the maps at the same scale!"
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:59 CDT