mount & umount read-only floppy: unmount failed: Input/output error ??

[Rob]

I think I've figured it out - here's a script(1) of trying to mount a
write-protected floppy:

  root at goo # uname -sr
  FreeBSD 4.8-RELEASE
  root at goo # mount /dev/fd0 /mnt
  root at goo # ll /mnt
  total 3
  drwxr-xr-x   2 root  wheel  512 Jun 28 14:04 .
  drwxr-xr-x  21 root  wheel  512 May 19 18:57 ..
  root at goo # umount /mnt
  umount: unmount of /mnt failed: Input/output error

However, here's the vidcontrol(1) dump of the same commands:

  root at goo # uname -sr
  FreeBSD 4.8-RELEASE
  root at goo # mount /dev/fd0 /mnt
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  root at goo # ll /mnt
  total 3
  drwxr-xr-x   2 root  wheel  512 Jun 28 14:04 .
  drwxr-xr-x  21 root  wheel  512 May 19 18:57 ..
  root at goo # umount /mnt
  fd0c: hard error writing fsbn 56 of 56-63 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 1 hd 1 sec 3)
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  fd0c: hard error writing fsbn 16 of 16-18 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 0 hd 0 sec 17)
  fd0c: hard error writing fsbn 56 of 56-63 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 1 hd 1 sec 3)
  fd0c: hard error writing fsbn 16 of 16-18 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 0 hd 0 sec 17)
  fd0c: hard error writing fsbn 56 of 56-63 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 1 hd 1 sec 3)
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  fd0c: hard error writing fsbn 16 of 16-18 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 0 hd 0 sec 17)
  fd0c: hard error writing fsbn 56 of 56-63 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 1 hd 1 sec 3)
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  fd0c: hard error writing fsbn 16 of 16-18 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 0 hd 0 sec 17)
  fd0c: hard error writing fsbn 56 of 56-63 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 1 hd 1 sec 3)
  fd0c: hard error writing fsbn 240 (ST0 40<abnrml> ST1 2<write_protect>
ST2 0 cyl 6 hd 1 sec 7)
  fd0c: hard error writing fsbn 16 of 16-18 (ST0 40<abnrml> ST1
2<write_protect> ST2 0 cyl 0 hd 0 sec 17)
  umount: unmount of /mnt failed: Input/output error

Since I'm doing this on ttyv0, I see the errors on the console - but
they don't appear in the typescript.

I'm guessing that you're doing this in a non-console shell, and the
errors are appearing elsewhere - maybe /var/log/messages?

----- Original Message -----
From: "Rob Lahaye" <lahaye at users.sourceforge.net>
Subject: Re: mount & umount read-only floppy: unmount failed:
Input/output error ??


>
> Rob wrote:
> > That's strange - I get errors as soon as I try and do this, before
the
> > filesystem is even available.
> >
> > Perhaps the updates from mounting the floppy aren't being written
out to
> > the actual media until you try to unmount it - some kind of caching
> > issue?
> >
> > What happens if you try to touch a file on the (incorrectly)
writeable
> > floppy?
>
> Are you also using FreeBSD 4.8?
>
> I have created the installation floppy from the kern.flp file.
> I then made this floppy readonly. I put that into my floppy drive
> and...
>
> # mount -t ufs /dev/fd0 /mnt
> # ls -lo /mnt
> total 1301
> drwxr-xr-x  2 root  wheel  -     512 Apr  3 20:06 boot
> -r-xr-xr-x  1 root  wheel  - 1324900 Apr  3 20:06 kernel.gz
> # touch /mnt/kernel.gz
> # ls -lo /mnt
> total 1301
> drwxr-xr-x  2 root  wheel  -     512 Apr  3 20:06 boot
> -r-xr-xr-x  1 root  wheel  - 1324900 Jun 30 19:17 kernel.gz
> # umount /mnt
> umount: unmount of /mnt failed: Input/output error
> #
>
> Notice that the time has changed due to the 'touch' of the file
> despite being readonly!!
>
> The very little I know about filesystems, I guess the 'touch' has
> been applied to the cache, not to the actual floppy.
> The umount forces a sync, which can't be done due to readonly.
>
> Something is fishy here, isn't it?
>
> Rob.
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"
>