From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Some questions about Reiser4 Date: Sat, 10 May 2003 20:22:24 +0400 Message-ID: <3EBD2740.7060501@namesys.com> References: <000c01c30b6a$d7f12590$0200a8c0@xpstation> <3EAA8008.4020401@namesys.com> <000b01c30bf7$bf47b080$0200a8c0@xpstation> <3EAA98EB.3040702@namesys.com> <001e01c30c03$740efb80$0200a8c0@xpstation> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <001e01c30c03$740efb80$0200a8c0@xpstation> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Fred -- Speed Up -- Cc: reiserfs-list@namesys.com Fred -- Speed Up -- wrote: >So, what you call "inodes" within Reiser4 are stat data (last access time, >right, ...) and a way to find the files's data (not directly the physical >adress, but a piece of information determining exactly the file), mainly for >VFS compatibility purposes. Are 'inodes' converted to keys when Reiser4 gets >them from VFS, or do they represent a physical adress on the disk ? > We don't call them inodes, we call them stat data, and stat data are stored in the tree where they can be found by their key like everything else. > >Now I'm going to reformulate the question I asked you about big file storage >: >Big files need more than one extent. But according to the documentation, >there seems to be only one pointer associated to each file. So how can you >point out multiple extents necessary to store big files, using extent >pointers in the tree ? > >Be sure I'm awaiting the great Hans and his core dev team ;-) > >Fred > > > > > -- Hans