From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: revisiting "Hard link across subvolumes"
Date: Sun, 10 Oct 2010 21:53:59 +0200 [thread overview]
Message-ID: <4CB219D7.4080908@wpkg.org> (raw)
>> The link across subvolumes is not allowable. In the beginning it was
>> possible, but that was source of bugs. See the thread "Hard link across
>> subvolumes"
>>
>> http://www.mail-archive.com/linux-btrfs <at> vger.kernel.org/msg03286.html
Similar for cp --reflink across subvolumes - also won't work.
If btrfs is to support deduplication one day, it has to work across
subvolumes - otherwise, it won't be very useful.
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2010-10-10 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 19:53 Tomasz Chmielewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-09 7:52 revisiting "Hard link across subvolumes" David Nicol
2010-10-09 13:44 ` Goffredo Baroncelli
2010-10-09 19:26 ` David Nicol
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=4CB219D7.4080908@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
/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.