From: Goldwyn Rodrigues <rgoldwyn@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Ocfs2-devel Digest, Vol 138, Issue 31 review
Date: Wed, 14 Oct 2015 22:25:02 -0500 [thread overview]
Message-ID: <561F1C8E.80504@suse.com> (raw)
In-Reply-To: <2015101509311504278915@h3c.com>
On 10/14/2015 09:54 PM, Zhangguanghui wrote:
> Thanks for reply, just like what Goldwyn said, there is a critical
> result for such a simple process.
> It has encountered EROFS all the time while calling ocfs2_start_trans,
> even if the storage is back to normal.
> I 'm trying to make some
> other changes and don't know if the error is still being shown.
> Any feedback or suggestionabout this process (positive or negative)
> would be greatly appreciated.
> thanks again
>
Have you tried fsck.ocfs2? If yes, what does the log say?
--
Goldwyn
prev parent reply other threads:[~2015-10-15 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1701.1440805574.13254.ocfs2-devel@oss.oracle.com>
2015-10-14 7:49 ` [Ocfs2-devel] Ocfs2-devel Digest, Vol 138, Issue 31 review Zhangguanghui
2015-10-14 8:13 ` Joseph Qi
2015-10-14 8:45 ` Zhangguanghui
2015-10-14 8:57 ` Joseph Qi
2015-10-14 11:53 ` Goldwyn Rodrigues
2015-10-15 2:54 ` Zhangguanghui
2015-10-15 3:25 ` Goldwyn Rodrigues [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=561F1C8E.80504@suse.com \
--to=rgoldwyn@suse.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