Hi, this is just a small correction to my previous mail.
On Thu, Jan 22, 2009 at 10:54:53AM +0100, Carl Fredrik Hammar wrote: > Take copy store as an example. The copy store makes a copy-on-write > copy of another store and discards changes when closed. For instance, > a copy store over a zero store is useful for backing /tmp. > > If a copy store where to migrate, then all modifications would also be > copied. Writes made to the copy would not be reflected in the original > and vice versa. Because of this, the copy store has the enforced flag set, > which makes storeio refuse migration requests. It seems I read a bit too much into a comment regarding the enforced flag. The actual mechanism that prevents migration is its marshalling method that always returns EOPNOTSUPP. Just so nobody gets hung up on this little miss. ;-) Regards, Fredrik
