advertisement

Article:
  Automated Backups with Existing Tools
Subject:   Errors
Date:   2004-02-10 22:21:19
From:   jb-
I'm getting an error that it can't attach in the hdiutil attach step. The disk is still churning away and creating the 82GB file for the backups. Outside of a for/next loop to make it wait any suggestions?
Full Threads Oldest First

Showing messages 1 through 4 of 4.

  • Errors
    2004-02-11 01:42:03  peterhickman [Reply | View]

    Not sure what the problem could be. For me a 12 Gb backup takes around 52 minutes, so it would take around six hours for you, all things being equal.

    If you could email me your values for SOURCE and FILEDEST along with the output of df I'll have a quick look at it.
    • Errors
      2004-02-11 07:26:50  jb- [Reply | View]

      It is creating the .dmg properly. HOwever I'm getting these errors

      hdiutil: attach failed - No such file or directory

      Validating target..."/Volumes/backup_2004-02-10" is not a volume



      couldn't validate target - No such file or directory.


      When I do an ls the file is there but is sill growing in size and I can see the disk writing (creating the empty disk image). If I wait until the image has been created and then comment out the hdiutil create line it seems to work fine (its running now). I could add a SLEEP NNN line but I'm looking for a cleaner way.

      • Errors
        2004-02-11 07:43:45  peterhickman [Reply | View]

        The error makes sense if the hdiutil -create is still running when it attempts to attach the .dmg. If it was still creating it then it is not formated correctly.

        I note that there appears to be a stray pipe '|' character at the end of line 21. Dont know how that got there. Is the pipe in the script you are using?
        • Errors
          2004-02-11 08:03:43  jb- [Reply | View]

          Apparently it is a result of the stray pipe. I took it out, changed the 5 to a 20 and the script seems to be running happily. It is taking upwards of five minutes to create the .dmg (70GB on a Firewire 400 drive) - should it be a different format?