Benno Senoner writes:
 > "Stephen C. Tweedie" wrote:
 > >
 > > Exactly.  It keeps a record of in-progress filesystem operations so
 > > that entire complex operations, such as renames, always complete
 > > atomically even if you reboot half-way through.  It eliminates the
 > > need for an fsck at reboot.
 >
 > I plan to make some multimedia workstations which plays big audio/video
 > files,
 > from a soft-RAID array.
 > but actually the customer , in the worst case (in case of an fsck) must
 > turn on the power of the machine 30-60min (for a 90% full 70GB array)
 > before actual usage.
 > In my case the machines can not remain powered up all the time, because
 > the machines will be used for presentations at different locations.

I'm new to raid discussion.  Why would you expect a 60 minute fsck
everytime?  Would the boot up not skip that if the shutdown was clean?
Journaling seems like a complicated solution to save the time of an
occassional fsck.  Am I missing the obvious here?

Regards,
Billy
--
Rhino Engineering
Linux Solution Provider
[EMAIL PROTECTED]

Reply via email to