From: David Greaves <david@dgreaves.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Partitioned arrays initially missing from /proc/partitions
Date: Tue, 24 Apr 2007 11:49:06 +0100 [thread overview]
Message-ID: <462DE0A2.6000701@dgreaves.com> (raw)
In-Reply-To: <17965.18112.135843.417561@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Neil Brown wrote:
> This problem is very hard to solve inside the kernel.
> The partitions will not be visible until the array is opened *after*
> it has been created. Making the partitions visible before that would
> be possible, but would be very easy.
>
> I think the best solution is Mike's solution which is to simply
> open/close the array after it has been assembled. I will make sure
> this is in the next release of mdadm.
>
> Note that you can still access the partitions even though they do not
> appear in /proc/partitions. Any attempt to access and of them will
> make them all appear in /proc/partitions. But I understand there is
> sometimes value in seeing them before accessing them.
>
> NeilBrown
For anyone else who is in this boat and doesn't fancy finding somewhere in mdadm
to hack, here's a simple program that issues the BLKRRPART ioctl.
This re-reads the block device partition table and 'works for me'.
I think partx -a would do the same job but for some reason partx isn't in
utils-linux for Debian...
Neil, isn't it easy to just do this after an assemble?
David
[-- Attachment #2: raid_readparts.c --]
[-- Type: text/x-csrc, Size: 642 bytes --]
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/ioctl.h>
#include <stdlib.h>
#include <fcntl.h>
#include <stdio.h>
#include <linux/raid/md_u.h>
#include <linux/major.h>
#include </usr/include/linux/fs.h>
int main(int argc, char *argv[])
{
int fd;
if (argc != 2)
fprintf(stderr, "Usage: %s <md device>\n", argv[0]);
if ((fd = open(argv[1], O_RDONLY)) == -1) {
fprintf(stderr, "Can't open md device %s\n", argv[1]);
return -1;
}
if (ioctl(fd, BLKRRPART, NULL) != 0) {
fprintf(stderr, "ioctl failed\n");
close (fd);
return -1;
}
close (fd);
return 0;
}
next prev parent reply other threads:[~2007-04-24 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:53 Partitioned arrays initially missing from /proc/partitions Mike Accetta
2007-04-23 14:56 ` David Greaves
2007-04-23 19:31 ` Mike Accetta
2007-04-23 23:52 ` Neil Brown
2007-04-24 9:22 ` David Greaves
2007-04-24 10:57 ` Neil Brown
2007-04-24 12:00 ` David Greaves
2007-04-24 10:49 ` David Greaves [this message]
2007-04-24 11:38 ` Neil Brown
2007-04-24 12:32 ` David Greaves
2007-05-07 8:28 ` David Greaves
2007-05-07 9:01 ` Neil Brown
2007-04-24 15:39 ` Doug Ledford
2007-04-24 9:37 ` David Greaves
2007-04-24 9:46 ` David Greaves
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=462DE0A2.6000701@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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 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.