From: Nagy Zoltan Subject: metafs Date: Sat, 22 Mar 2008 14:27:54 +0100 Message-ID: <47E5095A.5050707@bteam.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: linux-fsdevel@vger.kernel.org Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:54447 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753291AbYCVN17 (ORCPT ); Sat, 22 Mar 2008 09:27:59 -0400 Received: from nuk.teteny.elte.hu ([157.181.96.2]) by mx2.mail.elte.hu with esmtp (Exim) id 1Jd3lE-0002Kl-JZ from for ; Sat, 22 Mar 2008 14:27:57 +0100 Received: from devel.teteny.bme.hu ([152.66.235.6]) by nuk.teteny.elte.hu with esmtp (Exim 3.36 #1 (Debian)) id 1Jd3lE-0004Nk-00 for ; Sat, 22 Mar 2008 14:27:48 +0100 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello all, sorry for the large posting - and for my intermediate english. the past few months i tried to figure out a better way to organize data, because in extereme conditions automatic/dynamic (re)organiziation would be very good to have - i recently found this paper, which i found very similar to this: http://bryanmills.net:8086/uploads/metafs/bmills-final.pdf i imagined a two sided approach to came up with an acceptable solution * object tagging: it is obvious that people can give very precise information to a given object, in this example i would take some papers [obj1] - filename: 'something1.pdf' type = "paper" filetype = "application/pdf" title = {Title1}, author = {Author1}, year = {2005}, [obj2] - filename: 'xasd1.XXXpdf' type = "paper" filetype = "pdf" title = {Title2}, author = {Author2}, year = {2005} [obj3] - filename: 'qqq.pdf' type = "paper" filetype = "pdf" title = {Title3}, author = {Author3}, /** year = {2005} no set **/ [obj4] - filename: 'asd.png' type = "image/png" filetype = "png" title = {Title2}, author = {Author2}, year = {2005} all this data is accessible thru extended attributes * layout rules the user must give some guidance - about in what way he want's to see those files in this example i will choose the following rules: x_node0 = _root_ x_node1 = {parent:x_node0} {entry:"paper", require:{type = "paper"}, unassigned:{collect,"unassigned"} } x_node2 = {parent:x_node1} {entry:"by_year"} x_node3 = {parent:x_node2} {entry:#year, type:collection, unassigned:{collect,"year-not-set"} x_node4 = {parent:x_node3} {entry:#author|'_'|#title, unassigned:{cascade} } i hope that this understandable the desired layout would be for those files: / /paper /paper/by_year /paper/by_year/2005 /paper/by_year/2005/Author1_Title1.pdf --> [obj1] /paper/by_year/2005/Author2_Title2.pdf --> [obj2] /paper/by_year/year-not-set/qqq.pdf --> [obj3] /unassigned/asd.png --> [obj4] and if someone adds some new rules x_node5 = {parent:x_node2} {entry:"by_author", type:collection, unassigned:{collect,"unknown-author"} x_node6 = {parent:x_node5} {entry:#title|'_'|#year } then the following nodes should appear /paper/by_author /paper/by_author/Author1/Title1_2003 --> [obj1] [...] the biggest power of this, that it is possible for an object to show up at many places dynamically. i think that this can be implemented as an 'overlay' (userland)filesystem, with some lightweight database help i know that algorithm for this kind of dynamic layout comes at a very high price - it is/and will be a problem, it will be a big challange to minimize it's impact on the overall performance - but for now, i think about a relativly 'slow' changing object set. what's the biggest problem with this? how could it be - more adaptive to user's needs - faster at runtime - i welcome tips for implementing it - the right way - ..or why should i forget it :) cheers, kirk