Date: Fri, 29 Aug 1997 02:27:16 -0500 (CDT) From: Zach Heilig <zach@gaffaneys.com> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/4413: No way to unmount a floppy that goes bad while mounted. Message-ID: <199708290727.CAA10903@murkwood.gaffaneys.com> Resent-Message-ID: <199708290730.AAA17336@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4413
>Category: kern
>Synopsis: No way to unmount a floppy that goes bad while mounted.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Aug 29 00:30:01 PDT 1997
>Last-Modified:
>Originator: Zach Heilig
>Organization:
>Release: FreeBSD 2.2-STABLE i386
>Environment:
>Description:
I had a bsd formatted floppy mounted in /fd0 that went bad while it was in the
drive. When I went to unmount it, I got these errors on the console:
$ umount /dev/fd0
fd0c: hard error reading fsbn 56 of 56-63 (ST0 44<abnrml,top_head> ST1
4<sec_not_fnd> ST2 10<wrong_cyl> cyl 1 hd 1 sec 3)
fd0c: hard error reading fsbn 56 of 56-63 (ST0 44<abnrml,top_head> ST1
4<sec_not_fnd> ST2 10<wrong_cyl> cyl 1 hd 1 sec 3)
umount: /dev/fd0: Invalid argument
$ mount
/dev/sd0a on / (asynchronous, local)
/dev/sd0s1f on /usr (asynchronous, local, nodev)
/dev/sd1s1e on /home (asynchronous, local, nodev, nosuid)
/dev/sd0s1e on /var (asynchronous, local, nodev, nosuid)
procfs on /proc (local)
/dev/fd0 on /fd0 (asynchronous, local)
>How-To-Repeat:
I guess you would just have to wait for a floppy to go bad while it is
mounted.
>Fix:
I umounted it by puting a different write-protected floppy in the drive
and running umount.
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708290727.CAA10903>