All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Soeren Sonnenburg <reiserfs@nn7.de>
Cc: reiserfs-list@namesys.com
Subject: Re: trouble with reiserfs on ppc vs-3050: wait_buffer_until_released ...
Date: Mon, 28 Apr 2003 09:18:58 +0400	[thread overview]
Message-ID: <20030428051858.GA22805@namesys.com> (raw)
In-Reply-To: <1051397193.1232.4.camel@localhost>

Hello!

On Sun, Apr 27, 2003 at 12:46:53AM +0200, Soeren Sonnenburg wrote:

> > Ok, is this a new box? any chance to check if the memory is right?
> ok, so I ran the memtest tool for a night without it finding any
> errors... I did a full compare (not only md5sums) over network with the
> files I have on disk... they were the same... I let bonnie run and
> checked for corruption... nothing ... 
> Looks like all I can do is keeping an eye on it.

Hm, and given there was another report like this recently, it seems like
some reiserfs problem :(
Unfortunatelly we don't even have PPC (or other bigendian) hardware to test on.

Bye,
    Oleg

  reply	other threads:[~2003-04-28  5:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25  8:11 trouble with reiserfs on ppc vs-3050: wait_buffer_until_released Soeren Sonnenburg
2003-04-25  8:35 ` Soeren Sonnenburg
2003-04-25  8:47   ` Oleg Drokin
2003-04-25  9:05     ` Soeren Sonnenburg
2003-04-25  9:19       ` Oleg Drokin
2003-04-25  9:33         ` Soeren Sonnenburg
2003-04-25  9:46           ` Oleg Drokin
2003-04-25 10:12             ` Soeren Sonnenburg
2003-04-25 10:28               ` Oleg Drokin
2003-04-26 22:46                 ` Soeren Sonnenburg
2003-04-28  5:18                   ` Oleg Drokin [this message]
2003-04-28 19:54                     ` Soeren Sonnenburg
2003-04-29  5:21                       ` Oleg Drokin
2003-04-25  8:41 ` Vitaly Fertman
2003-04-25  9:01   ` Soeren Sonnenburg
2003-04-26 15:27 ` none
2003-04-28 20:14 ` Hans Reiser

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=20030428051858.GA22805@namesys.com \
    --to=green@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=reiserfs@nn7.de \
    /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.