From: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, libvir-list@redhat.com,
virt-tools-list@redhat.com
Subject: [Qemu-devel] fdisk still shows the "/dev/sdb" partitions even after the removal of scsi disk
Date: Thu, 13 Jun 2013 15:49:26 +0530 [thread overview]
Message-ID: <51B99CAE.2040006@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
Hi,
I have filed a bug "fdisk still shows the "/dev/sdb" partitions even
after the removal of scsi disk" for the upstream kernel.
Bug link:
https://bugs.launchpad.net/qemu/+bug/1190525
RHEL guest shows the partittions even after the removal of scsi disk:
fdisk still shows the "/dev/sdb" partitions even after the removal of
scsi disk.
Guest details:
-------------------
Kernel : 2.6.32-358
Host Details :
Upstream Kernel, Qemu, Libvirt and virt-manager
---------------------------------------------------------------------
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
libvirt version : 1.0.5
virt-install : 0.600.3
Steps to reproduce the issue:
I. Add the SCSI disk through the virt-manager.
2. Create the partition using fdisk (eg: /dev/sbb)
3. Create a filesystem and format using mkfs.ext3 or mkfs.ext4
4. Remove the scsi disk through the virt-manager.
5. Again run the fdisk /dev/sdb, the guests still shows the partition
even after the removal of the disk.
This issue is not seen with virt-io disk.
This issue is also reproducible without even creating the partitions.
Expected Result:
The output of fdisk /dev/sd* should not show the enties after the
removal of scsi disks
Thanks,
Chandrashekar
[-- Attachment #2: Type: text/html, Size: 2028 bytes --]
next reply other threads:[~2013-06-13 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 10:19 chandrashekar shastri [this message]
2013-06-13 12:50 ` [Qemu-devel] fdisk still shows the "/dev/sdb" partitions even after the removal of scsi disk Laszlo Ersek
2013-06-13 16:44 ` chandrashekar shastri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51B99CAE.2040006@linux.vnet.ibm.com \
--to=cshastri@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virt-tools-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).