I have a lib lock and it won’t release the storage until it can run vic.
/opt/Autodesk/io/bin/vic -af
3 Likes
Use VIC to find and remove unreferenced frames
It’s possible that there may be unreferenced media on your storage using up space. Unreferenced media can be video or audio frames which exist on your media storage that are not referenced by any clip or project, yet they still exist on the media storage and are therefore still taking up space.
The following steps cover the process of identifying and removing unreferenced media:
- Run the following command from a shell to identify your stone&wire partition:
/opt/Autodesk/sw/sw_df
You will get some output in your shell similar to the following:
Partition Free Total %use iFree iTotal %use
7 1834810 1926635 5 N/A N/A N/A
In this example we can see the active partition is Partition 7
2. We can now use VIC (Volume Integrity Check) to check partition 7 to see if there is any unreferenced media. Run the following command:
/opt/Autodesk/io/bin/vic -v stonefs7
You will see the VIC output in the shell, if you have any unreferenced media you will see something similar to the following near the bottom of the output:
Verifying audio stonefs frames ...
Verified 1 active audio frames
VIC: Found 25000 active video frames having wire ref count too high
VIC: Found 1 active audio frame having wire ref count too high
Recovering lost frames ...
Recovered 0 lost frames ...
Processing unreferenced (leaked) media on volume stonefs7...:
{
Resolution "VIDEO_1920x1080_143": 25000 frame files.
Resolution "AUDIO_1": 1 sound files.
}
Integrity check successful in 0.388295 sec
Unlocking volume stonefs7 …
Closing volume stonefs7…
Uninitialising thread manager.
- The text highlighted in red in the output above shows that there are 25,000 unreferenced video frames and 1 unreferenced audio frame. We can use VIC again with the -f option to remove this unreferenced media and free up the storage space it is using.
WARNING: using VIC with the -f option is destructive, if you are unsure about deleting unreferenced media skip to step 5
If you are sure you can safely delete the unreferenced media run the following command:
/opt/Autodesk/io/bin/vic -v stonefs7 -f
You will see the VIC output in the shell, near the bottom of the output you will see something similar to the following:
VIC: Found 25000 active video frames having wire ref count too high
VIC: Found 1 active audio frame having wire ref count too high
Recovering lost frames ...
Recovered 0 lost frames ...
Removing unreferenced (leaked) media on volume stonefs7...:
{
Resolution "VIDEO_1920x1080_143": 25000 frame files.
Resolution "AUDIO_1": 1 sound files.
}
Integrity check successful in 0.330049 sec
Unlocking volume stonefs7 …
Closing volume stonefs7…
Uninitialising thread manager.
- The text highlighted in red in the output above shows the unreferenced media being removed. Run VIC again to ensure there is no more unreferenced media in your partition:
/opt/Autodesk/io/bin/vic -v stonefs7
You will see the VIC output in the shell, near the bottom of the output you should now see something similar to the following:
Recovering lost frames ...
Recovered 0 lost frames ...
Processing unreferenced (leaked) media on volume stonefs7...:
{
}
Integrity check successful in 0.0289726 sec
Unlocking volume stonefs7 ...
Closing volume stonefs7...
Uninitialising thread manager.
You can see in the output above that there is no longer any unreferenced media in this partition.
- If your VIC output from step 2 shows that you have unreferenced media in your stone&wire partition, but you’re not sure if you can safely delete it, you can run VIC with the -p option to dump any unreferenced media into a new library in an already existing project, so that you can then go into that project and check if the media can be safely deleted.
Launch Flame and create a new project which can be used to dump the unreferenced media in to, in this example a project called ‘test’ was created. When the new project is created quit back out of Flame.
6. Run VIC with the following options to dump all of the unreferenced media into the ‘test’ project:
/opt/Autodesk/io/bin/vic -v stonefs7 -p test
You will see the VIC output in the shell, near the bottom of the output you should see something similar to the following:
Recovering lost frames …
Recovered 0 lost frames …
Processing unreferenced (leaked) media on volume stonefs7…:
{
Resolution “VIDEO_1920x1080_143”: 25002 frame files.
Creating new library “Recovered_Media_flame2018_2_users”
Adding 25002 frames to library …
Resolution “AUDIO_1”: 3 sound files.
Appending to library “Recovered_Media_flame2018_2_users”
Adding 3 audio segments to library …
}
Integrity check successful in 1.7352 sec
Unlocking volume stonefs7 …
Uninitialising thread manager.
The red text in the output above shows that the unreferenced video and audio has been moved to a library called ‘Recovered_Media_flame2018_2_users’ within the test project.
7. Launch Flame and go into the test project, then browse through the Recovered Media library to determine if any of the media needs to be saved, or can be safely deleted. Important: all of the video frames will appear in one large clip, so you will need to scroll through the whole clip to be sure there is nothing important which might be in the middle or at the end of the clip.
8. If you’re happy that the recovered media can be deleted, you can delete the entire ‘test’ project using the method outlined at the start of this article.
Source: How to free up space on Flame media storage | Flame Products | Autodesk Knowledge Network
7 Likes
Thank you!!
Thakt alot!!! This save my day!
Had to Recover my System. Thanks to Neat Video installtion.
But now its up and running again.
Best regards
Sebastian
I’ve run into a similar thing. Trying to run vic and I get the following: VOLUMEMGT : Using 1 as root partition.
DLmpd daemon on 169.254.157.153 is not responding.
Could not test existence of process 14184 on host 169.254.157.153.
DLmpd daemon on 169.254.72.247 is not responding.
Could not test existence of process 1524 on host 169.254.72.247.
DLmpd daemon on 169.254.197.10 is not responding.
Could not test existence of process 8493 on host 169.254.197.10.
DLmpd daemon on 169.254.56.37 is not responding.
Could not test existence of process 14526 on host 169.254.56.37.
DLmpd daemon on 169.254.141.42 is not responding.
Could not test existence of process 5615 on host 169.254.141.42.
Cannot obtain an exclusive lock on volume: close other apps or use lazy mode (-l).
The following process(es) must be stopped in order to run a full volume integrity check:
Cannot obtain an exclusive lock on volume: close other apps or use lazy mode (-l).
The following process(es) must be stopped in order to run a full volume integrity check:
6 active connections on volume stonefs1:
Application PID Host #Conn
--------------------------------------------------------------------------------
flame 14184 (unknown) (169.254.157.153) 1
vic 77496 mac-studio (192.168.1.205) 1
flame 1524 (unknown) (169.254.72.247) 1
flame 8493 (unknown) (169.254.197.10) 1
flame 14526 (unknown) (169.254.56.37) 1
flame 5615 (unknown) (169.254.141.42) 1
Checking active volume users ... \[ OK \]
Checking active volume users ... \[ OK \]
Failed to lock target stonefs1.
Closing target stonefs1…
Stopping managed threads.
I’ve run a killall flame and still get the same thing
Maybe you can find something in the Flame Infobytes. Try Vic - removing locks or Clearing Flame user locks.
https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/7b0tOqwRkWYbFIc7TjINAj.html
Thank you.
For anyone else running into this:
https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/511r0Va4GM0dRj1BFf8vCb.html
1 Like