[Top] [All Lists]

Re: Filestreams (and 64bit inodes)

To: Timothy Shimmin <tes@xxxxxxx>
Subject: Re: Filestreams (and 64bit inodes)
From: Richard Scobie <richard@xxxxxxxxxxx>
Date: Wed, 11 Jun 2008 11:09:12 +1200
Cc: xfs@xxxxxxxxxxx
In-reply-to: <484DDDB3.70000@xxxxxxx>
References: <484B15A3.4030505@xxxxxxxxxxx> <484CA425.3080606@xxxxxxxxxxx> <484DDDB3.70000@xxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2
Timothy Shimmin wrote:

BTW, Sam Vaughan wrote some tutorial notes on the allocator and in particular
filestreams which I've pasted below:
(I thought it might be here:
 http://oss.sgi.com/projects/xfs/training/ but I can't see it
 in the allocator lab and slides).

I did actually find an entry for filestreams in slide 6.

While there I also found the information on 64bit inodes.

My filesystem is 9.6TB and could well end up with a large quantity of 1-15MB files stored and the statement:

"Operating system interfaces and legacy software products often mandate the use of 32 bit inode numbers even on systems that support 64 bit inode numbers."

makes me wonder how common this still is in practice - the slide was written in 2006)?

My initial preference would be to go with 64 bit inodes for performance reasons, but as one cannot revert the fs back to 32 bit inodes once committed, I am somewhat hesitant.

Or am I worrying unecessarily about the negative impact of 32 bit inodes, given 9.6TB full of 1 to 15MB files?



<Prev in Thread] Current Thread [Next in Thread>