Jungle Disk 2.60c Released – Cloud Files access restored

We’ve been working continuously throughout the weekend with the Cloud Files team to help ease the capacity constraints we previously discussed and restore full access to  to Jungle Disk users of Cloud Files. Through our investigation we’ve determined that a significant cause of the problem was a bug in Jungle Disk 2.60a that prevented the directory cache system from working properly and resulted in an excessive load on the Cloud Files system even under normal operation. We have corrected the error and Jungle Disk 2.60c is now available for download.

All Jungle Disk users of Cloud Files now need to upgrade to 2.60c to restore access. Once you have upgraded, you should have complete access again to all your files. We also recommend that Amazon S3 users upgrade as well – the bug also affected Amazon S3 online disks and results in extra LIST queries and slower backups. In addition, the Cloud Files team found it necessary to release a number of infrastructure updates over the next few days to further optimize usage between Jungle Disk and Cloud Files.  We will keep any disruption from maintenance to a minimum.

The full list of changes in 2.60c is below. A number of other fixes are included and as a bonus we’re including a new feature that was originally planned for later – Growl support for OSX.

  • Added Growl support on Mac
  • Fixed directory cache bug that caused extra LIST requests
  • Fixed bandwidth limiting not working on Jungle Disk Plus uploads
  • Fixed loop in rm -rf on Linux
  • Fixed crash due to path lenth > 1024
  • Added fix for blank filenames to consistency check
  • Backup report now submitted correctly when time limit reached
  • Fixed import of legacy (pre-2.0) configuration files
  • Fixed crash when removing Amazon S3 account

We have posted additional details on the root cause of the problem and the steps we have took to correct the issue and prevent similar problems in the future.

13 Comments

  1. Chris said,

    March 23, 2009 @ 6:19 am

    Thanks for fixing the bandwidth limiting guys : )

  2. Chris said,

    March 23, 2009 @ 12:57 pm

    I thought I’d just poke at Rackspace again to see if it was up but even with 2.60c I cannot create a Rackspace container so somethings still not right over there…error I get is:

    “The online storage service seems to be unavailable at the moment. Please try again in a few minutes.”

  3. Jungle Dave said,

    March 23, 2009 @ 1:46 pm

    @Chris – we’ve kept creation of new Cloud Files online disks disabled for the time being, while we ensure everything returns to normal smoothly for existing customers. We’ll re-open Cloud Files for new JD users once the other optimizations currently in the works are complete.
    If you have existing Cloud Files online disks full access to them has been restored with 2.60c.

  4. Greg M. SMith said,

    March 23, 2009 @ 2:53 pm

    JungleDave: any eta on when new users will see CloudFiles access again? You said when “other optimizations currently in the works are complete”…are we talking hours, days, weeks?

    Thanks…

  5. Jungle Dave said,

    March 23, 2009 @ 3:22 pm

    @Greg – My best guess is later this week, but we want to make sure the changes are tested to avoid any unhappy surprises. We’ll be posting more details as they become available.

  6. Jason said,

    March 24, 2009 @ 9:51 am

    @Dave – will the 2.60c be the latest release w/ the CloudFiles fixes? I guess what I’m asking is…are the rest of the changes all on Rackspace’s end? I dont wanna roll out 2.60c and have to go back and reinstall everywhere again in a week or two.
    Thanks!

  7. Jungle Dave said,

    March 24, 2009 @ 12:18 pm

    @Jason – right now we’re not expecting further client-side changes in the short term (barring uncovering an unknown bug).

  8. Dan said,

    March 26, 2009 @ 4:04 pm

    I was wondering, is there a way to change the name of your CloudFile containers?

  9. Jungle Dave said,

    March 26, 2009 @ 4:23 pm

    @Dan – no, not currently.

  10. Chris said,

    March 29, 2009 @ 11:34 pm

    You should rename the title of this entry, it’s deceiving:

    “Jungle Disk 2.60c Released – Cloud Files access restored”

    to

    “Jungle Disk 2.60c Released – Cloud Files access restored for customers with existing containers.”

    It’s been over a week and your product still does not work as advertised for creation of new Rackspace Cloud Files containers.

  11. Joe Perrin said,

    April 3, 2009 @ 5:19 pm

    Please provide an update regarding when creation of new Rackspace Cloud Files containers will be enabled.

    I’ve been waiting for at least an update.

    Thanks,

    Joe.

  12. Kevin said,

    April 4, 2009 @ 9:12 am

    I signed up for purpose of Cloud Files and I can’t even use it?

  13. Jungle Dave said,

    April 4, 2009 @ 4:46 pm

    We’ve posted an update on the cloud files status in our most recent blog update. It’s taken longer than we would have liked but should be available this week.

RSS feed for comments on this post · TrackBack URI

Leave a Reply