From: Alex Elder <aelder@sgi.com>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: Allison Henderson <achender@linux.vnet.ibm.com>, xfs@oss.sgi.com
Subject: Re: XFS Test Case:252 - Shows Wrong Output
Date: Thu, 14 Jul 2011 13:40:15 -0500 [thread overview]
Message-ID: <1310668815.2067.53.camel@doink> (raw)
In-Reply-To: <BANLkTi=yk3Z2KUnwtr6-H1BNhWG-XvJZPw@mail.gmail.com>
On Fri, 2011-06-24 at 12:45 +0530, Amit Sahrawat wrote:
> This has to be an issue with everyone who is using XFS version which is not
> supporting "fpunch" but still none has raised this. As per my view, the
> support checking function *_require_xfs_io_falloc_punch() *is not working
> correctly otherwise it should return from that point.
>
> *Instead of:*
> echo $testio | grep -q "not found"
> If we are sure of a *"hole"* from that command, then we can grep for "hole"
> in $testio.
>
> Please correct me if I am wrong.
>
> Thanks & Regards,
> Amit Sahrawat
I think what you are saying is that in your environment,
_require_xfs_io_falloc_punch() is not properly deciding
whether the fpunch operation is supported. And you are
suggesting a way to determine it properly, is that right?
Unfortunately it is difficult to know whether your
suggestion is a proper fix without knowing details of
your current system, as well as details about what
you are seeing that is incorrect.
We welcome suggested fixes from people. Often that
takes the form of a patch that proposes a fix, but
if enough precise information is provided about the
problem we can sometimes develop a fix for you.
Can you supply either a patch with a proposed fix,
or else provide more information about exactly
what you are seeing? Otherwise I don't think
we're going to be able to help.
Thanks.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-14 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:24 XFS Test Case:252 - Shows Wrong Output Amit Sahrawat
2011-06-22 10:48 ` Amit Sahrawat
2011-06-22 17:22 ` Allison Henderson
2011-06-22 17:36 ` Allison Henderson
2011-06-23 5:51 ` Amit Sahrawat
2011-06-23 6:20 ` Dave Chinner
2011-06-23 6:36 ` Amit Sahrawat
2011-06-23 10:57 ` Amit Sahrawat
2011-06-23 11:30 ` Amit Sahrawat
2011-06-24 7:15 ` Amit Sahrawat
2011-07-14 18:40 ` Alex Elder [this message]
2011-06-22 22:57 ` Dave Chinner
2011-06-23 5:47 ` Amit Sahrawat
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=1310668815.2067.53.camel@doink \
--to=aelder@sgi.com \
--cc=achender@linux.vnet.ibm.com \
--cc=amit.sahrawat83@gmail.com \
--cc=xfs@oss.sgi.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