From: Jens Benecke <jens-unibw@spamfreemail.de>
To: reiserfs-list@namesys.com
Subject: Re: Strange errors with 2.4.22 patches (from Chris) and bonnie++
Date: Thu, 04 Dec 2003 13:44:32 +0100 [thread overview]
Message-ID: <bqna7g$8gg$1@sea.gmane.org> (raw)
In-Reply-To: 1070478784.27611.105.camel@tiny.suse.com
Chris Mason wrote:
>> so... the worst-case impact on this bug is that reiserfs will report
>> "disk full" when you still have some space available. Right? No data
>> loss, corruption, or similar Bad Things(tm)?
>>
> Correct. I'll have a fix available today along with a remerge of data
> logging and quota against 2.4.23.
Thank you!
>> btw, what are the patches that SuSE uses? IIRC, SuSE ships with
>> data-logging enabled, right?
> SUSE ships data logging and the xattr patches, along with a few others.
What patches exactly?
Are they available in public to be applied to a vanilla kernel?
--
Jens Benecke (jens-unibw@spamfreemail.de)
http://www.hitchhikers.de - Europaweite kostenlose Mitfahrzentrale
http://www.spamfreemail.de - 100% saubere Postfächer - garantiert!
http://www.rb-hosting.de - PHP ab 9? - SSH ab 19? - günstiger Traffic
next prev parent reply other threads:[~2003-12-04 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bq8f7u$ufn$1@sea.gmane.org>
2003-11-28 16:46 ` Strange errors with 2.4.22 patches (from Chris) and bonnie++ Hans Reiser
2003-11-29 19:27 ` Christian Mayrhuber
2003-12-01 13:30 ` Chris Mason
2003-12-01 16:00 ` Christian Mayrhuber
2003-12-01 17:21 ` slow stat() ? David Bernick
2003-12-01 17:30 ` Chris Mason
2003-12-01 7:47 ` Hans Reiser
2003-12-11 4:44 ` update on " David Bernick
2003-12-01 17:43 ` David Bernick
2003-12-01 17:57 ` Chris Mason
2003-12-02 11:57 ` David Bernick
2003-12-01 8:02 ` Strange errors with 2.4.22 patches (from Chris) and bonnie++ Jens Benecke
2003-12-01 13:49 ` Chris Mason
2003-12-02 8:35 ` Jens Benecke
2003-12-03 19:13 ` Chris Mason
2003-12-04 12:44 ` Jens Benecke [this message]
2003-12-04 16:28 ` Chris Mason
2003-12-04 16:33 ` 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='bqna7g$8gg$1@sea.gmane.org' \
--to=jens-unibw@spamfreemail.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.