Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 476244[details]
vdsm.log
Description of problem:
created lots of vms from pool, during creation process, noticed the following error:
4a905402-8498-429c-b46c-083cc096a1b6::ERROR::2011-01-31 16:01:15,856::blockVolume::529::Storage.Volume::(getMetaOffset) missing offset tag on volume f967d8f8-3
5fd-4122-ad92-f1e0fc7c4c44
4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,856::resourceManager::517::ResourceManager::(releaseResource) Trying to release resource 'a545
fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595'
4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,857::resourceManager::532::ResourceManager::(releaseResource) Released resource 'a545fb3b-027c
-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595' (0 active users)
4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,857::resourceManager::537::ResourceManager::(releaseResource) Resource 'a545fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595' is free, finding out if anyone is waiting for it.
4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,858::resourceManager::544::ResourceManager::(releaseResource) No one is waiting for resource 'a545fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595', Clearing records.
4a905402-8498-429c-b46c-083cc096a1b6::ERROR::2011-01-31 16:01:15,858::task::854::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 862, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 299, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 110, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 885, in createVolume
srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID)
File "/usr/share/vdsm/storage/blockSD.py", line 355, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/blockVolume.py", line 218, in create
mysd.produceVolume(imgUUID, volUUID).setLegality(volume.LEGAL_VOL)
File "/usr/share/vdsm/storage/volume.py", line 380, in setLegality
self.setMetaParam(LEGALITY, legality)
File "/usr/share/vdsm/storage/volume.py", line 756, in setMetaParam
meta = self.getMetadata(nocache=nocache)
File "/usr/share/vdsm/storage/blockVolume.py", line 542, in getMetadata
offs = self.getMetaOffset()
File "/usr/share/vdsm/storage/blockVolume.py", line 530, in getMetaOffset
raise se.VolumeMetadataReadError("missing offset tag on volume %s" % self.volUUID)
VolumeMetadataReadError: Error while processing volume meta data: ('missing offset tag on volume f967d8f8-35fd-4122-ad92-f1e0fc7c4c44',)
Run and protect: createVolume, args: ( sdUUID=a545fb3b-027c-458c-
b76f-5facf67ac8cc spUUID=a8e3a5e0-1437-4dfb-9ac5-c6835227a074 imgUUID=035b1408-3156-40ee-b872-3c3606f8d595 size=5368709120 volFormat=4 preallocate=2 diskType=2
volUUID=f967d8f8-35fd-4122-ad92-f1e0fc7c4c44 desc=_ActiveImage_FC-rhel6-194_Mon Jan 31 16:02:05 IST 2011 srcImgUUID=45465a33-75f6-447d-9fc4-dc9f4de8836a srcVo
lUUID=9a2a526f-1dbd-4665-8f7e-00220e424fbb)
Thread-6086::INFO::2011-01-31 16:16:22,881::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: createVolume, Return response: {'status': {'message': 'OK', 'code': 0}, 'uuid': '28ee2a60-6e1d-49f2-aa69-fe6f873ec43a'}
repro steps:
1) create vm
2) create template
3) create pool of 200 vms
4) watch log.
Comment 2Eduardo Warszawski
2011-02-10 13:17:23 UTC
The bug is a result of a race between the blockVolume.create() thread and another thread doing lvs on the same VG.
The race is removed when the legality is set with all the metadata instead to do an extra lvm operation.
Comment 3Eduardo Warszawski
2011-02-24 08:23:42 UTC
*** Bug 597807 has been marked as a duplicate of this bug. ***
Created attachment 476244 [details] vdsm.log Description of problem: created lots of vms from pool, during creation process, noticed the following error: 4a905402-8498-429c-b46c-083cc096a1b6::ERROR::2011-01-31 16:01:15,856::blockVolume::529::Storage.Volume::(getMetaOffset) missing offset tag on volume f967d8f8-3 5fd-4122-ad92-f1e0fc7c4c44 4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,856::resourceManager::517::ResourceManager::(releaseResource) Trying to release resource 'a545 fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595' 4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,857::resourceManager::532::ResourceManager::(releaseResource) Released resource 'a545fb3b-027c -458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595' (0 active users) 4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,857::resourceManager::537::ResourceManager::(releaseResource) Resource 'a545fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595' is free, finding out if anyone is waiting for it. 4a905402-8498-429c-b46c-083cc096a1b6::DEBUG::2011-01-31 16:01:15,858::resourceManager::544::ResourceManager::(releaseResource) No one is waiting for resource 'a545fb3b-027c-458c-b76f-5facf67ac8cc_imageNS.035b1408-3156-40ee-b872-3c3606f8d595', Clearing records. 4a905402-8498-429c-b46c-083cc096a1b6::ERROR::2011-01-31 16:01:15,858::task::854::TaskManager.Task::(_setError) Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 862, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/task.py", line 299, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/share/vdsm/storage/spm.py", line 110, in run return self.func(*args, **kwargs) File "/usr/share/vdsm/storage/spm.py", line 885, in createVolume srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID) File "/usr/share/vdsm/storage/blockSD.py", line 355, in createVolume volUUID, desc, srcImgUUID, srcVolUUID) File "/usr/share/vdsm/storage/blockVolume.py", line 218, in create mysd.produceVolume(imgUUID, volUUID).setLegality(volume.LEGAL_VOL) File "/usr/share/vdsm/storage/volume.py", line 380, in setLegality self.setMetaParam(LEGALITY, legality) File "/usr/share/vdsm/storage/volume.py", line 756, in setMetaParam meta = self.getMetadata(nocache=nocache) File "/usr/share/vdsm/storage/blockVolume.py", line 542, in getMetadata offs = self.getMetaOffset() File "/usr/share/vdsm/storage/blockVolume.py", line 530, in getMetaOffset raise se.VolumeMetadataReadError("missing offset tag on volume %s" % self.volUUID) VolumeMetadataReadError: Error while processing volume meta data: ('missing offset tag on volume f967d8f8-35fd-4122-ad92-f1e0fc7c4c44',) Run and protect: createVolume, args: ( sdUUID=a545fb3b-027c-458c- b76f-5facf67ac8cc spUUID=a8e3a5e0-1437-4dfb-9ac5-c6835227a074 imgUUID=035b1408-3156-40ee-b872-3c3606f8d595 size=5368709120 volFormat=4 preallocate=2 diskType=2 volUUID=f967d8f8-35fd-4122-ad92-f1e0fc7c4c44 desc=_ActiveImage_FC-rhel6-194_Mon Jan 31 16:02:05 IST 2011 srcImgUUID=45465a33-75f6-447d-9fc4-dc9f4de8836a srcVo lUUID=9a2a526f-1dbd-4665-8f7e-00220e424fbb) Thread-6086::INFO::2011-01-31 16:16:22,881::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: createVolume, Return response: {'status': {'message': 'OK', 'code': 0}, 'uuid': '28ee2a60-6e1d-49f2-aa69-fe6f873ec43a'} repro steps: 1) create vm 2) create template 3) create pool of 200 vms 4) watch log.