Not enough bytes in image stream

Hi
I'm developing a program that reads/modifies/saves PDF files. I found a strange imagestream in the PDFReference Document:
2385 0 obj
<</Length 255/Filter /FlateDecode/Width 155/Height 76/BitsPerComponent 8/ColorSpace 36619 0 R/Type /XObject/Subtype /Image>>
stream
[Binary Data]
endstream
endobj
36619 0 obj
[/Indexed /DeviceCMYK 153 2378 0 R]
endobj
2378 0 obj
<</Length 264/Filter/FlateDecode>>
stream
[Binary Data]
endstream
endobj
The decoded stream of object 2385 is 5080 bytes long.
The decodes stream of object 2378 is 616 bytes long.
Strange:
Height/Width*BitsPerComponent = 76*155*8 = 94240 bits = 11780 bytes!
The length of the stream is only 5080 bytes long.
Aren´t there to less bytes for the image?
Or did i misunderstand something?
PDF viewers can display this PDF correctly, so there must be something I dont know...
What is the secret?
Thanks for your help!

I've found the error now. It was my FlateDecode algorythm which had a too small buffer for some streams, which had a very good compression rate. So they were cut. There aren´t much streams which such a compression rate, so I didn´t realize this a long time.
Thanks anyway!
Have a good day!

