[Drbd-dev] Re: drbd in linux-ha cvs
Philipp Reisner
philipp.reisner at linbit.com
Tue Sep 7 11:45:50 CEST 2004
> > > waere es sinnvoll sowas zu haben:
> > >
> > > drbdadm dump_meta_data r0 (oder info oder wie immer wir das nennen
> > > wollen)
> > >
> > > output would be bash sourceable:
> > > GEN_COUNT=SOME:LONGER:STRING:WITH:NUMBERS:AND:STUFF
[...]
> > Ideas:
> > 1) We move the read_gc.pl/write_gc.pl to the user directory.
> > 2) Make them to one C program: drbdmeta
> > -> in the future the module never creates the meta data
> > block. One can use drbdmeta to create, read and
> > modify the drbdmeta block. drbdmeta refuses to write
> > to it as long as the module is loaded (configured).
> > 3) drbdadm is the nice frontend to drbdmeta is it is to
> > drbdsetup.
[...]
> > So with continuing the current way of doing things, I would
> > extend the interface in this way:
> >
> > drbdadm md-set-gc 1:2:3:4:5:6 r0
> > drbdadm md-get-gc 1:2:3:4:5:6 r0
> > drbdadm md-get/set-{la-size|consistent|etc...} resources....
> > drbdadm md-create r0
[...]
> I do NOT want to make it easy to _modify_ on-disk meta data.
> if it is too easy (or even documented), people will screw up,
> and blame us for it.
>
Right! All (at least most) of the "set" methods must be undocumented.
(And not visible in the usage)
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
More information about the drbd-dev
mailing list