On Wed, Mar 11, 2009 at 9:22 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Not true. Beagle simply used a feature that was broken in reiser, perhaps because nobody before had used it. And guess what? Finally they found what was wrong in the kernel and corrected it. Nothing was broken on beagle. It is a confirmed reiserfs implementation bug.
Ok, I stand corrected. But, IF beagle wasn't forced as a default install, then that problem wouldn't have been such a problem. Like I just replied to Randall, Beagle wasn't ready to be in a released version of SuSE. It was pushed in just like KDE4 before it was stable(not ready - stable). Finding an fixing an unknown issue in reiser only helps that system, but having a useless and unused app be the problem isn't much better of a reason.
That was true previously, but not currently. I "love" that filesystem, but the current implementation is starting to break and fail on several places. For instance, I have external media (USB) formatted as reiserfs, and it gets corrupted every time I write to it from 11.0. So badly corrupted that it takes several hours to fsck and repair. It was fine under 10.3, and seems to work under 11.1.
I haven't noticed any issues like that, but I generally have my external media in FAT32/NTFS in order to use it with WinDoZe. Since USB is slow anyway, I've never been worried about using a faster fs on it.
I have more bugs reported against reiserfs :-(
And, since no one is bothering to maintain it very well, they may never get fixed. Maybe ext4 will live up to the hype. There are newer and more interesting fs's coming that will hopefully be worthwhile replacements for reiser. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org