On Mon, May 1, 2017 at 4:17 PM, J. Hart <jfhart...@gmail.com> wrote: > 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.
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. Thanks. > > > J. Hart > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
