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
Right now the umount_all_rids.py command only umounts entries for drives which are visible to the OS. This means it leaves stubs in /depot for drives that have vanished for one reason or another.
Want to think about the proper way to do this, as I suspect just detecting/erasing the stub file might not be right. For instance, if you have a "blipped" RID that has written GB of data to SSD, you don't just want to erase that.
The text was updated successfully, but these errors were encountered:
Right now the umount_all_rids.py command only umounts entries for drives which are visible to the OS. This means it leaves stubs in /depot for drives that have vanished for one reason or another.
Want to think about the proper way to do this, as I suspect just detecting/erasing the stub file might not be right. For instance, if you have a "blipped" RID that has written GB of data to SSD, you don't just want to erase that.
The text was updated successfully, but these errors were encountered: