similar to: Cannot remove freshly created logical volumes

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

I've upgraded my x86_64 4.2 box to the latest kernel 2.6.9.34 and tried an lvm snapshot. It worked fine and I was able to mount the snapshot etc. Now I cannot seem to remove the snapshot. If I try a 'lvremove' it asks if I want to remove the 'active' snapshot, if I say yes it just hangs and the box goes to 99% wait io, however the disk lights do not come on during this. The

Hi. I'm trying to install CENTOS 4.2Beta for sparc, and i got this exception: +------------+ Exception Occurred +-------------+ | | | An unhandled exception has occurred. # | | This is most likely a bug. Please copy # | | the full text of this exception and file # | | a detailed bug report against anaconda at # | |

Hi. I'm trying to install CENTOS 4.2Beta for sparc, and i got this exception: +------------+ Exception Occurred +-------------+ | | | An unhandled exception has occurred. # | | This is most likely a bug. Please copy # | | the full text of this exception and file # | | a detailed bug report against anaconda at # | |

On 06.07.2017 15:35, Robert Nichols wrote: > On 07/06/2017 04:43 AM, Volker wrote: >> Hi all, >> >> one of my lv has become completely unaccessible. Every read access >> results in a buffer io error: >> >> Buffer I/O error on dev dm-13, logical block 0, async page read >> >> this goes for every block in the lv. A ddrescue failed on every single

hi, My volume group is vg. Inside that i have around 10 lvm partitions (each of 100GB). When I try to remove partitions using lvremove /dev/vg/lvm1 It acts like the machine freezes and after a long time the lvremove process gets killed saying "Killed" Whats wrong here. I don't see anything interesting in /var/log/message Thanks Paras.

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

I am not sure if it''s a xen bug or lvm bug, or just my bad hardware, but here''s how to reproduce: /dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size. #lvcreate -L8192M -s -n snap1 vg0 #mount /dev/vg0/snap1 /mnt do some copying files here #umount /mnt #lvremove /dev/vg0/snap1 not removed! it says can''t allocated memory #xm mem-set 0 512 #lvremove

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband

Hi Alasdair and all, This is the dm-ioband version 1.10.5 release. This patch can be applied cleanly to current agk's tree. The only change from the previous version is that some blktrace messages are added by Alan D. Brunelle, thanks Alan. Alasdair, Could you please tell me your opinion about merging dm-ioband to upstream? What else do I have to do? Is there any possibility that dm-ioband