The days of the plain filesystems like FAT32 and ext2 seem to have past. Newer operating systems are offering journal, 64-bit filesystems, with features like supporting terrabytes of filesizes or attaching attributed meta-data in them. Today we are interviewing (in a given set of questions) the main people behind IBM's JFS, NameSys' ReiserFS and SGI's XFS. Read on about the status of their filesystems, their abilities and what they are aiming for the future.
Permalink for comment
To read all comments associated with this story, please click here.
Actually, you'll probably find that with modern hard drives, the time in which you can search the entire FS and simply examine each file is not very long anymore. That is why you make a "noindex" bfs volume for holding, say, your source trees. If I were to design a new filesystem today, I would leave _out_ indexing since that means you incur quite an overhead for day-to-day operations (and an increase in code complexity, of course) to gain "quick finding of files". Someone with a modern disk and, say, ext2fs, how long does it take to run a find command? (Genuine question, not a troll.)
Actually, you'll probably find that with modern hard drives, the time in which you can search the entire FS and simply examine each file is not very long anymore. That is why you make a "noindex" bfs volume for holding, say, your source trees. If I were to design a new filesystem today, I would leave _out_ indexing since that means you incur quite an overhead for day-to-day operations (and an increase in code complexity, of course) to gain "quick finding of files". Someone with a modern disk and, say, ext2fs, how long does it take to run a find command? (Genuine question, not a troll.)