Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!cornell!rochester!pt.cs.cmu.edu!f.word.cs.cmu.edu!eht From: eht@f.word.cs.cmu.edu (Eric Thayer) Newsgroups: comp.sys.next Subject: FYI: eject diskA mount diskB Message-ID: <5110@pt.cs.cmu.edu> Date: 3 Jun 89 17:47:10 GMT Reply-To: eht@f.word.cs.cmu.edu (Eric Thayer) Organization: Carnegie-Mellon University, CS/RI Lines: 17 Keywords: I just ejected a disk; call it disk A and I pushed in disk B and the system didn't realize that it was a new disk and scribbled all over it. I couldn't recover disk B by fsck and the data was lost (I had a backup though). One strange thing that happened was that after I ejected disk A. Automount prompted me to put it back in after several seconds (although I didn't explicitly ask for anything from the disk (there a always things going on which I am unaware though)). I dutifully pushed disk A back in the slot and then ejected it again. This time whoever wanted the disk didn't want it (at least not during the time that I waited to see if the message would appear again). So I pushed disk B in the slot and automount didn't realize it was a new disk and proceeded to torch the disk. Beware! ...eric -- Eric H. Thayer Carnegie Mellon School of Computer Science (412) 268-{8724,6973} 5000 Forbes Ave, Pittsburgh, PA 15213 --