On Tue, May 2, 2017 at 3:52 AM, J. Hart <jfhart...@gmail.com> wrote: > On 05/01/2017 02:52 PM, Filipe Manana wrote: >> >> On Mon, May 1, 2017 at 4:17 PM, J. Hart <jfhart...@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
So I managed to use the image and try it myself with the 4.11 kernel codebase. No problems found sending those snapshots. Please try a 4.11 kernel, as there's a few send fixes in there that should fix the issue. Thanks! > > > 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. > -- 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
