All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Norbert Scheibner <scno@gmx.net>
Cc: "Klaus A. Kreil" <klaus.kreil@univie.ac.at>, linux-btrfs@vger.kernel.org
Subject: Re: cross-subvolume cp --reflink
Date: Sun, 01 Apr 2012 22:27:38 +0300	[thread overview]
Message-ID: <4F78AC2A.8050408@gmail.com> (raw)
In-Reply-To: <20120401183912.61760@gmx.net>

On 1/4/2012 9:39 =CE=BC=CE=BC, Norbert Scheibner wrote:
>> On: Sun, 01 Apr 2012 19:22:42 +0200"Klaus A. Kreil" wrote
>
>> I am just an interested reader on the btrfs list and so far have nev=
er
>> posted or sent a message to the list, but I do have a dedup bash scr=
ipt
>> that searches for duplicates underneath a directory (provided as an
>> argument) and hard links identical files.
>>
>> It works very well for an ext3 filesystem, but I guess the basics sh=
ould
>> be the same for a btrfs filesystem.
Thanks for the nice script, it works fine here!
I just added a du -sh "$1" line at the beginning and end to see how muc=
h=20
space it saves.
>
> Everyone feel free to correct me here, but:
> At the moment there is a little problem with the maximum number of ha=
rd links in a directory. So I wouldn't use them wherever possible to av=
oid any thinkable problems in the near future.
>
> Plus to hard link 2 files means, that change one file You change the =
other one. It's something You either don't want to happen or something,=
 which could be done in better ways. The cp --reflink method on a COW-f=
s is a much smarter method.
thats true, cp --reflink is much better. Also am I wrong that btrfs has=
=20
a limitation on the number of hard links that can only be fixed with a=20
disk format change?
>
> Plus hard links across subvolumes do match the case of hard links acr=
oss devices on a traditional fs, which is forbidden.
>
> Plus hard links In my opinion should really be substituted by soft li=
nks, because hard links are not transparent at the first sight and can =
not be copied as it.
>
> So no, I'd rather want the patch to allow cross-subvolume cp --reflin=
k in the kernel and I will wait for that to happen.
>
> Greetings
>     Norbert

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-01 19:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 15:27 cross-subvolume cp --reflink Norbert Scheibner
2012-04-01 15:30 ` Konstantinos Skarlatos
2012-04-01 16:41   ` Norbert Scheibner
2012-04-01 16:45     ` Konstantinos Skarlatos
2012-04-01 17:07       ` Norbert Scheibner
2012-04-01 17:19         ` Konstantinos Skarlatos
2012-04-01 18:11           ` Norbert Scheibner
2012-04-01 19:42             ` Konstantinos Skarlatos
     [not found]         ` <4F788EE2.4010105@univie.ac.at>
2012-04-01 18:39           ` Norbert Scheibner
2012-04-01 19:27             ` Konstantinos Skarlatos [this message]
2012-04-02  8:29               ` David Sterba
2012-04-01 15:42 ` Jérôme Poulin
2012-04-28 23:53   ` Hubert Kario
2012-04-29 20:05     ` Norbert Scheibner
2012-08-17  4:20       ` james northrup
2012-08-17  5:20         ` Marc MERLIN
2012-08-19  5:08           ` Mitch Harder
2012-08-19  6:43             ` Marc MERLIN
     [not found]       ` <CAPkEcwgSZ8umbFeuZ-fQAFAprBubL58eFSf4TQ=Z13ks8i9DOQ@mail.gmail.com>
2012-08-20 18:08         ` Jérôme Poulin
2012-08-21  0:20           ` james northrup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F78AC2A.8050408@gmail.com \
    --to=k.skarlatos@gmail.com \
    --cc=klaus.kreil@univie.ac.at \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=scno@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.