From: 2843600@ccs-lab10 (Steve Frampton) Subject: Bug in 'msdos' file system? Date: 23 Feb 1993 15:00:08 GMT
Hello!
I am running the TAMU .99p4 release of Linux. Wonderful! But I did run
across what appears to be a serious bug last night while attempting to
copy a Linux (unix) file onto an 'msdos' mounted partition.
I mounted my DOS drive C: as: mount -t msdos /dev/hda1 /dos/c:
No problem. I could access my DOS files as if they were normal unix files.
I then tried to move a file over onto DOS:
mv /home/frampton/myfile.txt /dos/c:
The 'mv' seemed to finish, so I executed a 'sync'. The 'sync' command seemed
to hang there. In fact I had to log on using another pty and issue a ps
command. Interestingly enough, the 'mv' and 'sync' commands were still in
the process list. So I tried to 'kill' them off -- but they wouldn't budge.
This was even the case when I used the 'kill -9' option. Talk about your
zombie processes! :-)
Shutting down the system (with the 'shutdown' command) didn't seem to work,
as it probably issued another 'sync' which hung up again. After a few
minutes, I rebooted.
Afterward, I couldn't even boot Linux anymore! I had to use the boot disk
and run an 'efsck' command to clear things up (yes, I'm using the extended
file system). Being fairly new to Linux, I had only but to agree with what
'efsck' suggested needed fixing. I can only assume that things are back to
normal now (it *appears* to work now).
Anyway, is this a known bug with the extended file system, the 'msdos' file
system, or both?
Thanks...
====================================================================
Steve Frampton Preferred: <frampton@vicuna.ocunix.on.ca>
Kingston, Ontario Alternate: <2843600@jeff-lab.queensu.ca>