From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] How to handle Bad Block relocation with LVM?
Date: Thu, 29 Nov 2012 19:10:36 -0500 [thread overview]
Message-ID: <k98thr$l1s$1@ger.gmane.org> (raw)
In-Reply-To: <50B78579.2040102@bmsi.com>
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
On 12-11-29 10:55 AM, Stuart D Gathman wrote:
>
> Having helped people in such situations (where internet at least was
> working), I've used the attached script to help find affected LVs and files.
Awesome script!
Much thanks!
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2012-11-30 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 8:52 [linux-lvm] Re: How to handle Bad Block relocation with LVM? Eric Hopper
2003-02-14 11:27 ` Joe Thornber
2012-11-28 13:27 ` [linux-lvm] " Brian Murrell
2012-11-28 13:57 ` Zdenek Kabelac
2012-11-29 12:26 ` Brian J. Murrell
2012-11-29 14:04 ` Lars Ellenberg
2012-11-29 22:53 ` Brian J. Murrell
2012-11-29 15:55 ` Stuart D Gathman
2012-11-30 0:10 ` Brian J. Murrell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 16:00 Roland
2003-02-10 19:18 Rocky Lee
2003-02-11 8:24 ` Heinz J . Mauelshagen
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='k98thr$l1s$1@ger.gmane.org' \
--to=brian@interlinx.bc.ca \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).