Re: [ovirt-users] moving disk failed.. remained locked

2017-02-23 Thread David Teigland
On Thu, Feb 23, 2017 at 08:11:50PM +0200, Nir Soffer wrote: > > [g.cecchi@ovmsrv05 ~]$ sudo sanlock client renewal -s > > 922b5269-ab56-4c4d-838f-49d33427e2ab > > timestamp=1207533 read_ms=2 write_ms=0 next_timeouts=0 next_errors=0 > > timestamp=1207554 read_ms=2 write_ms=0 next_timeouts=0

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-23 Thread Nir Soffer
On Wed, Feb 22, 2017 at 12:20 PM, Gianluca Cecchi wrote: > On Wed, Feb 22, 2017 at 10:59 AM, Nir Soffer wrote: >> >> >> >> Lesson, use only storage without problems ;-) > > > hopefully... ;-) > >> >> >> Can you share the output of: >> >> >> >>

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Gianluca Cecchi
On Wed, Feb 22, 2017 at 10:59 AM, Nir Soffer wrote: > > > Lesson, use only storage without problems ;-) > hopefully... ;-) > >> Can you share the output of: > >> > >> sanlock client renewal -s 900b1853-e192-4661-a0f9-7c7c396f6f49 > > > > > > No, the storage domain has

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Nir Soffer
On Wed, Feb 22, 2017 at 11:45 AM, Gianluca Cecchi wrote: > On Wed, Feb 22, 2017 at 9:56 AM, Nir Soffer wrote: >> >> >> >> Gianluca, what is domain 900b1853-e192-4661-a0f9-7c7c396f6f49? >> >> is this the domain you are migrating to in the same time?

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Gianluca Cecchi
On Wed, Feb 22, 2017 at 9:56 AM, Nir Soffer wrote: > > > Gianluca, what is domain 900b1853-e192-4661-a0f9-7c7c396f6f49? > > is this the domain you are migrating to in the same time? > That was the id of the storage domain created on the LUN with problems at storage array

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Nir Soffer
On Wed, Feb 22, 2017 at 10:32 AM, Nir Soffer wrote: > On Wed, Feb 22, 2017 at 10:31 AM, Nir Soffer wrote: >> On Mon, Feb 20, 2017 at 4:49 PM, Gianluca Cecchi >> wrote: >>> Hello, >>> I'm trying to move a disk from one storage

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Gianluca Cecchi
On Wed, Feb 22, 2017 at 9:32 AM, Nir Soffer wrote: > On Wed, Feb 22, 2017 at 10:31 AM, Nir Soffer wrote: > > > > > This means that sanlock could not initialize a lease in the new volume > created > > for the snapshot. > > > > Can you attach sanlock.log? >

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Nir Soffer
On Wed, Feb 22, 2017 at 10:31 AM, Nir Soffer wrote: > On Mon, Feb 20, 2017 at 4:49 PM, Gianluca Cecchi > wrote: >> Hello, >> I'm trying to move a disk from one storage domain A to another B in oVirt >> 4.1 >> The corresponding VM is powered on in

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-22 Thread Nir Soffer
On Mon, Feb 20, 2017 at 4:49 PM, Gianluca Cecchi wrote: > Hello, > I'm trying to move a disk from one storage domain A to another B in oVirt > 4.1 > The corresponding VM is powered on in the mean time > > When executing the action, there was already in place a disk move

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Fred Rolland
I opened a bug for the task cleaner issue: https://bugzilla.redhat.com/show_bug.cgi?id=1425705 Did you managed to copy the disk ? For better tracking, can you open a bug with the details and logs ? Thanks, Fred On Tue, Feb 21, 2017 at 3:36 PM, Gianluca Cecchi wrote:

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Gianluca Cecchi
The problem itself seems related with snapshot and with the disk (430Gb in size). Failed to complete snapshot 'test3' creation for VM 'dbatest6'. VDSM ovmsrv07 command HSMGetAllTasksStatusesVDS failed: Could not acquire resource. Probably resource factory threw an exception.: () Snapshot 'test3'

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Gianluca Cecchi
On Tue, Feb 21, 2017 at 11:47 AM, Fred Rolland wrote: > Add before the command (with your db password): PGPASSWORD=engine > > for example: > PGPASSWORD=engine /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -T > > PGPASSWORD=engine

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Fred Rolland
Add before the command (with your db password): PGPASSWORD=engine for example: PGPASSWORD=engine /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -T PGPASSWORD=engine /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t disk -u engine -q On Tue, Feb 21, 2017 at 12:23 PM, Gianluca

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Gianluca Cecchi
I see here utilitues: https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities/ In particular unlock_entity.sh that should be of help in my case, as I see here: http://lists.ovirt.org/pipermail/users/2015-April/032576.html New path in 4.1 is now

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-21 Thread Gianluca Cecchi
On Tue, Feb 21, 2017 at 7:01 AM, Gianluca Cecchi wrote: > On Mon, Feb 20, 2017 at 10:51 PM, Gianluca Cecchi < > gianluca.cec...@gmail.com> wrote: > >> On Mon, Feb 20, 2017 at 8:46 PM, Fred Rolland >> wrote: >> >>> Can you please send the whole

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-20 Thread Gianluca Cecchi
On Mon, Feb 20, 2017 at 10:51 PM, Gianluca Cecchi wrote: > On Mon, Feb 20, 2017 at 8:46 PM, Fred Rolland wrote: > >> Can you please send the whole logs ? (Engine, vdsm and sanlock) >> >> > vdsm.log.1.xz: >

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-20 Thread Gianluca Cecchi
On Mon, Feb 20, 2017 at 8:46 PM, Fred Rolland wrote: > Can you please send the whole logs ? (Engine, vdsm and sanlock) > > vdsm.log.1.xz: https://drive.google.com/file/d/0BwoPbcrMv8mvWTViWEUtNjRtLTg/view?usp=sharing sanlock.log

Re: [ovirt-users] moving disk failed.. remained locked

2017-02-20 Thread Fred Rolland
Can you please send the whole logs ? (Engine, vdsm and sanlock) On Mon, Feb 20, 2017 at 4:49 PM, Gianluca Cecchi wrote: > Hello, > I'm trying to move a disk from one storage domain A to another B in oVirt > 4.1 > The corresponding VM is powered on in the mean time > >