-
Notifications
You must be signed in to change notification settings - Fork 118
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
Please support in-place writing of nested images #285
Comments
Alternatively, using |
Or |
As far as I can see, the flag to enable reflink/clone was never implemented for Writing in place would target the first disk image using that filesystem? And copy to others from there? It seems that would be complex to implement. |
I would implement in place only if the fs image is used exactly once. |
That's the common use-case and I think it makes sense to optimize that |
The downside of using I concur with optimizing the common case (image being used exactly once). What is requested here is an optimization and not expected to pose a semantic difference. I recommend labeling the issue wishlist in any case. |
When writing an ext4 or vfat image to a partition, the filesystem image is first created and then copied. Given larger images (e.g. including Gnome), this poses a non-trivial slowdown (especially when the /tmp location is not yet tmpfs). Many of the filesystem management utils now support offesets and sizes and therefore support in-place creation in a larger image in principle.
For instance
mkfs.ext4
has-E offset=...
. Formtools
, the offset can be added to an image filename after@@
.The text was updated successfully, but these errors were encountered: