From: Hifumi Hisashi <hifumi.hisashi@lab.ntt.co.jp>
To: michael chang <thenewme91@gmail.com>
Cc: reiser@namesys.com, reiserfs-dev@namesys.com,
reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fix problems related to journaling in Reiserfs
Date: Thu, 01 Sep 2005 09:02:43 +0900 [thread overview]
Message-ID: <43164523.7030301@lab.ntt.co.jp> (raw)
In-Reply-To: <b14e81f005083106423c6adc4@mail.gmail.com>
michael chang wrote:
>Surely we don't want this. Look at the papers on Namesys's websites,
>about the atomicaty and the banking example. But that's just my
>personal opinion. Besides, I believe it's more likely that usually
>the power gets lost than the SCSI or IDE cable gets disconnected,
>AFAIK...
>
>
A write() syscall with the O_SYNC flag must ensure that not only
file data block
but also journal (meta-data update) are written to a disk when this
syscall end.
But, current implementation of Reiserfs does not do that. If a system
crashes,
a filesystem recovers from the journal transaction log. But, Reiserfs
may not
recover in some cases.
I checked other filesystems like ext3, jfs, xfs. Those filesystem
write transactions
to a disk everytime write() with the O_SYNC is performed. In those
filesystem,
I have no trouble mentioned above.
I should say, the Reiserfs would be "un"reliable filesystem..........
next prev parent reply other threads:[~2005-09-01 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 12:39 [PATCH] fix problems related to journaling in Reiserfs Hifumi Hisashi
2005-08-31 13:42 ` michael chang
2005-09-01 0:02 ` Hifumi Hisashi [this message]
2005-09-01 0:37 ` michael chang
2005-09-01 3:30 ` Hans Reiser
2005-09-01 7:47 ` Vladimir V. Saveliev
2005-09-01 3:35 ` Hans Reiser
2005-09-02 2:03 ` Chris Mason
2005-10-04 8:47 ` Hifumi Hisashi
2005-10-04 10:40 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43164523.7030301@lab.ntt.co.jp \
--to=hifumi.hisashi@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=thenewme91@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.