[5115] in SIPB bug reports
project.sipbsrc and the 4GB disk
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Thu Jan 19 18:15:37 1995
From: ghudson@MIT.EDU
Date: Thu, 19 Jan 1995 18:11:23 -0500
To: sipb-afsreq@MIT.EDU
Cc: bug-sipb@MIT.EDU, ljr@MIT.EDU
project.sipbsrc has been inaccessible for most of today, and attempts
to vos dump project.sipbsrc.backup have failed. A salvage of
project.sipbsrc yielded a bunch of errors and didn't bring the volume
back onlin. Marc has done a tar of project.sipbsrc.backup onto opus,
and we will probably try to restore from that when he gets back.
We've had enough trouble with this Micropolis 4GB disk that we thought
we should get a replacement for it, so I called R Squared. I learned
that:
* We only have an advance replacement on the disk, not the
enclosure, so they are only shipping us a disk. We must
replace the disk in the enclosure and send them the old disk
(with the enclosure) back.
* It's a "vendor swap", so the new disk won't arrive until
Monday or Tuesday, because they don't send us the disk until
the vendor sends them the disk.
* We can use their shipping materials to ship the old disk
back.
I wasn't aware of these arrangements when we ordered the disk (and Don
Ricks assured me that they keep swap disks in stock), but I guess
that's how it is.
We have at least three options:
1. We can try to borrow an enclosure for the new disk, put it
on rosebud2, move the data onto it, and then move it back
into the old 4GB disk's enclosure (probably necessary to
avoid paperwork).
2. We can move the data onto one of the 4GB news disks which
are likely to arrive on Monday or Tuesday.
3. We can move the existing data off of the 4GB disk onto
other disks (we can use up to 3GB of spare disk to do
this), and move it back onto the new disk. If we take this
option, we should start moving the data off of the existing
disk now. This has the advantage that we can ship back the
old disk almost immediately after receiving the new one.
