On Sat, 25 Mar 2017 23:00:20 -0400
"J. Hart" wrote:
> I have a Btrfs filesystem on a backup server. This filesystem has a
> directory to hold backups for filesystems from remote machines. In this
> directory is a subdirectory for each machine. Under each machine
> subdirectory is one direct
"make clean-all" leaves generated files under the "kernel-shared" directory.
This causes problems when trying to build under the same tree when the
absolute path changes.
For example if you mount the source tree in one location,
generate/build, then mount it in a different location, clean-all,
re
On Sun, Mar 26, 2017 at 02:14:36PM +0500, Roman Mamedov wrote:
> You could have done time-based snapshots on the top level (for /backup/), say,
> every 6 hours, and keep those for e.g. a month. Then don't bother with any
> other kind of subvolumes/snapshots on the backup machine, and do backups fro
> [ ... ] In each filesystem subdirectory are incremental
> snapshot subvolumes for that filesystem. [ ... ] The scheme
> is something like this:
> /backup///
BTW hopefully this does not amounts to too many subvolumes in
the '.../backup/' volume, because that can create complications,
where "too
A Gentoo user reports that snapper broke after upgrading to btrfs-progs-4.10.
snapper: symbol lookup error: /usr/lib64/libbtrfs.so.0: undefined
symbol: __error
https://bugs.gentoo.org/show_bug.cgi?id=613890
It seems that the __error symbol is referenced, but not included in libbtrfs.
Exporting
[ ... ]
> BUT if i take a snapshot from the system, and want to transfer
> it to the external HD, i can not set a parent subvolume,
> because there isn't any.
Questions like this are based on incomplete understanding of
'send' and 'receive', and on IRC user "darkling" explained it
fairly well:
>
At 03/26/2017 06:03 AM, Moritz Sichert wrote:
Hi,
I tried to configure qgroups on a btrfs filesystem but was really surprised
that when you snapshot a subvolume, the snapshot will not be assigned to the
qgroup the subvolume was in.
As an example consider the small terminal session in the at
Reported-by: Chris
Signed-off-by: Qu Wenruo
---
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefile
index fdc63c3a..d1af4311 100644
--- a/Makefile
+++ b/Makefile
@@ -502,6 +502,7 @@ clean: $(CLEANDIRS)
@echo "Cleaning"
$(Q)$(RM) -f -- $(progs) *.o *.o
At 03/25/2017 07:21 AM, Liu Bo wrote:
On Fri, Mar 24, 2017 at 10:00:27AM +0800, Qu Wenruo wrote:
Unlike other place calling btrfs_map_block(), in raid56 scrub, we don't
use bio_counter to protect from race against dev replace.
This patch will use bio_counter to protect from the beginning of c
27.03.2017 03:39, Qu Wenruo пишет:
>
>
> At 03/26/2017 06:03 AM, Moritz Sichert wrote:
>> Hi,
>>
>> I tried to configure qgroups on a btrfs filesystem but was really
>> surprised that when you snapshot a subvolume, the snapshot will not be
>> assigned to the qgroup the subvolume was in.
>>
>> As
At 03/27/2017 11:26 AM, Andrei Borzenkov wrote:
27.03.2017 03:39, Qu Wenruo пишет:
At 03/26/2017 06:03 AM, Moritz Sichert wrote:
Hi,
I tried to configure qgroups on a btrfs filesystem but was really
surprised that when you snapshot a subvolume, the snapshot will not be
assigned to the qgro
Just some consideration, since I've faced similar but no exactly same
problem: use rsync, but create snapshots on target machine. Blind rsync
will destroy deduplication of your snapshots and take huge amount of
storage, so it's not a solution. But you can rsync --inline your
snapshots in chrono
12 matches
Mail list logo
