Bug 709222 - Eject floppy in qemu-monitor before umount it in the guest cause floppy data lost
Summary: Eject floppy in qemu-monitor before umount it in the guest cause floppy data ...
Keywords:
Status: CLOSED DUPLICATE of bug 703789
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 06:12 UTC by Mike Cao
Modified: 2011-05-31 06:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-31 06:47:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Cao 2011-05-31 06:12:03 UTC
Description of problem:
write data to mount point after eject floppy in qemu-monitor cause floppy data lost 

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.start guest with floppy
eg:<commandLine> -drive file=/home/b.vfd,if=floppy,cache=none,format=raw
2.in the guest mount /dev/fd0 /mnt
3.mkdir /mnt/tt1 
4.mkdir /mnt/tt2
5.eject floppy in qemu-monitor (qemu)eject floppy0
6.umount /dev/fd0 in the guest #umount /dev/fd0
7,add floppy in qemu-monitor (qemu)change floppy0 /home/b.vfd
8.remount floppy  #mount /dev/fd0 /opt
  
Actual results:
two directories tt1 tt2 created in step 3/4 could not found in /dev/fd0

Expected results:
no data lost in floppy

Additional info:

Comment 1 Mike Cao 2011-05-31 06:47:59 UTC

*** This bug has been marked as a duplicate of bug 703789 ***


Note You need to log in before you can comment on or make changes to this bug.