Date: Mon, 30 Jun 2003 21:00:56 +0900 From: Rob Lahaye <lahaye@users.sourceforge.net> To: Rob <listone@deathbeforedecaf.net>, freebsd-questions@FreeBSD.ORG Subject: Re: mount & umount read-only floppy: unmount failed: Input/output error ?? Message-ID: <3F002678.6050405@users.sourceforge.net> In-Reply-To: <000601c33efe$08c06e30$a4b826cb@goo> References: <3EFFFE5A.7060500@snu.ac.kr><00d201c33eeb$05075870$a4b826cb@goo><3F000966.5000102@users.sourceforge.net><011b01c33ef0$059c0510$a4b826cb@goo><3F000FC6.7000300@users.sourceforge.net><000601c33ef6$c4908b70$a4b826cb@goo><3F001AD8.2030805@users.sourceforge.net> <001101c33ef9$95181c70$a4b826cb@goo> <3F001E97.2090401@snu.ac.kr> <000601c33efe$08c06e30$a4b826cb@goo>
next in thread | previous in thread | raw e-mail | index | archive | help
Rob wrote: > > Yep - just tried > > mount -u -r -f /mnt > > and also > > umount -f /tmp > > Both fail with I/O errors, presumably from the fdc0 device. Also when > rebooting, the failed sync interferes with unmounting other filesystems, > causing fsck(8)s on the way back up. > > But mount/umount can't just ignore the device status - if it says things > are broken, what should they do? I don't know. I may have given wrongly the impression that I am familiar with this matter. I am not at all. I just noticed a very illogical behaviour when mounting my readonly floppy; that's all. With my simple mind, I would say: 'mount' should be able to detect that you do a read/write-mount, but the medium is readonly; so it should give an error message and NOT mount. BUT: if it does mount the medium (floppy), then umount should also do its job; and not, as it is now, refuse to umount. Rob.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F002678.6050405>