search for: thin_pool

On Fri, Jun 26, 2015 at 10:51 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: >> , or alternatively making the LVs >> redundant after install is a single command (each) and you can choose >> whether it should be mere mirroring or some MD manged RAID level (modulo >> the LVM RAID MD monitoring issue). > > > I hadn't realized that. That's an

...ost 3 drives in a RAID6 array and the structure of all of the LVM pools and nodes was lost. This array was 1/2 of a redundant (replica 2) gluster config (will be adding additional 3rd soon for split brain/redundancy with failure issues). The failed drives were replaced, the array rebuilt, all the thin_pools and thin_volumes recreated, LUKS recreated and now the data from the other half has been bulk copied to the rebuilt mirror locations. It's time to bring gluster back online. The original gluster data was not part of the raid failure and all the names are the same (except one LV, thin_lv, and...

...00TB of storage was scrambled. This array was 1/2 of a redundant (replica 2) gluster config (will be adding additional 3rd soon for split brain/redundancy with failure issues) so the data was not lost but just running in a degraded mode. The failed drives were replaced, the array rebuilt, all the thin_pools and thin_volumes recreated, LUKS recreated and now the data from the other half has been bulk copied to the rebuilt mirror locations - along with all the .glusterfs space - not sure if that should be copied over or not. It's time to bring gluster back online. The original gluster data was not...