All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Hart" <jfhart085@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: re: ERROR: rename o3528-7220-0 -> usr failed: Directory not empty
Date: Mon, 01 May 2017 11:17:48 -0400	[thread overview]
Message-ID: <5907519C.2020204@gmail.com> (raw)

I've got more information on the following error :

At subvol /mnt/ArchPri/backup/primary/thinkcentre/root/backup.0.2
At snapshot backup.0.2017.04.21.03.11.40
ERROR: rename o3528-7220-0 -> usr failed: Directory not empty

I've filed a bug report with additional details at:

https://bugzilla.kernel.org/show_bug.cgi?id=195619

This error occurs during a series of "btrfs send" invocations.  It does 
not occur on all of them, but always at the same point in the operation, 
and so appears to be specific to (dependent on) the data being sent.

I have a test case down to the following:

su -
btrfs send --no-data temp/backup.0.2017.04.17.07.57.17 | btrfs rec temp/test
sync
btrfs send --no-data -p temp/backup.0.2017.04.17.07.57.17 
temp/backup.0.2017.04.21.03.11.40 | btrfs rec temp/test

The error should be something like:
At subvol temp/backup.0.2017.04.21.03.11.40
At snapshot backup.0.2017.04.21.03.11.40
ERROR: rename o3528-7220-0 -> usr failed: Directory not empty

I will probably need to provide the data somehow, or at least the output 
from "btrfs send".  The original data is several GB in size.

J. Hart


             reply	other threads:[~2017-05-01 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 15:17 J. Hart [this message]
2017-05-01 18:52 ` ERROR: rename o3528-7220-0 -> usr failed: Directory not empty Filipe Manana
2017-05-02  2:52   ` J. Hart
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=5907519C.2020204@gmail.com \
    --to=jfhart085@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.