public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Iustin Pop <iusty@k1024.org>
To: Rekrutacja119 <rekrutacja119@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs I/O error
Date: Sun, 24 Feb 2008 10:01:06 +0100	[thread overview]
Message-ID: <20080224090106.GD27124@teal.hq.k1024.org> (raw)
In-Reply-To: <2db2c6b80802231414m38f70795n7f24fea1a40195df@mail.gmail.com>

On Sat, Feb 23, 2008 at 11:14:32PM +0100, Rekrutacja119 wrote:
> so i should use the list i got from badblocks with dd but with bs=1024? are
> you sure? i'm not sure what is my block size, but xfs_info says this:
the block size of the filesystem has no relation to the block size
badblocks uses in checking the block device.
> 
[...]
> 
> i think i made it with 4K stack size ... well anyways, i should use the list
> i got earlier and just try dd but with bs=1024... ? don't want to erase more
> than i have to. (i want to do it so i can smartctl -t offline /dev/sdb then,
> so maybe it will somehow see that these blocks are broken and mark them)

I don't understand what do you want to do with smartctl at all. How
would offlining the disk would help?

Again, I would:
  - take the block list given by badblocks
  - verify that each block can't be read  first via dd if=/dev/...
    of=/dev/null bs=1024 count=1 seek=NUMBER_FROM_BADBLOCK
  - if confirmed that you got the right 'bad' blocks, use that for dd
    with bs=1024 to write zeroes over them

As Eric confirmed, you probably already destroyed some good data on the
drive.

regards,
iustin

  reply	other threads:[~2008-02-24  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 21:46 xfs I/O error Rekrutacja119
2008-02-23 22:00 ` Fwd: " Rekrutacja119
2008-02-23 22:08 ` Iustin Pop
2008-02-23 22:14   ` Rekrutacja119
2008-02-24  9:01     ` Iustin Pop [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
2009-07-31 20:36   ` Emmanuel Florac

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=20080224090106.GD27124@teal.hq.k1024.org \
    --to=iusty@k1024.org \
    --cc=rekrutacja119@gmail.com \
    --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