The potential is certainly there. Most jfs use delayed writing. When you
save something to disk, it isn't immediately flushed to disk. Had you
ran 'sync' prior to pushing the power button, perhaps the file would've
been intact? If you use EXT3 and set it to full data journaling mode, it
might've made it that way also. In that mode, EXT3 journals meta data
and file data.
-Walt
Xianglong Yuan wrote:
-Paulo Sergio Lemes Queiroz [05 Dec 2001 13:15 -0200] wrote:
http://oss.sgi.com/projects/xfs/faq.html#nulls
Thanks. Is this true for all the journaling FS, say ReiserFS,
JFS?
Xianglong Yuan
Xianglong Yuan wrote:
Hi, there,
I've just transferred my old ext2 FS into XFS FS and did the
following test. What I got surprises me.
First, I modify a file with vim, save it, and go back to bash
shell. Then, I hit the power button to crash the system
instantly. Now I restart the system and the XFS FS comes back
gracefully. However, when I try to open the just saved file,
nothing is there, not the new modified content, not even the old
content. All the content in the file is wiped off by a stream
of weird symbols. Is the XFS FS supposed to behavior like that?
It seems to me XFS is really not a safe FS to count on when
system crashing. I presumed that I should have my old content
back. Did I asked too much here? Thanks in advance.
Xianglong Yuan
--
Paulo Sergio Lemes Queiroz
Analista de Sistemas
Definity Linux | Esc Telecomunica??es
|