public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: linux-kernel@vger.kernel.org, Nikita Danilov <god@namesys.com>
Subject: Re: [OT] Howl of soul...
Date: Sun, 26 Aug 2001 15:41:30 +0400	[thread overview]
Message-ID: <3B88E06A.85235122@namesys.com> (raw)
In-Reply-To: <E15aK0R-000M5f-00@f8.mail.ru>

Samium Gromoff wrote:
> 
>      dear people!
> 
>    Sorry for OT, but i want only good to you, lkml
>  people...
>    If you are to buy a new ide drive, do not buy
>  recent IBM 7200 drives!!!
>    The story begins when at February of this year i`ve bought
>  perfectly shining ever-fast IBM DTLA-307045...
>    After 3 months i`ve hardly regreted about such
>  decision: drive started to covers himself with a thick
>  layer of logical-not-physical badblocks (ie lowlevel
>  reformat doesnt show anything).
>    So i went to storagereview and lerned about the matter.
>  As i found, these drives had an internal controller bug.
> 
>    So i said okay, while restoring 3rd time my reiserfs
>  and dumping data to spare drive, and went to
>  replace the drive to perfectly new and shining
>  IBM IC35L040AVER07-0 also known as 60GXP.
> 
>    Now i`am heavily punished for that.
>  Badblocks are reapperaing on runtime.
>    After they appeared first time i`ve attached large
>  fan to the drive, so it was cold(!) to touch. Also
>  i stopped to transport the drive between boxes.
> 
>    Nevertheless these fscking logical badblocks
>  appeared again twice.
> 
>    The fact is, that we had bought these drives
>  with my friend synchronusly, and now he owns
>  quantum drive, after 75gxp and 60gxp...
>    Ofcourse he had similar problems.... (btw he use windoze)
> 
>    I am _tired_ fixing my poor reiserfs root partition.
>    I can say that now i`am expert on how to restore
>  badblocked reiserfs partiotions... ;(
> 
>    Beware.
> 
> ---
> 
> cheers,
> 
>    Samium Gromoff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


I am confused, you and your friend both had problems, and you used IBM and he
used quantum?  Do they have similar electronics?

Take a look at www.namesys.com, there is a badblocks patch, god@namesys.com will
tell you details about it.

hans

  parent reply	other threads:[~2001-08-26 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 16:40 [OT] Howl of soul Samium Gromoff
2001-08-24 18:33 ` Justin Guyett
2001-08-24 20:00   ` Alan Cox
2001-08-24 20:08     ` David Huen
2001-08-24 20:34     ` Paul Jakma
2001-08-25  1:26     ` Mike Castle
2001-08-26 11:41 ` Hans Reiser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-25 12:41 Samium Gromoff
2001-08-25 20:11 Samium Gromoff
2001-08-26 22:06 ` Barry K. Nathan
2001-09-07 16:12   ` Marco Colombo
2001-08-26 12:13 Samium Gromoff
2001-09-26  3:01 Samium Gromoff
2001-08-29 20:30 ` Pavel Zaitsev

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=3B88E06A.85235122@namesys.com \
    --to=reiser@namesys.com \
    --cc=_deepfire@mail.ru \
    --cc=god@namesys.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