Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run out of memory and segfault reported? #10

Closed
uestcmahone opened this issue Mar 27, 2020 · 1 comment
Closed

Run out of memory and segfault reported? #10

uestcmahone opened this issue Mar 27, 2020 · 1 comment

Comments

@uestcmahone
Copy link

  1. After executing two concurrent tasks for ext4 and f2fs fuzz for about 36 hours on x86_64 server with 282GB memory , ext4-combined-consistency and f2fs-combined-consistency reported segfault,
    and I found there is not enough memory available, tmpfs-separate consumes almost all memory, is this a bug or is it caused by my misuse?

none tmpfs 142G 142G 0 100% /tmp/mosbench/tmpfs-separate/1
none tmpfs 142G 142G 0 100% /tmp/mosbench/tmpfs-separate/4

~/hydra/src$ free -m
total used free shared buff/cache available
Mem: 289419 1510 1006 279783 286903 5485
Swap: 95366 9741 85625

@squizz617
Copy link
Contributor

squizz617 commented Apr 1, 2020

For performance, tmpfs uses the main memory instead of disk to store files. It seems that too many bug reports (logs and buggy disk images) were stored under tmpfs, and as a result your system ran out of memory. Segfault of ext4-combined-consistency must be another side-effect of that.
You can consider using a disk with some free space left instead of tmpfs, or occasionally clearing the log directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants