From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: meyering@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH] Print correct md device name if write_init_super fails
Date: Wed, 22 Feb 2012 12:00:15 +0100 [thread overview]
Message-ID: <4F44CABF.7070508@redhat.com> (raw)
In-Reply-To: <20120222065335.268c8aae@notabene.brown>
On 02/21/12 20:53, NeilBrown wrote:
> On Tue, 21 Feb 2012 13:30:02 +0100 Jes.Sorensen@redhat.com wrote:
>> diff --git a/Create.c b/Create.c
>> index 90ff3ed..702ac34 100644
>> --- a/Create.c
>> +++ b/Create.c
>> @@ -926,7 +926,7 @@ int Create(struct supertype *st, char *mddev,
>> if (st->ss->write_init_super(st)) {
>> fprintf(stderr,
>> Name ": Failed to write metadata to %s\n",
>> - dv->devname);
>> + mddev);
>> st->ss->free_super(st);
>> goto abort_locked;
>> }
>
> Hi Jes,
> this doesn't seem right. You message would print e.g.
>
> mdadm: Failed to write metadata to /dev/md1
>
> but one doesn't write metadata to an array, one writes it to the member
> devices.
> Each ->write_init_super function should print out a message if a write
> fails. So I think we just remove the error message here, and make sure
> each ->write_init_super does print an error in each case (there might be a
> couple of holes).
>
> Could you try that approach instead?
Hi Neil,
Makes sense - this was the best I could do in the global context, but I
see the various write_init_super() functions already print errors.
Replacement patch coming your way in 60 seconds or so.
Cheers,
Jes
prev parent reply other threads:[~2012-02-22 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 12:30 [PATCH] Print correct md device name if write_init_super fails Jes.Sorensen
2012-02-21 19:53 ` NeilBrown
2012-02-22 11:00 ` Jes Sorensen [this message]
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=4F44CABF.7070508@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=meyering@redhat.com \
--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.