From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: hard links across snapshots/subvolumes are actually a bad idea.
Date: Thu, 25 Nov 2010 14:48:28 +0100 [thread overview]
Message-ID: <4CEE692C.4080409@wpkg.org> (raw)
> I'm just not certain whether bcp works across subvolumes or not.
It doesn't seem to work across subvolumes.
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2010-11-25 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 13:48 Tomasz Chmielewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-24 22:07 hard links across snapshots/subvolumes are actually a bad idea David Nicol
2010-11-24 22:47 ` Erik Logtenberg
2010-11-24 23:29 ` Gordan Bobic
2010-11-24 23:57 ` cwillu
2010-11-25 0:18 ` Gordan Bobic
2010-11-25 0:31 ` cwillu
2010-11-25 8:00 ` Gordan Bobic
2010-11-25 9:36 ` 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=4CEE692C.4080409@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.