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

[Forknet] Lock vital files to prevent mocknet corruption #10959

Open
Tracked by #10542
VanBarbascu opened this issue Apr 5, 2024 · 0 comments
Open
Tracked by #10542

[Forknet] Lock vital files to prevent mocknet corruption #10959

VanBarbascu opened this issue Apr 5, 2024 · 0 comments

Comments

@VanBarbascu
Copy link
Contributor

VanBarbascu commented Apr 5, 2024

Forknet has files like that should be immutable. Suck files are snapshots used to revert to when a test is restarted. Getting in that state takes time to achieve and if one host gets corrupted, it may invalidate the whole forknet test.

To prevent accidental loss, those files can be marked as immutable with file attributes:

# set the immutable attribute
sudo chattr +i folder_name

# remove the immutable attribute
sudo chattr -i folder_name
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

No branches or pull requests

1 participant