All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] OCFS2: Log -EIO errors just when hit them.
Date: Thu, 23 Apr 2009 00:18:01 +0800	[thread overview]
Message-ID: <49EF4339.4020706@oracle.com> (raw)
In-Reply-To: <49EF3AC7.9050608@oracle.com>

Hi,

I noticed ocfs2_end_buffer_io_sync() is only for 1.2
need to do something for 1.4

regards,
wengang.

Wengang Wang wrote:
> Hi Sunil and Joel,
>
> For the EIO log problem, ocfs2_end_buffer_io_sync() is used as the 
> callback function b_end_io
> for both READ and WRITE.
> I noticed that in this function,
>
> if (!uptodate)
>     mlog_errno(-EIO);
>
> Isn't the 2 lines enough to log EIO errors?
>
> regards,
> wengang.
>
> Sunil Mushran wrote:
>   
>> I imagine this is for the unlogged EIOs that have been reported.
>>
>> From my scan, at least in mainline, all these EIOs are being logged
>> by the caller. So this patch is not adding any value. Can you double
>> check that please?
>>
>> Now it could be that the reported EIOs are on 1.2/1.4 and that those
>> trees are missing the mlogs. In that case, the patch should be specific
>> to the tree.
>>
>> BTW, the (u64) should be (unsigned long long). This ensures that
>> it compiles warning free on all arches.
>>
>>     
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>   

  reply	other threads:[~2009-04-22 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  7:38 [Ocfs2-devel] [PATCH 1/1] OCFS2: Log -EIO errors just when hit them wengang wang
2009-04-17 21:48 ` Sunil Mushran
2009-04-22 15:41   ` Wengang Wang
2009-04-22 16:18     ` Wengang Wang [this message]
2009-04-22  8:37       ` Tao Ma
2009-04-22 16:53         ` Wengang Wang

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=49EF4339.4020706@oracle.com \
    --to=wen.gang.wang@oracle.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.