From: "B. J. Zolp" <bjzolp@wisc.edu>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Drive failure
Date: Thu May 15 18:36:01 2003 [thread overview]
Message-ID: <200305151834.10480.bjzolp@wisc.edu> (raw)
In-Reply-To: <20030515203908.66A9CAE4F5@basilica.la.naos.co.nz>
On Thursday 15 May 2003 15:39, Ewen McNeill wrote:
> In message <200305150917.21504.bjzolp@wisc.edu>, "B. J. Zolp" writes:
> >On Thursday 15 May 2003 03:14, Ewen McNeill wrote:
> >> - make sure you do the dd with an option to replace unreadable sectors
> >> with blank sectors (otherwise nothing will be written out for the
> >> unreadable sectors, causing everything to be "out of alignment" after
> >> the first bad block)
> >
> >I plan on using the noerror switch for dd, what else would I need to use
> > to make sure it replaces with blank sectors. I could not find anything
> > in info dd or man dd.
>
> The option I was thinking of is conv=noerror,sync
>
> The "noerror" is "continue reading after read errors", and the "sync"
> is "pad each input block with zero bytes to block size". Possibly GNU
> dd is better behaved, but my recollection is that at least some "dd"s
> will happily skip over blocks they can't read given "conv=noerror" (by
> assuming they just read 0 bytes that time), but result in effectively
> fewer blocks written out than read in, effectively shuffling everything
> after the blocks with errors down a bit. This is, suffice to say,
> a bad thing to have happen to your file system.
>
> You might want to practice a little with copying from the disk into some
> temporary location (eg outputting to /dev/null will do for this
> purpose), and watch the "input blocks" and "output blocks" counts that
> are reported -- if they're not the same, you're going to have a problem.
I'm doing a
dd bs=512 conv=noerror,sync if=/dev/hdf of=/dev/null
right now. It has been going for a few hours, but does not seem to be taking
up any cpu cycles (it looks hung up). I will let it go over night and see
how it is tomorrow. What would you suggest I do if the I can only get the
data on the HD up until the bad sector (or where ever it is hung up). This
is the last drive in the logical volume, so there was not too much data on
it, but how would I go about added the new replacement drive to the logical
volume without messing up my entire filesystem?
Thanks again.
bjz
>
> Ewen
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2003-05-15 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 10:41 [linux-lvm] Drive failure B. J. Zolp
2003-05-15 3:01 ` Herbert Poetzl
2003-05-15 3:14 ` Ewen McNeill
2003-05-15 9:17 ` B. J. Zolp
2003-05-15 15:39 ` Ewen McNeill
2003-05-15 18:36 ` B. J. Zolp [this message]
2003-05-15 18:55 ` Ewen McNeill
2003-05-18 13:24 ` Urs Thuermann
2003-05-15 9:09 ` B. J. Zolp
2003-05-15 16:49 ` Herbert Poetzl
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=200305151834.10480.bjzolp@wisc.edu \
--to=bjzolp@wisc.edu \
--cc=linux-lvm@sistina.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