From: Eric Sandeen <sandeen@sandeen.net>
To: Mike Gao <ygao.linux@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: What should to do with ASSERT failed
Date: Mon, 30 Aug 2010 18:32:08 -0500 [thread overview]
Message-ID: <4C7C3F78.5020500@sandeen.net> (raw)
In-Reply-To: <AANLkTinXDQoo7ZU+w2V7N7zBrxdS=Tc71MNZ7M4R5A9w@mail.gmail.com>
Mike Gao wrote:
> Thanks very much for help. The kernel is pretty old, 2.6.19 but the xfs
> is pretty new.
> the block size is 512 and use mmap for test with write and read compare.
> (xfstest 074).
>
> If I ignored this ASSERT(comment out), the test will failed. I guess
> because some pages never written to disk.
>
FWIW, in your case, if you are not expecting to do IO like test 194
then maybe you'd be better off w/o this patch if it's causing problems
in more normal IO patterns ...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-30 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 20:55 What should to do with ASSERT failed Mike Gao
2010-08-30 21:47 ` Eric Sandeen
2010-08-30 22:56 ` Mike Gao
2010-08-30 23:30 ` Eric Sandeen
2010-08-30 23:32 ` Eric Sandeen [this message]
2010-08-31 0:30 ` Dave Chinner
2010-08-31 22:50 ` Mike Gao
2010-08-31 23:39 ` Dave Chinner
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=4C7C3F78.5020500@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=ygao.linux@gmail.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