diff options
author | Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> | 2011-10-23 21:24:17 -0300 |
---|---|---|
committer | Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> | 2011-10-23 21:24:17 -0300 |
commit | e2055835fda3d2c99378231e4595472bf28631c4 (patch) | |
tree | 6676cc95ef8209a87cbfe29bbbb19fae0035cd99 /archiso/install/archiso_loop_mnt | |
parent | 91e11c30f46094bcc7352f42e11799f662b6b689 (diff) | |
download | archiso32-e2055835fda3d2c99378231e4595472bf28631c4.tar.xz |
[archiso] Allow persistent cow dm-snapshots.
Add some options to control where all COW files will be located.
Until this moment all files are located in a tmpfs filesystem.
Now is posible to set a device via a filesystem label or device node
plus a directory, where all these files will be stored.
All dm-snapshot devices will be persistent by default,
but this can be changed if wanted.
Take care, a filesystem that does not support sparse files maybe
is not the best choice for COW files, because they are created with
the same size (is apparent) like the read-only device (the image.fs inside .sfs).
Of course sooner or later, depending on use, these files actually end up
being as big as the read-only device.
KNOW-ISSUE: On shutdown in step "Unmounting Filesystems" will [FAIL],
all filesystem except $cow_device, will be unmounted/remounted-ro.
For this reason this change needs an archiso_shutdown hook, thats
unmount all block devices used by archiso. (Work in progress)
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Diffstat (limited to 'archiso/install/archiso_loop_mnt')
0 files changed, 0 insertions, 0 deletions