All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolae Mihalache <mache@abcpages.com>
To: reiserfs-list@namesys.com
Subject: Re: corrupted files
Date: Sun, 10 Apr 2005 20:50:01 +0200	[thread overview]
Message-ID: <42597559.1070203@abcpages.com> (raw)
In-Reply-To: <425829F9.3020606@web.de>

Linuxhippy wrote:
> Hi!
> 
>> Otherwise I inted to reformat completely that partition (should I 
>> still use reiserfs3? somehow I don't trust it anymore).
> 
> 
> I also had serveral problems with corrupted files - until I opend my 
> laptop and cleaned/sealed the conductors of my harddrive - till now it 
> works great!
> 
> ReiserFS is used on so many computers, even highest availability 
> systems, I think your bug is either hardware or controller-driver based...
> 
> lg Clemens
> 

Ah, I just run now a "badblocks -s -v -c 100000 -n -t random /dev/hdc8" 
which reads/writes big chunks of data on the partition and it returns 
plenty of bad blocks. When run with default args (ie few KB of data at a 
time), "badblocks" returns no error.
So it has nothing to do with reiserfs but rather with crappy hardware.

Sorry for bothering you and thanks for the good work you do with reiserfs!

mache

  reply	other threads:[~2005-04-10 18:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08 22:25 corrupted files Nicolae Mihalache
2005-04-09 13:00 ` Christian
2005-04-09 18:04   ` Nicolae Mihalache
2005-04-09 19:16     ` Linuxhippy
2005-04-10 18:50       ` Nicolae Mihalache [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-09 15:21 Corrupted files Leslie Rhorer
2014-09-09 15:50 ` Sean Caron
2014-09-09 16:03   ` Sean Caron
2014-09-09 22:24     ` Eric Sandeen
2014-09-09 22:57       ` Sean Caron
2014-09-10  1:00         ` Roger Willcocks
2014-09-10  1:23           ` Leslie Rhorer
2014-09-10  5:09         ` Eric Sandeen
2014-09-10  0:48       ` Leslie Rhorer
2014-09-10  1:10         ` Roger Willcocks
2014-09-10  1:31           ` Leslie Rhorer
2014-09-10 14:24             ` Emmanuel Florac
2014-09-10 14:49               ` Sean Caron
2014-09-09 16:08 ` Emmanuel Florac
2014-09-09 22:06 ` Dave Chinner
2014-09-10  1:12   ` Leslie Rhorer
2014-09-10  1:25     ` Sean Caron
2014-09-10  1:43       ` Leslie Rhorer
2014-09-10 14:31         ` Emmanuel Florac
2014-09-10 14:52           ` Grozdan
2014-09-10 15:12             ` Emmanuel Florac
2014-09-10 15:32               ` Grozdan
2014-09-10 14:54           ` Sean Caron
2014-09-10 23:18           ` Leslie Rhorer
2014-09-11 13:24           ` Greg Freemyer
2014-09-12  7:06             ` Emmanuel Florac
2014-09-10  1:53     ` Dave Chinner
2014-09-10  3:10       ` Leslie Rhorer
2014-09-10  3:33         ` Dave Chinner
2014-09-10  4:14           ` Leslie Rhorer
2014-09-10  4:22             ` Leslie Rhorer
2014-09-10 14:34               ` Emmanuel Florac
2014-09-10  4:51           ` Leslie Rhorer
2014-09-10  5:23             ` Dave Chinner
2014-09-11  5:47               ` Leslie Rhorer

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=42597559.1070203@abcpages.com \
    --to=mache@abcpages.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.