![]() | ||||||||||
Messages in this thread |
Hello, here is what I found the hard way (having lost the configuration of a firewall...): # mount /dev/fd0 /mnt/floppy/ mount: block device /dev/fd0 is write-protected, mounting read-only # mount -o remount,rw /mnt/floppy # echo $? 0 # touch /mnt/floppy/blabla # ls -l /mnt/floppy/blabla -rwxr-xr-x 1 root root 0 Oct 27 13:18 /mnt/floppy/blabla* # umount /mnt/floppy # echo $? 0 # mount /dev/fd0 /mnt/floppy/ mount: block device /dev/fd0 is write-protected, mounting read-only # ls -l /mnt/floppy/blabla ls: /mnt/floppy/blabla: No such file or directory The kernel actually tries to write to the floppy - the light is blinking (so everything looks nice from outside). Of course, there are kernel errors, seen in dmesg like: > end_request: I/O error, dev fd0, sector 21 > Buffer I/O error on device fd0, logical block 21 > lost page write due to I/O error on fd0 but these don't propagate to the user space in any way. The bug is present in both 2.4 and 2.6, and is specific to floppy devices. Other RO media I tried (CDROM, RO-exported NFS) are partially OK, in the sense that a write attempt returns an error; however, "mount -o remount,rw" always returns success (this might be a bug in mount). Regards, Evgeny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-27 10:04 [W:0.529 / U:0.330 seconds] ©2003-2008 Jasper Spaans | ||||||||||