[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080715224535.GB28739@fieldses.org>
Date: Tue, 15 Jul 2008 18:45:35 -0400
From: "J. Bruce Fields" <bfields@...ldses.org>
To: Sage Weil <sage@...dream.net>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
ceph-devel@...ts.sf.net
Subject: Re: Recursive directory accounting for size, ctime, etc.
On Tue, Jul 15, 2008 at 02:16:45PM -0700, Sage Weil wrote:
> On Tue, 15 Jul 2008, 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.
>
> Yes. I'm not sure it can really be avoided, though. I'm trying to lift
> the usual restriction of having to predefine what the
> volume/subvolume/qtree boundary is and then disallowing links/renames
> between then. When all of a file's links are contained within the
> directory you're looking at (i.e. something that might be a subvolume
> under that paradigm), things look sensible. If links span two directories
> and you're looking at recursive stats for a dir containing only one of
> them, then you're necessarily going to have some weirdness (you don't want
> to double-count).
Yeah, there's no clear right answer--that's partly why I was curious
about rctime specifically.
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists