All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jens Benecke <jens-usenet@spamfreemail.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Strange errors with 2.4.22 patches (from Chris) and bonnie++
Date: Fri, 28 Nov 2003 08:46:25 -0800	[thread overview]
Message-ID: <3FC77BE1.3070200@namesys.com> (raw)
In-Reply-To: <bq8f7u$ufn$1@sea.gmane.org>

Jens Benecke wrote:

>Hi,
>
>I applied the 2.4.22 patches from Chris Mason's SuSE FTP directory for data
>logging etc:
>
>available at 
>http://mirrors.mathematik.uni-bielefeld.de/pub/linux/suse/people/mason
>patches/data-logging/2.4.22/ or
>mirror.mcs.anl.gov/suse-people/mason/patches/data-logging/2.4.22/
>
>root         3109 Jul 11 21:10 02-akpm-b_journal_head-1.diff
>root        17133 Jul 11 21:10 04-reiserfs-sync_fs-4.diff
>root       155659 Jul 11 21:09 05-data-logging-39.diff
>root          650 Jul 11 21:10 06-write_times.diff
>root        41276 Jul 11 21:09 07-reiserfs-quota-28.diff
>root         3275 Jul 11 21:15 08-kinoded-9.diff
>root         2653 Jul 11 21:10 10-reiserfs-quota-link-fix.diff
>root          898 Oct 10 12:25 README
>
>This system is running 2.4.22-kernel from Debian (stable) with the
>GRsecurity 1.9.12 patch, on P4 optimization and no other patches, except
>for the above.
>
>
>Two problems appeared with the above patches:
>
>a) Synchronizing with drbd (www.drbd.org) shared devices slowed down to 
>   a crawl. I guess this might have something to do with the way drbd
>   inserts itself between block device and file system and the changed
>   sync behavoiur.
>   Sync rates were >5000k/s before and <500k/s after I patched.
>
>b) bonnie++ on a (previously created) reiserfs partition (with 
>   mkreiserfs 3.6.6) exited with random "disk full" errors, although 
>   the disk was never full. This didn't happen before.
>
>
>Details:
>
>  
>
>>bonnie++ -d . -s 2048 -m master1 -r 1024 -x 2 -u nobody:nogroup
>>    
>>
>
>Now bonnie++ exits randomly with "no space left on device" when 'df' clearly
>shows there is ample space left:
>
>Writing with putc()...  
>Writing intelligently...
>Can't write block.
>Bonnie: drastic I/O error (write(2)): No space left on device
>
>-rw-------    1 nobody   nogroup  474931200 Nov 28 22:04 Bonnie.19345.000
>-rw-------    1 nobody   nogroup         0 Nov 28 22:04 Bonnie.19345.001
>
>Dateisystem          1k-Blöcke    Benutzt Verfügbar Ben% montiert auf
>/dev/ide/host0/bus0/target0/lun0/part7
>                       3044184    945424   2098760  32% /var
>
>
>This did not happen before I applied the patches.
>To be honest, I don't know how to debug this.
>
>There is nothing in the syslog and nothing via 'dmesg' related to drbd or
>reiserfs.
>
>
>I would appreciate any help.
>Thank you! :-)
>
>
>  
>
there may be a holiday related delay in Chris's response, don't 
interpret it as a lack of interest....

-- 
Hans



       reply	other threads:[~2003-11-28 16:46 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 ` Hans Reiser [this message]
2003-11-29 19:27 ` Strange errors with 2.4.22 patches (from Chris) and bonnie++ 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
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=3FC77BE1.3070200@namesys.com \
    --to=reiser@namesys.com \
    --cc=jens-usenet@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.