From: "Krzysztof Błaszkowski" <kb@sysmikro.com.pl>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: posix_fallocate
Date: Tue, 11 May 2010 16:20:20 +0200 [thread overview]
Message-ID: <201005111620.21081.kb@sysmikro.com.pl> (raw)
In-Reply-To: <4BE85436.5040402@sandeen.net>
On Monday 10 May 2010 20:45, Eric Sandeen wrote:
> Krzysztof Błaszkowski wrote:
> > On Monday 10 May 2010 16:39, Eric Sandeen wrote:
> >> Krzysztof Błaszkowski wrote:
>
> ...
>
> >>> We stick with 2.6.31.5 which seems to be good for us. We do not change
> >>> kernels easily, as soon as higher revision arrives because it doesn't
> >>> make sense from stability point of view. We have seen too many times
> >>> regression bugs so if we are confident with some revision then there is
> >>> no point to change this.
> >>
> >> It was just a testing suggestion, but I already tested upstream and the
> >> problem persists, now just need to find the time to dig into it.
> >
> > I see and I am glad you confirmed this. Do you think that fallocate
> > called many times with fixed size and increasing offset will work better
> > than one time call with huge size @ 0 offset ?
>
> I'd expect that to work; it's certainly worth a test
agreed.
> , and please send your
> results back to the list ;)
okay, will do this tomorrow.
BUT let's think about possible results:
- test will fail. nothing to comment.
- test will pass. this is interesting case.
A passed test - does this test prove anything ?
it may but this is not obvious.
If the fault was caused by some algorithmic mistake (some table size, buffer
size according to input size) then the test result could be a proof.
but if it fails due to missing spinlock/mutex elsewhere then we talk about
probability of failure which depends on requested size.
bad news is that this failure happens at various sizes depending on hw
configuration. On some boxes the threshold point is abt 7T while another
boxes fail after e.g. 15T.
I am not sure about any relationship between these boxes in installed memory,
amount of logical cores and theirs frequency (and current workload)
In this later case the test will prove nothing. If i run it 5 times and it
passed 5 times it would mean only that i was lucky.
as long as we don't know the exact nature of this fault we can't consider such
test as reliable fix.
Krzysztof
PS of course i will try this just to satisfy curiosity tomorrow afternoon (PL
time) as all high capacity storage has been shipped to customers already.
>
> thanks,
> -Eric
>
> > Krzysztof
> >
> >> -Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-11 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 8:22 posix_fallocate Krzysztof Błaszkowski
2010-05-07 9:23 ` posix_fallocate Stan Hoeppner
2010-05-07 9:48 ` posix_fallocate Krzysztof Błaszkowski
2010-05-07 10:07 ` posix_fallocate Krzysztof Błaszkowski
2010-05-07 10:42 ` posix_fallocate Stan Hoeppner
2010-05-07 10:56 ` posix_fallocate Krzysztof Błaszkowski
2010-05-07 16:26 ` posix_fallocate Eric Sandeen
2010-05-07 16:53 ` posix_fallocate Eric Sandeen
2010-05-07 22:16 ` posix_fallocate Dave Chinner
2010-05-10 7:11 ` posix_fallocate Krzysztof Błaszkowski
2010-05-10 14:39 ` posix_fallocate Eric Sandeen
2010-05-10 18:17 ` posix_fallocate Krzysztof Błaszkowski
2010-05-10 18:45 ` posix_fallocate Eric Sandeen
2010-05-11 14:20 ` Krzysztof Błaszkowski [this message]
2010-05-11 14:54 ` posix_fallocate Eric Sandeen
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=201005111620.21081.kb@sysmikro.com.pl \
--to=kb@sysmikro.com.pl \
--cc=sandeen@sandeen.net \
--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