« RDS queued for Linux kernel inclusion! | Main | Converged fabric does not mean TCP/IP everywhere »

Filesystem testing

SSD’s, Journaling, and noatime/relatime | Thoughts by Ted

The chief mechanism for benchmarking Linux filesystems seems to be operations on the Linux kernel's source tree.

This seems to me a dangerous over-optimization for kernel developer-centric usage. What if people want to put files other than the Linux kernel source on their disk? Other use cases are completely untested!

OK I'm being facetious.

Dumb questions: Are snapshotted filesystems like btrfs, and version control systems like git two things that could converge, or do they just look like they could converge and really never will?



TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/10414

Comments (4)

A lot of people thought filesystems and databases would converge (WinFS,Reiser4) too. I don't think we will see anything mainstream here for at least another 5-10 years though. Oddly, IBM has pulled this off pretty well since the late '80s with what is currently called 'i OS'.

Mainly I see a COW FS like Btrfs being a compliment to userspace datastores like Git or a DB. Fast, almost free snapshots can be taken at will. Same idea as people using LVM to do hot DB backups.

I guess it all boils down to user space moves faster and is safer than kernel. The usual benefit of convergence is speed and access to raw hardware, but we always have to question the cost.

Matthew W. S. Bell:

A snapshotting filesystem could be used as a store for a VCS, but wouldn't be equivalent to one

Doug Newcomb:

If you want to give a filesystem a workout, aggregate lidar point data files and create raster data from the vector files. Also try reprojecting multigigbyte Erdas Imagine format data.

1. Not while POSIX rules. If you're storing your data with full versioning, including edit-merges, conflict resolution, and patch generation, then IMHO you've gone far beyond anything that can reasonably be shoehorned into the POSIX model. Maybe the Linux VFS will grow some very impressive new features, or maybe we'll have to wait for microkernels that never arrive.

2. The Sugar user interface (sugarlabs.org), originally developed for OLPC, is designed to do exactly this, by replacing the "file manager" in the UI with a version-aware object storage system that supports this sort of revision control. Currently this sort of versioning exists only in mockups and pre-alphas, so don't hold your breath.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on March 4, 2009 7:36 PM.

The previous post in this blog was RDS queued for Linux kernel inclusion!.

The next post in this blog is Converged fabric does not mean TCP/IP everywhere.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle