On 6/12/13 10:56 PM, Anand Jain wrote: > > > Per wiki an idea seems to maintain same code (probably > as much as possible) between btrfs-progs and btrfs > > There must have been a/few critical advantage, but > what are they ? > > Thanks, Anand
Because they work with the same on-disk structures, and need to perform many of the same tasks. So using the same code base means bugs get fixed once, features get written once, there is built-in consistency, more coverage, etc. I was just looking at an ext4 bug tonight where offline vs. online resize result in different filesystem images. In one case it leads to a bug, in the other it doesn't. The complex resize code is implemented twice, and implemented differently. Less code is good. Consistency is good. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
