From: mjt@nysv.org
To: Christophe Saout <christophe@saout.de>
Cc: "Ari Sovijärvi" <apz@flipperit.net>, reiserfs-list@namesys.com
Subject: Re: Broken reiser4 FS
Date: Wed, 25 Aug 2004 15:29:44 +0300 [thread overview]
Message-ID: <20040825122944.GO1284@nysv.org> (raw)
In-Reply-To: <1093436551.10608.7.camel@leto.cs.pocnet.net>
On Wed, Aug 25, 2004 at 02:22:31PM +0200, Christophe Saout wrote:
>
>I've also seen a bunch of these on my notebook. I'm ruling out memory
>problems, my hardware is reliable.
Wasn't there some discussion that there may be some issues with Reiser4
still committing journals during umount which leads to data loss in -mm4?
Or was it so that this was fixed in -mm4?
That should not destroy the directory plugin type, though.
>My notebook is sometimes low on memory and swaps a lot while I'm doing
>some disk I/O. This is perhaps increasing the chance of getting this
>corruption, I'm not sure.
That might be consistent with something about files being in swap during
umount and thus not commited?
I don't know if this is a shot in the dark or clutching at straws ;)
Any Namesys guys around? :)
--
mjt
prev parent reply other threads:[~2004-08-25 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 11:21 Broken reiser4 FS Ari Sovijärvi
2004-08-25 12:22 ` Christophe Saout
2004-08-25 12:29 ` mjt [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=20040825122944.GO1284@nysv.org \
--to=mjt@nysv.org \
--cc=apz@flipperit.net \
--cc=christophe@saout.de \
--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.