You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The du command reports significant data (e.g., 153MB) in the /ostree/repo/tmp/ directory after an update fails, whereas on systems with successful updates, this tmp folder remains empty. Additionally, the /ostree/repo/objects location also fills up, contributing to the issue.
It appears that the tmp directory is not being cleaned up properly. I've seen reports of users manually deleting these contents to free up disk space. However, the files in /ostree/repo/objects also occupy space, causing updates to fail on the Embedded Linux devices.
Request for Feedback:
Has anyone else experienced similar issues with the /ostree/repo/tmp/ directory not being cleaned up?
What are your thoughts on implementing an automated cleanup process for these directories?
Looking forward to your insights and suggestions for potential improvements.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The
ducommand reports significant data (e.g., 153MB) in the/ostree/repo/tmp/directory after an update fails, whereas on systems with successful updates, thistmpfolder remains empty. Additionally, the/ostree/repo/objectslocation also fills up, contributing to the issue.It appears that the
tmpdirectory is not being cleaned up properly. I've seen reports of users manually deleting these contents to free up disk space. However, the files in/ostree/repo/objectsalso occupy space, causing updates to fail on the Embedded Linux devices.Request for Feedback:
/ostree/repo/tmp/directory not being cleaned up?Looking forward to your insights and suggestions for potential improvements.
Beta Was this translation helpful? Give feedback.
All reactions