Hello !
Today I have downloaded and installed the latest CVS version of DRBD.
(and also latest beta heartbeat
I can't say it was very easy, but after 3 hours I'm able to mount
/export from /dev/drbd0 ;))
end test hearbeat.
Well, during installation I have descovered some number of problems and
now list it below:
1. Major number problem
In drbd.c major number defined as 43 (240 commented out) but
Makefile::dev creates drbd0 files
with major 240 I'm not quite sure what I did it in a right way but I
change Makefile to use 43 major
Does it posses any potential threat to the system ?
2. _Probably_ wrong order of arguments for datadisk script.
Both datadisk and drbd_common expect action as first argument and
resource as the second.
If you place datadisk to haresources file like this datadisk::drbd0 it
will be incorrectly called with
arguments order like this datadisk drbd0 start
Solution, not to use drbd0 at all and call just datadisk start, or
create simple script to reversing
argument order and place it to haresources file (as I did)
3. Not actually a bug and could be forgiven in respect for beta state,
but anyway, please add this
to release note - configuration file syntax changed, name of device file
changed (reflect it in your /etc/fstab)
4. what is difference bitween drbd_commOn and drbd_commUn ? drbd script
looks for it in /etc/ha.d/resource.d
but make install doesn't copy it from source directory
5. SAFE variable problem. Where should I place this variable ? I have
placed it to drbd_common, but probably
you have a different opinion on it.
SAFE=true problem. I'm running RedHat 6.2 with bash 1.14.7(1) and read
-n from "safe"
branch in datadisk script produce error msg:
read: unknown option: -n
read: usage: read [-r] [name...]
Just a question...
I'm using reiserfs for drbd device. Should I add "sync" flag to the
fstab to be fail-safe with "B" protocol ?
Thanks a lot !
With best regards.
--
Dim
Today I have downloaded and installed the latest CVS version of DRBD.
(and also latest beta heartbeat
I can't say it was very easy, but after 3 hours I'm able to mount
/export from /dev/drbd0 ;))
end test hearbeat.
Well, during installation I have descovered some number of problems and
now list it below:
1. Major number problem
In drbd.c major number defined as 43 (240 commented out) but
Makefile::dev creates drbd0 files
with major 240 I'm not quite sure what I did it in a right way but I
change Makefile to use 43 major
Does it posses any potential threat to the system ?
2. _Probably_ wrong order of arguments for datadisk script.
Both datadisk and drbd_common expect action as first argument and
resource as the second.
If you place datadisk to haresources file like this datadisk::drbd0 it
will be incorrectly called with
arguments order like this datadisk drbd0 start
Solution, not to use drbd0 at all and call just datadisk start, or
create simple script to reversing
argument order and place it to haresources file (as I did)
3. Not actually a bug and could be forgiven in respect for beta state,
but anyway, please add this
to release note - configuration file syntax changed, name of device file
changed (reflect it in your /etc/fstab)
4. what is difference bitween drbd_commOn and drbd_commUn ? drbd script
looks for it in /etc/ha.d/resource.d
but make install doesn't copy it from source directory
5. SAFE variable problem. Where should I place this variable ? I have
placed it to drbd_common, but probably
you have a different opinion on it.
SAFE=true problem. I'm running RedHat 6.2 with bash 1.14.7(1) and read
-n from "safe"
branch in datadisk script produce error msg:
read: unknown option: -n
read: usage: read [-r] [name...]
Just a question...
I'm using reiserfs for drbd device. Should I add "sync" flag to the
fstab to be fail-safe with "B" protocol ?
Thanks a lot !
With best regards.
--
Dim