Similar Messages

  • Not enough memory loading image

    I have a problem loading an Image in a Motorola 720. Using Image.createImage("name.png") throws an IoException, Not enough memory to load Image. The image decoding method takes a lot of memory.. or at least it looks like that.
    The image is an png 12k and 466x561. I am wondering if it will depend on the program used to save the image, I tried with photoshop and fireworks, without transparencies.
    Any help? any ideas how could I solve the problem loading the image?
    Thanks in advance

    After loading, the image will be 466*561*4 bytes in
    size, 1,045,704 bytes. This formula is incorrect. I have loaded images of size which multiple cross 135000 whereas T720 heap size is 540k

  • Data stream from OEM device, TCP/IP "not enough memory"

    Hi Everyone,
    I'm trying to catch a data stream from an OEM device over a TCP/IP link.  I can start the data stream, or pause/resume it, but the OEM device determines when the data stream has ended.  The data stream begins, and within 20 seconds, I get the famed "not enough memory" error.  Once this happens, data is lost from the stream, and quite often the final message indicating completion is missed.  I see two solutions to this.  1) Watch how many bytes are backed up on my TCP/IP port, and issue a pause command until I can process the backed up bytes at which point a resume will be issued.  ...or 2) Use my application's memory usage in the same manner.  Does anyone know how to do either of these things?
    Thanks much

    Hi Toader,
    Thanks for your response.
    1) I'm not sending any data.  I'm trying to consume an incoming data stream which is being driven by an OEM device.  This device basically has an FPGA hooked up to a 100Mbit/s hose.  You can start it, pause it and resume it.  Those are the available operations related to consuming the data stream.  I think the crux of the problem is deciding when to pause the OEM device to give the LabView app a chance to process and store the accumulated portion of the data stream.
    2) Sure, but it's not my program and is large and complicated.  I guess I could write my own program within a program, but I would rather use the existing architecture.  I might write my own micro app, but I doubt it will keep up with the FPGA driven hose.  If I could detect the condition leading up to the "not enough memory" error, which it seems many LV developers have encountered, but not really solved, then I could issue a pause to the OEM device.
    3) Well using a LabView application under a 2Ghz Windows box may not be sufficient hardware.  But I really think it's the Windows operating system that I'm having trouble with, not the hardware platform.
    I've tried several counters in the LabView application, watched task manager before/during/after the "not enough memory" error, and downloaded an interesting app called taskmanager.vi in an attempt to get something to correlate with the error message.  I've not succeeded yet.  Here's what I think is happening.  The Windows OS is managing my wireless hardware, when it receives a TCP/IP packet, it puts it in the Windows Message que of my LabView application.  I think the "not enough memory" error relates to a Windows OS allocation for my message que which is being exceeded.  Any Windows programmers out there who would know how to look at the application's message que during runtime?
    Thanks for your classic suggestions Toader, I may try a micro app which is spawned by the main app when its time to grab the data.  My intuition is that no software limited by the Windows OS is going to keep up with single minded FPGA hardware.
    I thought this very interesting discussion was the answer and it may still be, but after trying 30+ various counters under Memory, System, Process, TCP, and Server, none correlated to the error.
    http://forums.ni.com/t5/LabVIEW/System-monitor-counter/m-p/1653448/message-uid/1653448/highlight/tru...
    I also tried a taskmanager.vi, but none of the various flavors of memory tracked by that little gem correlated with the error either.  At this point, I started to wonder "what memory was there not enough of?".
    Terry

  • Trying to build a DVD image, DVDSP4 says not enough space

    I have many years' experience using DVD Studio Pro 4, so this hopefully is not a stupid question.
    I'm using an iMac with 80gb free and an external HDD with 12gb free.  I have authored a DVD in DVD Studio Pro 4.  The project says it's 4.6gb.
    I need to make a disc image file of the DVD so I can burn it to DVD media using another computer.  When I do this, it encodes for hours and then says "Formating Failed.  Not enough space of the output media"  (I might be paraphrasing.)
    The only possiblt output medias, the iMac and the external drive, both have plenty of space, and the project is under the limit.  So what gives?

    Let me try this again, because I think we're not communicating.
    I have authored a DVD Studio 4 project with menus and assets, etc.  It simulates just fine.  The tab on the top of the DVDSP screen indicates my project is 4.6gb.  This means I should have no problem turning this project into a DVD.  The computer I'm working on has no DVD burning capabilities so I want to create a disc image of the project instead of burning a DVD.  I have done this before, where DVDSP encodes and builds a file that I can then use Disk Utility to burn to a DVD.  So, once I have my disk image, I will transfer that file to another computer, and use Disk Utility on that second computer to burn the DVD from the disk image.
    NOW
    The problem I'm having is that DVDSP is not able to make the disk image.  When I go to "Build/Format", it should make a disk image, but instead, I get an error saying there is not enough space on the output device.  The "output device" in this case is my external Hard drive which has plenty of space.  That is why I am asking for help.

  • Not enough memory to manipulate image

    I created a report to print out 10 graphs(control image).
    But the program gives error:not enough memory to manipulate image. I did the same in other programs, I have the same number of graphs, there was no problem.
    what's the real reason of this error?
    I attach my printing routine here.
    Attachments:
    print_graphs.vi ‏57 KB

    I seperated the report into two(each with 5 graphs).the error persisted. then I open some other Labview program and run it with printing command. it did not print any thing, nor did it give any error.
    then when I ended the program and shut down LABVIEW, it gave out a warnning said: internal error occurred.
    I did not know what exacly the error is. I did try to to report the error to NI. and after that when I reopen my program (which gave out "not enough memory to manipulate images" error), and re-run it. it worked and I could print. the error did not appear this time. But I'm not sure if it would come out again later.

  • Cannot export my D800 images out of lightroom, message reads not enough memory. Anyone any ideas how

    cannot export my D800 images out of lightroom, message reads not enough memory. Anyone any ideas how to fix this?

    Is it Win7 32-Bit (that's where I've seen it happen). I would report it as a bug at the official Adobe site:
    http://feedback.photoshop.com/photoshop_family
    Beat

  • IPhoto deleting images in iPhone but failing to import as not enough space

    I've lost the images and films on my iPhone as unfortunately I have the import set up to auto-delete (aargh!). Not enough disk space in iPhoto but it still deleted everything on my iPhone.
    Any idea if I can recover the lost images from my iPhone?
    Thanks, Stephen

    first you must have a minimum of 10GB of free disk for the Mac to operate correctly plus any extra space for special programs - do not continue operating until you have adequate space - many bad things can happen if you do not have adequate free disk
    as to these photos you may be able to recover them using a program like media recover - http://download.cnet.com/MediaRECOVER/3000-2242_4-42741.html
    in the future never allow any computer to automatically delete photos from your camera - import them and properly disconnect your camera and be sure everything is good (I wait for at least one backup cycle) and then use the camera reformat command to erase the media card and renew its format
    LN

  • 6680-Voda live streaming-Not enough Bandwidth

    Got a Nokia 6680 yesterday and could get the streaming Sky on Voda live no problem. I have tried today, it is saying not enough bandwidth and to check my network settings.
    Not sure what to do at this point.
    Any help would be appreciated please.

    This is probably because you are not in a 3G reception area. The connection will be via GPRS and therefore not sufficient for video streaming (in most cases).
    You can generally tell by look at the service indicator what sort of area you are in.
    All About Symbian - News, reviews and software for S60 phones.

  • Could not print "image name" because there is not enough memory (RAM).

    I cannot print anything from Photoshop CS5. I always get the message:
    Could not print “image name” because there is not enough memory (RAM).
    I'm using Mac OS 10.6.8, with 8 GB RAM. I have tried setting memory usage to 100% of RAM (7379 MB for me). The "Ideal Range" is 4058-5313 MB. I cannot print anything, not even a 20 kB  file because I always get that error message.
    I've tried unistalling & reinstalling, just to see if that did anything. It didn't help.
    Does anyione have any ideas for what the problem is?
    Thanks,
    Dan
    (I don't have a problem printing from any other programs, like Gimp, but I want to print from Photoshop because of they way it allows you to adjust what part of the image you print when you are cropping the image during printing.)

    shanahan3030 wrote:
    …have tried setting memory usage to 100% of RAM (7379 MB for me…
    That is never a good idea.  You're starving the OS of RAM.  Try pulling it back to 70% or less.
    Also, clarify how much disk space you have left on your boot drive and on your scratch drive.

  • Failed (why else would I post). Error creating an image of Drive D:, rc = 2. Return Code -2147467259 0x80004005. "Not enough storage is available to process this command".

    Seems a common set of Return Codes to post so apologies that's not specific.
    To me appears the issue is related to the "Not enough storage is available to process this command" log entry. Looked into it and some SCCM 2007 issues that were related to too many sessions to the site server, but even after rebooting my MDT server
    I get the same issue.
    The server I am attempting to capture has a 60gb VHD with around 30gb actually used. The MDT Server has over 100GB free space.
    Here is from BDD.log:
      Console > Turning on VERIFY option for network share
    ZTIBackup 10/10/2014 12:56:30 PM
    0 (0x0000)
      Console > Scanning files and directories...
    ZTIBackup 10/10/2014 12:56:30 PM
    0 (0x0000)
      Console > Error imaging drive [D:\]
    ZTIBackup 10/10/2014 12:56:30 PM
    0 (0x0000)
      Console > Not enough storage is available to process this command.
    ZTIBackup 10/10/2014 12:56:31 PM
    0 (0x0000)
    Return code from command = 2 ZTIBackup
    10/10/2014 12:56:31 PM 0 (0x0000)
    Error creating an image of drive D:, rc = 2
    ZTIBackup 10/10/2014 12:56:31 PM
    0 (0x0000)
    Event 41036 sent: Error creating an image of drive D:, rc = 2
    ZTIBackup 10/10/2014 12:56:31 PM
    0 (0x0000)
    ZTIBackup COMPLETED.  Return Value = 2
    ZTIBackup 10/10/2014 12:56:32 PM
    0 (0x0000)
    ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2
    ZTIBackup 10/10/2014 12:56:32 PM
    0 (0x0000)
    Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2
    ZTIBackup 10/10/2014 12:56:32 PM
    0 (0x0000)
    Command completed, return code = -2147467259
    LiteTouch 10/10/2014 12:56:33 PM
    0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005
    LiteTouch 10/10/2014 12:56:33 PM
    0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005
    LiteTouch 10/10/2014 12:56:33 PM
    0 (0x0000)
    I'll post below full logs.

    imagex reported:
      Console > Error imaging drive [D:\]
      Console > Not enough storage is available to process this command.
    obvious question is: do you have enough free space on
    "\\arcadmin3\deploymentshare$\Captures\SIMSERVER.wim"
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • When streaming movies from itunes, I get an error that there is not enough storage

    I stream a movie for my kids and the ipad says that there is not enough storage available. I can stream from Vudu and Netflix with no issues. When I started streaming from itunes, I cannot due to this error.
    Still learning iOS, any help would be greatly appreciated!
    Thank you in advance!

    iTunes Store does not stream movies.

  • Can anyone help? I've just got my new iphone 6.  I'm restoring from the icloud but it's saying there's not enough storage for my photos....and I'm unable to access any images.  Help appreciated

    Hi,
    I've just moved on from an iphone 5 to an iphone 6.
    I'm now on my second attempt at restoring it through the icloud.
    My photos and videos are unavailable and it keeps saying I'm low on storage. At this stage it just keeps saying it's updating but it's been saying that for 8 hours and I still don;t have any photos available....any advice appreciated.  It's getting a little frustating
    Thanks,
    Emma

    The backup cannot be restored to the iPhone if there is not enough storage space available.

  • "Not enough space" - on DB.open

    Hello,
    My application is using BDB 3.3.1.
    I’m running with the following Parameters:
    m_dbEnv.set_cachesize(0, 536870912, 0);
    m_dbEnv.set_verbose(Db.DB_VERB_CHKPOINT, true);
    m_dbEnv.set_verbose(Db.DB_VERB_RECOVERY, true);
    m_dbEnv.set_verbose(Db.DB_VERB_DEADLOCK, true);
    m_dbEnv.set_verbose(Db.DB_VERB_WAITSFOR, true);
    m_dbEnv.set_lk_detect(Db.DB_LOCK_DEFAULT);
    m_dbEnv.set_lk_max_lockers(4096);
    m_dbEnv.set_lk_max_locks(1000000);
    m_dbEnv.set_lk_max(1000000);
    m_dbEnv.set_tx_max(70);
    m_dbEnv.set_lg_regionmax(204800);
    But despite of the relatively large numbers of lockers and transactions, I’m getting :
    com.sleepycat.db.DbException: Not enough space: Not enough space
    On: com.sleepycat.db.Db._open(Native Method)
    I want to know from lack of what resource the “Not enough space” is thrown?
    Is it because of cachesize/ lockers/ locks/ lockObjects or may be something else.
    Some statistics: when the error happened the whole BDB size was 5284880 bytes
    While I’m running now with 5546186 bytes and no error occur.
    Please advice what can be done to find the problem?
    If it seems like a memory leak – please advice, on how it can be found.
    Thank you in Advance
    Shira

    Hi,
    The "Not enough space" error is corresponding to ENOMEM - 12, that's described here:
    http://www.oracle.com/technology/products/berkeley-db/faq/db_faq.html#8
    This error indicates that some resource has been exhausted. There are several ways to find out what is causing this error:
    1) Configure the Berkeley DB error stream, which can be done like this:
    dbenv->set_errfile(dbenv, stderr);
    If you don't have a database environment handle, you can call this on the database handle:
    db->set_errfile(db, stderr);
    With this, you should see a message explaining what resource has been exhausted.
    2) Run the db_stat utility:
    db_stat -e -h /path/to/databases
    Usually you can solve the problem by configuring the lock limits ( http://www.oracle.com/technology/documentation/berkeley-db/db/ref/lock/max.html ) -- they are often what runs out, or the cache size ( http://www.oracle.com/technology/documentation/berkeley-db/db/ref/am_conf/cachesize.html ).
    Bogdan Coman

  • Blu-ray Dual layer code 25 "not enough space on media"

    Using Encore CS6 (Cloud edition) to build Blu ray Dual Layer on Mac. Project is 34.75 GB. While building Blu-ray Image all is well until Data written 34.75 GB of 34.75 GB. Then the dreaded "Blu-ray Error: "not enough free stoarage", Code: "25", Note: "Note enough space on media" comes up and the buld is stopped. I repeated by building a new project with the same results. There is over 100 GB of free space on the hard drive. I paritially rebuilt the project at 22.5 GB and tried it as a single layer image. Everything worked fine for that Blu-ray image, so it appears this could have something to do with the Dual layer nature of the larger project. Any help and guidance would be much appreciated.

    I would point out three points. You can try them in order:
    You can apply the 6.0.2 patch that is available (if you have not done so) because the patch has a fix around this issue.
    There is a lot of space requirements for the dual layer BD project. Here is the list of almost all the things that would need space:
    First the asset's indexed files would need space. For audio files, there might be conforming happening that again would need space.
    Then when yoy build the project, the assets will be transcoded (if already not or they are not Don't Transcode). This would take a considerable amount of space as the transcoded assets are complete footage which would be huge.
    Then while creating a image file, First all the files (muxed video streams) would be copied on the disc in a folder (generally named BDMV) and then at the final step, they would be copied from the BDMV folder to the iso file and finally the BDMV folder would get deleted. So this step would need almost double the size of your project. IF your project is say 35 GB, then this step alone would take more than 70GB.
                   So the space requirement for a 35 GB (Disc Info) project might go to almost 100 GB.
    But again there is some bug in size estimation for Motion menus and slideshows. Encore says that they will occupy lesser space but actually they are going to occupy more space. So if your project has motion menus or slideshow, then the estimation might be incorrect. So if it showing 35 GB (for example) and your project has motion menu or slideshow, then actually it might be 37GB or more or anything greater than 35GB depending on the slideshow and motion menu duration in the project.
    -Ramesh.

  • 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

Maybe you are looking for

  • Which imac would work best for Graphic Design?

    I am a Graphic Designer, currently using Creative Suite 2 (soon to be upgraded to CS3) and I need a new Mac for home. A Powermac takes up too much space, so I'm thinking about an imac with a 24" monitor and I have a few questions for the experts:) Wh

  • Having problem with mouse pionter in webpages

    i have a problem with mouse pionter in webpages since i've updated my firefox . when i'm reading a webpage and i click somewhere in the webpage,my mouse pointer goes from the normal pointer to the typing and selecting one. i also can not scroll up an

  • Problems with Snow Leopard and choosing startup disk.

    I just installed Snow Leopard 10.6.3 on my external drive to test it out. Most things seem to work just fine, but I'm having problems selecting a start up disk from system preferences. When I bring up start up disk, I see the internal and external dr

  • Catalyst 3500, 2900, 3700s

    I need a good reference with pictures of all the GBIC types, MTRJ, SFPs available along with the type of cables needed for each - SC, LC, ST -- Very confusing....

  • Unable to resolve service name

    I am vishnu prasath.i am a reader of oracle magazine. I need a help from you.I have installed Oracle 9i in my machine.when i was installed it asked me to enter SID.i entered as specified in the example ie test.acme.com where as Globaldatabase name=te