Re: journaling filesystem

Matthias Urlichs (smurf@work.smurf.noris.de)
16 Jun 1997 10:50:18 +0200


yodaiken@chelm.cs.nmt.edu (Victor Yodaiken) writes:
>
> an inode lookup table in the FS. All changes can be done on
> free blocks and committed only when the FS is in a consistent
> state.

You cannot do all your changes in free blocks. That would trash file
system performance really fast (can you say "100% fragmentation"?).

There may not even _be_ a 'consistent' state on a busy file system that's
used, eg., for a database. There may literally be months without a single
second in which no transaction is outstanding and no blocks are queued for
writing. But that's a problem no file system can solve without help from
the application.

-- 
A businessman is a hybrid of a dancer and a calculator.
               -- Paul Valery
-- 
Matthias Urlichs         \  noris network GmbH  /  Xlink-POP Nürnberg 
Schleiermacherstraße 12   \   Linux+Internet   /   EMail: urlichs@noris.de
90491 Nürnberg (Germany)   \    Consulting+Programming+Networking+etc'ing
   PGP: 1024/4F578875   1B 89 E2 1C 43 EA 80 44  15 D2 29 CF C6 C7 E0 DE
       Click <A HREF="http://info.noris.de/~smurf/finger">here</A>.    42