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

Failing to write more than 2147479552, unclear message #21

Closed
GoogleCodeExporter opened this issue Mar 29, 2015 · 3 comments
Closed

Failing to write more than 2147479552, unclear message #21

GoogleCodeExporter opened this issue Mar 29, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. ioping . -s 4G (actually starting from 2G)


What is the expected output? What do you see instead?

I expect normal workflow, instead I get:
ioping: write failed: Success

What version of the product are you using? On what operating system?

Centos 7.1
3.10.0-123.20.1.el7.x86_64
ioping 0.8

Please provide any additional information below.
At least the output does not lead to anywhere near problem. I have about 20Gig 
free, and it fails to write 2147479552. I use xfs here, and the limit is: 
Maximum File Size = 9 Million TB = 9 ExaB. It may be a problem on my system, 
yet the message given is unclear.

An excerpt from strace:
open("./ioping.jIXgE6", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
unlink("./ioping.jIXgE6")               = 0
pwrite(3, "********************************"..., 4294967296, 0) = 2147479552
write(2, "ioping: ", 8ioping: )                 = 8
write(2, "write failed", 12write failed)            = 12
write(2, ": ", 2: )                       = 2
write(2, "Success\n", 8Success
)                = 8

Original issue reported on code.google.com by mike.mer...@gmail.com on 25 Mar 2015 at 5:06

@GoogleCodeExporter
Copy link
Author

That's kernel limitation: syscalls read/write can handle up to MAX_RW_COUNT = 
2G-4K = 2147479552 at once.

I'll do something with that.

Original comment by koct9i on 25 Mar 2015 at 6:11

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

There are people on the internet suggesting using pwrite in a loop. At the 
first glance it seemed to me that pwrite arguments in the loop are messed up. 
I'll try to do something with it too.

Original comment by mike.mer...@gmail.com on 26 Mar 2015 at 6:13

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

fixed in git version

Original comment by koct9i on 29 Mar 2015 at 12:55

  • Added labels: ****
  • Removed labels: ****

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

No branches or pull requests

2 participants