Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi.
I have my DRBD device setup with:
resource dirvish01-data {
device /dev/drbd11;
disk /dev/datavg/dirvish01-data;
flexible-meta-disk internal;
on [insert "on" clauses"]
}
I added 20GB to the LVM LV with:
lvextend -L +20G /dev/datavg/dirvish01-data
on both hosts. On the primary host:
drbdadm adjust dirvish01-data
Then, I mounted /dev/drbd11 on /mnt and did:
xfs_growfs /mnt
First problem: The xfs_growfs only grew the filesystem by about 10GB, not
the full 20GB.
Second problem: Upon doing a "drbdadm down dirvish01-data ; drbdadm up
dirvish01-data", I get:
/dev/drbd11: Failure: (119) No valid meta-data signature found.
==> Use 'drbdadm create-md res' to initialize meta-data area. <==
Command 'drbdsetup /dev/drbd11 disk /dev/datavg/dirvish01-data
/dev/datavg/dirvish01-data internal --set-defaults --create-device
--on-io-error=detach' terminated with exit code 10
Obviously, this is bad ... Now I can't start my device and get access to my
data.
This is on Ubuntu 8.04LTS (Hardy) with kernel 2.6.18.8-xen-x64-20080924
(custom build, but growing the DRBD devices has worked previously). DRBD
version version: 8.2.6 (api:88/proto:86-88) GIT-hash:
3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by root at xen-80-31-00,
2008-09-25 01:10:05.
How can I convince DRBD to get my data back? I was under the impression
that the "flexible-meta-disk internal" would handle the "drbdadm adjust"
properly. Doing the suggested "drbdadm create-md dirvish01-data" indicates
I will loose my data, so I have not run that command as of yet.
Thanks,
Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20081111/8a216c5d/attachment.htm>