From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 450E31381F4 for ; Tue, 14 Aug 2012 17:52:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68448E08B1; Tue, 14 Aug 2012 17:52:06 +0000 (UTC) Received: from mx1.hadt.biz (sil.hadt.biz [5.9.16.100]) by pigeon.gentoo.org (Postfix) with ESMTP id 07972E002C for ; Tue, 14 Aug 2012 17:45:16 +0000 (UTC) Received: from [192.168.255.100] (p5DCC7EFD.dip.t-dialin.net [93.204.126.253]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.hadt.biz (Postfix) with ESMTPSA id 5A3CA40037 for ; Tue, 14 Aug 2012 19:45:16 +0200 (CEST) Message-ID: <502A8EAC.7060700@hadt.biz> Date: Tue, 14 Aug 2012 19:45:16 +0200 From: Michael Hampicke User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120722 Thunderbird/14.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Fast file system for cache directory with lot's of files References: <5029114E.8070402@admin-box.com> <502A0AA2.9030607@admin-box.com> In-Reply-To: <502A0AA2.9030607@admin-box.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 617263da-92cd-4c01-af7e-40d0b6f560dc X-Archives-Hash: 7df83b2b2f6484262404f82a621115b3 Am 14.08.2012 10:21, schrieb Daniel Troeder: > On 13.08.2012 16:53, Michael Hampicke wrote: >> 2012/8/13 Daniel Troeder > 3rd thought: purging old files with "find"? your cache system should >> have some kind of DB that holds that information. >> 3: Well, it's a 3rd party application that - in theory - should take >> care of removing old files. Sadly, it does not work as it's supposed to >> be, While time passes the number of orphans grow :( > There is also the possibility to write a really small daemon (less than > 50 lines of C) that registers with inotify for the entire fs and > journals the file activity to a sqlite-db. > > A simple sql-query from a cron/bash script will then give you all the > files to delete with paths. > > It will probably be less work to write the daemon than to do 40 > fs-benchmarks - and the result will be the most efficient. > That is an interesting idea, but I have never used inotify on such a huge file base, I am not sure what impact that has in terms of cpu cycles being used. But I am going to try this on some snowy winter weekend :)