From: Joseph Qi <jiangqi903@gmail.com>
To: Gang He <ghe@suse.com>, jlbec@evilplan.org, mfasheh@versity.com
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: give an obvious tip for dismatch cluster names
Date: Fri, 19 May 2017 08:46:41 +0800 [thread overview]
Message-ID: <f872a4c9-7040-85c2-1cd6-f8ee9304ba72@gmail.com> (raw)
In-Reply-To: <591DEB5B020000F900076CAE@prv-mh.provo.novell.com>
Hi Gang,
As you described, only fsdlm will return this error and fsdlm has
already print the same message. So why should we add it outside again?
Thanks,
Joseph
On 17/5/18 18:43, Gang He wrote:
> Hi Joseph,
>
>
>>>>
>> Hi Gang,
>>
>> How can we confirm EBADR is only because cluster name mismatch?
>> Since the cluster stack may be o2cb(o2dlm) or user(fsdlm).
> I looked through all the code of OCFS2 (include o2cb), there is not any place which returns this error.
> In fact, the function calling patch ocfs2_fill_super -> ocfs2_mount_volume -> ocfs2_dlm_init -> dlm_new_lockspace
> is very specific path, we can use this errorno to give the uses a more clear tip,
> since this case looks like a little common during cluster migration, but the customer can quickly
> get the failure cause if there is a error printing.
> Also, I think there is not possible to add this errorno in o2cb path during ocfs2_dlm_init, since o2cb code has been stable for
> a long time.
>
> Thanks
> Gang
>
>>
>> Thanks,
>> Joseph
>>
>> On 17/5/18 14:35, Gang He wrote:
>>> This patch is used to add an obvious error message, due to
>>> dismatch cluster names between on-disk and in the current cluster.
>>> We can meet this case during OCFS2 cluster migration, if we can
>>> give the user an obvious tip for why they can not mount the file
>>> system after migration, they can quickly fix this dismatch problem.
>>> Second, also move printing ocfs2_fill_super() errno to the front
>>> of ocfs2_dismount_volume() function, since ocfs2_dismount_volume()
>>> will also print it's own message.
>>>
>>> Signed-off-by: Gang He <ghe@suse.com>
>>> ---
>>> fs/ocfs2/super.c | 8 ++++++--
>>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
>>> index ca1646f..5575918 100644
>>> --- a/fs/ocfs2/super.c
>>> +++ b/fs/ocfs2/super.c
>>> @@ -1208,14 +1208,15 @@ static int ocfs2_fill_super(struct super_block *sb,
>> void *data, int silent)
>>> read_super_error:
>>> brelse(bh);
>>>
>>> + if (status)
>>> + mlog_errno(status);
>>> +
>>> if (osb) {
>>> atomic_set(&osb->vol_state, VOLUME_DISABLED);
>>> wake_up(&osb->osb_mount_event);
>>> ocfs2_dismount_volume(sb, 1);
>>> }
>>>
>>> - if (status)
>>> - mlog_errno(status);
>>> return status;
>>> }
>>>
>>> @@ -1843,6 +1844,9 @@ static int ocfs2_mount_volume(struct super_block *sb)
>>> status = ocfs2_dlm_init(osb);
>>> if (status < 0) {
>>> mlog_errno(status);
>>> + if (status == -EBADR)
>>> + mlog(ML_ERROR, "couldn't mount because cluster name on"
>>> + " disk does not match the running cluster name.\n");
>>> goto leave;
>>> }
>>>
>>>
>
next prev parent reply other threads:[~2017-05-19 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 6:35 Gang He
2017-05-18 9:42 ` [Ocfs2-devel] " Joseph Qi
2017-05-18 10:43 ` Gang He
2017-05-19 0:46 ` Joseph Qi [this message]
2017-05-19 2:15 ` Gang He
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=f872a4c9-7040-85c2-1cd6-f8ee9304ba72@gmail.com \
--to=jiangqi903@gmail.com \
--cc=ghe@suse.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@versity.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®