[6176] in Hotline Meeting

home help back first fref pref prev next nref lref last post

Aphro status

daemon@ATHENA.MIT.EDU (salemme@Athena.mit.edu)
Mon Sep 23 09:50:09 1991

From: salemme@Athena.mit.edu
Date: Mon, 23 Sep 91 09:47:20 -0400
To: op@Athena.mit.edu, ops@Athena.mit.edu
Cc: cfyi@Athena.mit.edu, hotline@Athena.mit.edu


Here is where we currently stand with Aphrodite:

	- it has been in service since last night around 7:30pm, but
	  /u3 and /u4 were not available to users
	- at around 7:30pm last night, we did incremental dumps of
	  the /u3 and /u4 partitions (onto the /backup partition on
	  aphro); we had previously verified that the full dump tape
	  of /u4 and /u3 written on Fri night was readable
	  [So, we knew that we could restore from tape if we had to,
	  with essentially no loss of data]
	- at around 8pm, we started dumping from aphro:{/u3,/u4} to
	  hecate:{/u1,/u2}. By 9:30am, the dumps seem to be about
	  80% done. [There have been over 300 soft errors logged on
	  aphro, but it has stayed up.]
	
What we need to do next:
	- wait until the dumps to hecate finish, then check them
	  using fsck, quotacheck, and possibly other testing
	- make sure quotas are working on hecate:/u1 and /u2
	- make massive changes in Moira to move all filsys entries
	  from aphro:/u3==>hecate:/u1 and aphro:/u4==>hecate:/u2
	- let users know that all lockers have been moved and are
	  now available [with no plans to move them again at this time]
	- call DEC and get aphro's disk 2 fixed [which will probably
	  involve loss of all data on the disk, which won't matter at
	  that time]

I'll send another update later.
					Anne

home help back first fref pref prev next nref lref last post