public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Eric Sandeen <sandeen@sandeen.net>, rnb <neil.bell@gmail.com>
Subject: Re: xfs i/O error
Date: Fri, 31 Jul 2009 11:08:22 +0200	[thread overview]
Message-ID: <200907311108.26491@zmi.at> (raw)
In-Reply-To: <4A726711.5050402@sandeen.net>


[-- Attachment #1.1: Type: text/plain, Size: 774 bytes --]

On Freitag 31 Juli 2009 Eric Sandeen wrote:
> Read errors can be somewhat recoverable, if you write to that sector
> it will remap if it can.

Yes, but I've never seen a disk who did not get other broken sectors 
later. When a disk starts to get bad sectors, others will come, just 
like a virus. Therefore: you get a bad sector -> replace disk. That's by 
far less pain and cheaper than the other scenario.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4


[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-07-31  9:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 17:03 xfs i/O error rnb
2009-07-30 19:13 ` Eric Sandeen
2009-07-30 21:45 ` rnb
2009-07-30 23:48   ` Michael Monnerie
2009-07-31  3:37     ` Eric Sandeen
2009-07-31  9:08       ` Michael Monnerie [this message]
2009-07-31 20:36   ` Emmanuel Florac
  -- strict thread matches above, loose matches on Subject: below --
2008-02-23 21:46 xfs I/O error Rekrutacja119
2008-02-23 22:08 ` Iustin Pop
2008-02-23 22:14   ` Rekrutacja119
2008-02-24  9:01     ` Iustin Pop
2008-02-24 11:52       ` Rekrutacja119
2008-02-24 12:31         ` Iustin Pop
2008-02-25 16:40           ` Rekrutacja119
2008-02-25 17:17             ` Eric Sandeen
2008-02-24  3:53 ` Eric Sandeen
2008-02-24 12:17 ` Ragnar Kjørstad
     [not found]   ` <2db2c6b80802250847m2d161f5n276026dae396d3cc@mail.gmail.com>
     [not found]     ` <20080225211055.GK29277@vestdata.no>
2008-02-26 20:13       ` Rekrutacja119

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=200907311108.26491@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=neil.bell@gmail.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox