Linked by Rahul on Sat 18th Oct 2008 11:29 UTC
Linux While Ext4 was originally merged in 2.6.19, it was marked as a development filesystem. It has been a long time coming but as planned, Ext4dev has been renamed to Ext4 in 2.6.28 to indicate its level of maturity and paving the way for production level deployments. Ext4 filesystem developer Ted Tso also endorsed Btrfs as a multi-vendor, next generation filesystem and along with the interest from Andrew Morton, Btrfs is planned to be merged before 2.6.29 is released. It will follow a similar development process to Ext4 and be initially marked as development only.
E-mail Print r 18   46 Comment(s)
Thread beginning with comment 334239
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Interesting!
by Morin on Mon 20th Oct 2008 09:08 UTC in reply to "Interesting!"
Member since:

But what kind of information does the file system have that helps to fix flipped bits? To me this rather looks like an ideal candidate for an error-correcting code at the lowest (sector) level.

Reply Parent Score: 2

RE[2]: Interesting!
by Kebabbert on Mon 20th Oct 2008 10:35 in reply to "RE: Interesting!"
Kebabbert Member since:

Yes, that is also a good alternative. The point is, the IO card should not manage the error correction. It should be done somewhere in the filesystem or so.

Reply Parent Score: 2

RE[3]: Interesting!
by Morin on Mon 20th Oct 2008 11:35 in reply to "RE[2]: Interesting!"
Morin Member since:

Again: Why? Error correction is a simple but time-consuming task that can easily be done by the disk hardware (i.e. a co-processor). There's no point in moving it to the filesystem layer - that would hurt performance because then the CPU had to do it, and not bring any advantage (at least I cannot see any advantage).

Edited 2008-10-20 11:39 UTC

Reply Parent Score: 2