More > JRiver Media Center 21 for Windows
Video files missing after large tag update
crisnee:
By the way, to the powers, I suggest that all files be deleted to the trash bin. That way the message "files too large for trash bin" gives one another chance to undo an erroneous delete or in this case avoid possible disaster.
Chris
mwillems:
--- Quote from: crisnee on November 17, 2015, 11:24:28 am ---Exactly. It just happened so quickly and unexpectedly and I wasn't doing much at all that there's not much help to give. I'd spent 5-10 minutes in this session and the last thing I did was okay one of those "this could take a long time" (tagging) messages. A Split second later the files were gone.
Chris
--- End quote ---
I would like to say that I had something very similar happen to me a twice in the last year. The most recent was a month or so ago. I was doing some tag editing of a few albums in a view on a Linux client with my windows server open in a VNC on the other monitor. Suddenly, I saw my server applying changes to all 60 thousand music files. The "change" in question was deleting the files! I managed to force quit MC and revert to an older library but by the time I'd stopped it about 3 thousand files had been deleted.
That was the second accidental library event I'd had in about six months. The first one happened in very similar circumstances (tag editing on linux client), but it didn't delete files; it "applied changes" to every audio file in my library and I had no idea what had even been changes (it would be nice to have some way to find out what tag changes are being made rather than just the number of files left to do, but that's a separate issue).
I wrote off the first one, because I was typing fast, I thought I might've miskeyed, or double-pressed or something (i.e. user error). But the second time I was sitting there quietly tagging a couple albums and there was no "accidental contact"; just sudden database mayhem. In both cases I restored from backup, so no data lost, but it was definitely scary.
I didn't pursue it because I had no way to reproduce anything, and I know that Linux MC still has some kinks (and I didn't want to spread FUD), but if other folks are seeing this, maybe it's worth discussion. I definitely stepped up the frequency of my backups.
RoderickGI:
Okay, we all stand corrected.
Deleting many gigabytes of data in a split second is most unusual, particularly if the data is on a rotating disk, and if it is many small files, as audio files would be.
It would be nice if there was some way to avoid that happening to other users, like me! I don't have backups of all my non-critical media files. :o
glynor:
I have an idea of what could have happened.
I was writing up my response to this thread and something occurred to me:
I know (from previous tests) if you select a whole swath of files, edit the [Filename] tag and make them all c:\foo.txt (or something similarly dumb), it will not hose you. It will move the first file to c:\foo.txt and then the system "overwrite files" dialog will come up and warn you of your mistake before too much damage is done. To obliterate everything, you'd have to click OK umpteen-thousand times over and over like a monkey.
But what about if you just clear the [Filename] tag? Edit it, delete what is there, but put nothing at all in the box. I've never tried that. So, I just tested it.
Yup, it obliterates the files. It also gives you a tagging error, and the file entry becomes broken in MC (1/2 way changed). But, before it does that, it deletes the files and they do not go to Recycle.
That should be fixed. If you are direct editing the [Filename] it should test the user entry and make sure a valid filename is entered before doing anything (or at least not just whitespace)!
I'm not sure that's what happened here. Because it isn't super instant (I watched it delete a few files, but doing the whole Library would have still taken a while), and it should have at least shown an error about tagging when done, so I'm not sure that was the case here. But, still not great, and could have been what bit mwillems.
Also worth mentioning, I had a similar experience to mwillems too, a good while back. I did post about it, but didn't have many details. I'll look for the post later.
mwillems:
--- Quote from: glynor on November 17, 2015, 06:06:22 pm ---I have an idea of what could have happened.
I was writing up my response to this thread and something occurred to me:
I know (from previous tests) if you select a whole swath of files, edit the [Filename] tag and make them all c:\foo.txt (or something similarly dumb), it will not hose you. It will move the first file to c:\foo.txt and then the system "overwrite files" dialog will come up and warn you of your mistake before too much damage is done. To obliterate everything, you'd have to click OK umpteen-thousand times over and over like a monkey.
But what about if you just clear the [Filename] tag? Edit it, delete what is there, but put nothing at all in the box. I've never tried that. So, I just tested it.
Yup, it obliterates the files. It also gives you a tagging error, and the file entry becomes broken in MC (1/2 way changed). But, before it does that, it deletes the files and they do not go to Recycle.
That should be fixed. If you are direct editing the [Filename] it should test the user entry and make sure a valid filename is entered before doing anything (or at least not just whitespace)!
I'm not sure that's what happened here. Because it isn't super instant (I watched it delete a few files, but doing the whole Library would have still taken a while), and it should have at least shown an error about tagging when done, so I'm not sure that was the case here. But, still not great, and could have been what bit mwillems.
Also worth mentioning, I had a similar experience to mwillems too, a good while back. I did post about it, but didn't have many details. I'll look for the post later.
--- End quote ---
That's a plausible model for what happened to me. It was certainly not instantaneous, but it was moving at a clip of a few dozen files a second, and I was confused for a minute about what was happening so it took me a minute or two to force quit (and to remember how to get into task manager via VNC). That's how it got to 3k in my case. It would have taken a while to iterate over everything, but if I hadn't been watching my server instance I'd have never realized it was happening until much later in the process.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version