[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [dm-devel] geometry of dm devices......



Thanks Darrick,

I actually saw that in the source to build 1.02.08 but unfortunately it
would be of no help in my situation.  You see I work in a storage/array
test environment and as for dm, we must specifically work with the
builds packaged with the releases of Redhat, Suse, etc.  I saw that
SLES10 had a build of 1.02.xx but I can also see that it was prior to
this new implementation.  We are unable to modify (unless required in a
customer support scenario) what is packaged with these releases.  Thanks
again. 

Regards,

Peter

-----Original Message-----
From: dm-devel-bounces redhat com [mailto:dm-devel-bounces redhat com]
On Behalf Of Darrick J. Wong
Sent: Tuesday, August 08, 2006 5:09 PM
To: device-mapper development
Subject: Re: [dm-devel] geometry of dm devices......

Peter Koutoupis wrote:

>> I understand the HDIO_GETGEO is an unsupported feature to dm 
>> devices....but under normal practices how would a normal end-user be 
>> able to obtain such geometry from a raw dm device?  I have read of

Wow, I'm late to the game.  If your kernel/software are new enough, you
can set a dm device's geometry via the DM_DEV_SET_GEOMETRY_CMD ioctl.
iirc, the userland equivalent is:

# dmsetup setgeometry /dev/foo cyl head spt start

...after which HDIO_GETGEO should return nonzero values.

You'll need kernel 2.6.16+ and I think the requisite version of dmsetup
is 1.02.  And to my (very limited) knowledge of multipath, geometry is
not set up automatically.

--D



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]