From: Jens Axboe <axboe@kernel.dk>
To: Konstantin Boyandin <konstantin@vpseer.com>
Cc: fio@vger.kernel.org
Subject: Re: fio 2.0.9 fails: shmget: No space left on device
Date: Fri, 21 Sep 2012 15:06:44 +0200 [thread overview]
Message-ID: <505C6664.7070907@kernel.dk> (raw)
In-Reply-To: <505C6557.1070003@vpseer.com>
On 09/21/2012 03:02 PM, Konstantin Boyandin wrote:
> Hello Jens,
>
> On 09/21/2012 07:37 PM, Jens Axboe wrote:
>> On 09/21/2012 02:34 PM, Konstantin Boyandin wrote:
>>> Hello Jens,
>>>
>>> On 09/21/2012 07:15 PM, Jens Axboe wrote:
>>>> On 09/21/2012 01:51 PM, Konstantin Boyandin wrote:
>>>>> Hello,
>>>>>
>>>>> When trying to run the command line
>>>>>
>>>>> fio --bs=4k --size=128m --direct=1 --runtime=10 --rw=randread
>>>>> --numjobs=32 --group_reporting --time_based --name=128m
>>>>>
>>>>> I see only this:
>>>>>
>>>>> shmget: No space left on device
>>>>> error: failed to setup shm segment
>>>>
>>>> Hmmm. Can you send me the output of:
>>>>
>>>> $ grep . /proc/sys/kernel/shm*
>>>
>>> /proc/sys/kernel/shmall:2097152
>>> /proc/sys/kernel/shmmax:33554432
>>> /proc/sys/kernel/shmmni:4096
>>> /proc/sys/kernel/shm_rmid_forced:0
>>>
>>>> $ ipcs -l
>>>
>>> ------ Shared Memory Limits --------
>>> max number of segments = 4096
>>> max seg size (kbytes) = 32768
>>> max total shared memory (kbytes) = 8388608
>>> min seg size (bytes) = 1
>>>
>>> ------ Semaphore Limits --------
>>> max number of arrays = 128
>>> max semaphores per array = 250
>>> max semaphores system wide = 32000
>>> max ops per semop call = 32
>>> semaphore max value = 32767
>>>
>>> ------ Messages: Limits --------
>>> max queues system wide = 6365
>>> max size of message (bytes) = 8192
>>> default max size of queue (bytes) = 16384
>>>
>>>> $ ipcs -m
>>>
>>> ------ Shared Memory Segments --------
>>> key shmid owner perms bytes nattch status
>>>
>>> The VM wasn't restarted after the fio failed run.
>>>
>>> fio was run by root user.
>>
>> Oh, try with this please.
>>
>> diff --git a/init.c b/init.c
>> index da1f472..b3215f5 100644
>> --- a/init.c
>> +++ b/init.c
>> @@ -254,7 +254,7 @@ static int setup_thread_area(void)
>> shm_id = shmget(0, size, IPC_CREAT | 0600);
>> if (shm_id != -1)
>> break;
>> - if (errno != EINVAL && errno != ENOMEM) {
>> + if (errno != EINVAL && errno != ENOMEM && errno != ENOSPC) {
>> perror("shmget");
>> break;
>> }
>
> The patch worked fine, thank you!
> fio works now as expected.
Excellent. Thanks for the report, fix has been committed.
--
Jens Axboe
prev parent reply other threads:[~2012-09-21 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 11:51 fio 2.0.9 fails: shmget: No space left on device Konstantin Boyandin
2012-09-21 12:15 ` Jens Axboe
2012-09-21 12:34 ` Konstantin Boyandin
2012-09-21 12:37 ` Jens Axboe
2012-09-21 13:02 ` Konstantin Boyandin
2012-09-21 13:06 ` Jens Axboe [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=505C6664.7070907@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=konstantin@vpseer.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