[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090108043824.GA16728@ioremap.net>
Date: Thu, 8 Jan 2009 07:38:24 +0300
From: Evgeniy Polyakov <zbr@...emap.net>
To: Daniel Phillips <phillips@...nq.net>
Cc: Jamie Lokier <jamie@...reable.org>, tux3@...3.org,
Theodore Tso <tytso@....edu>, linux-fsdevel@...r.kernel.org,
"Justin P. Mattock" <justinmattock@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Tux3] Tux3 report: A Golden Copy
Hi Daniel.
On Wed, Jan 07, 2009 at 06:50:59PM -0800, Daniel Phillips (phillips@...nq.net) wrote:
> Suppose a file delete event is sent, the external indexer dutifully
> deletes its index entry for the file, then the machine crashes without
> completing the delete transaction. On reboot, the file still exists
> but it has leaked from the index. Ideas?
Sending delete event when delete is completed?
> > There was an extension to inotify posted a few months ago to do this.
> > Additional events when something becomes persistent.
>
> Do you have a pointer?
Somthing like that
http://lkml.org/lkml/2008/11/25/272
As of VFS s file-system indexer: what if vfs could provide an interface
to the lower-level FS to get the event flow which could be used by the
userspace the same way it reads the file, and if no such operation is
upported by the filesystem falback to the whole dir rescan...
--
Evgeniy Polyakov
--
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