[Gluster-users] Maintainance mode for bricks

[Tejas N. Bhise]

ok .. so if I understand correctly, you want to *replace* an existing export by a new export on a new machine, while keeping all data online and keep the source export of the replace in read mode so it can be copied off. Are there other processes also doing a read off the read only export/sub-volume, besides the rsync ?

Regards,
Tejas.

----- Original Message -----
From: "Fred Stober" <fred.stober at kit.edu>
To: "Tejas N. Bhise" <tejas at gluster.com>
Cc: gluster-users at gluster.org
Sent: Wednesday, April 14, 2010 5:50:33 PM
Subject: Re: [Gluster-users] Maintainance mode for bricks

On Wednesday 14 April 2010, Tejas N. Bhise wrote:
> Fred,
>
> Would you like to tell us more about the use case ? Like why would you want
> to do this ? If we take a brick out, it would not be possible to get it
> back in ( with the existing data ).

Ok, here is our use case:
We have a small test system running on 3 file servers. cluster/distribute is 
used to give a flat view of the file servers. Now have the problem that one 
file server is going to be replaced with a larger one. Therefore we want to 
put the old file server into read only mode to rsync the files to the new 
server. Unfortunately this will take ~2days. During this time it would be 
nice to keep the glusterfs in read/write mode.

If I understand it correctly, I should be able to use "lookup-unhashed" to 
reintegrate the new fileserver in the existing file system, when we switch 
off the old server.

Cheers,
Fred

-- 
Fred-Markus Stober
stober at cern.ch
Karlsruhe Institute of Technology