[Bug 605721] Re: tgtd target will not start unless it's configured with allow-in-use yes
I see you ran it in your comment above, but was it immediately after the error happened or some time later? -- tgtd target will not start unless it's configured with allow-in-use yes https://bugs.launchpad.net/bugs/605721 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt 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 605721] Re: tgtd target will not start unless it's configured with allow-in-use yes
Hmm looking at the code I think its buggy. I'm not sure what it is
actually trying to do but it doesn't seem to be doing it right in any
case. It appears to be 8 bit shifting left, and then checking for 0. If
the device is in use lsof returns 0 if it is not then it returns 1, at
least as best as I can tell, in which case doing the bit shift causes
the problem. I am not sure why it was added, but it probably was needed
for something.
# Check if userspace uses this device
my $lsof_check = check_exe(lsof);
if ($lsof_check ne 1) {
system(lsof $backing_store /dev/null);
my $exit_value = $? 8;
if ($exit_value eq 0) {
execute(# Device $backing_store is used (already tgtd
target?).);
execute(# Run 'lsof $backing_store' to see the
details.);
return 0;
}
}
return 1;
}
--
tgtd target will not start unless it's configured with allow-in-use yes
https://bugs.launchpad.net/bugs/605721
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt 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 605721] Re: tgtd target will not start unless it's configured with allow-in-use yes
It appears to be a bug caused by using this: system(lsof $backing_store /dev/null); instead of: system(lsof $backing_store /dev/null 21); -- tgtd target will not start unless it's configured with allow-in-use yes https://bugs.launchpad.net/bugs/605721 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt 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 605721] Re: tgtd target will not start unless it's configured with allow-in-use yes
I was confused earlier about the direction of bitshift since the wrong calling convention was causing it to always return 0. -- tgtd target will not start unless it's configured with allow-in-use yes https://bugs.launchpad.net/bugs/605721 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt 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 605721] Re: tgtd target will not start unless it's configured with allow-in-use yes
Forgot the # in the closes line in the upload. It was fixed in tgt 1:1.0.4-1ubuntu3 ** Changed in: tgt (Ubuntu Maverick) Status: Triaged = Fix Released -- tgtd target will not start unless it's configured with allow-in-use yes https://bugs.launchpad.net/bugs/605721 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
The fix from upstream appears to work. This bug can be closed out once the fix goes into Maverick and will be in a ppa for alpha-2 testing from what Tim has said on IRC. Thanks for all the help Tim! -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 565771] Re: Please stop disabling the VMware ESX driver
won't fix per hallyn ** Changed in: libvirt (Ubuntu) Status: New = Won't Fix -- Please stop disabling the VMware ESX driver https://bugs.launchpad.net/bugs/565771 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
sendfile is used by openjdk-6 directly in the following file: http://pastebin.com/tceugS7r -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
During test of the following kernel it prints the following to dmesg once for each pass: ae0f36f0b964caf916c2ffc9f84b28c0f91c18a2-maverick [ 365.268713] /home/rtg/kern/maverick/kern-64/ubuntu- maverick/fs/read_write.c:849 should this happen? -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
0a87a0c1b12f56bd556fd4506041966717c87fb1-maverick failed as expected [ 129.980324] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.931445] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.946722] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.956955] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.966482] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.975832] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.985221] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 178.995507] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.004812] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.014215] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.023585] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.032934] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.042205] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.051533] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.060871] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.070252] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.079538] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.089084] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.099589] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) [ 179.110479] /home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849 816256e0 (null) --- afef312909fa10e603a05e030b2ee2feebde8d9f-maverick works -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
Works with 23eb3b64b5e44680c867e165fe1cd18e57fba255 (required compile fix, probably the same one as Tim mentioned earlier). -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
He appears to have made another update related to sendfile on May 26. However, I am not sure if it fixes this problem or that it has been applied to mainline yet. http://marc.info/?a=119980668900012r=1w=2 -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
Tracked down to occurring in 2.6.33rc1, so will be checking between that and 2.6.32-15.5 -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
After changing my test to just be registering the images per Dave's recommendation I was able to come up with this list: I tested the following kernels, 10 times each: Passed: v2.6.32 (10/10) v2.6.32.15.5-lucid (10/10) Failed: v2.6.33 (10/10) v2.6.34-rc3-maverick (10/10) v2.6.34-lucid (09/10) (weird python failure instead for 1 of them, see below) So it looks like it broken between 2.6.32.15.5 and 2.6.33. -- Sun Jun 20 23:57:09 CDT 2010: == extracting image == Warning: no ramdisk found, assuming '--ramdisk none' kernel : lucid-server-uec-amd64-vmlinuz-virtual ramdisk: none image : lucid-server-uec-amd64.img Sun Jun 20 23:57:17 CDT 2010: == bundle/upload kernel == Sun Jun 20 23:57:19 CDT 2010: == bundle/upload image == Traceback (most recent call last): File /usr/bin/euca-bundle-image, line 231, in module main() File /usr/bin/euca-bundle-image, line 209, in main encrypted_file, key, iv, bundled_size = euca.encrypt_image(tgz_file) File /usr/lib/python2.6/dist-packages/euca2ools/__init__.py, line 579, in encrypt_image k=EVP.Cipher(alg='aes_128_cbc', key=unhexlify(key), iv=unhexlify(iv), op=1) TypeError: Odd-length string failed to bundle image lucid-server-uec-amd64.img failed bundle/upload/register of image Encrypting image -- -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 566793] Re: [SRU] euca-get-console-output gives first 64k of output, not most recent
Should this bug be reopened, since we reverted the patch? It seems incorrect to leave it marked Fix Released as least, either Triaged or Won't Fix seem better. -- [SRU] euca-get-console-output gives first 64k of output, not most recent https://bugs.launchpad.net/bugs/566793 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
works: Linux beagle 2.6.32-020632-generic #020632 SMP Thu Dec 3 10:09:58 UTC 2009 x86_64 GNU/Linux Linux beagle 2.6.32-0206321505-generic #0206321505 SMP Wed Jun 2 19:09:40 UTC 2010 x86_64 GNU/Linux bad: Linux beagle 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC 2010 x86_64 GNU/Linux -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
Hmm I tried 2.6.33 again just to be certain and now it is working on 2.6.33, hmm :-\ -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
I now can't get it to crash anymore. I am upgrading from maverick alpha 1 to current and then will do further testing. -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 588861] Re: pad block corrupted error when trying to register an image with 2.6.34 kernel
I tried upgrading to current and now I can't see my nc anymore. :-\ -- pad block corrupted error when trying to register an image with 2.6.34 kernel https://bugs.launchpad.net/bugs/588861 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 590929] [NEW] eucalyptus create and delete volumes sometimes fail on lvm commands
Public bug reported:
When testing out bug 586134 I found another issue and although similar
to bug 517086 appears not to be the same issue.
If you create for example 200 1GB volumes like this:
for i in `seq 1 200` ; do euca-create-volume -z cluster1 -s 1 ; done
You will end up with quite a few failed. If you look in the logs it is
usually caused by vgcreate failing for unknown reasons as the output of
the command is not logged. If you run the same command on the command
line that failed it will then work.
Also if you then delete all the volumes like this:
for i in `euca-describe-volumes | awk '{print $2}'` ; do euca-delete-
volume $i ; done
You will end up with a huge number that do not get removed. If you look
in the logs it is usually caused by lvremove failing for unknown reasons
like with vgcreate. Again if you run the same command on the command
line that failed it will then work.
Also despite the failure to properly delete the volume euca-describe-
volumes will have invalid information. For example if you delete the
volume it will no longer show up in the list but it will still be there
as seen by losetup and vgscan, and will still be set back up by
eucalyptus when rebooted but it will not show up in the euca-describe-
volume list.
Chris
** Affects: eucalyptus (Ubuntu)
Importance: Medium
Status: Confirmed
** Affects: eucalyptus (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
** Description changed:
When testing out bug 586134 I found another issue and although similar
to bug 517086 appears not to be the same issue.
If you create for example 200 1GB volumes like this:
for i in `seq 1 200` ; do euca-create-volume -z cluster1 -s 1 ; done
You will end up with quite a few failed. If you look in the logs it is
usually caused by vgcreate failing for unknown reasons as the output of
the command is not logged. If you run the same command on the command
line that failed it will then work.
Also if you then delete all the volumes like this:
for i in `euca-describe-volumes | awk '{print $2}'` ; do euca-delete-
volume $i ; done
You will end up with a huge number that do not get removed. If you look
in the logs it is usually caused by lvremove failing for unknown reasons
like with vgcreate. Again if you run the same command on the command
line that failed it will then work.
+ Also despite the failure to properly delete the volume euca-describe-
+ volumes will have invalid information. For example if you delete the
+ volume it will no longer show up in the list but it will still be there
+ as seen by losetup and vgscan, and will still be set back up when
+ rebooted by eucalyptus but it will not show up in the euca-describe-
+ volume list.
+
Chris
** Description changed:
When testing out bug 586134 I found another issue and although similar
to bug 517086 appears not to be the same issue.
If you create for example 200 1GB volumes like this:
for i in `seq 1 200` ; do euca-create-volume -z cluster1 -s 1 ; done
You will end up with quite a few failed. If you look in the logs it is
usually caused by vgcreate failing for unknown reasons as the output of
the command is not logged. If you run the same command on the command
line that failed it will then work.
Also if you then delete all the volumes like this:
for i in `euca-describe-volumes | awk '{print $2}'` ; do euca-delete-
volume $i ; done
You will end up with a huge number that do not get removed. If you look
in the logs it is usually caused by lvremove failing for unknown reasons
like with vgcreate. Again if you run the same command on the command
line that failed it will then work.
Also despite the failure to properly delete the volume euca-describe-
volumes will have invalid information. For example if you delete the
volume it will no longer show up in the list but it will still be there
- as seen by losetup and vgscan, and will still be set back up when
- rebooted by eucalyptus but it will not show up in the euca-describe-
+ as seen by losetup and vgscan, and will still be set back up by
+ eucalyptus when rebooted but it will not show up in the euca-describe-
volume list.
Chris
--
eucalyptus create and delete volumes sometimes fail on lvm commands
https://bugs.launchpad.net/bugs/590929
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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
This might actually be a problem with lvm, but even if it is caused by lvm it should still be properly caught by eucalyptus so that if the delete volume failure happens it will show up in euca-describe-volumes ** Also affects: eucalyptus (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: eucalyptus (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: eucalyptus (Ubuntu Lucid) Status: New = Confirmed -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
This appears to be caused by eucalyptus not checking the return values it gets. -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
And to top it off lvm does not document its return codes, at least not in the man pages anyway. -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
It appears lvm always returns error code 5 on failure... for any kind of failure. So I'm not sure exactly what we should do here to fix this problem. Often the problem is actually just a can't get lock issue like the following, but without having a useful error code we can't know when to retry or to just fail. 20.35.01.198672267 /sbin/vgcreate vg-lDNyug.. /dev/loop6 /var/lock/lvm/P_orphans: flock failed: Resource temporarily unavailable Can't get lock for orphan PVs status = 5 -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
http://fedoraproject.org/wiki/LVM/liblvm -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
It appears the liblvm library is in newer lvm2 source which is in Debian unstable. Whether converting eucalyptus to it is actually needed and/or if it would be enough to help fix these sorts of issues is still unknown. From a cursory look it appears it may be useful. -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 590929] Re: eucalyptus create and delete volumes sometimes fail on lvm commands
It seems its not so much the not checking for the return code as not doing the right thing afterwards. If it receives an error it appears to just throw an exception and does not clean up after itself, at least for the createLogicalVolume case. -- eucalyptus create and delete volumes sometimes fail on lvm commands https://bugs.launchpad.net/bugs/590929 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 582925] Re: OOo needs mount.cifs to default to nobrl if possible
** Changed in: samba (Ubuntu Lucid) Status: New = Invalid ** Changed in: samba (Ubuntu) Status: New = Invalid ** Changed in: samba (Ubuntu Lucid) Milestone: ubuntu-10.04.1 = None ** Changed in: samba (Ubuntu) Importance: High = Undecided ** Changed in: samba (Ubuntu Lucid) Importance: High = Undecided -- OOo needs mount.cifs to default to nobrl if possible https://bugs.launchpad.net/bugs/582925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 583530] Re: vm-builder 0.12.3-0ubuntu1 crashes and causes loop devices to be stuck
I didn't use ctrl-c vm-builder just bombed out probably due to other bugs and didn't clean up the resulting mess, and I couldn't figure out how to clean it up later without rebooting. -- vm-builder 0.12.3-0ubuntu1 crashes and causes loop devices to be stuck https://bugs.launchpad.net/bugs/583530 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder 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 583479] [NEW] vm-builder 0.12.3-0ubuntu1 is missing the --tmp option
Public bug reported: The vmbuilder manpage mentions a --tmp option to allow using other than /tmp but it does not actually work when you try to use it with vmbuilder kvm ubuntu, this is probably for similar reasons to bug 536940. ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- vm-builder 0.12.3-0ubuntu1 is missing the --tmp option https://bugs.launchpad.net/bugs/583479 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder 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 582925] [NEW] OOo needs mount.cifs to default to nobrl if possible
Public bug reported: Binary package hint: samba This doesn't affect me directly but I maintain OpenOffice.org for Ubuntu. It appears after getting numerous reports that OOo does not save properly to cifs mounted filesystems that the cause is due to the fact the 'nobrl' option is not being used. The root cause of this bug may be a problem in OOo itself but according to the man page of mount.cifs it sounds like it would probably be a good idea to use this option in any case. nobrl Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks). Some of the OOo bugs, I may have missed some, are bug 486443, and bug 578402. Also upstream bug http://qa.openoffice.org/issues/show_bug.cgi?id=93957 among 10 other cifs related bugs, probably all caused by lack of nobrl. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: smbfs 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that Date: Wed May 19 11:26:35 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100128) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SambaClientRegression: No SourcePackage: samba ** Affects: samba (Ubuntu) Importance: High Status: New ** Affects: samba (Ubuntu Lucid) Importance: High Status: New ** Tags: amd64 apport-bug lucid -- OOo needs mount.cifs to default to nobrl if possible https://bugs.launchpad.net/bugs/582925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 582925] Re: OOo needs mount.cifs to default to nobrl if possible
** Attachment added: CifsVersion.txt http://launchpadlibrarian.net/48733924/CifsVersion.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48733925/Dependencies.txt ** Attachment added: SambaInstalledVersions.txt http://launchpadlibrarian.net/48733926/SambaInstalledVersions.txt ** Changed in: samba (Ubuntu) Importance: Undecided = High ** Description changed: Binary package hint: samba This doesn't affect me directly but I maintain OpenOffice.org for Ubuntu. It appears after getting numerous reports that OOo does not save properly to cifs mounted filesystems and that the cause is due to the fact the 'nobrl' option is not being used. The root cause of this bug may be a problem in OOo itself but according to the man page of mount.cifs it sounds like it would probably be a good idea to use this option in any case. nobrl -Do not send byte range lock requests to the server. This is -necessary for certain applications that break with cifs style -mandatory byte range locks (and most cifs servers do not yet -support requesting advisory byte range locks). + Do not send byte range lock requests to the server. This is + necessary for certain applications that break with cifs style + mandatory byte range locks (and most cifs servers do not yet + support requesting advisory byte range locks). Some of the OOo bugs, I may have missed some, are bug 486443, and bug - 578402. Also upstream bug 93957 among 10 other cifs related bugs, - probably all caused by lack of nobrl. + 578402. Also upstream bug + http://qa.openoffice.org/issues/show_bug.cgi?id=93957 among 10 other + cifs related bugs, probably all caused by lack of nobrl. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: smbfs 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that Date: Wed May 19 11:26:35 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100128) ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SambaClientRegression: No SourcePackage: samba ** Also affects: samba (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: samba (Ubuntu Lucid) Milestone: None = ubuntu-10.04.1 ** Changed in: samba (Ubuntu Lucid) Importance: Undecided = High ** Description changed: Binary package hint: samba This doesn't affect me directly but I maintain OpenOffice.org for Ubuntu. It appears after getting numerous reports that OOo does not save - properly to cifs mounted filesystems and that the cause is due to the - fact the 'nobrl' option is not being used. The root cause of this bug - may be a problem in OOo itself but according to the man page of - mount.cifs it sounds like it would probably be a good idea to use this - option in any case. + properly to cifs mounted filesystems that the cause is due to the fact + the 'nobrl' option is not being used. The root cause of this bug may be + a problem in OOo itself but according to the man page of mount.cifs it + sounds like it would probably be a good idea to use this option in any + case. nobrl Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks). Some of the OOo bugs, I may have missed some, are bug 486443, and bug 578402. Also upstream bug http://qa.openoffice.org/issues/show_bug.cgi?id=93957 among 10 other cifs related bugs, probably all caused by lack of nobrl. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: smbfs 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that Date: Wed May 19 11:26:35 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100128) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SambaClientRegression: No SourcePackage: samba -- OOo needs mount.cifs to default to nobrl if possible https://bugs.launchpad.net/bugs/582925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 582925] Re: OOo needs mount.cifs to default to nobrl if possible
I found that we do have a way to disable locking entirely for cifs in OOo that we can use if this bug isn't considered good or safe to fix by enabling nobrl. -- OOo needs mount.cifs to default to nobrl if possible https://bugs.launchpad.net/bugs/582925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 582925] Re: OOo needs mount.cifs to default to nobrl if possible
The workaround for OOo required updating coreutils to detect cifs which I have added a patch for in bug 582980. -- OOo needs mount.cifs to default to nobrl if possible https://bugs.launchpad.net/bugs/582925 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 273930] Re: oosplash.bin crashed with SIGSEGV in splash_create_window() under KVM
This appears to be some sort of KVM issue, or at least it isn't reproducible anywhere else. ** Summary changed: - oosplash.bin crashed with SIGSEGV in splash_create_window() + oosplash.bin crashed with SIGSEGV in splash_create_window() under KVM ** Package changed: openoffice.org (Ubuntu) = kvm (Ubuntu) ** Changed in: kvm (Ubuntu) Status: Invalid = New -- oosplash.bin crashed with SIGSEGV in splash_create_window() under KVM https://bugs.launchpad.net/bugs/273930 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm 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
