public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Andrew Robinson <andrew.rw.robinson@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)
Date: Tue, 12 Dec 2006 17:27:06 -0500	[thread overview]
Message-ID: <457F2CBA.8010904@cfl.rr.com> (raw)
In-Reply-To: <457F0F7D.9090207@wolfmountaingroup.com>

> No.  I still see corruption on Suse with Reiser FS.  It's always very 
> subtle (like the last block of a file doesn;t get copied or gets
> corrupted.   We have been running our ftp server on ReiserFS, and as 
> soon as I can get it moved back to ext3, we are doing so.
> We have had a lot of issues with corrupted RPM files and builds on 
> ReiserFS.  If you can get the files copied to the
> FS ok, they seem to stay that way.  moving a lot of data with recursive 
> copies seems troublesome and some of the files
> seem to get the ends clipped off of them.

If your comment here was in reply to my general comment about resierfs 
stability and not the specific hibernation issue the OP was having, 
please edit the quote down to just that portion instead of quoting the 
entire message, including the quotes it was replying to.

I wonder what kernel version you are running.  Since you mention rpms, I 
will assume you are running redhat, and likely are using a rather old 
kernel.



  reply	other threads:[~2006-12-12 22:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 18:44 ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means) Andrew Robinson
2006-12-12 19:28 ` Phillip Susi
2006-12-12 20:22   ` Jeff V. Merkey
2006-12-12 22:27     ` Phillip Susi [this message]
2006-12-12 22:16       ` Jeff V. Merkey
2006-12-12 22:45 ` Olivier Galibert
2006-12-15 16:15   ` Pavel Machek
2006-12-16  9:07     ` Jeffrey V. Merkey
2006-12-22 20:34       ` suspend to disk (was Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)) Pavel Machek
2006-12-13  8:37 ` ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means) Tejun Heo

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=457F2CBA.8010904@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=andrew.rw.robinson@gmail.com \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox