The SCE1010 alert "Not enough disk space"

My SCE1010 show the alert "Not enough disk space" in log.
I find old discuss , someone say can delete the file: /tffs0/SYSTEM/PREVDBG.TXT , because the file is too big.
But I don't confirm  delete the file will not effect system work fine.
Could everyone help me to solve the problem ?
Thank you very much.
Log shows:
SCE#>show log | i disk
2012-12-25 00:50:44 | WARN  | CPU #000 | Not enough disk space.
2012-12-25 00:50:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-26 09:07:57 | WARN  | CPU #000 | Not enough disk space.
2012-12-26 09:07:57 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-27 17:40:09 | WARN  | CPU #000 | Not enough disk space.
2012-12-27 17:40:09 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-29 01:57:20 | WARN  | CPU #000 | Not enough disk space.
2012-12-29 01:57:20 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-30 11:54:34 | WARN  | CPU #000 | Not enough disk space.
2012-12-30 11:54:34 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-31 20:51:49 | WARN  | CPU #000 | Not enough disk space.
2012-12-31 20:51:49 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-02 05:19:01 | WARN  | CPU #000 | Not enough disk space.
2013-01-02 05:19:01 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-03 13:31:12 | WARN  | CPU #000 | Not enough disk space.
2013-01-03 13:31:12 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-05 03:28:45 | WARN  | CPU #000 | Not enough disk space.
2013-01-05 03:28:45 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-06 13:21:00 | WARN  | CPU #000 | Not enough disk space.
2013-01-06 13:21:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-07 21:18:05 | WARN  | CPU #000 | Not enough disk space.
2013-01-07 21:18:05 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-09 05:00:04 | WARN  | CPU #000 | Not enough disk space.
2013-01-09 05:00:04 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-10 14:52:16 | WARN  | CPU #000 | Not enough disk space.
2013-01-10 14:52:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-12 03:29:34 | WARN  | CPU #000 | Not enough disk space.
2013-01-12 03:29:34 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-13 13:01:44 | WARN  | CPU #000 | Not enough disk space.
2013-01-13 13:01:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-14 21:28:53 | WARN  | CPU #000 | Not enough disk space.
2013-01-14 21:28:53 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-16 05:30:58 | WARN  | CPU #000 | Not enough disk space.
2013-01-16 05:30:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-17 19:43:29 | WARN  | CPU #000 | Not enough disk space.
2013-01-17 19:43:29 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-19 02:45:28 | WARN  | CPU #000 | Not enough disk space.
2013-01-19 02:45:28 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-20 13:22:47 | WARN  | CPU #000 | Not enough disk space.
2013-01-20 13:22:47 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-21 21:14:55 | WARN  | CPU #000 | Not enough disk space.
2013-01-21 21:14:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-23 05:22:05 | WARN  | CPU #000 | Not enough disk space.
2013-01-23 05:22:05 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-24 19:14:35 | WARN  | CPU #000 | Not enough disk space.
2013-01-24 19:14:35 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-26 04:01:48 | WARN  | CPU #000 | Not enough disk space.
2013-01-26 04:01:48 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-27 12:53:58 | WARN  | CPU #000 | Not enough disk space.
2013-01-27 12:53:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-28 20:36:09 | WARN  | CPU #000 | Not enough disk space.
2013-01-28 20:36:09 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-30 06:03:35 | WARN  | CPU #000 | Not enough disk space.
2013-01-30 06:03:35 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-31 18:56:02 | WARN  | CPU #000 | Not enough disk space.
2013-01-31 18:56:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-02 02:48:06 | WARN  | CPU #000 | Not enough disk space.
2013-02-02 02:48:06 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 10:55:07 | WARN  | CPU #000 | Not enough disk space.
2013-02-03 10:55:07 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 11:50:10 | WARN  | CPU #000 | Not enough disk space.
2013-02-03 11:50:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-04 21:37:16 | WARN  | CPU #000 | Not enough disk space.
2013-02-04 21:37:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-06 10:44:39 | WARN  | CPU #000 | Not enough disk space.
2013-02-06 10:44:39 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-07 18:46:44 | WARN  | CPU #000 | Not enough disk space.
2013-02-07 18:46:44 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-09 03:23:55 | WARN  | CPU #000 | Not enough disk space.
2013-02-09 03:23:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-10 11:36:02 | WARN  | CPU #000 | Not enough disk space.
2013-02-10 11:36:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-11 19:53:10 | WARN  | CPU #000 | Not enough disk space.
2013-02-11 19:53:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-13 09:55:40 | WARN  | CPU #000 | Not enough disk space.
2013-02-13 09:55:40 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-14 19:57:55 | WARN  | CPU #000 | Not enough disk space.
2013-02-14 19:57:55 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-16 04:20:07 | WARN  | CPU #000 | Not enough disk space.
2013-02-16 04:20:07 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-17 12:12:19 | WARN  | CPU #000 | Not enough disk space.
2013-02-17 12:12:19 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-19 02:09:51 | WARN  | CPU #000 | Not enough disk space.
2013-02-19 02:09:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-20 09:41:58 | WARN  | CPU #000 | Not enough disk space.
2013-02-20 09:41:58 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-21 17:39:08 | WARN  | CPU #000 | Not enough disk space.
2013-02-21 17:39:08 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-23 03:21:28 | WARN  | CPU #000 | Not enough disk space.
2013-02-23 03:21:28 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-24 11:18:43 | WARN  | CPU #000 | Not enough disk space.
2013-02-24 11:18:43 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-26 00:36:10 | WARN  | CPU #000 | Not enough disk space.
2013-02-26 00:36:10 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-27 08:13:12 | WARN  | CPU #000 | Not enough disk space.
2013-02-27 08:13:12 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-27 14:51:13 | WARN  | CPU #000 | Not enough disk space.
2013-03-27 14:51:13 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-28 22:43:19 | WARN  | CPU #000 | Not enough disk space.
2013-03-28 22:43:19 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-29 22:44:54 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-03-30 07:00:26 | WARN  | CPU #000 | Not enough disk space.
2013-03-30 07:00:26 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 07:02:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 35MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 21:27:56 | WARN  | CPU #000 | Not enough disk space.
2013-03-31 21:27:56 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-02 05:10:02 | WARN  | CPU #000 | Not enough disk space.
2013-04-02 05:10:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-03 13:57:11 | WARN  | CPU #000 | Not enough disk space.
2013-04-03 13:57:11 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-04 21:24:16 | WARN  | CPU #000 | Not enough disk space.
2013-04-04 21:24:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-05 21:25:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-06 11:11:45 | WARN  | CPU #000 | Not enough disk space.
2013-04-06 11:11:45 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-07 18:33:53 | WARN  | CPU #000 | Not enough disk space.
2013-04-07 18:33:53 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-09 02:46:02 | WARN  | CPU #000 | Not enough disk space.
2013-04-09 02:46:02 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 02:47:40 | WARN  | CPU #000 | Available disk space at '/tffs0' is 29MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 08:08:00 | WARN  | CPU #000 | Not enough disk space.
2013-04-10 08:08:00 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 08:09:38 | WARN  | CPU #000 | Available disk space at '/tffs0' is 32MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 17:35:16 | WARN  | CPU #000 | Not enough disk space.
2013-04-11 17:35:16 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-12 17:36:51 | WARN  | CPU #000 | Available disk space at '/tffs0' is 34MB which is under 45MB. Some management operations may fail to execute.
2013-04-13 07:12:46 | WARN  | CPU #000 | Not enough disk space.
2013-04-13 07:12:46 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 07:14:24 | WARN  | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 12:54:48 | WARN  | CPU #000 | Not enough disk space.
2013-04-14 12:54:48 | WARN  | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-15 12:56:25 | WARN  | CPU #000 | Available disk space at '/tffs0' is 30MB which is under 45MB. Some management operations may fail to execute.
SCE#>

