Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I think what Lars was saying is:
Do not mkfs on the initial device, mkfs on the /dev/drbdX device,
because the last 128MB on the initial device will be eaten for
meta-data.
-Ross
________________________________
From: drbd-user-bounces at lists.linbit.com
[mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Dan Gahlinger
Sent: Friday, February 09, 2007 10:42 AM
To: drbd-user at lists.linbit.com
Subject: Re: [DRBD-user] Reproduceable error - creating a single
directorycauses drbd to fail
Yes, I don't really follow that.
the stuff about "shrinking the partition".
I resized the partition, but that just makes it worse.
Definitely missing something there.
Which probably explains why using the other meta-disk type
works.
Dan.
On 2/8/07, Lars Ellenberg <Lars.Ellenberg at linbit.com> wrote:
/ 2007-02-08 18:17:20 -0500
\ Dan Gahlinger:
> Lars, could be.
>
> I meant "no" in that one point.
>
> I was able to "fix" the problem. By changing the
metadisk to a device
> instead of internal.
> mkdir does not show the same problem.
>
> btw mystery piece, when I use Reiser or XFS, I can't
get drbd to work.
> always get an error.
> I'll scan through the logs and see what I can find,
the config is pretty
> basic.
>
> Take the drbd.conf from the same
(share/packages...etc) and make only minor
> changes, thus:
>
> on amd {
> device /dev/drbd0;
> disk /dev/sda3;
> address 192.168.22.11:7788;
> meta-disk internal;
> }
>
> I entered a "fake" second system (whether I do it with
the systems connected
> or not made no difference so I'm just trying to simply
it), as I'm trying to
> only make it work on one system for now.
> then I used:
> /etc/init.d/drbd start
> drdbsetup /dev/drbd0 primary --do-what-I-say
> mount /dev/drbd0 /test
> cd /test
> tar -xvf /test.tar
so. you use internal drbd metadata,
but you created the file system on the lower level
device.
ho hum. no further comment.
I guess you get to it sooner or later :->
I give you one further hint:
in the kernel log, just before ext3 will remount
readonly,
it will say "access beyond end of device".
> >never heard of what you describe,
> >unless it was user error -- or bad hardware.
:-/
--
: Lars Ellenberg Tel
+43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax
+43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe
http://www.linbit.com <http://www.linbit.com> :
__
please use the "List-Reply" function of your email
client.
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070209/31ff2f84/attachment.htm>