From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rudy Gevaert <Rudy.Gevaert@UGent.be>
Subject: better alternative to part multpath -l output?
Date: Thu, 05 Jan 2012 14:33:41 +0100
Message-ID: <4F05A6B5.1020509@UGent.be>
Reply-To: device-mapper development <dm-devel@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <dm-devel-bounces@redhat.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/dm-devel>,
	<mailto:dm-devel-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/dm-devel>
List-Post: <mailto:dm-devel@redhat.com>
List-Help: <mailto:dm-devel-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/dm-devel>,
	<mailto:dm-devel-request@redhat.com?subject=subscribe>
Sender: dm-devel-bounces@redhat.com
Errors-To: dm-devel-bounces@redhat.com
To: dm-devel@redhat.com
List-Id: dm-devel.ids

Hello,

Can anybody suggest a better alternative to parsing multpath -l <device> 
to get the underlying devices that are part of the multipath?

Thanks in advance,

Rudy