Bernd Eckenfels wrote:
In article <[email protected]> you wrote:I believe that on 64 bit platforms, Linux has a 64 bit clean VFS. Python says 2**64 is 18446744073709551616, and that's roughly:18,446,744,073,709,551,616 bytes 18,446,744,073,709 megs 18,446,744,073 gigs 18,446,744 terabytes 18,446 ... what are those, pedabytes (petabytes?) 18 zetabytes
There you go. I deal with this a lot so, those are the names. Linux is currently limited to 16 TB per VFS mount point, it's all mute, unless VFS gets fixed. mmap won't go above this at present. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: what is our answer to ZFS?
- From: Bill Davidsen <[email protected]>
- Re: what is our answer to ZFS?
- From: Christoph Hellwig <[email protected]>
- Re: what is our answer to ZFS?
- References:
- Re: what is our answer to ZFS?
- From: Bernd Eckenfels <[email protected]>
- Re: what is our answer to ZFS?
- Prev by Date: Re: 2.6.14.2 detects only one processor (out of 2)
- Next by Date: Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Previous by thread: Re: what is our answer to ZFS?
- Next by thread: Re: what is our answer to ZFS?
- Index(es):
 |