From: Arsene Gschwind <arsene.gschwind@unibas.ch>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath disk size
Date: Wed, 12 Apr 2006 14:19:21 +0200 [thread overview]
Message-ID: <443CF049.40003@unibas.ch> (raw)
In-Reply-To: <443C098D.1090604@unibas.ch>
I've found something strange, 2 declaration of SERIAL_SIZE with
different sizes
libmultipath/structs.h:#define SERIAL_SIZE 17
path_priority/pp_balance_units/pp_balance_units.c:#define SERIAL_SIZE 255
In my case the first buffer size is to small because pp->serial has a
size of 17 chars and when you look at my output it has 40 chars.
By setting libmultipath/structs.h:#define SERIAL_SIZE to 255 it works
for me and the returned volume size is correct.
I'm not sure if this is the right solution, it would be great if someone
could verify that issue.
Thanks a lot for your work
Arsène
URZ- AG wrote:
>
>
> Christophe Varoqui wrote:
>
>>>
>> Thanks for this report.
>>
>> I can't reproduce this here.
>>
>> I'm afraid I'll have to ask you to try and refine your report though.
>> Use a debugger to track [m]pp->size changes, or try adding debugging
>> output in the key code areas : add_map_with_path(), coalesce_paths(),
>> ...
>>
>> Regards,
>> cvaroqui
>>
> Hello Christophe,
>
> I'm not a C Guru but i think i have been able to track it down.
> It seems that when discovering the device for paths after the
> get_serial (discovery.c) function the size has changed.
> I've entered two debug entries in scsi_ioctl_pathinfo() which prints
> out pp->size, one before get_serial call and one after and the size
> has changed when the second print its value. So far I've seen, this
> function should not change anything to the size, but it seems to write
> to that pointer, could it be that this function writes out of a buffer
> size?
> I'm not comfortable with the debugger so I have not been able to debug
> that in deep.
> It would be great if you could give me some more instructions on how
> to analyze/debug it .
>
> Regards,
> Arsène
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--
***********************************************************
Gschwind Arsene
Universitaet Rechenzentrum (URZ)
Klingelbergstrasse 70
CH-4056 Basel
SWITZERLAND
Languages : F/E/D
WWW: <http://www.urz.unibas.ch>
Mail: <Arsene DOT Gschwind AT unibas DOT ch>
************************************************************
next prev parent reply other threads:[~2006-04-12 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 8:47 multipath disk size URZ- AG
2006-04-07 22:31 ` Christophe Varoqui
2006-04-11 19:54 ` URZ- AG
2006-04-12 12:19 ` Arsene Gschwind [this message]
2006-04-12 19:45 ` Christophe Varoqui
2006-04-13 9:34 ` Arsene Gschwind
2006-04-13 16:41 ` Arsene Gschwind
-- strict thread matches above, loose matches on Subject: below --
2006-03-30 16:06 Arsene Gschwind
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=443CF049.40003@unibas.ch \
--to=arsene.gschwind@unibas.ch \
--cc=dm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.