Re: [ovirt-users] Missing dom_md/ids file

2016-02-19 Thread Cameron Christensen
I was able to recreate the dom_md/ids file using the provided
instructions. The data center and gluster storage are active. Thank
you.
Cameron
On Sat, 2016-02-20 at 00:24 +0200, Nir Soffer wrote:
> On Fri, Feb 19, 2016 at 11:54 PM, Cameron Christensen
>  wrote:
> > I cannot put the gluster domain into maintenance. I'm believe this
> > is
> > because the data center has a status of Non responsive (because a
> > host
> > cannot connect to storage or start SPM). The only option available
> > on the
> > gluster storage is activate. I have put all the hosts into
> > maintenance. Is
> > this enough to continue with the initialize lockspace step?
> 
> Yes, if all hosts are in maintenance, no host will access the gluster
> storage domain, and you can repair is safely.
> 
> > 
> > On Fri, 2016-02-19 at 23:34 +0200, Nir Soffer wrote:
> > 
> > On Fri, Feb 19, 2016 at 10:58 PM, Cameron Christensen
> >  wrote:
> > 
> > Hello,
> > 
> > I am using glusterfs storage and ran into a split-brain issue. One
> > of the
> > file affected by split-brain was dom_md/ids. In attempts to fix the
> > split-brain issue I deleted the dom_md/ids file. Is there a method
> > to
> > recreate or reconstruct this file?
> > 
> > 
> > You can do this:
> > 
> > 1. Put the gluster domain to maintenance (via engine)
> > 
> > No host should access it while you reconstruct the ids file
> > 
> > 2. Mount the gluster volume manually
> > 
> > mkdir repair
> > mount -t glusterfs :/ repair/
> > 
> > 3. Create the file:
> > 
> > touch repair//dom_md/ids
> > 
> > 4. Initialize the lockspace
> > 
> > sanlock direct init -s :0:repair//dom_md/ids:0
> > 
> > 5. Unmount the gluster volume
> > 
> > umount repair
> > 
> > 6. Activate the gluster domain (via engine)
> > 
> > The domain should become active after a while.
> > 
> > 
> > David: can you confirm this is the best way to reconstruct the ids
> > file?
> > 
> > Nir

signature.asc
Description: This is a digitally signed message part
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Missing dom_md/ids file

2016-02-19 Thread Nir Soffer
On Fri, Feb 19, 2016 at 11:54 PM, Cameron Christensen
 wrote:
> I cannot put the gluster domain into maintenance. I'm believe this is
> because the data center has a status of Non responsive (because a host
> cannot connect to storage or start SPM). The only option available on the
> gluster storage is activate. I have put all the hosts into maintenance. Is
> this enough to continue with the initialize lockspace step?

Yes, if all hosts are in maintenance, no host will access the gluster
storage domain, and you can repair is safely.

>
> On Fri, 2016-02-19 at 23:34 +0200, Nir Soffer wrote:
>
> On Fri, Feb 19, 2016 at 10:58 PM, Cameron Christensen
>  wrote:
>
> Hello,
>
> I am using glusterfs storage and ran into a split-brain issue. One of the
> file affected by split-brain was dom_md/ids. In attempts to fix the
> split-brain issue I deleted the dom_md/ids file. Is there a method to
> recreate or reconstruct this file?
>
>
> You can do this:
>
> 1. Put the gluster domain to maintenance (via engine)
>
> No host should access it while you reconstruct the ids file
>
> 2. Mount the gluster volume manually
>
> mkdir repair
> mount -t glusterfs :/ repair/
>
> 3. Create the file:
>
> touch repair//dom_md/ids
>
> 4. Initialize the lockspace
>
> sanlock direct init -s :0:repair//dom_md/ids:0
>
> 5. Unmount the gluster volume
>
> umount repair
>
> 6. Activate the gluster domain (via engine)
>
> The domain should become active after a while.
>
>
> David: can you confirm this is the best way to reconstruct the ids file?
>
> Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Missing dom_md/ids file

