From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Glen H <glen.hertz@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs send | receive error: no such file or directory
Date: Mon, 9 Nov 2015 08:50:15 -0500 [thread overview]
Message-ID: <5640A497.2060701@gmail.com> (raw)
In-Reply-To: <CABtZWNH4rzzTtBwvt6Xs+nf=8aiJrbsCAVZB3QzPEnEfi-Cs5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On 2015-11-08 16:28, Glen H wrote:
> Hi,
>
> I really enjoy the features of btrfs but send|receive is failing me so
> my backups are not working. I'm using "btrbk" to backup my drives
> (all local) and one of the three subvolumes errors out. When I run
> this command from the terminal it errors out:
>
>> btrfs send /mnt/ssd/_btrbk_snap/@.20151108 | btrfs receive /mnt/backup2tb/
> At subvol /mnt/ssd/_btrbk_snap/@.20151108
> At subvol @.20151108
> ERROR: send ioctl failed with -2: No such file or directory
> ERROR: unexpected EOF in stream.
Have you ever run any kind of data deduplication (bedup, duperemove, or
something else) on the source filesystem? I've seen errors like this in
the past when trying to send from a filesystem that I had run
deduplication on (and I don't think that the patches to fix it made into
the version of Mint you're using).
That aside, there are two things that I've found that can fix some (but
not all) send/receive errors:
1. Run a balance on the filesystem (either a full balance, or use
filters to select just the block in question).
2. Force the file that it's choking on to be re-written (you can use
'btrfs receive -vv' to see what files it's processing, although be
prepared for _a lot_ of output).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-11-09 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 21:28 btrfs-progs send | receive error: no such file or directory Glen H
2015-11-09 1:09 ` Duncan
2015-11-09 13:50 ` Austin S Hemmelgarn [this message]
2015-11-10 3:11 ` Glen H
2015-11-10 12:19 ` Austin S Hemmelgarn
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=5640A497.2060701@gmail.com \
--to=ahferroin7@gmail.com \
--cc=glen.hertz@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.