A journaling filesystem writes a transaction log to disk, then does the
actual updating slightly later.  The idea is, if the system dies, the 
filesystem integrity can be preserved by reading the transaction log,
and deleting incomplete transactions at the time of the crash.  The
purpose is to be able to quickly and reliably recover from the type of
system crash that would result from a power outage, etc.

The reiserfs on Linux is pretty good, although I've found it to be 
slightly incompatible with a few things, like Win4Lin and I understand
there's some possibility of file-locking incompatibilities with Samba.  

Pat Wade mentioned something about UFS/softupdates on FreeBSD.  Is that 
a journaling filesystem?  Has anyone tried it out?

At 08:54 AM 3/12/2001 -0800, jakob <[EMAIL PROTECTED]> wrote:
>Downfalls to FreeBSD? Well, there's not much I don't like. About the only
>thing is I wish FreeBSD had a journaling FS, they need one desperately, to
>enter into certain server markets. FS-level ACLs would be cool, too, but I

Reply via email to