From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Neil Brown <neilb@suse.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
st0ff@npl.de, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: md lock issue, I suppose
Date: Thu, 24 Jun 2010 20:07:27 +0200 [thread overview]
Message-ID: <20100624180727.GA9038@lazy.lzy> (raw)
In-Reply-To: <20100622082233.2015caee@notabene.brown>
Hi,
thanks for the hint, basically that exactly
what was needed, i.e. informing the kernel
about the new partition.
The only different with your suggestion was
to use "addpart", instead of "partx".
Thanks again,
bye,
pg
On Tue, Jun 22, 2010 at 08:22:33AM +1000, Neil Brown wrote:
> On Mon, 21 Jun 2010 23:25:21 +0200
> Piergiorgio Sartor <piergiorgio.sartor@nexgo.de> wrote:
>
> > Any other suggestions or ideas?
> >
>
> You cannot use the BLKRRPART ioctl while any partition of the device is open.
> However you can use BLKPG_ADD_PARTITION to add a new partition providing it
> doesn't overlap any existing partition.
> Unfortunately parted doesn't use this ioctl, nor am I aware of anything which
> does. (Google suggests something called DeviceKit does, but I know nothing
> about that).
> You could write a program which reads the the partition table and tries to
> add each partition individually. Some might fail but others might succeed.
> ... or maybe you don't need to- 'partx' in util-linux-ng seems to do what you
> want.
>
> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
piergiorgio
next prev parent reply other threads:[~2010-06-24 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 20:42 md lock issue, I suppose Piergiorgio Sartor
2010-06-21 21:08 ` Stefan /*St0fF*/ Hübner
2010-06-21 21:25 ` Piergiorgio Sartor
2010-06-21 22:22 ` Neil Brown
2010-06-24 18:07 ` Piergiorgio Sartor [this message]
2010-06-25 12:39 ` CoolCold
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=20100624180727.GA9038@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=st0ff@npl.de \
/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).