Hi! Der Herr Hofrat wrote:
>>With ext2fs I lost sometimes very important source code files >>- this shouldn't happen with ReiserFS (and ext3fs) ... >> > > That can happen with reiserfs aswell - Reiserfs will not fuss at you at bootup > but if you have a large filesystem then you will see random 0 size files apear > after a few hard-lockups (not rtl related you can get this from "normal" kernel > lockups or powerfailure aswell) - the bad thing about reiserfs is that you will > not notice it until you happen to stumble over the file when you need it. That happened to me with ext2 ... When you must answer some 100 times (y) to 'delete inode' you will press and hold the enter key ... - now I have no screensaver, ... ;-) But a journaling filesystem gives me at least the chance to save my data and to start afterwards the realtime program. > This is quite well reprocuable on high load fs-trafic - mount a system via nfs > (100Mbit) and cp -a /NFS_SRC /NEW_LOCAL_DIR , lockup the system and reiserfs > will not be able to balance the trees any more -> files are corupt or lost. > > The other problem with reiserfs (havent tried ext3) is that during tree > balancing the fs stalls thus if you are doing heavy data loging you will > loos data. That is a problem that also botheres other heavy loging appps > like network logers on reiserfs (argus, etc.) Good data logging isn't the playground of reiser. I read some status items about ext3 ... Semms to work but very 'beta'. http://beta.redhat.com/index.cgi?action=ext3 The advantage seems to be the easy upgrade from ext2 The disadvantage: speed ;-( And as I read - no balanced trees (that's maybe an advantage). I installed it 2 weeks ago with Redhat 7.2 - no problems so far (but this workstation isn't really used -> no tests ...) Oh, I forgot: RPMs and SRPMs ... nothing for a Debian user ;-) > Also you still need to have the boot partition on ext2 (one can mount it ro > though) I think that's no more true ... I'm booting from a Reiser partition ... (but that's gettin' off-topic) Is there one filesystem that's "best for realtime"? I guess realtime means always: filesystem (and disk writes/reads) are Linux part -> lowest priority ... If there's a heavy load realtime thing -> no filesystem operations. Stefan -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