Dear Minja.
I have the same problem
Can you see my dir -r ?
SCE#dir -r
File list for /tffs0/
     512    WED AUG 13 19:01:34 2008       DIAG                   DIR
     512    WED AUG 13 19:04:00 2008       SYSTEM                 DIR
     512    WED AUG 13 19:13:50 2008       APP                    DIR
     512    WED AUG 13 19:13:50 2008       IMAGES                 DIR
     512    TUE NOV 18 08:48:18 2008       ENGAGE                 DIR
18189911    TUE APR 16 23:08:26 2013       RELEASE_.SLI          
    2356    TUE JUN 02 17:14:46 2009       SCRIPT.TXT            
                7 File(s)               18194827 bytes
File list for /tffs0/DIAG
     512    WED AUG 13 19:01:34 2008       .                      DIR
     512    WED AUG 13 19:01:34 2008       ..                     DIR
                2 File(s)               1024 bytes
File list for /tffs0/SYSTEM
     512    WED AUG 13 19:04:00 2008       .                      DIR
     512    WED AUG 13 19:04:00 2008       ..                     DIR
   25643    FRI MAY 03 12:02:50 2013       BOOTLOG.TX2           
     512    WED AUG 13 19:12:46 2008       BACKUP                 DIR
   25441    MON FEB 11 21:30:54 2013       BOOTLOG.TX3           
   39115    TUE MAY 14 01:29:42 2013       CONFIG.TXT            
   25658    FRI MAY 03 12:34:36 2013       BOOTLOG.TX1           
       0    MON FEB 11 13:48:44 2013       BSPFAIL.TXT           
   25647    SAT MAY 11 06:01:36 2013       BOOTLOG.TXT           
       0    WED OCT 07 10:18:02 2009       USRCONST.TXT          
     512    THU OCT 09 05:31:36 2008       PREVCONF               DIR
     512    WED OCT 07 10:23:12 2009       PQIINST                DIR
                12 File(s)              144064 bytes
