From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: davidnicol@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BUG: Link from sub volume, then remove the subvolume -> wrong link
Date: Thu, 17 Dec 2009 09:00:04 +0900 [thread overview]
Message-ID: <4B297484.8010408@jp.fujitsu.com> (raw)
In-Reply-To: <934f64a20912150931q46aea2eer12bc907ecb0137fc@mail.gmail.com>
Supporting it may be not so confusing, but it may need
a little format change to record tree and inode number.
I think it's not so acceptable.
Regards,
taruisi
(2009/12/16 2:31), David Nicol wrote:
> how about supporting the operation, as a feature, and allowing a file
> to be in two different subvolumes at the same time? Would that make
> the link semantics too confusing?
>
prev parent reply other threads:[~2009-12-17 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 19:54 BUG: Link from sub volume, then remove the subvolume -> wrong link Goffredo Baroncelli
2009-12-12 0:24 ` TARUISI Hiroaki
2009-12-12 13:54 ` Goffredo Baroncelli
2009-12-12 18:39 ` Andy Lutomirski
2009-12-13 23:42 ` TARUISI Hiroaki
2009-12-14 18:43 ` Andrew Lutomirski
2009-12-15 0:15 ` TARUISI Hiroaki
2009-12-15 4:04 ` Andy Lutomirski
2009-12-15 17:31 ` David Nicol
2009-12-17 0:00 ` TARUISI Hiroaki [this message]
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=4B297484.8010408@jp.fujitsu.com \
--to=taruishi.hiroak@jp.fujitsu.com \
--cc=davidnicol@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox