From: "Al Boldi" <a1426z@gawab.com>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: RE: reiser4 plugins
Date: Tue, 28 Jun 2005 09:37:24 +0300 [thread overview]
Message-ID: <200506280637.JAA07320@raad.intranet> (raw)
In-Reply-To: <42C05F16.5000804@xfs.org>
Hans Reiser wrote:
> Steve, there is a remark about XFS below which you are going to be
> more expert on.
>
> Theodore Ts'o wrote:
>
>>
>>XFS has similar issues where it assumes that hardware has powerfail
>>interrupts, and that the OS can use said powerfail interrupt to stop
>>DMA's in its tracks on an power failure, so that you don't have
>>garbage written to key filesystem data structures when the memory
>>starts suffering from the dropping voltage on the power bus faster
>>than the DMA engine or the disk drives. So XFS is a great filesystem
>>--- but you'd better be running it on a UPS, or on a system which has
>>power fail interrupts and an OS that knows what to do. Ext3, because
>>it does physical block journalling, does not suffer from this problem.
>>(Yes, Resierfs uses logical journalling as well, so it suffers from
>>the same problem.)
>>
True now, not so around 2.4.20 when XFS was rock-solid. I think they tried
to improve on performance and broke something. I wish they would fix that
because it forced me back to ext3, as in consistency over performance any
time.
next parent reply other threads:[~2005-06-28 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42C05F16.5000804@xfs.org>
2005-06-28 6:37 ` Al Boldi [this message]
2004-08-25 22:28 silent semantic changes with reiser4 Andrew Morton
2004-08-26 8:31 ` Hans Reiser
2004-08-26 8:45 ` Andrew Morton
2004-08-26 12:18 ` Christophe Saout
2004-08-26 12:49 ` Christoph Hellwig
2004-08-26 13:00 ` Christophe Saout
2004-08-26 13:07 ` Christoph Hellwig
2004-08-26 13:17 ` reiser4 plugins (was: silent semantic changes with reiser4) Christophe Saout
2004-08-26 13:24 ` Christoph Hellwig
2004-08-26 13:35 ` Christophe Saout
2004-08-26 13:40 ` Christoph Hellwig
2004-08-26 13:58 ` Christophe Saout
2004-08-26 23:55 ` reiser4 plugins Hans Reiser
2004-08-27 12:04 ` Nikita Danilov
2004-08-27 18:15 ` Hans Reiser
2004-08-27 18:55 ` Nikita Danilov
2004-08-28 9:53 ` Hans Reiser
2004-08-28 13:47 ` Nikita Danilov
2004-08-28 23:45 ` Hans Reiser
2004-08-29 9:35 ` Nikita Danilov
2004-08-29 11:17 ` Alex Zarochentsev
2004-08-27 22:29 ` Steve Bergman
2004-08-28 6:54 ` Hans Reiser
2004-08-29 11:42 ` Alex Zarochentsev
2004-08-26 23:54 ` Hans Reiser
2004-08-28 10:59 ` reiser4 plugins (was: silent semantic changes with reiser4) Alexander Lyamin
2004-08-28 11:12 ` Christoph Hellwig
2004-08-28 12:05 ` Alexander Lyamin
2004-08-28 13:56 ` Christoph Hellwig
2004-08-28 19:23 ` Alexander Lyamin
2004-08-28 22:36 ` reiser4 plugins Hans Reiser
2004-08-28 17:18 ` reiser4 plugins (was: silent semantic changes with reiser4) Linus Torvalds
2004-08-28 19:03 ` Alexander Lyamin
2004-08-28 19:09 ` Christoph Hellwig
2004-08-28 21:41 ` reiser4 plugins Hans Reiser
2004-08-30 16:02 ` Herbert Poetzl
2004-08-30 18:55 ` 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=200506280637.JAA07320@raad.intranet \
--to=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).