From: Nils Steinger <nst@voidptr.de>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send reproducibly fails for a specific subvolume after sending 15 GiB, scrub reports no errors
Date: Sun, 22 Nov 2015 22:59:36 +0100 [thread overview]
Message-ID: <56523AC8.7050205@voidptr.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Hi,
I recently ran into a problem while trying to back up some of my btrfs
subvolumes over the network:
`btrfs send` works flawlessly on snapshots of most subvolumes, but keeps
failing on snapshots of a certain subvolume — always after sending 15 GiB:
btrfs send /btrfs/snapshots/home/2015-11-17_03:28:14_BOOT-AUTOSNAPSHOT |
pv | ssh kappa "btrfs receive /mnt/300gb/backups/snapshots/zeta/home/"
At subvol /btrfs/snapshots/home/2015-11-17_03:28:14_BOOT-AUTOSNAPSHOT
At subvol 2015-11-17_03:28:14_BOOT-AUTOSNAPSHOT
ERROR: send ioctl failed with -2: No such file or directory
15GB 0:34:34 [7,41MB/s]
I've tried piping the output to /dev/null instead of ssh and got the
same error (again after sending 15 GiB), so this seems to be on the
sending side.
However, btrfs scrub reports no errors and I don't get any messages in
dmesg when the btrfs send fails.
What could cause this kind of error?
And is there a way to fix it, preferably without recreating the FS?
Regards,
Nils Steinger
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next reply other threads:[~2015-11-22 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 21:59 Nils Steinger [this message]
2015-11-23 5:49 ` btrfs send reproducibly fails for a specific subvolume after sending 15 GiB, scrub reports no errors Duncan
2015-11-23 12:26 ` Austin S Hemmelgarn
2015-11-23 21:10 ` Nils Steinger
2015-11-24 5:42 ` Duncan
2015-11-24 12:46 ` Austin S Hemmelgarn
2015-11-24 18:48 ` Christoph Anton Mitterer
2015-11-24 20:44 ` Austin S Hemmelgarn
2015-11-24 20:50 ` Christoph Anton Mitterer
2015-11-24 20:58 ` Austin S Hemmelgarn
2015-11-24 21:17 ` Christoph Anton Mitterer
2015-11-24 21:27 ` Hugo Mills
2015-11-24 21:36 ` Christoph Anton Mitterer
2015-11-24 22:08 ` Hugo Mills
2015-11-26 15:44 ` Duncan
2015-11-24 21:11 ` Filipe Manana
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=56523AC8.7050205@voidptr.de \
--to=nst@voidptr.de \
--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.