On Sat, 18 Aug 2001, Federico Sevilla III wrote:
..
> It's not the fsck that is the matter here. It's whether your data is
> sent to disk on time or not. Try this:
I've tried that power-off trick on reiserfs. Screwed me once. For example,
edit /etc/lilo.conf then power-off the machine. When you turn the machine
back on, parang na-rollback yung pag-edit mo ng lilo.conf!!
Moral of the story: poor man's sync is still good to have =)
Note that even with a full-journaling filesystem (not just metadata
journal) this same behavior will still be seen: full-journaling (i.e.
logging) filesystems still cache the data for efficiency, so unless you
have a battery-backed cache.. you'll still lose some data.
Journaling does not guarantee no-data-loss, it guarantees filesystem
integrity. Those are two very different things.
In any case, the kernel bdflush runs every 30 seconds I believe, so "poor
man's sync" from cron is not really necessary.
--
Orlando Andico <[EMAIL PROTECTED]>
Mosaic Communications, Inc.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d(-) s: a-25 C++++ UBLSI++++$ P+++ L+++>++++ E- W++ N(+)
o K? w O-- M- !V PS(++) PE- Y PGP-- t(+)@ 5(+) X++@ R(+) tv@
b++ DI++ G e++@ h--(*) r% y+
------END GEEK CODE BLOCK------
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