File list for /tffs0/SYSTEM/BACKUP
     512    WED AUG 13 19:12:46 2008       .                      DIR
     512    WED AUG 13 19:12:46 2008       ..                     DIR
9151426    MON FEB 11 21:29:48 2013       DBG_LOG.DF1           
   16310    MON FEB 11 13:48:56 2013       FAIL.DFL              
                4 File(s)               9168760 bytes
File list for /tffs0/SYSTEM/PREVCONF
     512    THU OCT 09 05:31:36 2008       .                      DIR
     512    THU OCT 09 05:31:36 2008       ..                     DIR
   39115    MON MAY 13 16:06:16 2013       CONFIG.TX8            
   39115    MON MAY 13 16:26:16 2013       CONFIG.TX7            
   39115    MON MAY 13 17:24:02 2013       CONFIG.TX6            
   39115    MON MAY 13 17:28:44 2013       CONFIG.TX5            
   39115    MON MAY 13 17:51:52 2013       CONFIG.TX4            
   39115    TUE MAY 14 00:56:44 2013       CONFIG.TX3            
   39115    TUE MAY 14 01:13:00 2013       CONFIG.TX2            
   39115    TUE MAY 14 01:29:46 2013       CONFIG.TX1            
   39115    MON MAY 13 15:38:40 2013       CONFIG.TX9            
                11 File(s)              353059 bytes
File list for /tffs0/SYSTEM/PQIINST
     512    WED OCT 07 10:23:12 2009       .                      DIR
     512    WED OCT 07 10:23:12 2009       ..                     DIR
                2 File(s)               1024 bytes
File list for /tffs0/APP
     512    WED AUG 13 19:13:50 2008       .                      DIR
     512    WED AUG 13 19:13:50 2008       ..                     DIR
17184659    MON FEB 11 21:48:58 2013       EN37592.SLI           
                3 File(s)               17185683 bytes
File list for /tffs0/IMAGES
     512    WED AUG 13 19:13:50 2008       .                      DIR
     512    WED AUG 13 19:13:50 2008       ..                     DIR
113609411    MON FEB 11 21:09:14 2013       SEOS.PKG              
                3 File(s)               113610435 bytes
File list for /tffs0/ENGAGE
     512    TUE NOV 18 08:48:18 2008       .                      DIR
     512    TUE NOV 18 08:48:18 2008       ..                     DIR
  647546    TUE MAY 14 00:55:44 2013       MYENGAG2.PQB          
  580274    TUE MAY 14 01:28:48 2013       BATCH.SER             
    3673    TUE MAY 14 01:29:38 2013       TEMP.DSS              
  647559    TUE MAY 14 01:11:58 2013       MYENGAG1.PQB          
  647347    TUE MAY 14 01:28:44 2013       MYENGAGE.PQB          
  647557    MON MAY 13 17:50:54 2013       MYENGAG3.PQB          
                8 File(s)               3174980 bytes
                        373579776  total bytes used
                        20791296   total bytes free

