From: Marc MERLIN <marc@merlins.org>
To: Matt McKinnon <matt@techsquare.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send/receive error
Date: Mon, 11 May 2015 16:46:04 -0700 [thread overview]
Message-ID: <20150511234604.GF15670@merlins.org> (raw)
In-Reply-To: <55512147.5030708@techsquare.com>
On Mon, May 11, 2015 at 05:38:15PM -0400, Matt McKinnon wrote:
> Hello,
>
> What's the best way to deal with this send/receive error?
Typically get a new kernel where this is fixed, Filipe
has been working on fixing them.
What kernel was this on?
Marc
> ---
>
> Create a readonly snapshot of 'users' in
> '/export/r2/.incrementals/users_ro.20150511_17:28:53'
> At subvol /export/r2/.incrementals/users_ro.20150511_17:28:53
> At snapshot users_ro.20150511_17:28:53
> ERROR: rename o46709324-421364-0 ->
> fspace2/120430RU/bold_nopace/SPMana failed. Directory not empty
>
> ---
>
> ./btrfs --version
> btrfs-progs v4.0
>
>
> -Matt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2015-05-11 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 21:38 btrfs send/receive error Matt McKinnon
2015-05-11 23:46 ` Marc MERLIN [this message]
2015-05-12 1:00 ` Matt McKinnon
2015-05-12 14:41 ` Marc MERLIN
2015-05-13 15:51 ` Matt McKinnon
-- strict thread matches above, loose matches on Subject: below --
2016-06-22 12:01 Lubos Kolouch
2016-06-22 16:10 ` Michael Duell
2016-06-23 7:02 ` Lubos Kolouch
2016-06-23 22:51 ` Michael Duell
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=20150511234604.GF15670@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=matt@techsquare.com \
/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.