[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu30.2 --- eucalyptus (1.6.2-0ubuntu30.2) lucid-proposed; urgency=low * Revert: node/handlers_kvm.c: fix console bug (was only showing first 64K), LP: #566793 * clc/modules/www/src/main/java/edu/ucsb/eucalyptus/admin/server/EucalyptusWebBackendImpl.java: - fix user enumeration and account brute force, LP: #579942 * debian/eucalyptus-sc.upstart: Bump maximum number of loop devices for SC to 512, LP: #586134 eucalyptus (1.6.2-0ubuntu30.1) lucid-proposed; urgency=low Address LP: #565101 * debian/eucalyptus.conf: set default JVM_MEM option * debian/eucalyptus-common.eucalyptus.upstart: use $JVM_MEM from eucalyptus.conf, or default to 512m * tools/eucalyptus.conf.5: document the JVM_MEM option Cherry-pick upstream commit r1223..1227: * node/handlers.c, node/handlers_kvm.c: handle situation where NC's do not detach pthreads, LP: #567371 * node/handlers_kvm.c: fix console bug (was only showing first 64K), LP: #566793 * clc/modules/storage-common/src/main/java/edu/ucsb/eucalyptus/storage/StorageManager.java, clc/modules/storage-common/src/main/java/edu/ucsb/eucalyptus/storage/fs/FileSystemStorageManager.java, clc/modules/walrus/src/main/java/edu/ucsb/eucalyptus/cloud/ws/WalrusImageManager.java, clc/modules/walrus/src/main/java/edu/ucsb/eucalyptus/cloud/ws/WalrusManager.java, clc/modules/wsstack/src/main/java/com/eucalyptus/ws/handlers/ServiceSinkHandler.java: - fix Walrus OOM errors (java heap), LP: #565101 -- Chris Cheney cche...@ubuntu.com Fri, 04 Jun 2010 00:39:00 -0500 ** Changed in: eucalyptus (Ubuntu Lucid) Status: Fix Committed = Fix Released -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
Please upload the lucid fix to maverick as soon as possible (SRU policy). Bumping priority. ** Changed in: eucalyptus (Ubuntu Maverick) Milestone: lucid-updates = maverick-alpha-2 -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
This bug was fixed in the package eucalyptus - 1.6.2+bzr1230-0ubuntu1 --- eucalyptus (1.6.2+bzr1230-0ubuntu1) maverick; urgency=low [ Colin Watson ] * debian/eucalyptus-cloud.eucalyptus-cloud-publication.upstart: Only start after avahi-daemon has started. [ Dave Walker (Daviey) ] * Merge upstream branch, 1.6.2 (r1230) * Switch to dpkg-source 3.0 (quilt) format - Extracted the following patches from our bzr branch, into flat patches. * debian/build-jars: Replaced asm2 with asm3-all to match new groovy dependency. * clc/modules/www/src/main/java/edu/ucsb/eucalyptus/admin/server/EucalyptusWebBackendImpl.java: - fix user enumeration and account brute force. Courtesy of Chris Cheney. (LP: #579942) * debian/eucalyptus-sc.upstart: Bump maximum number of loop devices for SC to 512. (LP: #586134) -- Dave Walker (Daviey) davewal...@ubuntu.com Mon, 14 Jun 2010 13:48:17 +0100 ** Changed in: eucalyptus (Ubuntu Maverick) Status: Triaged = Fix Released -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Branch linked: lp:~davewalker/eucalyptus/maverick_to_quilt -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
Both Chris and I tested this. I run 2 loops: * allocating and deallocating 200 devices; * allocating and deallocating 513 devices. Both worked as expected. We *did* see errors, but they are unrelated to this bug (see bug 590929). As such, I consider this bug fixed. ** Tags added: verification-done ** Tags removed: verification-needed -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: eucalyptus (Ubuntu Lucid) Status: Triaged = Fix Committed ** Tags added: verification-needed -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Branch linked: lp:ubuntu/lucid-proposed/eucalyptus -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Description changed: Eucalyptus versions: ii eucalyptus-common 1.6.2-0ubuntu30.1 ii eucalyptus-java-common1.6.2-0ubuntu30.1 ii eucalyptus-sc 1.6.2-0ubuntu30.1 Bug 430846 and bug 498174 partially dealt with this issue. But, on an SC (perhaps also on the Walrus?) currently you cannot create more than 32 volumes -- trying to create the 33rdvolume will fail with the SC reporting: ERROR [BlockStorage:pool-10-thread-5] com.eucalyptus.util.EucalyptusCloudException: Could not create loopback device for //var/lib/ eucalyptus/volumes/vol-x. Please check the max loop value and permissions This, of course, is an artificial restriction: Consider a SC with a few terabytes of disc space, and consider euca-create-volumes usually running with a few tens of giga for the allocation (-s)... the system very fast reaches saturation, and real disc utilisation is still (probably) in the few units of percent. So, either this should be set in /etc/eucalyptus/eucaliptus.*conf, or eucalyptus should dynamically create the needed /dev/loppxxx. - *Notes*: + *Notes*: (1) setting this on the upstart script would allow for an initial setup, but would require the SC to be restarted for the new value to take effect, which will probably cause a temporary interruption of volume service. (2) I wonder how the system would behave on a reboot... + + == + + IMPACT: + * This bug affects people trying to create more than 32 SC volumes. + + ADDRESSED: + * This bug is addressed by creating more loopback devices (512) in the eucalyptus-sc upstart job. + + REPRODUCE: + * To reproduce this issue, try to create more than 32 SC volumes. You should not be able to do so. + + REGRESSION POTENTIAL: + * The chances for regression are relatively low. + + == -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
This appears to have worked for me up to 50 1GB volumes (actually allocated 52) then it started failing giving me the error in the log file: Your proposed upload exceeds the maximum allowed object size. (edu.ucsb.eucalyptus.cloud.EntityTooLargeException) I have plenty of space on my physical disk so this might be some configuration option somewhere. --- VOLUME vol-5EEE064E 1 cluster1available 2010-06-07T15:46:45.163Z VOLUME vol-5EDB064C 1 cluster1available 2010-06-07T15:48:13.219Z VOLUME vol-5F100652 1 cluster1available 2010-06-07T15:48:11.546Z VOLUME vol-5A140630 1 cluster1available 2010-06-07T15:47:17.402Z VOLUME vol-53E405FB 1 cluster1available 2010-06-07T15:47:16.295Z VOLUME vol-5A120630 1 cluster1available 2010-06-07T15:47:15.132Z VOLUME vol-59F0062B 1 cluster1available 2010-06-07T15:47:19.435Z VOLUME vol-5BA30654 1 cluster1available 2010-06-07T15:47:13.564Z VOLUME vol-598B0627 1 cluster1available 2010-06-07T15:48:09.349Z VOLUME vol-5FCA065B 1 cluster1failed 2010-06-07T15:47:17.824Z VOLUME vol-59900625 1 cluster1unavailable 2010-06-07T15:48:17.719Z VOLUME vol-59B4061D 1 cluster1available 2010-06-07T15:47:10.239Z VOLUME vol-5A4F0638 1 cluster1failed 2010-06-07T15:47:13.013Z VOLUME vol-59F6062E 1 cluster1unavailable 2010-06-07T15:48:17.033Z VOLUME vol-537005F7 1 cluster1available 2010-06-07T15:48:15.373Z VOLUME vol-59430623 1 cluster1available 2010-06-07T15:48:10.004Z VOLUME vol-5FFC065E 1 cluster1available 2010-06-07T15:48:06.419Z VOLUME vol-59890628 1 cluster1available 2010-06-07T15:47:12.535Z VOLUME vol-4D9B05C3 1 cluster1available 2010-06-07T15:46:28.121Z VOLUME vol-5F87065C 1 cluster1available 2010-06-07T15:48:16.439Z VOLUME vol-59820625 1 cluster1available 2010-06-07T15:48:12.686Z VOLUME vol-5985062A 1 cluster1available 2010-06-07T15:47:20.595Z VOLUME vol-591D0623 1 cluster1available 2010-06-07T15:48:13.773Z VOLUME vol-58960616 1 cluster1available 2010-06-07T15:47:22.804Z VOLUME vol-5A1A0633 1 cluster1available 2010-06-07T15:47:18.268Z VOLUME vol-5989061E 1 cluster1available 2010-06-07T15:48:14.861Z VOLUME vol-6066066F 1 cluster1available 2010-06-07T15:47:23.346Z VOLUME vol-597D0623 1 cluster1available 2010-06-07T15:47:15.802Z VOLUME vol-5E4F064C 1 cluster1available 2010-06-07T15:47:09.079Z VOLUME vol-59D20628 1 cluster1available 2010-06-07T15:48:15.883Z VOLUME vol-59580625 1 cluster1available 2010-06-07T15:48:07.651Z VOLUME vol-5A1B0636 1 cluster1available 2010-06-07T15:47:16.842Z VOLUME vol-596C061B 1 cluster1available 2010-06-07T15:47:21.518Z VOLUME vol-597B062E 1 cluster1available 2010-06-07T15:48:07.101Z VOLUME vol-59480621 1 cluster1available 2010-06-07T15:47:14.141Z VOLUME vol-5F870653 1 cluster1available 2010-06-07T15:48:12.129Z VOLUME vol-5F81065A 1 cluster1available 2010-06-07T15:47:07.054Z VOLUME vol-5A55063A 1 cluster1available 2010-06-07T15:48:08.217Z VOLUME vol-589D0619 1 cluster1available 2010-06-07T15:47:14.593Z VOLUME vol-611A0675 1 cluster1available 2010-06-07T15:48:08.769Z VOLUME vol-59D30628 1 cluster1available 2010-06-07T15:47:21.041Z VOLUME vol-5FD1065B 1 cluster1available 2010-06-07T15:47:19.989Z VOLUME vol-59BE063A 1 cluster1available 2010-06-07T15:48:14.228Z VOLUME vol-528605D9 1 cluster1available 2010-06-07T15:47:11.947Z VOLUME vol-598A062A 1 cluster1available 2010-06-07T15:47:04.444Z VOLUME vol-5F0A0650 1 cluster1available 2010-06-07T15:48:11.004Z VOLUME vol-583E060F 1 cluster1available 2010-06-07T15:47:22.064Z VOLUME vol-5917061E 1 cluster1
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
The above issue was caused by having my UEC set to 50GB limit for volumes. I changed it to 200GB under Configuration - Clusters - Disk space reserved for volumes and it allowed me to create 194 of them. It then started having problems from what appears to be a different but related bug of not properly cleaning up after failed/unavailable volumes. I am still testing that problem though. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
My removal errors are probably related to 517086, but the creation error appears to be new according to C de-Avillez, it is failing at vgcreate, example follows: 12:32:54 DEBUG [SystemUtil:pool-10-thread-4] Running command: ///usr/lib/eucalyptus/euca_rootwrap dd if=/dev/zero of=//var/lib/eucalyptus/volumes/vol-613B0677 count=1 bs=1M seek=1027 12:32:54 INFO [ServiceSinkHandler:ReplyQueue.10] :1275931974448:eucalyptus:uid:admin:cb7fa02b-1b7c-4f2a-807d-f171acfa1876:MSG_SERVICED:CreateVolumeResponseType:165: 12:32:54 DEBUG [SystemUtil:pool-10-thread-5] Running command: ///usr/lib/eucalyptus/euca_rootwrap vgcreate vg-sGXOSQ.. /dev/loop92 12:32:54 DEBUG [SystemUtil:pool-10-thread-4] Running command: ///usr/lib/eucalyptus/euca_rootwrap losetup -f 12:32:54 INFO [LVM2Manager:pool-10-thread-4] losetup /dev/loop93 //var/lib/eucalyptus/volumes/vol-613B0677 12:32:54 INFO [LVM2Manager:pool-10-thread-4] 12:32:54 INFO [LVM2Manager:pool-10-thread-4] 12:32:54 DEBUG [SystemUtil:pool-10-thread-4] Running command: ///usr/lib/eucalyptus/euca_rootwrap pvcreate /dev/loop93 12:32:54 INFO [AOEManager:pool-10-thread-2] Trying e5.7 12:32:54 DEBUG [SystemUtil:pool-10-thread-4] Running command: ///usr/lib/eucalyptus/euca_rootwrap vgcreate vg-6E6tMQ.. /dev/loop93 12:32:54 INFO [AOEManager:pool-10-thread-1] Trying e5.8 12:32:54 INFO [BlockStorageStatistics:pool-10-thread-3] Service: StorageController Version: 1.6.2 Volumes: 86 Space Used: 91268055040 12:32:54 INFO [BlockStorageStatistics:pool-10-thread-3] Service: StorageController Version: 1.6.2 Volumes: 86 Space Used: 92341796864 12:32:54 INFO [ServiceSinkHandler:ReplyQueue.10] :1275931974956:eucalyptus:uid:admin:60f67a28-1c90-4c26-9a93-0426f5e83f85:MSG_SERVICED:CreateVolumeResponseType:50: 12:32:54 DEBUG [SystemUtil:pool-10-thread-3] Running command: ///usr/lib/eucalyptus/euca_rootwrap dd if=/dev/zero of=//var/lib/eucalyptus/volumes/vol-58B20615 count=1 bs=1M seek=1027 12:32:54 ERROR [SystemUtil:pool-10-thread-4] com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap vgcreate vg-6E6tMQ.. /dev/loop93 com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap vgcreate vg-6E6tMQ.. /dev/loop93 at edu.ucsb.eucalyptus.util.SystemUtil.run(SystemUtil.java:91) at edu.ucsb.eucalyptus.storage.LVM2Manager.createVolumeGroup(LVM2Manager.java:170) at edu.ucsb.eucalyptus.storage.LVM2Manager.createLogicalVolume(LVM2Manager.java:390) at edu.ucsb.eucalyptus.storage.LVM2Manager.createVolume(LVM2Manager.java:435) at edu.ucsb.eucalyptus.cloud.ws.BlockStorage$VolumeCreator.run(BlockStorage.java:789) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) 12:32:54 ERROR [BlockStorage:pool-10-thread-4] com.eucalyptus.util.EucalyptusCloudException: Unable to create volume group vg-6E6tMQ.. for /dev/loop93 -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
I manually ran: # /usr/lib/eucalyptus/euca_rootwrap vgcreate vg-6E6tMQ.. /dev/loop93 Volume group vg-6E6tMQ.. successfully created So I am not sure what is going on. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
Actually my volume removal errors seem to be different than the other
bug at least in several of the cases I have looked at. They are also
lvremove issues like the vgcreate ones.
---
12:53:57 DEBUG [SystemUtil:pool-10-thread-5] Running command:
///usr/lib/eucalyptus/euca_rootwrap lvremove -f /dev/vg-qJp0gg../lv-XL682g..
12:53:57 INFO [AbstractClusterMessageDispatcher:New I/O client worker #2-26]
:1275933237619:GetKeysType:uid:eucalyptus:eucalyptus:MSG_SENT:[GetKeysType
serviceTag=self correlationId=9b4bb56a-6eab-4031-9993-39eb7bc5b6c4 userId=null
effectiveUserId=null _return=false statusMessage=null]:
12:53:57 INFO [AbstractClusterMessageDispatcher:New I/O client worker #2-27]
:1275933237647:DescribeNetworksType:uid:eucalyptus:eucalyptus:MSG_SENT:[DescribeNetworksType
nameserver=10.0.0.16 clusterControllers=[10.0.0.16]
correlationId=707c04e9-6b93-480c-94cd-137256854560 userId=eucalyptus
effectiveUserId=eucalyptus _return=false statusMessage=null]:
12:53:57 INFO [ClusterUtil:New I/O client worker #2-26]
---
12:53:57 INFO [ClusterUtil:New I/O client worker #2-26] - [ cluster1 ]
Cluster certificate valid=true
12:53:57 INFO [ClusterUtil:New I/O client worker #2-26] - [ cluster1 ] Node
certificate valid=true
12:53:57 INFO [ClusterUtil:New I/O client worker #2-26]
---
12:53:57 INFO [AbstractClusterMessageDispatcher:New I/O client worker #2-30]
:1275933237661:DescribePublicAddressesType:uid:eucalyptus:eucalyptus:MSG_SENT:[DescribePublicAddressesType
correlationId=dbbc8856-e385-4809-a800-a97c56779e63 userId=eucalyptus
effectiveUserId=eucalyptus _return=false statusMessage=null]:
12:53:57 INFO [AbstractClusterMessageDispatcher:New I/O client worker #2-30]
:1275933237708:DescribePublicAddressesResponseType:uid:eucalyptus:eucalyptus:MSG_SENT:[DescribePublicAddressesResponseType
addresses=[10.0.0.32, 10.0.0.33, 10.0.0.34, 10.0.0.35, 10.0.0.36, 10.0.0.37,
10.0.0.38, 10.0.0.39, 10.0.0.40, 10.0.0.41, 10.0.0.42, 10.0.0.43, 10.0.0.44,
10.0.0.45, 10.0.0.46, 10.0.0.47, 10.0.0.48] mapping=[, , , , , , , , , , , , ,
, , , ] correlationId=dbbc8856-e385-4809-a800-a97c56779e63 userId=eucalyptus
effectiveUserId=null _return=true statusMessage=null]:
12:53:57 DEBUG [SystemUtil:pool-10-thread-3] Running command:
///usr/lib/eucalyptus/euca_rootwrap pvremove /dev/loop55
12:53:57 INFO [AbstractClusterMessageDispatcher:New I/O client worker #2-28]
:1275933237712:DescribeResourcesType:uid:eucalyptus:eucalyptus:MSG_SENT:[DescribeResourcesType
instanceTypes=[VmTypeInfo{name='m1.small', memory=192, disk=2, cores=1},
VmTypeInfo{name='c1.medium', memory=256, disk=5, cores=1},
VmTypeInfo{name='m1.large', memory=512, disk=10, cores=2},
VmTypeInfo{name='m1.xlarge', memory=1024, disk=20, cores=2},
VmTypeInfo{name='c1.xlarge', memory=2048, disk=20, cores=4}]
correlationId=d97ca222-d730-40d5-8a2f-7bb640da5d20 userId=eucalyptus
effectiveUserId=eucalyptus _return=false statusMessage=null]:
12:53:57 ERROR [SystemUtil:pool-10-thread-5]
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
lvremove -f /dev/vg-qJp0gg../lv-XL682g..
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap
lvremove -f /dev/vg-qJp0gg../lv-XL682g..
at edu.ucsb.eucalyptus.util.SystemUtil.run(SystemUtil.java:91)
at
edu.ucsb.eucalyptus.storage.LVM2Manager.removeLogicalVolume(LVM2Manager.java:186)
at
edu.ucsb.eucalyptus.storage.LVM2Manager.deleteVolume(LVM2Manager.java:612)
at
edu.ucsb.eucalyptus.cloud.ws.BlockStorage$VolumeDeleter.run(BlockStorage.java:844)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
12:53:57 ERROR [BlockStorage:pool-10-thread-5]
com.eucalyptus.util.EucalyptusCloudException: Unable to remove logical volume
/dev/vg-qJp0gg../lv-XL682g..
--
SC: Maximum number of loop devices should be configurable
https://bugs.launchpad.net/bugs/586134
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
So this bug regarding loop devices seems to be fixed but there is a new bug 590929 opened about the problems with creating/deleting volumes having problems with lvm. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Branch linked: lp:~ccheney/ubuntu/lucid/eucalyptus/lucid-sru -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Changed in: eucalyptus (Ubuntu Lucid) Assignee: (unassigned) = Chris Cheney (ccheney) ** Changed in: eucalyptus (Ubuntu Lucid) Status: New = Triaged ** Changed in: eucalyptus (Ubuntu Lucid) Importance: Undecided = High -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
** Changed in: eucalyptus (Ubuntu) Assignee: (unassigned) = Chris Cheney (ccheney) ** Also affects: eucalyptus (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu Maverick) Importance: High Assignee: Chris Cheney (ccheney) Status: Triaged -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
new test, using resources provided by Etienne Goyer (et merci beaucoup Etienne!): I successfully allocated 257 volumes. This is interesting, in one aspect: I understood we could have a max of 256 volumes and 256 snapshots. It seems that the real maximum is 512 (to be tested); but we may end up eating on the snapshots area if we go above (to be tested). -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
proposing for lucid-updates. Changes will be made to /etc/init /eucalyptus-sc.conf (and, perhaps, to /etc/eucalyptus/eucalyptus.conf?) raising the loopback devices to 512 (256 max volumes, plus one snapshot per volume). ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = High ** Changed in: eucalyptus (Ubuntu) Milestone: None = lucid-updates -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
*Note* per Dan, the NCs use one loopback device per VM *startup*. Currently we are defaulting to 32 loopback in the upstart script, so we should be good to up-to 32 *simultaneous* instances startups. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
Marking Triaged, given the results of the teleconference. ** Changed in: eucalyptus (Ubuntu) Status: New = Triaged -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 586134] Re: SC: Maximum number of loop devices should be configurable
I have tested it on the test rig: updated the upstart script to allocate 512 /dev/loopnnn, and successfully created 50 volumes (the max we can create right now). -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
