All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2: why not set EROFS when clearing bits multiple times
Date: Wed, 6 Nov 2013 09:05:48 +0800	[thread overview]
Message-ID: <527995EC.402@huawei.com> (raw)
In-Reply-To: <527983CA.8050403@oracle.com>

On 2013/11/6 7:48, Srinivas Eeda wrote:
> On 11/05/2013 12:20 AM, Joseph Qi wrote:
>> In ocfs2_block_group_clear_bits, when num_bits != bits_cleared, it just
>> log an error message without setting EROFS.
>>
>> The code is below:
>>
>> 	/*
>> 	 * If encountered, it means we are clearing bits multiple times. While
>> 	 * we are handling the case, we still need to be alerted to its
>> 	 * occurrence. Hence, marking it as an ERROR and not NOTICE.
>> 	 */
>> 	if (num_bits != bits_cleared) {
>> 		mlog(ML_ERROR, "Trying to clear %u bits at offset %u in group "
>> 		     "descriptor # %llu (device %s), needed to clear %u bits\n",
>> 		     num_bits, bit_off,
>> 		     (unsigned long long)le64_to_cpu(bg->bg_blkno),
>> 		     alloc_inode->i_sb->s_id, bits_cleared);
>> 	}
>>
>> If this case happens, does it mean the filesystem have already been
>> inconsistent? If so, why not set EROFS when this case happens?
>> Or anyone knows which case will casue bits to be cleared multiple times?
> in the past we have seen a case where the number of free bits were more 
> than actual bits which took fs read only. I think running fsck fixed 
> this count but didn't report any other issues. So it appeared there is a 
> case where we were trying to free some bits twice. Since there was no 
> real corruption we didn't take the fs read only.
> 
> My guess is this problem may in code paths of releasing unused 
> localalloc bits back to global bitmap.
> 
Thanks for your quick reply.
Any more details about the case which led to this change? Now we have
encountered this error message but have no idea why it happened.
And we will investigate the code paths what your mentioned.

>> Thanks very much.
>>
>>
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel at oss.oracle.com
>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 
> 

      reply	other threads:[~2013-11-06  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  8:20 [Ocfs2-devel] ocfs2: why not set EROFS when clearing bits multiple times Joseph Qi
2013-11-05 23:48 ` Srinivas Eeda
2013-11-06  1:05   ` Joseph Qi [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=527995EC.402@huawei.com \
    --to=joseph.qi@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.