-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
r2: expending a file don't seem to work as expected #23475
Comments
|
Resizing the underlying fd doesnt imply syncing it up with the map. Those are different io layers, you can disable io.va with the e command or use omr manually. And i think omfg also updated map sizes not just perms but im just answering from memory. Maybe @condret knows more ways to achieve the same |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Description
I'm using r2 as a simple hex editor. While doing so I noticed that expending a binary file with
r
and checking the result withpx
shows that the file size was not affected. Thew
command doesn't seem to be aware of the additionally allocated space too. If I quit withq
and open the same file again I see that the size was changed correctly. Truncating the file withr
seems to work properly.Test
The text was updated successfully, but these errors were encountered: