Clean library dry run

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
Intropy Offline
Junior Member
Posts: 6
Joined: Jan 2013
Reputation: 0
Post: #1
Is there any way to do a dry run a clean library and get a report on what would have been removed without actually removing anything? Something seems to have gone awry with my NAS, and I notice some missing files. I would like to try and get a run down on what is missing.
find quote
Ned Scott Offline
Team-Kodi Wiki Guy
Posts: 20,391
Joined: Jan 2011
Reputation: 258
Location: Arizona, USA
Post: #2
You could use profiles to make a duplicate library of the main (original) profile/user. Then you can compare the two libraries. Just make sure to select the option to copy the database from master profile, rather than share database with master profile.

You can make easy links to the XBMC wiki using double brackets around common XBMC words: [[debug log]] = debug log, [[Video library]] = Video library, [[SMB]] = SMB , [[userdata]] = userdata, etc
find quote
pr0xZen Offline
Fan
Posts: 432
Joined: Feb 2014
Reputation: 17
Post: #3
What about export library -> clean library and see changes -> import library? Or did I miss simething?

If I have helped you or increased your knowledge - please click the plus to the left below to give thanks
find quote
Intropy Offline
Junior Member
Posts: 6
Joined: Jan 2013
Reputation: 0
Post: #4
Is there a "clean library and see changes" command, or do you just mean "clean library" then see what changes? How would I do that? Is it logged somewhere?
find quote
pr0xZen Offline
Fan
Posts: 432
Joined: Feb 2014
Reputation: 17
Post: #5
You should see any changes in the xbmc log, but what I suggested was to first export your library "to single file". Then, run a normal "clean library" session. Make note of the changes that is discovered. After that, you import the library you exported before "clean library".

If I have helped you or increased your knowledge - please click the plus to the left below to give thanks
find quote
Intropy Offline
Junior Member
Posts: 6
Joined: Jan 2013
Reputation: 0
Post: #6
The log helps. I didn't realize it would do that. With logging either of the techniques you two have mentioned sounds pretty similar and reasonable (without logging they didn't really sound any better than comparing the library against the filesystem).
find quote
pr0xZen Offline
Fan
Posts: 432
Joined: Feb 2014
Reputation: 17
Post: #7
Both options pretty much do the same, with the former you just take the extra profile out of the equation, along with any (low-level) risk of making library cleaning changes permanent without "backup" - in case you got accidentally got the "use same library" / "clone library" wrong.

Manually comparing libary to filesystem would be a tedious task. If you do the "clean library", XBMC will throw a pop-up for each missing library entry. This method can be useful if you just have a few "missing" videos. If the ammount is beyond "a few", then I agree - referring to the log afterwards for a "listing" would probably be a much better option.

If I have helped you or increased your knowledge - please click the plus to the left below to give thanks
find quote