Re: [ovirt-users] VM failed to start | Bad volume specification
On Mar 19, 2015, at 03:18 , Punit Dambiwal hypu...@gmail.com wrote: Hi All, Is there any one have any idea about this problem...it seems it's bug either in Ovirt or Glusterfs...that's why no one has the idea about itplease correct me if i am wrong…. Hi, as I said, storage access times out; so it seems to me as a gluster setup problem, the storage domain you have your VMs on is not working… Thanks, michal Thanks, Punit On Wed, Mar 18, 2015 at 5:05 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi Michal, Would you mind to let me know the possible messedup things...i will check and try to resolve itstill i am communicating gluster community to resolve this issue... But in the ovirtgluster setup is quite straightso how come it will be messedup with reboot ?? if it can be messedup with reboot then it seems not good and stable technology for the production storage Thanks, Punit On Wed, Mar 18, 2015 at 3:51 PM, Michal Skrivanek michal.skriva...@redhat.com wrote: On Mar 18, 2015, at 03:33 , Punit Dambiwal hypu...@gmail.com wrote: Hi, Is there any one from community can help me to solve this issue...?? Thanks, Punit On Tue, Mar 17, 2015 at 12:52 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi, I am facing one strange issue with ovirt/glusterfsstill didn't find this issue is related with glusterfs or Ovirt Ovirt :- 3.5.1 Glusterfs :- 3.6.1 Host :- 4 Hosts (Compute+ Storage)...each server has 24 bricks Guest VM :- more then 100 Issue :- When i deploy this cluster first time..it work well for me(all the guest VM created and running successfully)but suddenly one day my one of the host node rebooted and none of the VM can boot up now...and failed with the following error Bad Volume Specification VMId :- d877313c18d9783ca09b62acf5588048 VDSM Logs :- http://ur1.ca/jxabi you've got timeouts while accessing storage…so I guess something got messed up on reboot, it may also be just a gluster misconfiguration… Engine Logs :- http://ur1.ca/jxabv [root@cpu01 ~]# vdsClient -s 0 getVolumeInfo e732a82f-bae9-4368-8b98-dedc1c3814de 0002-0002-0002-0002-0145 6d123509-6867-45cf-83a2-6d679b77d3c5 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 status = OK domain = e732a82f-bae9-4368-8b98-dedc1c3814de capacity = 21474836480 voltype = LEAF description = parent = ---- format = RAW image = 6d123509-6867-45cf-83a2-6d679b77d3c5 uuid = 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 disktype = 2 legality = LEGAL mtime = 0 apparentsize = 21474836480 truesize = 4562972672 type = SPARSE children = [] pool = ctime = 1422676305 - I opened same thread earlier but didn't get any perfect answers to solve this issue..so i reopen it... https://www.mail-archive.com/users@ovirt.org/msg25011.html Thanks, Punit ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Joop, No split brainbut i have find some disconnecting error in the brick logs :- --- [2015-03-19 09:47:38.201769] I [login.c:82:gf_auth] 0-auth/login: allowed user names: 6ba6d773-cf70-4ba9-98d3-d2e31bcbb14c [2015-03-19 09:47:38.201819] I [server-handshake.c:585:server_setvolume] 0-ds01-server: accepted client from cpu01-13039-2015/03/19-09:47:37:502523-ds01-client-0-0-0 (version: 3.6.1) [2015-03-19 09:47:38.243512] I [server.c:518:server_rpc_notify] 0-ds01-server: disconnecting connection from cpu01-13039-2015/03/19-09:47:37:502523-ds01-client-0-0-0 [2015-03-19 09:47:38.243579] I [client_t.c:417:gf_client_unref] 0-ds01-server: Shutting down connection cpu01-13039-2015/03/19-09:47:37:502523-ds01-client-0-0-0 - On Thu, Mar 19, 2015 at 5:42 PM, Joop jvdw...@xs4all.nl wrote: Please keep it on the list. On 19-3-2015 10:10, Punit Dambiwal wrote: Hi Joop, How i can check the split-brain or not ???i already reblance the storage nodes and also run the heal command for the consistency gluster volume heal YourVolume info split-brain Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Michal, The Storage domain is up and running and mounted on all the host nodes...as i updated before that it was working perfectly before but just after reboot can not make the VM poweron... [image: Inline image 1] [image: Inline image 2] [root@cpu01 log]# gluster volume info Volume Name: ds01 Type: Distributed-Replicate Volume ID: 369d3fdc-c8eb-46b7-a33e-0a49f2451ff6 Status: Started Number of Bricks: 48 x 2 = 96 Transport-type: tcp Bricks: Brick1: cpu01:/bricks/1/vol1 Brick2: cpu02:/bricks/1/vol1 Brick3: cpu03:/bricks/1/vol1 Brick4: cpu04:/bricks/1/vol1 Brick5: cpu01:/bricks/2/vol1 Brick6: cpu02:/bricks/2/vol1 Brick7: cpu03:/bricks/2/vol1 Brick8: cpu04:/bricks/2/vol1 Brick9: cpu01:/bricks/3/vol1 Brick10: cpu02:/bricks/3/vol1 Brick11: cpu03:/bricks/3/vol1 Brick12: cpu04:/bricks/3/vol1 Brick13: cpu01:/bricks/4/vol1 Brick14: cpu02:/bricks/4/vol1 Brick15: cpu03:/bricks/4/vol1 Brick16: cpu04:/bricks/4/vol1 Brick17: cpu01:/bricks/5/vol1 Brick18: cpu02:/bricks/5/vol1 Brick19: cpu03:/bricks/5/vol1 Brick20: cpu04:/bricks/5/vol1 Brick21: cpu01:/bricks/6/vol1 Brick22: cpu02:/bricks/6/vol1 Brick23: cpu03:/bricks/6/vol1 Brick24: cpu04:/bricks/6/vol1 Brick25: cpu01:/bricks/7/vol1 Brick26: cpu02:/bricks/7/vol1 Brick27: cpu03:/bricks/7/vol1 Brick28: cpu04:/bricks/7/vol1 Brick29: cpu01:/bricks/8/vol1 Brick30: cpu02:/bricks/8/vol1 Brick31: cpu03:/bricks/8/vol1 Brick32: cpu04:/bricks/8/vol1 Brick33: cpu01:/bricks/9/vol1 Brick34: cpu02:/bricks/9/vol1 Brick35: cpu03:/bricks/9/vol1 Brick36: cpu04:/bricks/9/vol1 Brick37: cpu01:/bricks/10/vol1 Brick38: cpu02:/bricks/10/vol1 Brick39: cpu03:/bricks/10/vol1 Brick40: cpu04:/bricks/10/vol1 Brick41: cpu01:/bricks/11/vol1 Brick42: cpu02:/bricks/11/vol1 Brick43: cpu03:/bricks/11/vol1 Brick44: cpu04:/bricks/11/vol1 Brick45: cpu01:/bricks/12/vol1 Brick46: cpu02:/bricks/12/vol1 Brick47: cpu03:/bricks/12/vol1 Brick48: cpu04:/bricks/12/vol1 Brick49: cpu01:/bricks/13/vol1 Brick50: cpu02:/bricks/13/vol1 Brick51: cpu03:/bricks/13/vol1 Brick52: cpu04:/bricks/13/vol1 Brick53: cpu01:/bricks/14/vol1 Brick54: cpu02:/bricks/14/vol1 Brick55: cpu03:/bricks/14/vol1 Brick56: cpu04:/bricks/14/vol1 Brick57: cpu01:/bricks/15/vol1 Brick58: cpu02:/bricks/15/vol1 Brick59: cpu03:/bricks/15/vol1 Brick60: cpu04:/bricks/15/vol1 Brick61: cpu01:/bricks/16/vol1 Brick62: cpu02:/bricks/16/vol1 Brick63: cpu03:/bricks/16/vol1 Brick64: cpu04:/bricks/16/vol1 Brick65: cpu01:/bricks/17/vol1 Brick66: cpu02:/bricks/17/vol1 Brick67: cpu03:/bricks/17/vol1 Brick68: cpu04:/bricks/17/vol1 Brick69: cpu01:/bricks/18/vol1 Brick70: cpu02:/bricks/18/vol1 Brick71: cpu03:/bricks/18/vol1 Brick72: cpu04:/bricks/18/vol1 Brick73: cpu01:/bricks/19/vol1 Brick74: cpu02:/bricks/19/vol1 Brick75: cpu03:/bricks/19/vol1 Brick76: cpu04:/bricks/19/vol1 Brick77: cpu01:/bricks/20/vol1 Brick78: cpu02:/bricks/20/vol1 Brick79: cpu03:/bricks/20/vol1 Brick80: cpu04:/bricks/20/vol1 Brick81: cpu01:/bricks/21/vol1 Brick82: cpu02:/bricks/21/vol1 Brick83: cpu03:/bricks/21/vol1 Brick84: cpu04:/bricks/21/vol1 Brick85: cpu01:/bricks/22/vol1 Brick86: cpu02:/bricks/22/vol1 Brick87: cpu03:/bricks/22/vol1 Brick88: cpu04:/bricks/22/vol1 Brick89: cpu01:/bricks/23/vol1 Brick90: cpu02:/bricks/23/vol1 Brick91: cpu03:/bricks/23/vol1 Brick92: cpu04:/bricks/23/vol1 Brick93: cpu01:/bricks/24/vol1 Brick94: cpu02:/bricks/24/vol1 Brick95: cpu03:/bricks/24/vol1 Brick96: cpu04:/bricks/24/vol1 Options Reconfigured: diagnostics.count-fop-hits: on diagnostics.latency-measurement: on nfs.disable: on user.cifs: enable auth.allow: 10.10.0.* performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.stat-prefetch: off cluster.eager-lock: enable network.remote-dio: enable cluster.quorum-type: auto cluster.server-quorum-type: server storage.owner-uid: 36 storage.owner-gid: 36 server.allow-insecure: on network.ping-timeout: 100 [root@cpu01 log]# - [root@cpu01 log]# gluster volume status Status of volume: ds01 Gluster process PortOnline Pid -- Brick cpu01:/bricks/1/vol1 49152 Y 33474 Brick cpu02:/bricks/1/vol1 49152 Y 40717 Brick cpu03:/bricks/1/vol1 49152 Y 18080 Brick cpu04:/bricks/1/vol1 49152 Y 40447 Brick cpu01:/bricks/2/vol1 49153 Y 33481 Brick cpu02:/bricks/2/vol1 49153 Y 40724 Brick cpu03:/bricks/2/vol1 49153 Y 18086 Brick cpu04:/bricks/2/vol1 49153 Y 40453 Brick cpu01:/bricks/3/vol1 49154 Y 33489 Brick cpu02:/bricks/3/vol1 49154 Y 40731 Brick cpu03:/bricks/3/vol1 49154 Y 18097 Brick cpu04:/bricks/3/vol1 49154 Y 40460
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Joop, How i can check the split-brain or not ???i already reblance the storage nodes and also run the heal command for the consistency On Thu, Mar 19, 2015 at 4:36 PM, Joop jvdw...@xs4all.nl wrote: On 19-3-2015 9:25, Punit Dambiwal wrote: Hi Michal, The Storage domain is up and running and mounted on all the host nodes...as i updated before that it was working perfectly before but just after reboot can not make the VM poweron... Did you check if you're suffering from a split-brain situation? My test setup sometimes does when not being careful when updating glusterfs/ovirt. Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Please keep it on the list. On 19-3-2015 10:10, Punit Dambiwal wrote: Hi Joop, How i can check the split-brain or not ???i already reblance the storage nodes and also run the heal command for the consistency gluster volume heal YourVolume info split-brain Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
On 19-3-2015 9:25, Punit Dambiwal wrote: Hi Michal, The Storage domain is up and running and mounted on all the host nodes...as i updated before that it was working perfectly before but just after reboot can not make the VM poweron... Did you check if you're suffering from a split-brain situation? My test setup sometimes does when not being careful when updating glusterfs/ovirt. Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Michal, Would you mind to let me know the possible messedup things...i will check and try to resolve itstill i am communicating gluster community to resolve this issue... But in the ovirtgluster setup is quite straightso how come it will be messedup with reboot ?? if it can be messedup with reboot then it seems not good and stable technology for the production storage Thanks, Punit On Wed, Mar 18, 2015 at 3:51 PM, Michal Skrivanek michal.skriva...@redhat.com wrote: On Mar 18, 2015, at 03:33 , Punit Dambiwal hypu...@gmail.com wrote: Hi, Is there any one from community can help me to solve this issue...?? Thanks, Punit On Tue, Mar 17, 2015 at 12:52 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi, I am facing one strange issue with ovirt/glusterfsstill didn't find this issue is related with glusterfs or Ovirt Ovirt :- 3.5.1 Glusterfs :- 3.6.1 Host :- 4 Hosts (Compute+ Storage)...each server has 24 bricks Guest VM :- more then 100 Issue :- When i deploy this cluster first time..it work well for me(all the guest VM created and running successfully)but suddenly one day my one of the host node rebooted and none of the VM can boot up now...and failed with the following error Bad Volume Specification VMId :- d877313c18d9783ca09b62acf5588048 VDSM Logs :- http://ur1.ca/jxabi you've got timeouts while accessing storage…so I guess something got messed up on reboot, it may also be just a gluster misconfiguration… Engine Logs :- http://ur1.ca/jxabv [root@cpu01 ~]# vdsClient -s 0 getVolumeInfo e732a82f-bae9-4368-8b98-dedc1c3814de 0002-0002-0002-0002-0145 6d123509-6867-45cf-83a2-6d679b77d3c5 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 status = OK domain = e732a82f-bae9-4368-8b98-dedc1c3814de capacity = 21474836480 voltype = LEAF description = parent = ---- format = RAW image = 6d123509-6867-45cf-83a2-6d679b77d3c5 uuid = 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 disktype = 2 legality = LEGAL mtime = 0 apparentsize = 21474836480 truesize = 4562972672 type = SPARSE children = [] pool = ctime = 1422676305 - I opened same thread earlier but didn't get any perfect answers to solve this issue..so i reopen it... https://www.mail-archive.com/users@ovirt.org/msg25011.html Thanks, Punit ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
On Mar 18, 2015, at 03:33 , Punit Dambiwal hypu...@gmail.com wrote: Hi, Is there any one from community can help me to solve this issue...?? Thanks, Punit On Tue, Mar 17, 2015 at 12:52 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi, I am facing one strange issue with ovirt/glusterfsstill didn't find this issue is related with glusterfs or Ovirt Ovirt :- 3.5.1 Glusterfs :- 3.6.1 Host :- 4 Hosts (Compute+ Storage)...each server has 24 bricks Guest VM :- more then 100 Issue :- When i deploy this cluster first time..it work well for me(all the guest VM created and running successfully)but suddenly one day my one of the host node rebooted and none of the VM can boot up now...and failed with the following error Bad Volume Specification VMId :- d877313c18d9783ca09b62acf5588048 VDSM Logs :- http://ur1.ca/jxabi you've got timeouts while accessing storage…so I guess something got messed up on reboot, it may also be just a gluster misconfiguration… Engine Logs :- http://ur1.ca/jxabv [root@cpu01 ~]# vdsClient -s 0 getVolumeInfo e732a82f-bae9-4368-8b98-dedc1c3814de 0002-0002-0002-0002-0145 6d123509-6867-45cf-83a2-6d679b77d3c5 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 status = OK domain = e732a82f-bae9-4368-8b98-dedc1c3814de capacity = 21474836480 voltype = LEAF description = parent = ---- format = RAW image = 6d123509-6867-45cf-83a2-6d679b77d3c5 uuid = 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 disktype = 2 legality = LEGAL mtime = 0 apparentsize = 21474836480 truesize = 4562972672 type = SPARSE children = [] pool = ctime = 1422676305 - I opened same thread earlier but didn't get any perfect answers to solve this issue..so i reopen it... https://www.mail-archive.com/users@ovirt.org/msg25011.html Thanks, Punit ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi All, Is there any one have any idea about this problem...it seems it's bug either in Ovirt or Glusterfs...that's why no one has the idea about itplease correct me if i am wrong Thanks, Punit On Wed, Mar 18, 2015 at 5:05 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi Michal, Would you mind to let me know the possible messedup things...i will check and try to resolve itstill i am communicating gluster community to resolve this issue... But in the ovirtgluster setup is quite straightso how come it will be messedup with reboot ?? if it can be messedup with reboot then it seems not good and stable technology for the production storage Thanks, Punit On Wed, Mar 18, 2015 at 3:51 PM, Michal Skrivanek michal.skriva...@redhat.com wrote: On Mar 18, 2015, at 03:33 , Punit Dambiwal hypu...@gmail.com wrote: Hi, Is there any one from community can help me to solve this issue...?? Thanks, Punit On Tue, Mar 17, 2015 at 12:52 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi, I am facing one strange issue with ovirt/glusterfsstill didn't find this issue is related with glusterfs or Ovirt Ovirt :- 3.5.1 Glusterfs :- 3.6.1 Host :- 4 Hosts (Compute+ Storage)...each server has 24 bricks Guest VM :- more then 100 Issue :- When i deploy this cluster first time..it work well for me(all the guest VM created and running successfully)but suddenly one day my one of the host node rebooted and none of the VM can boot up now...and failed with the following error Bad Volume Specification VMId :- d877313c18d9783ca09b62acf5588048 VDSM Logs :- http://ur1.ca/jxabi you've got timeouts while accessing storage…so I guess something got messed up on reboot, it may also be just a gluster misconfiguration… Engine Logs :- http://ur1.ca/jxabv [root@cpu01 ~]# vdsClient -s 0 getVolumeInfo e732a82f-bae9-4368-8b98-dedc1c3814de 0002-0002-0002-0002-0145 6d123509-6867-45cf-83a2-6d679b77d3c5 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 status = OK domain = e732a82f-bae9-4368-8b98-dedc1c3814de capacity = 21474836480 voltype = LEAF description = parent = ---- format = RAW image = 6d123509-6867-45cf-83a2-6d679b77d3c5 uuid = 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 disktype = 2 legality = LEGAL mtime = 0 apparentsize = 21474836480 truesize = 4562972672 type = SPARSE children = [] pool = ctime = 1422676305 - I opened same thread earlier but didn't get any perfect answers to solve this issue..so i reopen it... https://www.mail-archive.com/users@ovirt.org/msg25011.html Thanks, Punit ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi, Is there any one from community can help me to solve this issue...?? Thanks, Punit On Tue, Mar 17, 2015 at 12:52 PM, Punit Dambiwal hypu...@gmail.com wrote: Hi, I am facing one strange issue with ovirt/glusterfsstill didn't find this issue is related with glusterfs or Ovirt Ovirt :- 3.5.1 Glusterfs :- 3.6.1 Host :- 4 Hosts (Compute+ Storage)...each server has 24 bricks Guest VM :- more then 100 Issue :- When i deploy this cluster first time..it work well for me(all the guest VM created and running successfully)but suddenly one day my one of the host node rebooted and none of the VM can boot up now...and failed with the following error Bad Volume Specification VMId :- d877313c18d9783ca09b62acf5588048 VDSM Logs :- http://ur1.ca/jxabi Engine Logs :- http://ur1.ca/jxabv [root@cpu01 ~]# vdsClient -s 0 getVolumeInfo e732a82f-bae9-4368-8b98-dedc1c3814de 0002-0002-0002-0002-0145 6d123509-6867-45cf-83a2-6d679b77d3c5 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 status = OK domain = e732a82f-bae9-4368-8b98-dedc1c3814de capacity = 21474836480 voltype = LEAF description = parent = ---- format = RAW image = 6d123509-6867-45cf-83a2-6d679b77d3c5 uuid = 9030bb43-6bc9-462f-a1b9-f6d5a02fb180 disktype = 2 legality = LEGAL mtime = 0 apparentsize = 21474836480 truesize = 4562972672 type = SPARSE children = [] pool = ctime = 1422676305 - I opened same thread earlier but didn't get any perfect answers to solve this issue..so i reopen it... https://www.mail-archive.com/users@ovirt.org/msg25011.html Thanks, Punit ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
- Original Message -
From: Vered Volansky ve...@redhat.com
To: Punit Dambiwal hypu...@gmail.com
Cc: users@ovirt.org
Sent: Monday, March 2, 2015 7:20:08 AM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, March 1, 2015 4:58:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Please find the below required details :-
hosts :- 8 Hosts
domains :- Internal
Do you mean local?
Seems like 'internal' refers to the authentication domain instead of storage
domain.
vms :- more then 500
statuses :- running and some are down
versions :-
Ovirt :- 3.5.1
Glusterfs :- 3.6.1
Earlier it was working fine but after reboot one of the storage
node...problem started
I don't understand this sentence.
What kind of storage is it?
and now i am not able to create any VM...each time it
throws the same error VM 2c810a8d40e1abf67aa6d94d430b9574 is down with
error. Exit message: Bad volume specification {'index': 0, 'iface':
'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder': '1', 'address':
{'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type': 'pci',
'function': '0x0'}, 'volumeID': '70951592-ddd3-460f-a1d0-942f197120d7',
'apparentsize': '21474836480', 'imageID':
'7247a929-6bc9-4267-9086-f643eeda7596', 'specParams': {}, 'readonly':
'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de', 'reqsize':
'0',
'deviceId': '7247a929-6bc9-4267-9086-f643eeda7596', 'truesize':
'888942592',
'poolID': '0002-0002-0002-0002-0145', 'device': 'disk',
'shared': 'false', 'propagateErrors': 'off', 'optional': 'false'}.
I still need logs in order to help out.
Thanks,
Punit
On Thu, Feb 26, 2015 at 2:19 PM, Vered Volansky ve...@redhat.com wrote:
Hi Punit,
Engine log does not contain the snippet you quoted before.
It does have an occurrence of the same issue with another vm, but with
almost
only logins and logout, making it, once again, impossible to understand the
context.
Please give me some information as to your environment -
hosts, domains, vms, statuses, versions,
I also need more context as to what actions you were performing before this
failure, statuses before and after this specific action, but also some
scenarion that led to this issue.
I would still need the logs of the relevant timeframe. Pleas verify that
what
you send next time is indeed the relevant logs.
Regards,
Vered
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Wednesday, February 25, 2015 2:15:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Yes... it's new VM...even some of the old vm those can run previousely
but
now can not run now...
On Wed, Feb 25, 2015 at 3:07 PM, Vered Volansky ve...@redhat.com
wrote:
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org
Sent: Wednesday, February 25, 2015 6:19:53 AM
Subject: [ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the
following
error :-
VM vm1 is down with error. Exit message: Bad volume specification
{'index':
0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder':
'1',
'address': {'slot': '0x07', 'bus': '0x00', 'domain': '0x',
'type':
'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID':
'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID':
'0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off',
'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Please send engine and vdsm logs, it's impossible to help you without
context.
What's the history of the VM you were unable to start?
Is it a new VM?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Please find the below required details :-
hosts :- 8 Hosts
domains :- Internal
vms :- more then 500
statuses :- running and some are down
versions :-
Ovirt :- 3.5.1
Glusterfs :- 3.6.1
Earlier it was working fine but after reboot one of the storage
node...problem started and now i am not able to create any VM...each time
it throws the same error VM 2c810a8d40e1abf67aa6d94d430b9574 is down with
error. Exit message: Bad volume specification {'index': 0, 'iface':
'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder': '1', 'address':
{'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type': 'pci',
'function': '0x0'}, 'volumeID': '70951592-ddd3-460f-a1d0-942f197120d7',
'apparentsize': '21474836480', 'imageID':
'7247a929-6bc9-4267-9086-f643eeda7596', 'specParams': {}, 'readonly':
'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de', 'reqsize':
'0', 'deviceId': '7247a929-6bc9-4267-9086-f643eeda7596', 'truesize':
'888942592', 'poolID': '0002-0002-0002-0002-0145', 'device':
'disk', 'shared': 'false', 'propagateErrors': 'off', 'optional': 'false'}.
Thanks,
Punit
On Thu, Feb 26, 2015 at 2:19 PM, Vered Volansky ve...@redhat.com wrote:
Hi Punit,
Engine log does not contain the snippet you quoted before.
It does have an occurrence of the same issue with another vm, but with
almost only logins and logout, making it, once again, impossible to
understand the context.
Please give me some information as to your environment -
hosts, domains, vms, statuses, versions,
I also need more context as to what actions you were performing before
this failure, statuses before and after this specific action, but also some
scenarion that led to this issue.
I would still need the logs of the relevant timeframe. Pleas verify that
what you send next time is indeed the relevant logs.
Regards,
Vered
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Wednesday, February 25, 2015 2:15:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Yes... it's new VM...even some of the old vm those can run previousely
but
now can not run now...
On Wed, Feb 25, 2015 at 3:07 PM, Vered Volansky ve...@redhat.com
wrote:
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org
Sent: Wednesday, February 25, 2015 6:19:53 AM
Subject: [ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the
following
error :-
VM vm1 is down with error. Exit message: Bad volume specification
{'index':
0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder':
'1',
'address': {'slot': '0x07', 'bus': '0x00', 'domain': '0x',
'type':
'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID':
'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID':
'0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off',
'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Please send engine and vdsm logs, it's impossible to help you without
context.
What's the history of the VM you were unable to start?
Is it a new VM?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, March 1, 2015 4:58:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Please find the below required details :-
hosts :- 8 Hosts
domains :- Internal
Do you mean local?
vms :- more then 500
statuses :- running and some are down
versions :-
Ovirt :- 3.5.1
Glusterfs :- 3.6.1
Earlier it was working fine but after reboot one of the storage
node...problem started
I don't understand this sentence.
What kind of storage is it?
and now i am not able to create any VM...each time it
throws the same error VM 2c810a8d40e1abf67aa6d94d430b9574 is down with
error. Exit message: Bad volume specification {'index': 0, 'iface':
'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder': '1', 'address':
{'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type': 'pci',
'function': '0x0'}, 'volumeID': '70951592-ddd3-460f-a1d0-942f197120d7',
'apparentsize': '21474836480', 'imageID':
'7247a929-6bc9-4267-9086-f643eeda7596', 'specParams': {}, 'readonly':
'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de', 'reqsize': '0',
'deviceId': '7247a929-6bc9-4267-9086-f643eeda7596', 'truesize': '888942592',
'poolID': '0002-0002-0002-0002-0145', 'device': 'disk',
'shared': 'false', 'propagateErrors': 'off', 'optional': 'false'}.
I still need logs in order to help out.
Thanks,
Punit
On Thu, Feb 26, 2015 at 2:19 PM, Vered Volansky ve...@redhat.com wrote:
Hi Punit,
Engine log does not contain the snippet you quoted before.
It does have an occurrence of the same issue with another vm, but with almost
only logins and logout, making it, once again, impossible to understand the
context.
Please give me some information as to your environment -
hosts, domains, vms, statuses, versions,
I also need more context as to what actions you were performing before this
failure, statuses before and after this specific action, but also some
scenarion that led to this issue.
I would still need the logs of the relevant timeframe. Pleas verify that what
you send next time is indeed the relevant logs.
Regards,
Vered
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Wednesday, February 25, 2015 2:15:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Yes... it's new VM...even some of the old vm those can run previousely but
now can not run now...
On Wed, Feb 25, 2015 at 3:07 PM, Vered Volansky ve...@redhat.com wrote:
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org
Sent: Wednesday, February 25, 2015 6:19:53 AM
Subject: [ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the
following
error :-
VM vm1 is down with error. Exit message: Bad volume specification
{'index':
0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder':
'1',
'address': {'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type':
'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID':
'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID':
'0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off',
'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Please send engine and vdsm logs, it's impossible to help you without
context.
What's the history of the VM you were unable to start?
Is it a new VM?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Punit,
Engine log does not contain the snippet you quoted before.
It does have an occurrence of the same issue with another vm, but with almost
only logins and logout, making it, once again, impossible to understand the
context.
Please give me some information as to your environment -
hosts, domains, vms, statuses, versions,
I also need more context as to what actions you were performing before this
failure, statuses before and after this specific action, but also some
scenarion that led to this issue.
I would still need the logs of the relevant timeframe. Pleas verify that what
you send next time is indeed the relevant logs.
Regards,
Vered
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: Vered Volansky ve...@redhat.com
Cc: users@ovirt.org
Sent: Wednesday, February 25, 2015 2:15:02 PM
Subject: Re: [ovirt-users] VM failed to start | Bad volume specification
Hi Vered,
Yes... it's new VM...even some of the old vm those can run previousely but
now can not run now...
On Wed, Feb 25, 2015 at 3:07 PM, Vered Volansky ve...@redhat.com wrote:
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org
Sent: Wednesday, February 25, 2015 6:19:53 AM
Subject: [ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the
following
error :-
VM vm1 is down with error. Exit message: Bad volume specification
{'index':
0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder': '1',
'address': {'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type':
'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID':
'0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off',
'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Please send engine and vdsm logs, it's impossible to help you without
context.
What's the history of the VM you were unable to start?
Is it a new VM?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM failed to start | Bad volume specification
- Original Message -
From: Punit Dambiwal hypu...@gmail.com
To: users@ovirt.org
Sent: Wednesday, February 25, 2015 6:19:53 AM
Subject: [ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the following
error :-
VM vm1 is down with error. Exit message: Bad volume specification {'index':
0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw', 'bootOrder': '1',
'address': {'slot': '0x07', 'bus': '0x00', 'domain': '0x', 'type':
'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID': '0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Please send engine and vdsm logs, it's impossible to help you without context.
What's the history of the VM you were unable to start?
Is it a new VM?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] VM failed to start | Bad volume specification
Hi,
I try to start the VM but it's failed to start...and through the following
error :-
VM vm1 is down with error. Exit message: Bad volume specification
{'index': 0, 'iface': 'virtio', 'type': 'disk', 'format': 'raw',
'bootOrder': '1', 'address': {'slot': '0x07', 'bus': '0x00', 'domain':
'0x', 'type': 'pci', 'function': '0x0'}, 'volumeID':
'60c73bf0-d190-420b-917c-04aa00e52f10', 'apparentsize': '1073741824',
'imageID': '8ca66096-bd47-460d-9e09-2966e45b471b', 'specParams': {},
'readonly': 'false', 'domainID': 'e732a82f-bae9-4368-8b98-dedc1c3814de',
'reqsize': '0', 'deviceId': '8ca66096-bd47-460d-9e09-2966e45b471b',
'truesize': '1054048256', 'poolID': '0002-0002-0002-0002-0145',
'device': 'disk', 'shared': 'false', 'propagateErrors': 'off', 'optional':
'false'}.
Please help me to solve this issue
Thanks,
Punit
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
