From: Hendrik Friedel <hendrik@friedels.name>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: How to move a btrfs volume to a smaller disk
Date: Wed, 9 Mar 2016 22:46:09 +0100 [thread overview]
Message-ID: <56E099A1.8040506@friedels.name> (raw)
Hello,
I intend to move this subvolume to a new device.
btrfs fi show /mnt2/Data_Store/
Label: 'Data_Store' uuid: 0ccc1e24-090d-42e2-9e61-d0a1b3101f93
Total devices 1 FS bytes used 47.93GiB
devid 1 size 102.94GiB used 76.03GiB path /dev/sdb4
(fi usage at the bottom of this message)
The new device (sda4) is 8G smaller unfortunately.
sda 8:0 0 111.8G 0 disk
└─sda4 8:4 0 103.5G 0 part
sdb 8:16 0 119.2G 0 disk
└─sdb4 8:20 0 111G 0 part /mnt2/Data_Store
Thus, btrfs replace does not work
What would you suggest now to move the FS (it does contain many subvolumes)?
I tried btrfs send /mnt2/Data_Store/read_only_snapshot/ | btrfs receive
/mnt/sda4/
but this only created an empty subvolume /mnt/sda4/read_only_snapshot/
So, then
btrfs device add /dev/sda4 /mnt/Data_Store
btrfs balance start /mnt/Data_Store
btrfs device remove /dev/sdb4 /mnt/Data_Store
?
Or is there a better option?
Regards,
Hendrik
btrfs fi usage /mnt2/Data_Store/
Overall:
Device size: 102.94GiB
Device allocated: 74.03GiB
Device unallocated: 28.91GiB
Device missing: 0.00B
Used: 47.96GiB
Free (estimated): 53.24GiB (min: 53.24GiB)
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 512.00MiB (used: 0.00B)
Data,single: Size:69.00GiB, Used:44.67GiB
/dev/sdb4 69.00GiB
Metadata,single: Size:5.00GiB, Used:3.29GiB
/dev/sdb4 5.00GiB
System,single: Size:32.00MiB, Used:16.00KiB
/dev/sdb4 32.00MiB
Unallocated:
/dev/sdb4 28.91GiB
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next reply other threads:[~2016-03-09 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 21:46 Hendrik Friedel [this message]
2016-03-09 21:50 ` How to move a btrfs volume to a smaller disk Hugo Mills
2016-03-09 22:03 ` Hendrik Friedel
2016-03-11 3:29 ` Satoru Takeuchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E099A1.8040506@friedels.name \
--to=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).