From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How to handle Bad Block relocation with LVM?
Date: Tue Feb 11 08:24:02 2003 [thread overview]
Message-ID: <20030211152045.A10750@sistina.com> (raw)
In-Reply-To: <002101c2d16b$515d2580$c70aa8c0@RD.proware.com.tw>; from gozila@ms20.url.com.tw on Tue, Feb 11, 2003 at 09:17:16AM +0800
On Tue, Feb 11, 2003 at 09:17:16AM +0800, Rocky Lee wrote:
>
>
> Hi all
>
> I heard LVM can't not handle BBR, is that true?
No, not by now. IBM seems to be working on a BBR target for device-mapper
though.
>
> If so,
> It maybe a serious problem to me.
Is drive-level bbr not sufficient for you ?
> is there a trick to handle BBR with LVM + MD?
No.
>
> Thank you if anyone can help to answer these question.
>
> Rocky Lee
>
>
> _______________________________________________
> 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/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-02-11 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:18 [linux-lvm] How to handle Bad Block relocation with LVM? Rocky Lee
2003-02-11 8:24 ` Heinz J . Mauelshagen [this message]
2003-02-14 8:52 [linux-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
2023-03-15 16:00 Roland
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=20030211152045.A10750@sistina.com \
--to=mauelshagen@sistina.com \
--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;
as well as URLs for NNTP newsgroup(s).