From: GEO <1g2e3o4@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send handle missing space on target device
Date: Wed, 06 Aug 2014 23:20:20 +0200 [thread overview]
Message-ID: <8854735.1A2mADRSs8@linuxpc> (raw)
Hi,
I wonder how I should handle missing space on the backup device when doing
incremental backup with btrfs send?
I mean for the initial bootstrap it is easy, I simply compare the free space
of the target device with the size of home (we are talking about incremental
backups of home), but how should I handle this with
sudo btrfs send -p @home-backup @home-backup | sudo btrfs receive /mnt/backup/
What will happen by default if the space on the target is not enough? Will the
command start writing to /mnt/backup/ at all and stop when the disk is full,
or will it return an error code? If it doesn't return an error code, how can I
handle this before the transaction?
Thanks in advance!
reply other threads:[~2014-08-06 21:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8854735.1A2mADRSs8@linuxpc \
--to=1g2e3o4@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.