Open GoogleCodeExporter opened 9 years ago
IIUC the reason why this happens is the second 'zumastor define master',
regardless
with or without '--samba', destroys zumastor's database for this volume.
It also happens if you do 'zumastor forget volume' and 'zumastor create
volume': you
don't lose data or snapshots but snapshots are not mounted anymore.
Thus, this is expected behavior, i. e. not a bug but a feature. The question
is, is
this the right behavior?
Original comment by pgqui...@gmail.com
on 8 Feb 2008 at 7:57
Currently, any change on the '--samba' or '--export' options will only affect
the
snapshots that are created afterwards. You need to restart 'zumastor master' to
have
the existing snapshots also reflect the change. This is mostly for the sake of
simplicity. We don't need to worry about synchronization when 'zumastor master'
may
create/delete snapshots during the change.
I think it is a missing feature. We need to provide a way that allows users to
change
any configuration easily.
Original comment by jiahotc...@gmail.com
on 8 Feb 2008 at 11:20
Original issue reported on code.google.com by
pgqui...@gmail.com
on 31 Jan 2008 at 5:22