public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: "Krzysztof Błaszkowski" <kb@sysmikro.com.pl>
Cc: xfs@oss.sgi.com
Subject: Re: posix_fallocate
Date: Mon, 10 May 2010 09:39:48 -0500	[thread overview]
Message-ID: <4BE81AB4.7000600@sandeen.net> (raw)
In-Reply-To: <201005100911.52491.kb@sysmikro.com.pl>

Krzysztof Błaszkowski wrote:
> On Friday 07 May 2010 18:53, Eric Sandeen wrote:
>> Eric Sandeen wrote:
>>> Krzysztof Błaszkowski wrote:
>>>> Hello,
>>>>
>>>> I use this to preallocate large space but found an issue.
>>>> Posix_fallocate works right with sizes like 100G, 1T and even 10T on
>>>> some boxes (on some other can fail after e.g. 7T threshold) but if i
>>>> tried e.g. 16T the user space process would be "R"unning forever and it
>>>> is not interruptible. Furthermore some other not related processes like
>>>> sshd, bash enter D state. There is nothing in kernel log.
>> Oh, one thing you should know is that depending on your version of glibc,
>> posix_fallocate may be writing 0s and not using preallocation calls.
> 
> I am absolutely sure that recent libc doesn't emulate this syscall 

right, recent glibc does not (unless the underlying fs doesn't support it)

...

> 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.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-05-10 14:37 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       ` Eric Sandeen [this message]
2010-05-10 18:17         ` posix_fallocate Krzysztof Błaszkowski
2010-05-10 18:45           ` posix_fallocate Eric Sandeen
2010-05-11 14:20             ` posix_fallocate Krzysztof Błaszkowski
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=4BE81AB4.7000600@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=kb@sysmikro.com.pl \
    --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