From: "JP Howard" <jh_lists@fastmail.fm>
To: "Chris Mason" <mason@suse.com>,
"Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: Oleg Drokin <green@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Oops with in nfsd - 2.4.19-pre6
Date: Thu, 31 Oct 2002 21:08:28 UT [thread overview]
Message-ID: <20021031210828.45F4A216991@server5.fastmail.fm> (raw)
On 31 Oct 2002 15:38:19 -0500, "Chris Mason" <mason@suse.com> said:
<...>
> The idea is that during boundless operations (creating a hole, and
> truncates), the journal code wasn't properly reserving log blocks.
<...>
Chris, what can trigger this situation? We're currently running
data=journal on 2.4.20pre in production--are we at risk?
next reply other threads:[~2002-10-31 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:08 JP Howard [this message]
2002-10-31 21:30 ` Oops with in nfsd - 2.4.19-pre6 Chris Mason
2002-11-01 14:46 ` Christopher Barry
2002-11-12 17:29 ` Philippe Gramoullé
2002-11-13 18:14 ` Chris Mason
2002-11-13 18:40 ` Philippe Gramoullé
2002-11-13 20:23 ` Chris Mason
2002-11-14 2:33 ` Chris Mason
2002-11-27 20:54 ` Data-Logging Progess?! (was: Oops with in nfsd - 2.4.19-pre6) Manuel Krause
2002-11-28 10:18 ` Philippe Gramoullé
2002-11-28 19:23 ` Manuel Krause
2002-11-14 16:04 ` Oops with in nfsd - 2.4.19-pre6 Philippe Gramoullé
2002-11-14 16:32 ` Chris Mason
2002-11-14 17:41 ` Philippe Gramoullé
2002-11-14 17:46 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:12 JP Howard
2002-10-29 14:59 Philippe Gramoullé
2002-10-29 15:14 ` Oleg Drokin
2002-10-29 15:20 ` Philippe Gramoullé
2002-10-29 15:26 ` Oleg Drokin
2002-10-31 20:38 ` Chris Mason
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=20021031210828.45F4A216991@server5.fastmail.fm \
--to=jh_lists@fastmail.fm \
--cc=green@namesys.com \
--cc=mason@suse.com \
--cc=philippe.gramoulle@mmania.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.