From: Hans Reiser <reiser@namesys.com>
To: Jim Miller <jimm@simutronics.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Need Warm Fuzzies, ReiserFS (3)
Date: Mon, 20 Dec 2004 09:27:37 -0800 [thread overview]
Message-ID: <41C70B89.7010000@namesys.com> (raw)
In-Reply-To: <41C66615.5010206@simutronics.com>
Jim Miller wrote:
> Hi everyone,
>
> I have recently been burned by the XFS file system -- After a recent
> system crash/hang we experienced a lot of file corruption and needed
> to restore from a backup that was ~12hrs old. It seems that XFS keeps
> a lot of journal info in memory and a sudden system crash (hang)
> prevents it from writing out the journal.
> We run a few game servers that have a large number of large and small
> files that are actively accessed (and restoring from a backup 12hrs
> old made a lot of our gamers very unhappy). We were running EXT3
> (which in the past recovered nicely from hangs/crashes) but
> performance was so bad we needed a new FS so 6mos ago a decision was
> made to go with XFS. I would like to switch to ReiserFS (v3) (I
> understand Reiser4 isn't quite ready for production use) and was
> hoping to get the warm fuzzies about making this decision. I know
> it's much faster than ext3 but at this point I need to feel good about
> it's ability to recover from a sudden system hang/crash/reset.
>
>
> Thanks,
> Jim
>
>
>
>
>
>
>
>
>
>
It is probably tunable in XFS how long it keeps it in ram.
prev parent reply other threads:[~2004-12-20 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 5:41 Need Warm Fuzzies, ReiserFS (3) Jim Miller
2004-12-20 12:31 ` Christian Mayrhuber
2004-12-20 15:38 ` Tom Vier
2004-12-20 16:25 ` Christian Mayrhuber
2004-12-20 16:32 ` Spam
2004-12-20 20:24 ` Christian Mayrhuber
2004-12-20 20:31 ` Spam
2004-12-20 20:55 ` Christian Mayrhuber
2004-12-20 21:26 ` Tom Vier
2004-12-20 21:34 ` Spam
2004-12-21 15:49 ` Tom Vier
2004-12-20 19:23 ` Tom Vier
2004-12-20 20:04 ` Christian Mayrhuber
2004-12-20 17:27 ` Hans Reiser [this message]
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=41C70B89.7010000@namesys.com \
--to=reiser@namesys.com \
--cc=jimm@simutronics.com \
--cc=reiserfs-list@namesys.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.