-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Data loss when interrupting import #4283
Comments
That sounds bad! Is the original problem (the interrupted import that deletes files) something you can reproduce reliably? Can you get a verbose log from that? |
It is not easy to reproduce, no. It happened again later, but with another file. `$ beet -vv import /media/hendrik2/Scharnier/Muziek\ te\ sorteren/ 2> beet.log /media/hendrik2/Scharnier/Muziek te sorteren/An Pierlé/Helium Sunset (+ enkele andere) (3 items)
selection (default 1), Skip, Use as-is, as Tracks, Group albums,Enter search, enter Id, aBort? 4
The file is indeed nowhere to be found. Another try, without plugins: /media/hendrik2/Scharnier/Muziek te sorteren/An Pierlé/Helium Sunset (+ enkele andere) (3 items)
selection (default 1), Skip, Use as-is, as Tracks, Group albums,Enter search, enter Id, aBort? 4
/media/hendrik2/Scharnier/Muziek te sorteren/An Pierlé/Helium Sunset (+ enkele andere) /media/hendrik2/Scharnier/Muziek te sorteren/Andrew Bird/Oh! The Grandeur (1 items)
selection (default 1), Skip, Use as-is, as Tracks, Group albums,Enter search, enter Id, aBort? 5
(Something going wrong with formatting here, tried fixing it, but to no avail.) |
another case, see log |
I'm really sorry, but there's not much we can do without a way to reproduce the problem. |
I have figured out a pattern. Unsure whether this is the same problem, but it looks similar.
Notice the file size of the ‘old’ files, which are indeed no longer there. If I then choose M, it crashes after a while. Attached is the log. The obvious workaround is to delete the database file and re-import everything. |
While I can't tell what a brief glance what the actual issue could be; the obvious workaround here should rather be to first use |
As you know you moved the files, it is safe to use the Beets will then
If you need a different music ID (muscbrainz, discogs, etc) you will have to either clear the exiting tags or pass an ID on the command line |
remove old works, thanks. I could not find that documented? |
We might still consider making this a safer experience:
Note that in any case, this is about using beets out of spec: Beets for the most part assumes that it's in exclusive control of the library (including associated files). So we might decide that none of the above is really worth the effort (I won't be the one to implement this anyway...). |
Well, might I suggest at least a more meaningful error message? Something like: ‘The file X in you library was not found, it is probably moved or deleted on the file system. Use “beet remove old” to update your library.’ |
Closing in favor of #4342, which is probably the same. |
I am importing my music collection for the first time. At a certain moment I had to interrupt the proces. That took a while, so I hit Ctrl-c. Now, if I restart, it resumes, but after a while a song is not found in the new location where beets expects it, and it is also no longer in the old location. Data loss!
Problem
Running this command in verbose (
-vv
) mode:It is still running in verbose mode…
Led to this problem:
Here's a link to the music files that trigger the bug (if relevant):
it is on a local external usb drive
Setup
$ python2 --version
Python 2.7.18
$ beet --version
beets version 1.6.0
Python version 3.8.10
plugins: chroma, fetchart, fromfilename, lastgenre
(different python versions, that’s interesting)
My configuration (output of
beet config
) is:I tried removing .beets/musiclibrary.db, but the error seems to persist.
The text was updated successfully, but these errors were encountered: