Eric Schrock <[EMAIL PROTECTED]> wrote:
> Yes, there are multi-petabyte systems out there. Though you may
> disagree, I personally don't think its unreasonable to expect such
> filesystems to pass the 16 exabyte range within the next 20 years.
> Neither did the ZFS designers, hence the 128-bit ca
On Wed, Oct 12, 2005 at 09:28:52PM +0100, Peter Tribble wrote:
>
> How far has this been tested?
>
> I know I tested it, just to see how well it worked, about 6 months ago.
> On a fairly small machine, 10,000 filesystems was starting to get
> "interesting".
>
> I just wonder, seeing as we would
[EMAIL PROTECTED] wrote:
But since the typical filesystem only allocates around 25% of inodes
before it fills up, it would be more like a full 100TB before you get to
such huge inode numbers, with filesizes staying what they are.
Okay - I wasn't clear on if inodes were allocated sequentially or
On Wed, 2005-10-12 at 18:58, Eric Schrock wrote:
>
> Yes, unfortunately this is the case. But it will only affect
> filesystems with more than 3 billion files on them. There's not much
> that can be done about this - if you want to have more than 2^32 files,
> you need more than 32 bits to uniqu
On Wed, 2005-10-12 at 17:41, Sarah Jelinek wrote:
> Daniel,
>
> To clear up a misconception about MTB UFS. The maximum density of inodes
> that can be in a MTB UFS filesystem is 1 inode per megabyte of space.
> This does not mean that a megabyte of space is used for every file. It
> simply mean
>Well at least it won't require a Dysan Sphere sized data center! :-)
You do realize when we go to quantum computing, the topology of the disk
storage is no longer an issue, right?
This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential,
On Wed, 12 Oct 2005, Bill Sommerfeld wrote:
> and, unless my math is off by a few orders of magnitude, a 2^128-block
> pool at current storage densities would require a data center of roughly
> the scale of Larry Niven's "Ringworld"...
Well at least it won't require a Dysan Sphere sized data cent
Sarah Jelinek schrieb:
Daniel,
To clear up a misconception about MTB UFS. The maximum density of inodes
that can be in a MTB UFS filesystem is 1 inode per megabyte of space.
This does not mean that a megabyte of space is used for every file. It
simply means you cannot have more than a million
On Wed, 2005-10-12 at 12:58, Eric Schrock wrote:
> There is little expectation that anyone will be able to fill a ZFS
> filesystem, ever[2]. There is reasonable expectation, however, that in
> the next 10-20 years we will pass the 64-bit limit for some use cases.
and, unless my math is off by a f
Yes, there are multi-petabyte systems out there. Though you may
disagree, I personally don't think its unreasonable to expect such
filesystems to pass the 16 exabyte range within the next 20 years.
Neither did the ZFS designers, hence the 128-bit capability.
Note that we are talking about filesys
On Wed, Oct 12, 2005 at 10:34:49AM -0700, Alan Coopersmith wrote:
>
> So does this mean 32-bit apps that didn't need to be largefile aware in
> the past because they only touched small files now need to become largefile
> aware to avoid problems with ZFS if they call stat()?(Granted, they've
>
Eric Schrock <[EMAIL PROTECTED]> wrote:
> There is little expectation that anyone will be able to fill a ZFS
> filesystem, ever[2]. There is reasonable expectation, however, that in
> the next 10-20 years we will pass the 64-bit limit for some use cases.
Do you believe that there currently alrea
>Eric Schrock wrote:
>> ZFS inode numbers are 64 bits. The current implemenation restricts this
>> to a 48-bit usable range, but this is not an architectural restriction.
>> Future enhancements plan to extend this to the full 64 bits.
>>
>> 32-bit apps that attempt to stat() a file whose inode n
Eric Schrock wrote:
ZFS inode numbers are 64 bits. The current implemenation restricts this
to a 48-bit usable range, but this is not an architectural restriction.
Future enhancements plan to extend this to the full 64 bits.
32-bit apps that attempt to stat() a file whose inode number is greate
ZFS inode numbers are 64 bits. The current implemenation restricts this
to a 48-bit usable range, but this is not an architectural restriction.
Future enhancements plan to extend this to the full 64 bits.
32-bit apps that attempt to stat() a file whose inode number is greater
than 32 bits will re
Daniel,
To clear up a misconception about MTB UFS. The maximum density of inodes
that can be in a MTB UFS filesystem is 1 inode per megabyte of space.
This does not mean that a megabyte of space is used for every file. It
simply means you cannot have more than a million or so files per
teraby
Daniel Rock <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] schrieb:
> >>ZFS is a 128 bit filesystem, isn't it?
> >
> > Depends on whether it's large file aware or not, I'd say.
> >
> > (the ino field in stat64 is 64 bits)
>
> So to fully utilize a ZFS file system the average file size has to be
[EMAIL PROTECTED] schrieb:
ZFS is a 128 bit filesystem, isn't it?
Depends on whether it's large file aware or not, I'd say.
(the ino field in stat64 is 64 bits)
So to fully utilize a ZFS file system the average file size has to be 16 EB?
People are already moaning today that on MT-UFS the a
[EMAIL PROTECTED] wrote:
> >Now what happens to a 32 bit application that calls stat(2)
> >on a file that uses an inode number that is outside the
> >32 bit scope. Whill this cause stat(2) to return a EOVERFLOW
> >condition in this case when stat(2) is called from a 32 bit
> >application?
>
> Dep
>ZFS is a 128 bit filesystem, isn't it?
>
>So I hope it uses 128 bit inode numbers too.
>but it should at least use 64 bit for inode numbers.
>
>Now what happens to a 32 bit application that calls stat(2)
>on a file that uses an inode number that is outside the
>32 bit scope. Whill this cause
ZFS is a 128 bit filesystem, isn't it?
So I hope it uses 128 bit inode numbers too.
but it should at least use 64 bit for inode numbers.
Now what happens to a 32 bit application that calls stat(2)
on a file that uses an inode number that is outside the
32 bit scope. Whill this cause stat(2) t
21 matches
Mail list logo
