Slashdot Mirror
Reaching Beyond Two-Terabyte Filesystems
Jeremy Andrews writes: "Peter Chubb posted a patch to the lkml, with which he's now managed to mount a 15 terabyte file (using JFS and the loopback device). Without the patch, Peter explains, "Linux is limited to 2TB filesystems even on 64-bit systems, because there are various places where the block offset on disc are assigned to unsigned or int 32-bit variables."
Peter works on the Gelato project in Australia. His efforts include cleaning up Linux's large filesystem support, removing 32-bit filesystem limitations. When I asked him about the new 64-bit filesystem limits, he offered a comprehensive answer and this interesting link. The full thread can be found here on KernelTrap.
Reaching beyond terabytes, beyond pentabytes, on into exabytes. I feel this sudden discontent with my meager 60 gigabyte hard drive..."
If all this should have a reason, we would be the last to know.
Aside from all sorts of quantum fiddly bit problems, I wonder just how long it will be before we can store the state of every neuron in a brain (doesn't have to be human, at least not at first) on a hard drive.
Of course, then what would you do with it?
AMCGLTD.COM. Where cats, science fictio
Petabytes, please!
what is that, 5 bytes? ;-P
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Keep it up guys - until they create some sort of 'Linux kernel mailing list' the Slashdot front page is my only source for this information.
26^3 = 9 x 10^18 = 9 exabytes
check out the feature list.
but I worry about other data types.
For example, I grumple at the MS stupidity of putting all datafiles into one large container file in a database base under Access in Windows. Which is why I never use it. I prefer discrete files. If one gets hosed, then it is easier to fix.
obviously a database that is that big would run into other performance issues as well. Some of which is handled by moore's law, and some of which isn't.
for similar reasons I tend to divided my drive into various partitions, regardless of which OS I use.
"It is a greater offense to steal men's labor, than their clothes"
Danny.
I have written over 900 book reviews
For those who wish to communicate with the rest of the world, the following calculations actually make sense:
For the uninitiated, these terms are described here
Even accounting for your typographical error, 2^63 != 9 * 10^18 (9223372036854775808 != 9000000000000000000)
Reaching beyond terabytes, beyond pentabytes, on into exabytes
Woohoo! A filesytem on a tape drive, that's what I need.
When information is power, privacy is freedom.
Looks like we'll have to come up with a different naming scheme. Someone's already trademarked the exabyte.
Couldn't it weaken the trademark to have Western Digital or Seagate making a '9 exabyte' hard drive? Or HP or Sony making an 'exabyte-class' tape drive? Wouldn't a judge find (in favor of Exabyte) that the consumer would easily be confused?
*The USPTO are idiots.*
Give me my freedom, and I'll take care of my own security, thank you.
In other words when you try to save a file to lzipFS it might as well return, "yeah" immediately. You tell lzipFS to fsync() and it'll return "yeah" immediately
class lzipFS { /* what we save will be lossy so, what's the point? */
.....
long int fsync() {
// cache->doflush();
return YEEEEAH_FSYNC_SUCCESFUL;
.....
}}
A caveman dreams of being us, the incalculable power and riches. We dream of being Q, then what?