I was not able to reproduce this with 2.6.15-23-server. Perhaps you
could post a script that reproduces the error along with the specific
kernel / lvm versions installed.
It could also be an load related issue like this one
https://launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/71567 (no
on
I've reproduced this panic with a virgin (kernel.org) 2.6.15.7 (I reused
the ubuntu 2.6.15-23-server config with make oldconfig). I could NOT
reproduce the panic with 2.6.19.1. So logically methinks something was
fixed along the way.
Any pointers for what to do next? Anyone want to lend a hand in
True however, ViewCVS has now been renamed ViewVC which nicely reflects
that it is no longer just for CVS. So going forward is there a way to
install the CVS or Subversion components depending on whether svn or cvs
is installed? Or perhaps ask the user?
I think in any case I should file a bug repo
** Summary changed:
- viewcvs should depend on python-subversion
+ viewcvs should require on python-subversion
** Summary changed:
- viewcvs should require on python-subversion
+ viewcvs should require python-subversion
--
viewcvs should require python-subversion
https://launchpad.net/bugs/740
Public bug reported:
Binary package hint: viewcvs
viewcvs requires python-subversion for correct operation.
If this is not installed then it will fail with "ImportError: No module
named svn"
Also reported here
http://www.ubuntuforums.org/archive/index.php/t-86028.html
(although it seems pytho
In troubleshooting my open LVM kernel bug I've been able to reproduce
this one too.
--
pvcreate /dev/sda3 fails, /dev/evms/sda3 succeeds
https://launchpad.net/bugs/51413
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please find attached a full kernel trace showing "kernel BUG at
drivers/md/kcopyd.c:145!" (Kernel 2.6.15-23-server)
I've built a 153M VMware machine which reproduces this panic everytime.
If anyone would like to take a look at it I will make the VM available
for download.
(Please note this bug ha
dmesg irrelevant as this is reproducible on multiple machines, multiple
kernels.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Needs Info => Unconfirmed
--
LVM Snapshot removal causes intermittent kernel panic
https://launchpad.net/bugs/71567
--
ubuntu-bugs mailing list
ubuntu-bug
Clarification, It seems the lv can also be removed without having to
hack around with the device mapper.
--
(LVM) Booting fails if a snapshot LV is present on VG
https://launchpad.net/bugs/58627
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
Hi Ben,
I've been able to reproduce this on three different machines including
one machine I specially prepared for testing. This bug is reproducible
without vmware being installed.
If you install dapper with one PV, VG vg_sys and one lv lv_vmware (ext3)
then you should be able to run my crash.sh
I can reproduce this too with 2.6.15-26-386 #1 PREEMPT.
Recovery is simple, the device mapped just gets all out of sync. Rejig
the devices and remove the snapshot and reboot. eg:
mv /dev/mapper/vg_sys-lv_vmware /dev/mapper/vg_sys-lv_vmware_snap ;
mv /dev/mapper/vg_sys-lv_vmware-real /dev/mapper/v
I think this is somehow related to
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/58627
I've been able to reproduce that bug as well. Recovery protocol is
exactly the same.
--
LVM Snapshot removal causes intermittent kernel panic
https://launchpad.net/bugs/71567
--
ubunt
Hi Ian,
I've reproduced the crash with
Linux anvil 2.6.15-27-server #1 SMP Sat Sep 16 02:57:21 UTC 2006 i686 GNU/Linux
and
Linux ws75 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux
both are bog standard 6.06 Ubuntu kernels (no custom funny business). Other
versions are probabl
For what its worth it seems Red Hat ES 4 is unaffected. The test script
works as expected on RHES4 with lvm2-2.02.06-6.0.RHEL4, kernel
2.6.9-42.EL.
--
LVM Snapshot removal causes intermittent kernel panic
https://launchpad.net/bugs/71567
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is 100% reproducible for us. It seems that lvremove is not syncing
before removal of the snapshot. (or perhaps it is wrong to --force
removal of snapshot.) Calling 'sync' immediately before removing the
snapshot seems to mitigate the chance of a crash.
Tested with Ubuntu 6.06.1 i386, clean in
** Description changed:
Binary package hint: lvm2
We have a script that automates the creation and removal of a LVM
snapshots on our VMware servers. Three times now we have had machines go
down when the snapshot was removed. I have logs showing the machine
- going down immediately after
** Summary changed:
- LVM Snapshot removal causes intermittent kernel oops
+ LVM Snapshot removal causes intermittent kernel panic
--
LVM Snapshot removal causes intermittent kernel panic
https://launchpad.net/bugs/71567
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
** Attachment added: "Crash 2"
http://librarian.launchpad.net/5058782/Image048.jpg
--
LVM Snapshot removal causes intermittent kernel oops
https://launchpad.net/bugs/71567
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "Crash 3"
http://librarian.launchpad.net/5058642/Image049.jpg
--
LVM Snapshot removal causes intermittent kernel oops
https://launchpad.net/bugs/71567
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: lvm2
We have a script that automates the creation and removal of a LVM
snapshots on our VMware servers. Three times now we have had machines go
down when the snapshot was removed. I have logs showing the machine
going down immediately after the snapshot r
20 matches
Mail list logo
