From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sage Weil Subject: Re: Recursive directory accounting for size, ctime, etc. Date: Tue, 15 Jul 2008 14:51:56 -0700 (PDT) Message-ID: References: <20080715195333.GK21590@fieldses.org> <20080715204812.GD25803@fieldses.org> <20080715214442.GA9222@shareable.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "J. Bruce Fields" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, ceph-devel@lists.sf.net To: Jamie Lokier Return-path: Received: from cobra.newdream.net ([66.33.216.30]:34841 "EHLO cobra.newdream.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751306AbYGOVv5 (ORCPT ); Tue, 15 Jul 2008 17:51:57 -0400 In-Reply-To: <20080715214442.GA9222@shareable.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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