From: Konstantin Boyandin <konstantin@vpseer.com>
To: fio@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: fio 2.0.9 fails: shmget: No space left on device
Date: Fri, 21 Sep 2012 19:34:00 +0700 [thread overview]
Message-ID: <505C5EB8.5010701@vpseer.com> (raw)
In-Reply-To: <505C5A6A.5020904@kernel.dk>
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.
Sincerely,
Konstantin
next prev parent reply other threads:[~2012-09-21 12:34 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 [this message]
2012-09-21 12:37 ` Jens Axboe
2012-09-21 13:02 ` Konstantin Boyandin
2012-09-21 13:06 ` Jens Axboe
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=505C5EB8.5010701@vpseer.com \
--to=konstantin@vpseer.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
/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