Minor buglet (?) in mogtool

[Justin Azoff]

Gavin Brebner wrote:
> I've created my first test mogilefs system, and decided to start with
> the simplest possible configuration - a single storage location. 
> mogadm had no problems with me creating a 'single' storage class that
> had only a single copy, but running mogtool to inject data into the 
> file system led to an infinite loop of 
> 
> Beginning replication wait: 1
> Beginning replication wait: 1
> Beginning replication wait: 1
> Beginning replication wait: 1
[...]
> So, if the class has no replication, it will wait forever. If you're
> prepared to accept non-replicated file classes, then this code should
> be updated, otherwise mogadm should refuse to allow a non-replicated 
> storage class ?
> 
> Regards,
> 
> Gavin

The best fix would probably be for mogtool to fetch the mindevcount
variable from the server.  The python client uses min(mindevcount, 2) if
you specify verify_repcount=True...  I think due to get_paths
limitations at the time.


-- 
-- Justin Azoff
-- Network Performance Analyst