Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
I installed the kernel 2.6.14-1.1653_FC4 with the drbd
2.6.14_1.1653_FC4-0.7.14-1 (my actual version in production) there is no
problem...
If I use the kernel 2.6.14-1.1656_FC4 (the latest) with drbd 0.7.14 or
0.7.15 I have the problem.
Best regards.
Francis
Francis SOUYRI wrote:
> Hello,
>
> Another information when I start drbd (/etc/init.d/drbd start) I have
> the message:
>
> drbdX: No usable activity log found.
>
> Best regards.
>
> Francis
>
> Francis SOUYRI wrote:
>
>> Hello Diego,
>>
>> After stopping drbd on both nodes, bellow you have the result of the
>> commands on both nodes.
>>
>> [root at noeud1 ~]# lsmod | grep drbd
>> [root at noeud1 ~]# drbdadm -d resize named
>> drbdsetup /dev/drbd0 resize
>> [root at noeud1 ~]# drbdadm -d adjust named
>> Can not execdrbdsetup /dev/drbd0 disk /dev/vgroot/lvnamed internal -1
>> --on-io-error=panic
>> drbdsetup /dev/drbd0 syncer --rate=200M --group=1 --al-extents=257
>> drbdsetup /dev/drbd0 net 10.1.1.1:7788 10.1.1.2:7788 C
>> --sndbuf-size=1024k --on-disconnect=reconnect
>> [root at noeud1 ~]# lvdisplay /dev/vgroot/lvnamed
>> --- Logical volume ---
>> LV Name /dev/vgroot/lvnamed
>> VG Name vgroot
>> LV UUID 000000-0000-0000-0000-0000-0000-000001
>> LV Write Access read/write
>> LV Status available
>> # open 0
>> LV Size 256.00 MB
>> Current LE 64
>> Segments 1
>> Allocation normal
>> Read ahead sectors 0
>> Block device 253:1
>>
>>
>> [root at noeud2 ~]# lsmod | grep drbd
>> [root at noeud2 ~]# drbdadm -d resize named
>> drbdsetup /dev/drbd0 resize
>> [root at noeud2 ~]# drbdadm -d adjust named
>> Can not execdrbdsetup /dev/drbd0 disk /dev/vgroot/lvnamed internal -1
>> --on-io-error=panic
>> drbdsetup /dev/drbd0 syncer --rate=200M --group=1 --al-extents=257
>> drbdsetup /dev/drbd0 net 10.1.1.2:7788 10.1.1.1:7788 C
>> --sndbuf-size=1024k --on-disconnect=reconnect
>> [root at noeud2 ~]# lvdisplay /dev/vgroot/lvnamed
>> --- Logical volume ---
>> LV Name /dev/vgroot/lvnamed
>> VG Name vgroot
>> LV UUID 000000-0000-0000-0000-0000-0000-000002
>> LV Write Access read/write
>> LV Status available
>> # open 0
>> LV Size 256.00 MB
>> Current LE 64
>> Segments 1
>> Allocation normal
>> Read ahead sectors 0
>> Block device 253:2
>>
>> Best regards.
>>
>> Francis
>>
>> Diego Julian Remolina wrote:
>>
>>> Did you run the commands without having started drbd on both,
>>> primary and secondary?
>>>
>>> If drbd had been started already then stop it: /etc/init.d/drbd stop
>>>
>>> Diego
>>>
>>> Francis SOUYRI wrote:
>>>
>>>> Hello Diego,
>>>>
>>>> I have created new lvm partitions.
>>>>
>>>> Bellow you have the result of the drbdadm commands , I have a "Can
>>>> not exec" message for the "drbdadm -d adjust".
>>>>
>>>> [root at noeud1 ~]# drbdadm -d resize named
>>>> drbdsetup /dev/drbd0 resize
>>>> [root at noeud1 ~]# drbdadm -d adjust named
>>>> Can not execdrbdsetup /dev/drbd0 disk /dev/vgroot/lvnamed internal
>>>> -1 --on-io-error=panic
>>>> drbdsetup /dev/drbd0 syncer --rate=200M --group=1 --al-extents=257
>>>> drbdsetup /dev/drbd0 net 10.1.1.1:7788 10.1.1.2:7788 C
>>>> --sndbuf-size=1024k --on-disconnect=reconnect
>>>>
>>>> I have 4 drbds devices and the same problem with the 4 devices.
>>>>
>>>> [root at noeud2 ~]# drbdsetup /dev/drbd0 show
>>>> Lower device: 253:02 (dm-2)
>>>> Meta device: internal
>>>> Disk options:
>>>> on-io-error = panic
>>>> Local address: 10.1.1.2:7788
>>>> Remote address: 10.1.1.1:7788
>>>> Wire protocol: C
>>>> Net options:
>>>> timeout = 6.0 sec (default)
>>>> connect-int = 10 sec (default)
>>>> ping-int = 10 sec (default)
>>>> max-epoch-size = 2048 (default)
>>>> max-buffers = 2048 (default)
>>>> sndbuf-size = 1048576
>>>> ko-count = 0 (default)
>>>> Syncer options:
>>>> rate = 204800 KB/sec
>>>> group = 1
>>>> al-extents = 257
>>>> [root at noeud2 ~]# drbdsetup /dev/drbd1 show
>>>> Lower device: 253:04 (dm-4)
>>>> Meta device: internal
>>>> Disk options:
>>>> on-io-error = panic
>>>> Local address: 10.1.1.2:7789
>>>> Remote address: 10.1.1.1:7789
>>>> Wire protocol: C
>>>> Net options:
>>>> timeout = 6.0 sec (default)
>>>> connect-int = 10 sec (default)
>>>> ping-int = 10 sec (default)
>>>> max-epoch-size = 2048 (default)
>>>> max-buffers = 2048 (default)
>>>> sndbuf-size = 1048576
>>>> ko-count = 0 (default)
>>>> Syncer options:
>>>> rate = 204800 KB/sec
>>>> group = 2
>>>> al-extents = 257
>>>> [root at noeud2 ~]# drbdsetup /dev/drbd2 show
>>>> Lower device: 253:03 (dm-3)
>>>> Meta device: internal
>>>> Disk options:
>>>> on-io-error = panic
>>>> Local address: 10.1.1.2:7790
>>>> Remote address: 10.1.1.1:7790
>>>> Wire protocol: C
>>>> Net options:
>>>> timeout = 6.0 sec (default)
>>>> connect-int = 10 sec (default)
>>>> ping-int = 10 sec (default)
>>>> max-epoch-size = 2048 (default)
>>>> max-buffers = 2048 (default)
>>>> sndbuf-size = 1048576
>>>> ko-count = 0 (default)
>>>> Syncer options:
>>>> rate = 204800 KB/sec
>>>> group = 3
>>>> al-extents = 257
>>>> [root at noeud2 ~]# drbdsetup /dev/drbd3 show
>>>> Lower device: 253:05 (dm-5)
>>>> Meta device: internal
>>>> Disk options:
>>>> on-io-error = panic
>>>> Local address: 10.1.1.2:7791
>>>> Remote address: 10.1.1.1:7791
>>>> Wire protocol: C
>>>> Net options:
>>>> timeout = 6.0 sec (default)
>>>> connect-int = 10 sec (default)
>>>> ping-int = 10 sec (default)
>>>> max-epoch-size = 2048 (default)
>>>> max-buffers = 2048 (default)
>>>> sndbuf-size = 1048576
>>>> ko-count = 0 (default)
>>>> Syncer options:
>>>> rate = 204800 KB/sec
>>>> group = 4
>>>> al-extents = 257
>>>>
>>>> Best regards.
>>>>
>>>> Francis
>>>>
>>>> Diego Julian Remolina wrote:
>>>>
>>>>> Did you modify the sizes of the lvm partitions prior to trying to
>>>>> do this?
>>>>>
>>>>> Have you tried
>>>>> drbdadm -d resize resource
>>>>> and
>>>>> drbdam -d adjust resource
>>>>>
>>>>> Just to check everything is fine?
>>>>>
>>>>> Note that -d means dry-run so it would show you what is needed to
>>>>> adjust the drbd settings according to your drbd configuration.
>>>>>
>>>>> Since you seem to have already wiped out the data I would just go
>>>>> ahead and run:
>>>>>
>>>>> drbdadm resize resource
>>>>>
>>>>> I also noticed you provided an example on your configuration for
>>>>> resource using /dev/drbd0 but are trying to format /dev/drbd2, so
>>>>> double check your drbd.conf file to make sure it is configured
>>>>> appropriately.
>>>>>
>>>>> Diego
>>>>>
>>>>>
>>>>> Francis SOUYRI wrote:
>>>>>
>>>>>> Hello Corey,
>>>>>>
>>>>>> The mke2fs command use a size of 128Mo (131072 blocks of 1024).
>>>>>>
>>>>>> root at noeud1 ~]# mke2fs -j /dev/drbd2
>>>>>> mke2fs 1.38 (30-Jun-2005)
>>>>>> Filesystem label=
>>>>>> OS type: Linux
>>>>>> Block size=1024 (log=0)
>>>>>> Fragment size=1024 (log=0)
>>>>>> 32768 inodes, 131072 blocks
>>>>>> 6553 blocks (5.00%) reserved for the super user
>>>>>> First data block=1
>>>>>> Maximum filesystem blocks=67371008
>>>>>> 16 block groups
>>>>>> 8192 blocks per group, 8192 fragments per group
>>>>>> 2048 inodes per group
>>>>>> Superblock backups stored on blocks:
>>>>>> 8193, 24577, 40961, 57345, 73729
>>>>>>
>>>>>> Writing inode tables: done
>>>>>> Creating journal (4096 blocks): done
>>>>>> Writing superblocks and filesystem accounting information:
>>>>>> **** No return ****
>>>>>>
>>>>>> Best regards.
>>>>>>
>>>>>> Francis
>>>>>>
>>>>>> Corey Edwards wrote:
>>>>>>
>>>>>>> On Tue, 2006-01-10 at 10:17 +0100, Francis SOUYRI wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> When I try to access a drbd device, the command used freeze
>>>>>>>> like that:
>>>>>>>>
>>>>>>>> [root at noeud1 ~]# drbdsetup /dev/drbd0 primary --do-what-I-say
>>>>>>>> [root at noeud1 ~]# dd if=/dev/zero of=/dev/drbd0
>>>>>>>> dd: writing to `/dev/drbd0': No space left on device
>>>>>>>> 262145+0 records in
>>>>>>>> 262144+0 records out
>>>>>>>> **** no return ****
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> on noeud1 {
>>>>>>>> device /dev/drbd0;
>>>>>>>> disk /dev/vgroot/lvnamed;
>>>>>>>> address 10.1.1.1:7788;
>>>>>>>> meta-disk internal;
>>>>>>>> }
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Remember that with internal metadata the last 128MB of the disk are
>>>>>>> reserved. I've never used internal much so I can't say for sure,
>>>>>>> but
>>>>>>> this sounds like it could easily be caused by trying to write to
>>>>>>> that
>>>>>>> reserved section of the disk.
>>>>>>>
>>>>>>> Try mke2fs again and explicitly specify the size of the disk as
>>>>>>> 128MB
>>>>>>> smaller than the real size.
>>>>>>>
>>>>>>> Corey
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> drbd-user mailing list
>>>>>>> drbd-user at lists.linbit.com
>>>>>>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> drbd-user mailing list
>>>>>> drbd-user at lists.linbit.com
>>>>>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> drbd-user mailing list
>>>> drbd-user at lists.linbit.com
>>>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>>
>>>
>>>
>>>
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>