From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f178.google.com ([209.85.223.178]:33607 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751904AbbC2MbL (ORCPT ); Sun, 29 Mar 2015 08:31:11 -0400 Received: by iecvj10 with SMTP id vj10so99161028iec.0 for ; Sun, 29 Mar 2015 05:31:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20150323232212.GL31762@carfax.org.uk> Date: Sun, 29 Mar 2015 08:31:10 -0400 Message-ID: Subject: Re: btrfs dedup - available or experimental? Or yet to be? From: Rich Freeman To: Kai Krakow Cc: Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sun, Mar 29, 2015 at 7:43 AM, Kai Krakow wrote: > > With the planned performance improvements, I'm guessing the best way will > become mounting the root subvolume (subvolid 0) and letting duperemove work > on that as a whole - including crossing all fs boundaries. > Why cross filesystem boundaries by default? If you scan from the root subvolume you're guanteed to traverse every file on the filesystem (which is all that can be deduped) without crossing any filesystem boundaries. Even if you have btrfs on non-btrfs on btrfs there must be some other path that reaches the same files when scanning from subvolid 0. -- Rich