[15246] in Athena Bugs
sparc 8.1.7: floppy handling oddness
daemon@ATHENA.MIT.EDU (John Hawkinson)
Fri Jul 11 11:58:04 1997
Date: Fri, 11 Jul 1997 11:57:44 -0400
To: testers@MIT.EDU
Cc: bugs@MIT.EDU
From: John Hawkinson <jhawk@MIT.EDU>
Something appears to be messed up here.
Background:
A user from the W20 cluster asked me to help eject a floppy of his;
he had previously used "eject" to eject the floppy that was in the
drive prior to his arrival, but it did not work for his floppy.
I suggested he try "eject floppy", and that didn't work (!?).
"STOP-A / eject / go" worked fine, however.
Further examination showed that "eject fd" would work, but "eject
floppy" would not. Am I totally confused in a recollection that
"eject floppy" was recommended and used to work?
In any case, I tried to reproduce this on bobbi-harlow, an 8.1.7 SS4.
With no floppy in the drive, I got:
[bobbi-harlow!jhawk] ~> eject fd
floppy0: No such file or directory
[bobbi-harlow!jhawk] ~> eject floppy
floppy: No such file or directory
(as one might expect). I stuck in a DOS floppy, and seem
to be having problems ejecting it:
[bobbi-harlow!jhawk] ~> eject floppy
[bobbi-harlow!jhawk] ~> eject
[bobbi-harlow!jhawk] ~> volcheck
[bobbi-harlow!jhawk] ~> eject
[bobbi-harlow!jhawk] ~> eject floppy
[bobbi-harlow!jhawk] ~> eject fd
[bobbi-harlow!jhawk] ~> eject -f floppy
[bobbi-harlow!jhawk] ~> eject -f fd
[bobbi-harlow!jhawk] ~> eject -f fd0
[bobbi-harlow!jhawk] ~> eject -d
Default device is: /vol/dev/rdiskette0/lan_drv_59x
[bobbi-harlow!jhawk] ~> eject
[bobbi-harlow!jhawk] ~> eject -\?
eject: illegal option -- ?
usage: eject [-fndq] [name | nickname]
options: -f force eject
-n show nicknames
-d show default device
-q query for media present
[bobbi-harlow!jhawk] ~> eject -q
/vol/dev/rdiskette0/lan_drv_59x is available
But the device isn't mounted:
[bobbi-harlow!jhawk] /vol> mount
/ on /dev/dsk/c0t3d0s0 read/write/setuid on Thu Jul 10 21:25:27 1997
/usr on /dev/dsk/c0t3d0s5 read/write/setuid on Thu Jul 10 21:25:27 1997
/proc on /proc read/write/setuid on Thu Jul 10 21:25:27 1997
/dev/fd on fd read/write/setuid on Thu Jul 10 21:25:27 1997
/var on /dev/dsk/c0t3d0s6 read/write/setuid on Thu Jul 10 21:25:27 1997
/var/usr/vice on /dev/dsk/c0t3d0s3 setuid/read/write on Thu Jul 10 21:25:34 1997
/afs on AFS read/write on Thu Jul 10 21:25:41 1997
/mit/zlog on SMALL-GODS.MIT.EDU:/zlog read only/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 21:28:10 1997
/mit/bitbucket on JASON.MIT.EDU:/u1/bitbucket read/write/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 22:43:45 1997
Though it has devices in /vol:
[bobbi-harlow!jhawk] ~> ls -l /vol/*dsk
/vol/dsk:
total 0
brw-rw-rw- 1 nobody nobody 91, 1 Jul 11 11:08 lan_drv_59x
/vol/rdsk:
total 0
crw-rw-rw- 1 nobody nobody 91, 1 Jul 11 11:08 lan_drv_59x
Suggesting that I wasn't totally losing it when I thought
"eject floppy" was right:
[bobbi-harlow!jhawk] ~> eject /dev/diskette
/dev/rdiskette is busy (try 'eject floppy' or 'eject cdrom'?)
[bobbi-harlow!jhawk] ~> eject -f /dev/diskette
/dev/rdiskette is busy (try 'eject floppy' or 'eject cdrom'?)
[bobbi-harlow!jhawk] ~> eject -f /dev/diskette0
/dev/rdiskette0 is busy (try 'eject floppy' or 'eject cdrom'?)
[bobbi-harlow!jhawk] ~> eject -f /dev/rdiskette
/dev/rdiskette is busy (try 'eject floppy' or 'eject cdrom'?)
[bobbi-harlow!jhawk] ~> eject -f /dev/rdiskette0
/dev/rdiskette0 is busy (try 'eject floppy' or 'eject cdrom'?)
Yet it's not a defined alias:
[bobbi-harlow!jhawk] ~> eject -n
fd -> floppy0
fd0 -> floppy0
fd1 -> floppy1
diskette -> floppy0
diskette0 -> floppy0
diskette1 -> floppy1
rdiskette -> floppy0
rdiskette0 -> floppy0
rdiskette1 -> floppy1
cd -> cdrom0
cd0 -> cdrom0
cd1 -> cdrom1
sr -> cdrom0
sr0 -> cdrom0
/dev/sr0 -> cdrom0
vold has been running. Turning it off:
[bobbi-harlow!jhawk] ~# /etc/init.d/volmgt stop
[bobbi-harlow!jhawk] ~#
And then trying to eject produces no change:
[bobbi-harlow!jhawk] ~> eject /dev/diskette
[bobbi-harlow!jhawk] ~> eject /dev/diskette0
[bobbi-harlow!jhawk] ~> eject /dev/rdiskette0
[bobbi-harlow!jhawk] ~> eject /dev/rdiskette
[bobbi-harlow!jhawk] ~>
(nor does using "eject -f" help).
It's worth noting that /mit/consult/arch/sun4m_54/bin/eject.force
does not seem to work here either.
At this point I tried "eject" from the monitor and it
also did nothing. As did:
" floppy" $eject
At this point I ejected the disk with a paperclip.
I restarted vold with -v.
I reinserted the disk and then:
[bobbi-harlow!jhawk] ~> volcheck
[bobbi-harlow!jhawk] ~> mount
/ on /dev/dsk/c0t3d0s0 read/write/setuid on Thu Jul 10 21:25:27 1997
/usr on /dev/dsk/c0t3d0s5 read/write/setuid on Thu Jul 10 21:25:27 1997
/proc on /proc read/write/setuid on Thu Jul 10 21:25:27 1997
/dev/fd on fd read/write/setuid on Thu Jul 10 21:25:27 1997
/var on /dev/dsk/c0t3d0s6 read/write/setuid on Thu Jul 10 21:25:27 1997
/var/usr/vice on /dev/dsk/c0t3d0s3 setuid/read/write on Thu Jul 10 21:25:34 1997
/afs on AFS read/write on Thu Jul 10 21:25:41 1997
/mit/zlog on SMALL-GODS.MIT.EDU:/zlog read only/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 21:28:10 1997
/mit/bitbucket on JASON.MIT.EDU:/u1/bitbucket read/write/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 22:43:45 1997
/floppy/lan_drv_59x on /vol/dev/diskette0/lan_drv_59x read/write on Fri Jul 11 11:53:47 1997
[bobbi-harlow!jhawk] ~> eject
[bobbi-harlow!jhawk] ~> mount
/ on /dev/dsk/c0t3d0s0 read/write/setuid on Thu Jul 10 21:25:27 1997
/usr on /dev/dsk/c0t3d0s5 read/write/setuid on Thu Jul 10 21:25:27 1997
/proc on /proc read/write/setuid on Thu Jul 10 21:25:27 1997
/dev/fd on fd read/write/setuid on Thu Jul 10 21:25:27 1997
/var on /dev/dsk/c0t3d0s6 read/write/setuid on Thu Jul 10 21:25:27 1997
/var/usr/vice on /dev/dsk/c0t3d0s3 setuid/read/write on Thu Jul 10 21:25:34 1997
/afs on AFS read/write on Thu Jul 10 21:25:41 1997
/mit/zlog on SMALL-GODS.MIT.EDU:/zlog read only/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 21:28:10 1997
/mit/bitbucket on JASON.MIT.EDU:/u1/bitbucket read/write/nosuid/soft/rsize=1024/wsize=1024/timeo=8/retrans=7/remote on Thu Jul 10 22:43:45 1997
This surely seems wrong.
vold.log logged:
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/db_mem.so.1
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/label_dos.so.1
Fri Jul 11 11:53:24 1997 info: label_cdrom: init
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/label_cdrom.so.1
Fri Jul 11 11:53:24 1997 info: label_sun: init
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/label_sun.so.1
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/dev_cdrom.so.1
Fri Jul 11 11:53:24 1997 info: cdrom_use: /dev/rdsk/c0t6d0s2
Fri Jul 11 11:53:24 1997 info: dso_load: loaded /usr/lib/vold/dev_floppy.so.1
Fri Jul 11 11:53:25 1997 info: floppy_use: /dev/rdiskette0
Fri Jul 11 11:53:25 1997 info: dso_load: loaded /usr/lib/vold/dev_pcmem.so.1
Fri Jul 11 11:53:25 1997 info: vold: running
"volcheck" caused the disk to be mounted again.
Maybe all I'm concluding here is the mechanical automatic floppy
eject on this workstation is broken?
Regardless, there's something up with this "eject floppy"
vs. "eject fd" discrepancy.
Sorry this report is kind of fragemented, I've got to run.
--jhawk
