From: Loic Dachary <loic@dachary.org>
To: Phil Susi <psusi@ubuntu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: parted behavior change between 3.1 and 3.2
Date: Wed, 25 May 2016 00:30:42 +0200 [thread overview]
Message-ID: <5744D612.6050905@dachary.org> (raw)
In-Reply-To: <5ba70630-84af-f7b6-802c-933b1a26f273@ubuntu.com>
Hi Phil,
On 24/05/2016 19:16, Phil Susi wrote:
> On 5/23/2016 3:41 AM, Loic Dachary wrote:
>> Hi Philip,
>>
>> In the context of the Ceph ( http://ceph.com/ ) project, I'm trying
>> to figure out why parted 3.2 fixes a problem that shows in 3.1 [1].
>> In a nutshell, calling partprobe sometime fails with "device busy"
>> with 3.1 and when using 3.2 that never happens (all things are the
>> same, only parted changes). I took a look at the commits in
>> http://git.savannah.gnu.org/cgit/parted.git/log/ but I didn't see a
>> commit that would explain such a behavior change.
>>
>> Any pointer or idea you may have would be greatly appreciated :-)
>
> An strace would help, but if I had to guess, one significant change
> between 3.1 and 3.2 was the addition of the ability to resize mounted
> partitions, so it could be that partprobe is adjusting the size of a
> changed partition, and it used to not be able to do that if it is mounted.
>
That's an interesting lead, I'll double check if that could be the cause. Thanks very much for the hint !
I'll let you know how it evolves.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-24 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 7:41 parted behavior change between 3.1 and 3.2 Loic Dachary
2016-05-24 17:16 ` Phil Susi
2016-05-24 22:30 ` Loic Dachary [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-23 9:04 Loic Dachary
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=5744D612.6050905@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=psusi@ubuntu.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.