Re: ERROR: rename o3528-7220-0 -> usr failed: Directory not empty

2017-05-01 Thread J. Hart
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 thi

re: ERROR: rename o3528-7220-0 -> usr failed: Directory not empty

2017-05-01 Thread J. Hart
apshot 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 -- To unsubscribe from this list: send the lin

Re: ERROR: cannot find parent subvolume, can't see reason for it.

2017-04-30 Thread J. Hart
investigating a another error I have detailed in another message: ERROR: rename o3528-7220-0 -> usr failed: Directory not empty It is probably not related. I will file a report with Kernel.org bugzilla on it. On 04/30/2017 04:43 PM, Chris Murphy wrote: On Sat, Apr 29, 2017 at 9:10 PM, J. H

ERROR: rename o3528-7220-0 -> usr failed: Directory not empty

2017-04-30 Thread J. Hart
ostics I can. 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

Re: ERROR: cannot find parent subvolume, can't see reason for it.

2017-04-30 Thread J. Hart
ation I was attempting proceeds without error. On 04/30/2017 03:07 AM, Duncan wrote: [This mail was also posted to gmane.comp.file-systems.btrfs.] J. Hart posted on Sat, 29 Apr 2017 23:10:48 -0400 as excerpted: I see three previous threads (the first starting on March 25) with you as origin

ERROR: cannot find parent subvolume, can't see reason for it.

2017-04-29 Thread J. Hart
I am trying to do a "send -p src/snp1 src/snp2 dst/" and getting the following error: ERROR: cannot find parent subvolume The "src/snp1" is present in both "src/" and "dst/". The "src/snp2" is present in "src/" . The send works when "-p" is not used, but will not work when it is. I

backing up a collection of snapshot subvolumes

2017-04-24 Thread J. Hart
I have a remote machine with a filesystem for which I periodically take incremental snapshots for historical reasons. These snapshots are stored in an archival filesystem tree on a file server. Older snapshots are removed and newer ones added on a rotational basis. I need to be able to

Re: btrfs send extremely slow (almost stuck)

2017-04-14 Thread J. Hart
n enabled, that backup takes nearly seven hours. Sending a complete volume to a blank filesystem (so no reflinks are present at the destination) is a matter of only a few minutes. Many thanks to Hermann Schwarzler whose suggestion led me onto this. J. Hart -- To unsubscribe from this list: send

Unexpected: send/receive much slower than rsync ?

2017-04-11 Thread J. Hart
if no large files are present. I hope I'm overlooking something, and that this is not actually the case. Any ideas on this ? 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

Re: send snapshot from snapshot incremental

2017-03-28 Thread J. Hart
Don't be embarrassed. I'm a native speaker and still have trouble with most explanations.:-) On 03/28/2017 06:01 PM, Jakob Schürz wrote: Thanks for that explanation. I'm sure, i didn't understand the -c option... and my english is pretty good enough for the most things I need to know

Re: backing up a file server with many subvolumes

2017-03-27 Thread J. Hart
That is a very interesting idea. I'll try some experiments with this. Many Thanks for the assistance:-) J. Hart On 03/27/2017 01:57 AM, Marat Khalili wrote: Just some consideration, since I've faced similar but no exactly same problem: use rsync, but create snapshots on target machine

backing up a file server with many subvolumes

2017-03-25 Thread J. Hart
don't think I can use send/receive to do this. "Btrfs send" requires "read-only" snapshots, and snapshots are not recursive as yet. I think there are too many subvolumes which change too often to make doing this without recursion practical. Any thoughts would be most a