Mailing List Archive

Remove DRBD w/out Data Loss
I may have missed this answer when I checked the manual, but we need to convert a DRBD cluster node into standalone server without losing the data. Is that possible?

--Eric



Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
Re: Remove DRBD w/out Data Loss [ In reply to ]
You mean completely removing DRBD while preserving the data on its backing
device ? That should work out of the box, without any extra effort, as DRBD
works as a transparent layer and it does not modify the data on the backing
device.

Yannis




On Mon, 31 Aug 2020 at 09:39, Eric Robinson <eric.robinson@psmnv.com> wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I may have missed this answer when I checked the manual, but we need to
> convert a DRBD cluster node into standalone server without losing the data.
> Is that possible?
>
>
>
>
>
> --Eric
>
>
>
>
>
>
>
>
>
>
>
>
>
> Disclaimer : This email and any files transmitted with it are confidential
> and intended solely for intended recipients. If you are not the named
> addressee you should not disseminate, distribute, copy or alter this email.
> Any views or opinions presented in this
>
> email are solely those of the author and might not represent those of
> Physician Select Management. Warning: Although Physician Select Management
> has taken reasonable precautions to ensure no viruses are present in this
> email, the company cannot accept responsibility
>
> for any loss or damage arising from the use of this email or attachments.
>
>
>
>
>
> _______________________________________________
>
> Star us on GITHUB: https://github.com/LINBIT
>
> drbd-user mailing list
>
> drbd-user@lists.linbit.com
>
> https://lists.linbit.com/mailman/listinfo/drbd-user
>
> --
Sent from Gmail Mobile
Re: Remove DRBD w/out Data Loss [ In reply to ]
Yannis –

Here’s what I don’t understand.

The backing device is logical volume: /dev/vg1/lv1

The drbd volume is: drbd0

The filesystem is ext4 on /dev/drbd0

Since the filesystem is built on /dev/drbd0, not on /dev/vg1/lv1, if we remove drbd from the mix, can we then simply do:

# mount /dev/vg1/lv1 /mnt and find all the data there?

--Eric


From: Yannis Milios <yannis.milios@gmail.com>
Sent: Tuesday, September 1, 2020 4:47 AM
To: Eric Robinson <eric.robinson@psmnv.com>
Cc: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] Remove DRBD w/out Data Loss

You mean completely removing DRBD while preserving the data on its backing device ? That should work out of the box, without any extra effort, as DRBD works as a transparent layer and it does not modify the data on the backing device.

Yannis




On Mon, 31 Aug 2020 at 09:39, Eric Robinson <eric.robinson@psmnv.com<mailto:eric.robinson@psmnv.com>> wrote:













I may have missed this answer when I checked the manual, but we need to convert a DRBD cluster node into standalone server without losing the data. Is that possible?



--Eric









Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this

email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility

for any loss or damage arising from the use of this email or attachments.




_______________________________________________

Star us on GITHUB: https://github.com/LINBIT

drbd-user mailing list

drbd-user@lists.linbit.com<mailto:drbd-user@lists.linbit.com>

https://lists.linbit.com/mailman/listinfo/drbd-user
--
Sent from Gmail Mobile
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
Re: Remove DRBD w/out Data Loss [ In reply to ]
On 01/09/2020 22:43, Eric Robinson wrote:
>
> Yannis –
>
>  
>
> Here’s what I don’t understand.
>
>  
>
> The backing device is logical volume: /dev/vg1/lv1
>
>  
>
> The drbd volume is: drbd0
>
>  
>
> The filesystem is ext4 on /dev/drbd0
>
>  
>
> Since the filesystem is built on /dev/drbd0, not on /dev/vg1/lv1, if
> we remove drbd from the mix, can we then simply do:
>
>  
>
> # mount /dev/vg1/lv1 /mnt and find all the data there?  
>

Ideally what you do is something like this lot (untested but looks
reasonable)

umount it
remove it from /etc/fstab
drbdadm down $resource
drbdadm wipe-md $resource
stop drbd
remove drbd config files
remove drbd from the system
decide whether to extend your filesystem into the extra space that was
previously used by DRBD at the end of /dev/vg1/lv1 or whether to reduce
the size of the LV (assuming internal metadata).
if extending then run resize2fs/xfs_growfs as applicable
if removing extra space then I'll leave it to you to work out how much
you can safely remove without destroying the filesystem!

DRBD metadata is kept at the end of the block device it occupies so
there is extra space on the end of /dev/vg1/lv1 that is not part of the
filesystem that's on that block device.

Trevor

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.