-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> It does, but the code has been in testing -suse and on the reiserfs
> list. This dooesn't mean data=ordered is perfect, but it's not quite
> day one either. I can switch the default back, but I'd rather have a
> trial by fire ;-)
Oh please not, just have a look at german newsgroups, there are real flamewars
about the stability of reiserfs. Everytime someone has a disk problem and a
reiserfs partion is affected by it, then there are more than a dozen answers
that its the fault of reiserfs. PLEASE, don't prove them right.
The last example is less than 2 weeks old (see subject "Crash --> ReiserFS
screwed up"), since Tim told on de.comp.os.unix.linux.misc that badblocks
reported that his harddisk is ok, I told him to ask here. By his post here,
one could see, that his harddisk or ide connection was not so fine as he
previously stated, so we continued to discuss in on
de.comp.os.unix.linux.misc and finally could solve the problem by setting a
lower udma speed.
However, besides of the proper discussion about the ide problem, there was a
'sub' thread with about 50 messages about the instability of reiserfs!!!
IMHO, almost all of the reported reiserfs problems are due to hardware errors,
but some are also due to patches which are enabled by default by
distributions like Suse or RedHat.
Just another personal example: Before my first post on this list, I didn't
know much about reiserfs, only that it handles system crashes better then
ext2 and that I can have file >2GB on 2.4.x. So I went ahead and replaced
every ext2 partition by reiserfs on the next Suse-7.0 installation. Then the
problems arrived, since I also exported everything via nfs and since the Suse
installer had choosen the 3.5 format without warning me about it, I run into
serious trouble and reverted everything that was exported by nfs back to ext2
for the next 2 years.
Even until Suse-7.3, the 3.5 format was the default from the Suse patched
mkreiserfs, without warning the user about it.
I think -mm kernel are experimental and can include experimental stuff, but
later in the main line everything that is experimental for the 3.6 format
should be disabled by default. I wouldn't mind if it becomed included, but
marked as experimental, so that one can easily wouldn't include it in a
server kernel.
Sorry for my long (slightly off topic) message,
Bernd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAYiw0C8BUnAF+ydYRApYMAJ9KW83lYY9TJ7oIwiLmHwlub/cf3ACeIaSL
dPX8EuqpIH2kvMh+JPTrRGA=
=m5ez
-----END PGP SIGNATURE-----