2016-02-19 Thread Cameron Christensen
I cannot put the gluster domain into maintenance. I'm believe this is
because the data center has a status of Non responsive (because a host
cannot connect to storage or start SPM). The only option available on
the gluster storage is activate. I have put all the hosts into
maintenance. Is this enough to continue with the initialize lockspace
step?
On Fri, 2016-02-19 at 23:34 +0200, Nir Soffer wrote:
> On Fri, Feb 19, 2016 at 10:58 PM, Cameron Christensen
>  wrote:
> > Hello,
> > 
> > I am using glusterfs storage and ran into a split-brain issue. One
> > of the
> > file affected by split-brain was dom_md/ids. In attempts to fix the
> > split-brain issue I deleted the dom_md/ids file. Is there a method
> > to
> > recreate or reconstruct this file?
> 
> You can do this:
> 
> 1. Put the gluster domain to maintenance (via engine)
> 
> No host should access it while you reconstruct the ids file
> 
> 2. Mount the gluster volume manually
> 
> mkdir repair
> mount -t glusterfs :/ repair/
> 
> 3. Create the file:
> 
> touch repair//dom_md/ids
> 
> 4. Initialize the lockspace
> 
> sanlock direct init -s :0:repair//dom_md/ids:0
> 
> 5. Unmount the gluster volume
> 
> umount repair
> 
> 6. Activate the gluster domain (via engine)
> 
> The domain should become active after a while.
> 
> 
> David: can you confirm this is the best way to reconstruct the ids
> file?
> 
> Nir

signature.asc
Description: This is a digitally signed message part
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Missing dom_md/ids file

2016-02-19 Thread David Teigland
On Fri, Feb 19, 2016 at 11:34:28PM +0200, Nir Soffer wrote:
> On Fri, Feb 19, 2016 at 10:58 PM, Cameron Christensen
>  wrote:
> > Hello,
> >
> > I am using glusterfs storage and ran into a split-brain issue. One of the
> > file affected by split-brain was dom_md/ids. In attempts to fix the
> > split-brain issue I deleted the dom_md/ids file. Is there a method to
> > recreate or reconstruct this file?
> 
> You can do this:
> 
> 1. Put the gluster domain to maintenance (via engine)
> 
> No host should access it while you reconstruct the ids file
> 
> 2. Mount the gluster volume manually
> 
> mkdir repair
> mount -t glusterfs :/ repair/
> 
> 3. Create the file:
> 
> touch repair//dom_md/ids
> 
> 4. Initialize the lockspace
> 
> sanlock direct init -s :0:repair//dom_md/ids:0
> 
> 5. Unmount the gluster volume
> 
> umount repair
> 
> 6. Activate the gluster domain (via engine)
> 
> The domain should become active after a while.
> 
> 
> David: can you confirm this is the best way to reconstruct the ids file?

Yes, that looks right.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Missing dom_md/ids file

2016-02-19 Thread Nir Soffer
On Fri, Feb 19, 2016 at 10:58 PM, Cameron Christensen
 wrote:
> Hello,
>
> I am using glusterfs storage and ran into a split-brain issue. One of the
> file affected by split-brain was dom_md/ids. In attempts to fix the
> split-brain issue I deleted the dom_md/ids file. Is there a method to
> recreate or reconstruct this file?

You can do this:

1. Put the gluster domain to maintenance (via engine)

No host should access it while you reconstruct the ids file

2. Mount the gluster volume manually

mkdir repair
mount -t glusterfs :/ repair/

3. Create the file:

touch repair//dom_md/ids

4. Initialize the lockspace

sanlock direct init -s :0:repair//dom_md/ids:0

5. Unmount the gluster volume

umount repair

6. Activate the gluster domain (via engine)

The domain should become active after a while.


David: can you confirm this is the best way to reconstruct the ids file?

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Missing dom_md/ids file

2016-02-19 Thread Cameron Christensen
Hello,

I am using glusterfs storage and ran into a split-brain issue. One of
the file affected by split-brain was dom_md/ids. In attempts to fix the
split-brain issue I deleted the dom_md/ids file. Is there a method to
recreate or reconstruct this file?

Thanks,

Cameron

signature.asc
Description: This is a digitally signed message part
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users