From: "J. Hart" <jfhart085@gmail.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: ERROR: rename o3528-7220-0 -> usr failed: Directory not empty
Date: Mon, 01 May 2017 22:52:37 -0400 [thread overview]
Message-ID: <5907F475.10704@gmail.com> (raw)
In-Reply-To: <CAL3q7H772sxj0KVWQ6tWTrb=2fzvgCQxryyCDPzj4GaUWH2TGw@mail.gmail.com>
On 05/01/2017 02:52 PM, Filipe Manana wrote:
> On Mon, May 1, 2017 at 4:17 PM, J. Hart <jfhart085@gmail.com> wrote:
> Just use "btrfs-image -c 9 /dev/whatever image_file", it will create a
> compressed image where the data is replaced with zeroes (not needed to
> debug this problem anyway). Then uploaded it anywhere convenient for you.
I have prepared the image as per your instructions. It is 27 Mb in
size. I have no way to confirm whether or not it is correct, as the
documentation on how that might be done is unclear on that point. It was
also not clear whether or not the btrfs filesystem should be unmounted
as the documentation does not specify. A warning appears if it is
mounted, so I unmounted it to make the image.
I have at present no convenient location to upload it to. Can you
suggest one ?
If you can manage to load the image on to a btrfs filesystem, cd to the
mount point and do the following:
btrfs se --no-data snp1 | btrfs rec temp
btrfs se --no-data -p snp1 snp2 | btrfs rec temp # failure here
The error should be something like:
-su-3.2# btrfs se --no-data -p snp1 snp2 | btrfs rec temp # failure here
At subvol snp2
At snapshot snp2
ERROR: rename o3528-12-0 -> usr failed: Directory not empty
I have been able to get the requisite data from the original filesystem
to a completely different one, and recreate the error on the new
filesystem, so the error seems to follow along with the data involved.
next prev parent reply other threads:[~2017-05-02 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 15:17 ERROR: rename o3528-7220-0 -> usr failed: Directory not empty J. Hart
2017-05-01 18:52 ` Filipe Manana
2017-05-02 2:52 ` J. Hart [this message]
2017-05-17 15:36 ` Filipe Manana
-- strict thread matches above, loose matches on Subject: below --
2017-04-30 17:10 J. Hart
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=5907F475.10704@gmail.com \
--to=jfhart085@gmail.com \
--cc=fdmanana@kernel.org \
--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.