Similar Messages

  • What does error message when trying to burn DVD from iDVD mean "not enough disk space to burn the remaining assets"

    I created a DVD in idvd and now when trying to burn to DVD using external burner, I get the error message
    "not enough disk space to encode the remaining assets". I am using a brand new blank DVD.
    I have read the help info on computer but hasnt proved helpful.
    Any suggestions?

    iDVD requires a fair amount of disk space to carry out the encoding process; depending on your project, you may need to have over 25 GB free space on your startup hard drive.  How much free space do you have?

  • Receiving a "There is not enough disk space available to install the product" error in App store while I clearly have enough space?

    I am attempting to purchase Dues Ex: Human Revolution which requires 17GB to run, I currently have 27.34GB free.
    Even though I have 10GB more than the required space I still get the "There is not enough disk space available to install the product"
    Any ideas?

    HI...
    You need at the very least 15% free disk space. More if possible. Definitely not enough free space to install a 17GB app.
    OSX Tips Where did my Disk Space go?
    Freeing Up Hard Disk Space - Mac GuidesFreeing Up Hard Disk Space - Mac Guides
    And make sure your Mac meets the app's minimum requirements which according to the App Store is Mac OS X 10.7.3 or later under Information right side of the App Store window.
    edited by:  cs

  • Not Enough Disk Space while installing WebLogic 6.1sp1 on AIX

    While installing WebLogic Server I get the error message "Not Enough Disk Space"
    for the root (/) file system, although I am trying to install it in the /weblogic
    file system that has enough space for the installation.
    What is that extra info that I need to pass to the installer so that installs
    the server in /weblogic and not complain about lack of disk space in /.
    The relevant properties for installation under silent mode are as listed below:
    ### BEA Home Directory
    BEAHOME=/weblogic/sftw
    ### Product Installation Directory
    USER_INSTALL_DIR=/weblogic/sftw/6.1
    Thanks and Regards
    Kapil Singh Pawar

    Hi.
    I believe the installation creates temporary files in the /tmp directory from root.
    If that is part of your root file system then this may be the cause of your problem.
    Try changing your environment variable TMPDIR or TMP_DIR. If you are doing the
    silent install with the java command line try setting java.io.tmpdir to a different
    filesystem on the command line.
    Hope this helps,
    Michael
    Kapil Singh Pawar wrote:
    While installing WebLogic Server I get the error message "Not Enough Disk Space"
    for the root (/) file system, although I am trying to install it in the /weblogic
    file system that has enough space for the installation.
    What is that extra info that I need to pass to the installer so that installs
    the server in /weblogic and not complain about lack of disk space in /.
    The relevant properties for installation under silent mode are as listed below:
    ### BEA Home Directory
    BEAHOME=/weblogic/sftw
    ### Product Installation Directory
    USER_INSTALL_DIR=/weblogic/sftw/6.1
    Thanks and Regards
    Kapil Singh Pawar--
    Developer Relations Engineer
    BEA Support

  • Not enough disk space for asset ecoding

    Hi all,
    I have a dvdsp project with:
    a feature: 3.3 gb
    dvd extra: 289
    menu assets: 65mb
    and shows that it is 3.8 mb all together, but when i try to build/format it stops the build at the menu and gives the error message: Not enough disk space for asset encoding. I was running a test build when this happened. i have yet to add the audio for the extra thinking i still had some room on here to work with.
    I have burned dvd's up 4.5 without any issues. any ideas why this is happening?
    thanks,
    Mark

    I'm having the same problem. Except I have tried to switch locations for the Current Build and each time it says Not enough disk space for asset encoding. I have a 500GB raid with almost 400GB free and then another 500GB raid with about 130GB free. I really need help on this pronto!
    Another message it now brings up after it starts Encoding Assets: Insufficient disk space for encoding. Please free up disk space on your encoding target drive. Please Help!!
    Message was edited by: PapaSnowSmurf

  • FCP X version 10.1.1.  When Sharing to DVD I get the following alert " There was an error burning your discd.  Not enough Disk Space in Target Folder"  I have 700GB   free.  Where is this target folder located?  how can I fix this problem? not space prob

    Sharing to DVD I get the following alert " There was an error burning your disc.  Not enough Disk Space in Target Folder"  I have 700GB   free.  Where is this target folder located?  How can I fix this problem? This is definitely not a space problem. 
    Since starting with FCP X, there has been tons of issues, now that the product actually works with the exception above, makes it impossible to share the production.  Has Apple fixed this problem.  is there a knowledge base article on this?
    On another note, One reason I have not purchased support on FCP X is because you sold a product that never worked for almost an entire year or more.   Now I can finally finish my project,  I cannot share it.....Really.  This has to be fixed now, I am loosing money as I typed this.
    Regards,
    Rob Harris

    Just curious, why would repairing permissions, rebooting ( rebooted 2 times already today) or creating a new user possibly fix this.
    I cannot create a new user, that is way too much work.  I will repair permissions again,  I repaired permissions just a few days ago. Then I will reboot, login and turn off App Nap and rerun the Share DVD.
    There must be something seriously wrong with the OS if your are suggesting creating another user.   WOW!
    Rob H.

  • Error msg: Sending of password for user did not succeed. Mail server responded: Not enough disk space - what's the deal?

    I've been checking my email via webmail for a week and am back in the office today. Fired up Thunderbird, expecting it to pick up all my email, but it gets nothing and tells me…
    Sending of password for user [email protected] did not succeed. Mail server pop.ipower.com responded: Not enough disk space
    Haven't seen this particular error message come up in searches via google and at mozilla. There's definitely disk space on my machine. I'm running TB on a Mac (OSX 10.6.8). Disk Space options under Preferences > Advanced let me assign up to 1024 mb for the cache, which I've done, and cleared.
    Has anyone encountered this before? Got a solve/troubleshooting process? Thanks!

    Thanks. I do compact regularly (TB prompts me to) and did it (several times) via Preferences today to try and get TB past this error message.
    Also went thru and Trashed + Empty Trashed as many messages as possible from the inbox, just in case. Still no-go.

  • I am getting the following message "safari could not download the file (440MB) because there is not enough disk space.  disk utility says i have 249.8 GB of available disk space.  any suggestions as to what is the problem would be appreciated

    i am getting the following message "safari could not download the file (440 MB) because there is not enough disk space.  please delete files or download to another disk."  when i check system information it tells me i have 249.82 GB of disk space available.  any suggestions as to what i can do to resolve this problem.

    don
    thanks for your suggestion.  that is the same advice that i got from the geek squad at the local apple store.
    i did what he instructed but it did not work.  i have since called apple support twice regarding the problem.  they had me start the computer in safe mode, going into the library and deleting a phlist file (i think) do a repair disk permissions, do a repair disk, empty the cache, and finally the last guy told me to unplug the computer from the wall socket and restart.
    when i mentioned the advice you and the apple store guy gave me they sort of poo pooed it saying that was done when they did all this other stuff.
    i am now waiting for the download to be completed to see if unplugging the computer had any effect.
    thanks again for your kindness in answering my concern.

  • LR 5.5 upgrade. I only get the the 32 bit set up and an error when the 64 bit set up should be created. It says not enough disk space and no access to write. The disk space is ok and the 32 bit file was indeed created.

    LR 5.5 upgrade. I only get the the 32 bit set up and an error when the 64 bit set up should be created. It says not enough disk space and no access to write. The disk space is okay and the 32 bit file was indeed created. I have Windows 7 Home edition.

    Hi Rob, Thanks for your input. The temp location is on the C drive with 228 GB free space. My other drives have 123 GB and 204 GB of free space. I can see how the 32 bit set up is perfectly extracted when it stops when coming to the 64 bit set up. I have done the exercise several times and also made new downloads. I am using Norton 360 and Malwarebytes anti-malware but the dowload from Adobe should be trusted.

  • Not enough disk space available on the proxy

    Wondering if someone might be able to shed some light here.
    Trying to deploy a 16GB flar image, but it fails claiming there is not enough disk space on the proxy, however the proxy appears to have plenty of space in /var:
    The error:
    Task   : Download Image
                    Task Run ID : 23076
                    Target : PC->ocproxy-6c657073
                    Status : FAILED
                    Result : Failed to download image + combo-S10-v149.flar
                    Logs   :
                        05/01/2015 01:47:15 PM PDT INFO Task is posted to the Proxy Controller (ocproxy-6c657073), from the Enterprise Controller. (15011)
                        05/01/2015 01:47:18 PM PDT INFO Task is received by the Proxy Controller. (15012)
                        05/01/2015 01:47:18 PM PDT INFO ---enter into image task run----
                        05/01/2015 01:47:18 PM PDT INFO download image combo-S10-v149.flar:osFlarImage:,jsPostInstall.sh:osScript:,osp_status_firstboot.sh:osScript:,
                        05/01/2015 01:47:53 PM PDT ERROR Not enough disk space available on the proxy to download the file - /var/opt/sun/xvm/proxyImageCache/os/flars/combo-S10-v149.flar.
                        05/01/2015 01:47:53 PM PDT ERROR Image file does not exist - combo-S10-v149.flar.
                        05/01/2015 01:47:53 PM PDT ERROR Failed to download the url - /ImageDownload/FileDownload?fileName=/os/flars/combo-S10-v149.flar.
                        05/01/2015 01:47:53 PM PDT ERROR Failed to download image + combo-S10-v149.flar
    root@ocproxy:/# df -h
    Filesystem             Size   Used  Available Capacity  Mounted on
    rpool/ROOT/solaris-1    98G   3.3G        68G     5%    /
    /devices                 0K     0K         0K     0%    /devices
    /dev                     0K     0K         0K     0%    /dev
    ctfs                     0K     0K         0K     0%    /system/contract
    proc                     0K     0K         0K     0%    /proc
    mnttab                   0K     0K         0K     0%    /etc/mnttab
    swap                   5.5G   1.7M       5.5G     1%    /system/volatile
    objfs                    0K     0K         0K     0%    /system/object
    sharefs                  0K     0K         0K     0%    /etc/dfs/sharetab
    /usr/lib/libc/libc_hwcap1.so.1
                            71G   3.3G        68G     5%    /lib/libc.so.1
    fd                       0K     0K         0K     0%    /dev/fd
    rpool/ROOT/solaris-1/var
                            98G    13G        68G    17%    /var
    swap                   5.5G    96K       5.5G     1%    /tmp
    rpool/VARSHARE          98G   2.6M        68G     1%    /var/share
    rpool/export            98G    35K        68G     1%    /export
    rpool/export/home       98G    45K        68G     1%    /export/home
    Any ideas?
    -J

    Did you format your new drive to MAC OS Extended?
    Al

  • The file could not be imported: There is not enough disk space left

    The file could not be imported: There is not enough disk space left to import
    why? I have 53.1 Gb left and I can import the whole movie but when I broke it up into chapters to edit it will only import 2 edited chapters I don't like imovie
    anyone ??

    dananarama wrote:
    I just had the same problem this morning. I tried to import a 500MB mp4 into iMovie HD, and I have 9.5GB on my hard drive, but the same error message came up.
    If the 500MB mp4 file was highly compressed and iMovie converted it to DV, it's quite possible iMovie would run out of disk space.
    Although 9.5GB sounds like a lot, it's tiny when editing video. (Each hour of video is ~13GB.) When iMovie complains that it can't find the disk space it needs, it's not a good thing. Everything is put in jeopardy. Don't forget that thee Mac OS X itself needs a certain amount of elbow room. When it can't get it, big problems can occur.
    The main drive of your Mac should have at least 10-15% free disk space at all times, even AFTER iMovie/iDVD is done handling the video.
    Karl

  • There is not enough disk space available at the selected destination. Please choose another one or clear some space

    Importing a small motion movie into fcpx and I get this error "There is not enough disk space available at the selected destination. Please choose another one or clear some space"  the destination is a new 6TB raid thats empty.  I've created a new library  on that drive and still get the same error!  help..

    Did you format your new drive to MAC OS Extended?
    Al

  • Max payne 3 "Could not complete purchase, there is not enough disk space available to install the product."

    As most people should know, max payne 3 is a pretty big game, in fact, the second biggest game I know. However, when I try to purchase it, It says that it could not complete the purchase, there is  not enough disk space. Even though, the game requires 40 GB, I have well over 60 GB. Can anyone help me?

    You're downloading a large installer package that unpacks to an even larger set of installed files. There has to be enough space for both at the same time, plus a margin of safety to avoid the risk of a boot failure. You would probably need at least 80 GB of free space, maybe a little more.

  • "Not enough disk space" when there seems to be

    I'm a newbie to iDVD and iMovie (my last Mac was a Performa 6360--still using it for the family budget) and got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary features to import .wmv files (only way we could download one of the vidoe cameras).
    Issue: When she tries to import vidoes already on her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI"
    Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's deleted the trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
    On top of that, she also gets the same error message when she tries to burn the project onto a disk???
    I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
    Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.

    I'm a newbie to iDVD and iMovie (my last Mac was a Performa 6360--still using it for the family budget) and got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary features to import .wmv files (only way we could download one of the vidoe cameras).
    Issue: When she tries to import vidoes already on her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI"
    Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's deleted the trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
    On top of that, she also gets the same error message when she tries to burn the project onto a disk???
    I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
    Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.

  • "Not enough disk space" when there seems to be (+ rapid memory consumption)

    [Note: I originally posted this in the iDVD section, but due to an answer I got there to another question and further conversations with my daughter, figured out this is probably an iMovie question?]
    I'm a newbie to iDVD and iMovie and Forums (my last Mac was a Performa 6360--still using it for the family budget). I got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary software/features to import .wmv files (only way we could download one of the video cameras was by going from PC to Mac--can't remember if it was a Sony or Canon).
    Issue: When she tries to import vidoes into iMovie HD 6.0.3 which have already been transferred to her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI" [She says this is about a 4 min. clip.]
    Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's already deleted the Trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
    [Even more disturbing, just in the last couple of days with only a little time spent on the computer, the 28.8 GB has dropped to 2.3GB--obviously there is something she is doing that she is not aware of or shouldn't be doing that is consuming memory at a rapid pace.] On top of that, she also gets the same error message when she tries to burn the project onto a disk using iDVD???
    I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
    Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.

    Hello Karstn Schluter,
    This is fm's daughter who is havin ghte difficulites. at the end you tell me to try to answer 1-8 so i will try.
    1- how can you tell if the avi is containing divx? or not?? do I need to just keep this in mind when importing these files
    2- I have not brought in an external drive. I did try making my laptop computer a harddrive so I could import my imovie poject to my eMAC at one point, but it was not allowing me to do that either. Because I had to have it in DVD form or something
    3- No I did not segment the internal drive....sorry How do you do that??? Right now I am trying to find out what is taking up all the memory and Hard Disk Drive space....i do not know how to do that either....Do you know how???
    4-Yes I know flip4mac is for wmv....I guess what that question was emplying was that I also have wmv files that I am trying to import to imovieHD and that is not working either...I can get my avi to get into imovieHD, but not my wmv. files
    5-THank you for the tip with the trash then another question to this one how do you delet projects that are taking up memory that are no longer in use?
    6-Thank you for the tip...so then ignore the not enough disk space.....how can you alter the disk space so that you can save the project under save project as and not just save project?
    7- Sorry my dad was miss informed I cannot import the wmv. files to imovie and I cannot import imovie to iDVD I only have transferred one and then all of the other files are not seen as movies so I can not import them?? Does that make since
    8- When we were useing the Sony Camera originally we could not import the video to the MAC because it did not have the correct firewire cable and it would not been read onto the MAC computer. So, we have to buy the flip4mac equipment so that I would be able ot download the inoformation to the computer by a wmv.file dvd so we are having difficulites trying to import that file.
    I hope these answers clear up the question a little bit more and sorry that your answers brought out more questions. Thank you very much for helping me. I was using a different program in my college class so changing to imovie and idvd has been a huge struggle for me. Thank you once again.

Maybe you are looking for