From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH v2] ocfs2: return -EROFS to mount.ocfs2 if inode block is invalid
Date: Tue, 26 Dec 2017 19:22:54 +0800 [thread overview]
Message-ID: <5A42310E.5070401@huawei.com> (raw)
In-Reply-To: <63ADC13FD55D6546B7DECE290D39E373F2909146@H3CMLB12-EX.srv.huawei-3com.com>
Hi Changwei,
On 2017/12/26 19:18, Changwei Ge wrote:
> Hi Jun,
>
> On 2017/12/26 19:10, piaojun wrote:
>> If metadata is corrupted such as 'invalid inode block', we will get
>> failed by calling 'mount()' and then set filesystem readonly as below:
>>
>> ocfs2_mount
>> ocfs2_initialize_super
>> ocfs2_init_global_system_inodes
>> ocfs2_iget
>> ocfs2_read_locked_inode
>> ocfs2_validate_inode_block
>> ocfs2_error
>> ocfs2_handle_error
>> ocfs2_set_ro_flag(osb, 0); // set readonly
>>
>> In this situation we need return -EROFS to 'mount.ocfs2', so that user
>> can fix it by fsck and mount again rather than doing meaningless retry.
>> In addition, 'mount.ocfs2' should be updated correspondingly as it only
>> return 1 for all errno. And I will post a patch for 'mount.ocfs2' too.
>>
>> Signed-off-by: Jun Piao <piaojun@huawei.com>
>> Reviewed-by: Alex Chen <alex.chen@huawei.com>
>> ---
>> fs/ocfs2/super.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
>> index 040bbb6..f46f6a6 100644
>> --- a/fs/ocfs2/super.c
>> +++ b/fs/ocfs2/super.c
>> @@ -474,7 +474,7 @@ static int ocfs2_init_global_system_inodes(struct ocfs2_super *osb)
>> new = ocfs2_get_system_file_inode(osb, i, osb->slot_num);
>> if (!new) {
>> ocfs2_release_system_inodes(osb);
>> - status = -EINVAL;
>> + status = ocfs2_is_soft_readonly(osb) ? -EROFS : -EINVAL;
>> mlog_errno(status);
>> /* FIXME: Should ERROR_RO_FS */
>
> If your patch is applied, shall we remove above comment line?
>
> Thanks,
> Changwei
>
Good suggestion! If nobody rejects it, I will remove that comment.
thanks,
Jun
>> mlog(ML_ERROR, "Unable to load system inode %d, "
>> @@ -505,7 +505,7 @@ static int ocfs2_init_local_system_inodes(struct ocfs2_super *osb)
>> new = ocfs2_get_system_file_inode(osb, i, osb->slot_num);
>> if (!new) {
>> ocfs2_release_system_inodes(osb);
>> - status = -EINVAL;
>> + status = ocfs2_is_soft_readonly(osb) ? -EROFS : -EINVAL;
>> mlog(ML_ERROR, "status=%d, sysfile=%d, slot=%d\n",
>> status, i, osb->slot_num);
>> goto bail;
>>
>
> .
>
next prev parent reply other threads:[~2017-12-26 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 11:09 [Ocfs2-devel] [PATCH v2] ocfs2: return -EROFS to mount.ocfs2 if inode block is invalid piaojun
2017-12-26 11:18 ` Changwei Ge
2017-12-26 11:22 ` piaojun [this message]
2017-12-26 11:27 ` Changwei Ge
2017-12-26 11:31 ` Joseph Qi
2017-12-27 1:59 ` 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=5A42310E.5070401@huawei.com \
--to=piaojun@huawei.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 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.