Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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
--
Diego Julian Remolina
System Administrator - Systems Support Specialist III
Institute for Bioengineering and Bioscience
Georgia Institute of Technology
Phone (404) 385-0127
Fax (404) 894-2291
315 Ferst Drive
Atlanta, GA 30332-0363