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

Stop discarding disk contents #172

Merged
merged 1 commit into from
Feb 25, 2020
Merged

Stop discarding disk contents #172

merged 1 commit into from
Feb 25, 2020

Conversation

bgilbert
Copy link
Contributor

In 7b89735 we started issuing block discard requests over the destination disk, before install and after install failure, as a courtesy to SSD wear levelers and LVM thin pools. However, this assumes that the entire disk is ours to discard. Users might want to reprovision an existing machine without disturbing a data partition they've created on the boot disk; their Ignition config can then recreate the data partition in the same place and reuse the filesystem inside.

Discard the discard functionality for now. We shouldn't require users to explicitly specify --dont-delete-my-data, and the semantics of --delete-my-data (under whatever name, e.g. --discard-device) would be difficult to explain relative to the value they provide. Users can still run blkdiscard(8) before coreos-installer if they need that functionality.

Fixes #170.

In 7b89735 we started issuing block discard requests over the
destination disk, before install and after install failure, as a
courtesy to SSD wear levelers and LVM thin pools.  However, this
assumes that the entire disk is ours to discard.  Users might want to
reprovision an existing machine without disturbing a data partition
they've created on the boot disk; their Ignition config can then
recreate the data partition in the same place and reuse the filesystem
inside.

Discard the discard functionality for now.  We shouldn't require users
to explicitly specify --dont-delete-my-data, and the semantics of
--delete-my-data (under whatever name, e.g. --discard-device) would
be difficult to explain relative to the value they provide.  Users can
still run blkdiscard(8) before coreos-installer if they need that
functionality.

Fixes #170.
Copy link
Member

@cgwalters cgwalters left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My first instinct would have been an option but eh you're right, easier to use blkdiscard.

LGTM.

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

Successfully merging this pull request may close these issues.

Consider adding install option to skip erasing disk
2 participants