Server will be going down for Maitenance likely next week
Server is back with its new array.
Unfortunately it took longer than expected due to several complications:
1) The controller I used to create the new array was in a format the older model controller in my server couldn't use.
Because of this I ended up having to gank a spare controller and now have two raid controllers in the system (the original one drives the SSDs and the new one drives the new 3 TB disks).
2) The new controller I added wasn't supported by the kernel on the server so I had to build a new kernel.
Anyway the server is all back up and should stay up for good.
Server is going down to night in approximately 2 hours (8 PM PST)
It looks like the drives are not going to be coming until Friday so this is going to get delayed another week as time is needed to copy the data to the drives. The updated schedule is now Jun 27th or 28th.
Just a heads up that likely sometime next week (might be 2 weeks) so probably on June 20th or 21st.
It will be going down for possibly up to several hours. I am replacing the current raid array (8x1.5TB in raid6) which stores all data on the server to new disks (8x3TB in raid6).
The extra space is not really needed but the main reason for this is the current array has already had 2/8 drives fail (both within the last 6 months). These two disks have since been replaced but already have re-allocated sectors and the 6 other disks have been powered on 24/7 for over 4 years.
Basically I feel these disks have served out their lifetime and its time for new ones. The new disks are Hitachi which have proven to be far more reliable than what is in the server now (Seagate).
I will update this post next week with an exact date/time the server will be going down.
Click Here To Comment
ODI Pack 3
It's out! It was 5 years since ODIPack2 was released. Now, with a new era of simfile makers combined with many of the old ones, we have made a third pack! Only files of the highest quality have been accepted in this pack, and even so it includes a whopping 108 simfiles. This will be the last and grand finale in the ODIPack series, there has been a tremendous amount of work put into this project, enjoy =)!
Server was down for 6 hours
Pack aware server
I found another bug. The client will use the translated title/artist/subtitle when one is available. I had to re-index the packs/songs and modify the server code to check for that. Once I did that pack detection accuracy went up again and for me I went from 140 packs detected to 155. Please run /scan again if you haven't since this update.
There was a bug in the scanning which didn't handle packs where the unique identifier had special/foreign characters in it (utf8 string). This caused some packs to not be detected. I fixed this problem and now for me it is detecting 140 packs vs 130. I suggest everyone re-run a /scan.
Pack scanning has been enabled on the regular server.
Run /scan to scan packs. Keep in mind if your far away from the server it can take a minute or two. It must be ran from within a room.
Run /commonpacks to see what packs you have in common with others in the room. Keep in mind as of now only about half of the packs have abbreviations set so you will get comma's with no value as that means the pack has not been assigned a value yet. Also it won't display unless everyone has ran /scan (it will say which user needs to run it when you run /commonpacks).
I know this feature has been requested a lot. Originally I didn't think implementing something like this would be possible but this is kind of a hack around not modifying existing game protocol.
So after I spent some time indexing the packs I found that 1150 of the ~1300 packs listed on the site have at least one unique song in them and thus packs can be identified from the song assuming the client has not deleted songs out of their pack folders.
I added a /scan command (currently only on the beta server) that has the server go through the list to figure out what packs you have.
Currently the server just prints what packs it thinks you have.
As soon as I implement it (probably in the next few days or this weekend) the server should be able to store whac packs you have in the db (so just need to /scan when you add packs) and then a /commonpacks command you can run that will be able to check all the users in the room and print out what packs people have in common.
I would appreciate if some people would go on the beta server and test this feature out and see if it looks like the server is getting all (or most) of your packs and report back on how it worked (as well as how slow it was) by commenting on the forum.
It only took around 20 seconds to scan though 1150 packs on my home machine but being <5ms away from the server means it would go much quicker than foreign folks. When the final product is done it likely will only check the top 20-30% of the packs and not all in order to increase scan time.
The beta server as always is port 9999 so connect to:
Then make a room and then type /scan
Click Here To Comment