From: Sage Weil <sage@newdream.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ceph-devel@lists.sf.net
Subject: Re: Recursive directory accounting for size, ctime, etc.
Date: Tue, 15 Jul 2008 14:51:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0807151446140.1976@cobra.newdream.net> (raw)
In-Reply-To: <20080715214442.GA9222@shareable.org>
On Tue, 15 Jul 2008, Jamie Lokier wrote:
> J. Bruce Fields wrote:
> > I just wonder how one would explain to users (or application writers)
> > why changes to a file are reflected in the parent's rctime in one case,
> > and not in another, especially if the primary link is otherwise
> > indistinguishable from the others. The symptoms could be a bit
> > mysterious from their point of view.
>
> Btw, what happens when the primary link is deleted? Does another link
> become the primary link?
Yeah. It's initially moved to a hidden directory (along with
open-but-unlinked files), and then moved back into the hierarchy the next
time a remote link is used.
sage
next prev parent reply other threads:[~2008-07-15 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 18:28 Recursive directory accounting for size, ctime, etc Sage Weil
2008-07-15 19:47 ` Andreas Dilger
2008-07-15 20:26 ` Sage Weil
2008-07-15 19:53 ` J. Bruce Fields
2008-07-15 20:41 ` Sage Weil
2008-07-15 20:48 ` J. Bruce Fields
2008-07-15 21:16 ` Sage Weil
2008-07-15 22:45 ` J. Bruce Fields
2008-07-15 21:44 ` Jamie Lokier
2008-07-15 21:51 ` Sage Weil [this message]
2008-07-15 21:56 ` Jamie Lokier
2008-08-05 18:26 ` Pavel Machek
2008-08-08 13:11 ` John Stoffel
2008-08-08 23:32 ` Sage Weil
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=Pine.LNX.4.64.0807151446140.1976@cobra.newdream.net \
--to=sage@newdream.net \
--cc=bfields@fieldses.org \
--cc=ceph-devel@lists.sf.net \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).