Keyword list in iPhoto is too large for effective searches

My keyword list in iPhoto is rather long. If I start searching for a photo by keywords, the opened list is too long to fit on the screen. With other words all keywords before "G" can not be reached. What can I do?
Börries Kemper

Search using Smart Albums:
Keyword -> is -> etc
And then left Aple know the problem:
IPhoto menu -> Provide iPhoto Feedback

Similar Messages

Iphoto movies too large for screen after upgrade

My movies in iphoto recently stopped playing, so I turned to the forums and tried the fix related to upgrading to Snow Leopard. This mostly worked (I also had to open Quicktime 7 to kick it off), but now the movies, especially in portrait format, extend below the bottom of the screen. Since the resizing and controls are on the bottom of the pane, I have no way of accessing them, so I cannot play the clips or resize. Any suggestions?

Close off Safari from multitasking:
Double-tapping the Home button will bring up the running apps icons along with an app screenshot "card" above the icon. Tap-drag the app's -card- (NOT the icon) up and off the screen.
Next, reset the iPad:
Device Reset (won't affect settings/data/music/apps/etc)
1. Press and hold (& continue to hold) BOTH the Sleep/Wake button & the Home button.
2. Continue to hold BOTH (ignoring any other messages that may show) until you see the Apple logo on the screen.
3. Release BOTH buttons when you see the Apple logo and allow the device to boot normally.

HT1229 My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my

My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my iMac (that's my responsibility). I dragged it to Trash and when it started to move I clicked over to the new hard drive to confirm it had indeed been copied. I became nervous when I didn't see among the few files on this otherwise empty new hard drive anything that resembled a 280GB Library so I cancelled the migration to trash.
How can I be sure that my iphoto has been copied and that all my "metadata" survived in tact?

the new backup drive
I thought the new drive would be your data drive to host the iPhoto library. Do you also use it for TimeMachine backups?
I am unable to search either in email as well as Finder. I AM able to search within iPhoto though, thankfully
Spotlight may still be busy rebuildig its index.
You could try to rebuild the Spotlight Index, if you do see no progress:
Spotlight: How to re-index folders or volumes
I hope, other frequent posters will drop in. I have not used iPhoto 8.x in long time.

Trx F-53, The difference is too large for clearing Message no. F5263

Hi,
I created a PO, then I posted the goods receipt, the invoice and I was trying to
post the payment by F-53 trx.
When I select an open item from the list and I try to simulate the posting by the menu (Document, simulate), system replies by:
"*The difference is too large for clearing
Message no. F5263*"
Cannot understand why it is not possible to post the outgoing payment
Regards

Dear Sappione,
did You check the tolerances?
Check in transaction OBY6 the indicator 'No forex rate diff. when
clearing in LC' is not set the amount is converted with the exchange
rate valid at clearing date, in case You're clearing in LC a foreign document.
When you post a clearing transaction with rounding
differences, those differences are posted to an additional line item
GL accounts. This account determination is customized as follows :
FBKP - Exchange rate differences -
Exchange rate difference in open items - KDF -a/c XXXXXXXXX
(Realized gain exchange rate difference)
The accounts used for rounding differences when clearing
are the realized gain/loss exchange rate accounts.
please check all the 3 suggestions.
Mauri

OS10.3.1 a disaster! Among other things, the dsplay is too large for screen

I do not like OS 10.3 ! After my Z10 was updated to 10.3.1.1779 about a month ago, I access it because the password entry keyboard displayed for about 1/10 sec leaving a black screen.
After a device reset the device the keyboard remained visible but did not respond to touches (actually it did respond randomly to some). Finally another reset gave me a usable keyboard.
But the device always opens with an icon display about 20% too large for my screen and requires several shrink attempts before the proper size displays. Each attempt simply bounces back to the oversize state.
Unfortunately, this also happens with every app (including "Settings") opened. Yesterday, I couldn't return to the main of Settings because the sub-page wouldn't shrink to expose the "<' button - a close and re-open was the only way to get back to the main page.
Other points I hate about the OS: I've noticed my active wallpaper (not custom but from 10.2) is not listed in the the new 10.3 wallpaper list and since I don't know where its stored I can't try one of the newer ones without giving up on the present wallpaper.
The date displayed on the home screen is too faint to be read with my wallpaper. I know there are some people who think black on black is cool; they obviously have great eyesight. The new 10.3 compass is now totally useless and the new clock is not much better but is at least still usable by a change to a digital display.
I recently tried to check the time on a sunny afternoon and gave up because I couldn't make out the white lines on the black background. I find the stupidity of black on black unfathomable and in over 40 years of software development I have never seen something as wasteful of engineering time as products with poor user interfaces (i.e. black on black). Why can't these apps offer the user the ability to change the colour?
The calculator has also regressed. Again all black (cool!), though that's not the issue here. For the longest time I thought it no longer supported scientific operations until I accidentally got a lucky swipe to bring it into view.
However, the requirement of a half-dozen swipe attempts for each display change reduces this app to a space waster or only to be only useful for simple operations and units conversion. I'm going to try a reload of the OS but unfortunately that won't improve the apps.
Is this standard procedure that Blackberry destroys all (blackberry) apps of the previous version with new ones at each update and offers no way to get back or protect against such changes?

Hi All,
I have already checked below configuration T-Code Value :
T-Code : OBA0 :
Tolerance for Groups of G/L Accounts in Local Curre :
Debit posting : 0 TWD, Percentage 0 %
Credit posting : 0 TWD, Percentage 0 %
T-Code : OBA4 :
Upper limits for posting procedures :
Amount per document : 9,999,999,999,999
Amount per open item account item : 999,999,999,999
cash discount per line item : 1%
Permitted payment differences :
Revenue : Amount 100, Percent 1%, Cash discnt adj. to : 100
Expense : Amount 100, Percent 1%, Cash discnt adj. to : 100
I don't understand when AR open item amount is USD 100.3, and incoming payment 101.12, The system can auto clearing by current configuration, but change the AR open item amount to USD 0.3 and change incoming payment amount to 1.12, The system alert error message "The difference is too large for clearing". The same system configuration and the same "Not assigned" value in choosing open item screen, but produce different results!
How should i change the configuration?
Best regards,
Eric
Edited by: Eric Yang on Sep 12, 2008 2:12 AM

My time Machine keeps saying, "Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 345.74 GB but only 289.80 are available." I have already excluded files. I have a 1tb external drive. HELP!!!

For over two weeks now I have been frustated and not having my TIme Machine back up to my 1tb external drive. I dont understand why now its a problem. It keeps saying
"This backup is too large for the backup disk. The backup requires 345.74GB but only 289.80GB are avialable. Time Machine needs work space on the bakup disk, in addition to the space required to store backups. Open Time Machine preferences to select a large backup disk or make the bakup smaller by excluding files." So I have already excluded almost all of my files, and even deleted the backup disk yet, that quote still keeps popping up. I am truly at a wall with this. I have a Mac OS X version 10.7.5. CAN SOMEONE HELP ME PLEASE????

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

"Backup is too large for the backup volume" error

I've been backing up with TM for a while now, and finally it seems as though the hard drive is full, since I'm down to 4.2GB available of 114.4GB.
Whenever TM tries to do a backup, it gives me the error "This backup is too large for the backup volume. The backup requires 10.8 GB but only 4.2GB are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I understand that I have those two options, but why can't TM just erase the oldest backup and use that free space to make the new backup? I know a 120GB drive is pretty small, but if I have to just keep accumulating backups infinitely, I'm afraid I'll end up with 10 years of backups and a 890-zettabyte drive taking up my garage. I'm hoping there's a more practical solution.

John,
Please review the following article as it might explain what you are encountering.
*_“This Backup is Too Large for the Backup Volume”_*
First, much depends on the size of your Mac’s internal hard disk, the quantity of data it contains, and the size of the hard disk designated for Time Machine backups. It is recommended that any hard disk designated for Time Machine backups be +at least+ twice as large as the hard disk it is backing up from. You see, the more space it has to grow, the greater the history it can preserve.
*Disk Management*
Time Machine is designed to use the space it is given as economically as possible. When backups reach the limit of expansion, Time Machine will begin to delete old backups to make way for newer data. The less space you provide for backups the sooner older data will be discarded. [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
However, Time Machine will only delete what it considers “expired”. Within the Console Logs this process is referred to as “thinning”. It appears that many of these “expired” backups are deleted when hourly backups are consolidated into daily backups and daily backups are consolidated into weekly backups. This consolidation takes place once hourly backups reach 24 hours old and daily backups reach about 30 days old. Weekly backups will only be deleted, or ‘thinned’, once the backup drive nears full capacity.
One thing seems for sure, though; If a new incremental backup happens to be larger than what Time Machine currently considers “expired” then you will get the message “This backup is too large for the backup volume.” In other words, Time Machine believes it would have to sacrifice to much to accommodate the latest incremental backup. This is probably why Time Machine always overestimates incremental backups by 2 to 10 times the actual size of the data currently being backed up. Within the Console logs this is referred to as “padding”. This is so that backup files never actually reach the physically limits of the backup disk itself.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space. Do NOT, however, delete files from a Time Machine backup disk by manually mounting the disk and dragging files to the trash. You can damage or destroy your original backups by this means.
Additionally, deleting files you no longer wish to keep on your Mac does not immediately remove such files from Time Machine backups. Once data has been removed from your Macs' hard disk it will remain in backups for some time until Time Machine determines that it has "expired". That's one of its’ benefits - it retains data you may have unintentionally deleted. But eventually that data is expunged. If, however, you need to remove backed up files immediately, do this:
Launch Time Machine from the Dock icon.
Initially, you are presented with a window labeled “Today (Now)”. This window represents the state of your Mac as it exists now. +DO NOT+ delete or make changes to files while you see “Today (Now)” at the bottom of the screen. Otherwise, you will be deleting files that exist "today" - not yesterday or last week.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides. If it has been some time since you deleted the file from your Mac, you may need to go farther back in time to see the unwanted file. In that case, use the time scale on the right to choose a date prior to when you actually deleted the file from your Mac.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*Full Backup After Restore*
If you are running out of disk space sooner than expected it may be that Time Machine is ignoring previous backups and is trying to perform another full backup of your system? This will happen if you have reinstalled the System Software (Mac OS), or replaced your computer with a new one, or hard significant repair work done on your exisitng Mac. Time Machine will perform a new full backup. This is normal. [http://support.apple.com/kb/TS1338]
You have several options if Time Machine is unable to perform the new full backup:
A. Delete the old backups, and let Time Machine begin a fresh.
B. Attach another external hard disk and begin backups there, while keeping this current hard disk. After you are satisfied with the new backup set, you can later reformat the old hard disk and use it for other storage.
C. Ctrl-Click the Time Machine Dock icon and select "Browse Other Time Machine disks...". Then select the old backup set. Navigate to files/folders you don't really need backups of and go up to the Action menu ("Gear" icon) and select "Delete all backups of this file." If you delete enough useless stuff, you may be able to free up enough space for the new backup to take place. However, this method is not assured as it may not free up enough "contiguous space" for the new backup to take place.
*Outgrown Your Backup Disk?*
On the other hand, your computers drive contents may very well have outgrown the capacity of the Time Machine backup disk. It may be time to purchase a larger capacity hard drive for Time Machine backups. Alternatively, you can begin using the Time Machine Preferences exclusion list to prevent Time Machine from backing up unneeded files/folders.
Consider as well: Do you really need ALL that data on your primary hard disk? It sounds like you might need to Archive to a different hard disk anything that's is not of immediate importance. You see, Time Machine is not designed for archiving purposes, just as a backup of your local drive(s). In the event of disaster, it can get your system back to its' current state without having to reinstall everything. But if you need LONG TERM storage, then you need another drive that is removed from your normal everyday working environment.
This KB article discusses this scenario with some suggestions including Archiving the old backups and starting fresh [http://docs.info.apple.com/article.html?path=Mac/10.5/en/15137.html]
Let us know if this clarifies things.
Cheers!

HT1338 Since having my Macbook Pro attached to a large display screen, everything is too large for the screen. Is there a cure please?

Today I had my Mac linked to a projector screen, and since disconnection evrything from the desk top onwards has been too large for the screen. Before that evrything was perfect. I have tried zoom buttons etc, but nothing seems to work. Any help gratefully rceived.

So it's not the Zoom feature? Open System Preferences Universal Access pane Seeing tab. Make sure Zoom is turned OFF.
If it's not that, then you may have the resolution set so that it is not optimal for the built-in display. Open System Preferences Displays pane Display tab. The optimal resolution is usually the one at the top of the list of choices.

File too large for volume format?

I'm trying to copy a 4.6GB .m4v file from my hard disk to an 8GB USB flash drive.
When I drag the movie in the finder, I get a dialogue telling me the file "is too large for the volume's format". That's a new one for me. If the flash drive has 8GB available, and the file is only 4.6GB in size, how is that too large? Does it have to do with the way the flash drive is formatted? It's presently formatted as MS DOS FAT 32. Is that the problem? Do I need to reformat as HFS+? Or is it some other problem?

The flash drive is pre-formatted FAT32 which has a maximum allowable file size of 2 GBs. Change the flash drive format for OS X:
Drive Partition and Format
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.

Code too large for try statement

I have a jsp that I am getting the following exception on.
[ServletException in:/jsp/DLG_PTEN.jsp] Unable to compile class for JSP C:\Documents and Settings\ebsgam\My Documents\IBM\wsappdev51\workspace\StnWeb\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\DefaultEAR\StnWeb.war\jsp\_DLG_5F_PTEN.java:13576: code too large for try statement } catch (Throwable t) { ^ C:\Documents and Settings\ebsgam\My Documents\IBM\wsappdev51\workspace\StnWeb\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\DefaultEAR\StnWeb.war\jsp\_DLG_5F_PTEN.java:1165: code too large for try statement try { ^ 2 errors '
I am currently running this on Websphere Aplication Developer 5. First off I'm hoping that this error will go away when it is deployed to tomcat. But I wanted to see if anyone has had this problem and knows of a tweek or work around for it.
The jsp in question is not the longest one I have... but it has a large number of drop down list boxes .. using jstl <select><option>. and the drop downs have around 40 or 50 items in them.

in weblogic 8.1, i've met the same error, and solved the problem by adding param to weblogic.xml , like below:
<jsp-descriptor>
     <jsp-param>
          <param-name>noTryBlocks</param-name>
          <param-value>true</param-value>
     </jsp-param>
</jsp-descriptor>

(gdb)procfs: target_wait (wait_for_stop) : Value too large for defined ...

When trying to debug a cpp program using dbx within the solaris9 I get the following error.
How Can I fix this error? Please give me a help.
Thanks.
[UC]gdb nreUC100
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.9"...
(gdb) l
130 * 1 -
131 * 99 -
132 * DB Table : N/A
133 ******************************************************************************/
134 int
135 main(int argc, char* argv[])
136 {
137 struct sigaction stSig;
138
139 stSig.sa_handler = sigHandler;
(gdb)
140 stSig.sa_flags = 0;
141 (void) sigemptyset(&stSig.sa_mask);
142
143 sigaction(SIGSEGV, &stSig, 0);
144
145 if ((argc < 5) ||
146 (strlen(argv[1]) != NRATER_PKG_ID_LEN) ||
147 (strlen(argv[2]) != NRATER_SVC_ID_LEN) ||
148 (strlen(argv[3]) != NRATER_PROC_ID_LEN) ||
149 (isNumber(argv[4])))
(gdb)
150 {
151 Usage(argv[0]);
152
153 return NRATER_EXCEPT;
154 }
155
156 ST_PFNM_ARG stArg;
157 memset(&stArg, 0x00, sizeof(stArg));
158
159 memcpy(stArg.strPkgID_, argv[1], NRATER_PKG_ID_LEN);
(gdb) b 157
Breakpoint 1 at 0x1a668: file nreUC100.cpp, line 157.
(gdb) r 02 000001 000001 1
Starting program: /UC/nreUC100 02 000001 000001 1
couldn't set locale correctly
procfs: target_wait (wait_for_stop) line 3931, /proc/19793: Value too large for defined data type.
(gdb)

Sorry, there are not too many gdb experts that monitor
this forum. Assuming you are on Solaris, you can
use the truss command to see what gdb is doing.
First start gdb
% gdb
(gdb)
Then in another window, attach truss to it.
% pgrep gdb
12345
% truss -p 12345
The go back to gdb and run the program.
IS the line number in the gdb error a line number
in the gdb source code? Or is gdb complaining
about a location in your application source code?
If it's in your app, then looking at that line might
help you figure out what 's going on.
Otherwise, you can always download the gdb source
and grep for that error message and see what
makes it happen.
I found this similar problem when a user can't
debug a setuid program.
http://sources.redhat.com/ml/gdb-prs/2004-q1/msg00129.html
Here is another similar warning that I found with google.
http://www.omniorb-support.com/pipermail/omniorb-list/2005-May/026757.html
Perhaps you are debugging a 32-bit program with a 64-bit gdb or vice versa?

The message I get is: Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 111.27 GB but only 42.1 GB are available.

I have a problem with my Time Capsule. The message I get is: Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 111.27 GB but only 42.1 GB are available. As a result, my backups are no longer running. My umderstanding was that the Time Capsule would automatically delete old backups to make space. Can anyone help me figure out how to get my backups to run again?

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Time Machine backs up one MacBook, but "backup is too large" for second

We have two MacBooks running OS 10.5.8 and both are connected wirelessly to Time Capsule. My daughter's laptop backs up fine. But my wife's laptop fails. It backed up one time when I first installed it, but never since. The error message I get is that the backup is too large for the backup volume -- 71.8 GB required but only 7.4 GB available.
My daughter's machine has a lot of photos and iTunes files on it, so it shows 141 out of 150 GBs are used up. The Time Capsule, which I understood to have 1 TB actually shows only 7.4 GB out of 463 GB are available.
And actually, when I try to manually run Time Machine on my wife's machine I get the really long Preparing message, and then the Time Machine Error message about not enough volume.
Should a machine with 150 GB capacity really be taking so much space on Time Capsule, and why the difference between the 1 TB advertised capacity and the <500GB of memory that actually appears to be there?
Does any of this suggest I need to restore the external or internal drives?

Steve Hasler wrote:
We have two MacBooks running OS 10.5.8 and both are connected wirelessly to Time Capsule. My daughter's laptop backs up fine. But my wife's laptop fails. It backed up one time when I first installed it, but never since. The error message I get is that the backup is too large for the backup volume -- 71.8 GB required but only 7.4 GB available.
Does it make sense that it's trying to back up about 60 GB (Time Machine adds 20% for temporary workspace) from that Mac?
If so, see if it has the +Warn when old backups are deleted+ box checked in Time Machine Preferences > Options.
Click the Time Capsule in a Finder sidebar. If the Finder is in +Column View,+ you should see something like this:
|
except there should be two +sparse bundles+ listed in the third column. Right-click each one in turn, select +Get Info,+ and see what's shown for Size. Report back with the numbers. Also tell us if you have any other data on your TC, besides the 2 Mac's backups.
My daughter's machine has a lot of photos and iTunes files on it, so it shows 141 out of 150 GBs are used up. The Time Capsule, which I understood to have 1 TB actually shows only 7.4 GB out of 463 GB are available.
And actually, when I try to manually run Time Machine on my wife's machine I get the really long Preparing message, and then the Time Machine Error message about not enough volume.
That sounds like it's doing a "deep traversal," perhaps after a long time since the last backup, where it has to compare everything on the Mac to the backups, to figure out what needs to be backed-up.
Should a machine with 150 GB capacity really be taking so much space on Time Capsule
Sure. Time Machine will use up all the space available to it, then begin deleting the oldest backup(s) when it needs room for new ones.
and why the difference between the 1 TB advertised capacity and the <500GB of memory that actually appears to be there?</div>
It does sound like you have a 500 GB Time Capsule. The original ones were 500 GB; I'm not sure when the 1 TB version came out, and now you can get them with 2 TB. How old is it, and why do you think it's a 1 TB model?

Why is TM telling me backup is too large for disk?

Since upgrading to SL, I get this error message when I attempt to run TM back ups:
_+"This back up is too large for the backup disc. The backup requires 123.28gb but only 66.44gb are available."+_
My HD is currently holding 174gb of used space. The LaCie backup drive is 250gb and there is nothing else on this disk.
I thought the culprit might be some movie files i recently imported. I deleted all of those files from all TM backups but that didn't work. Then I tried to erase the backup drive and start over using Disk Utility. That didn't work either. I read on another post to dump the plist and restart the computer, then redesignate the backup drive. Still didn't work.
Any suggestions out there on what is happening and how to fix?

Jaydon wrote:
Not sure how i would tell if it's "scratch" or not.
Sorry, that's a common term for a "working" disk/partition/folder that is temporary and not to be saved.
Sorry for the fire drill. I thought a 250gb drive would logically be enough for 175gb worth of data.
Yes, Apple doesn't make that very clear.
I'll definitely look into a larger drive. Any recs on reliable brand?
Most any drive will work with Macs, and Time Machine.
If you think you ever might want to put a "bootable clone" on it, be sure it's a bootable drive. Most Intel Macs can boot from F/W or USB. But some Western Digitals won't boot a Mac. Their list of which ones should and +should not+ boot: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/stdadp.php?pfaqid=1787. But note the disclaimer that they don't support it +*at all.+*.
In addition, many of them have a built-in sleep mode that cannot be disabled, and sometimes interferes with Time Machine backups: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/stdadp.php?pfaqid=1376
Depending on what ports you have, FireWire 800 is by far the fastest; FireWire 400 next, and USB slowest (F/W 400 and USB 2.0 are rated about the same for short bursts, but F/W is faster for sustained transfers. Also, your Mac's CPU has to do more of the work with USB, so actual throughput is usually less).
Many folks think USB is less reliable than FireWire. If you do get USB, be sure to connect it to a port on your Mac, not a keyboard (that may be only USB 1.0). Try to avoid hubs, too.
If you're using USB, it's usually best to get a drive with it's own power supply, as taking power from your Mac can be a marginal proposition. Portable FireWire drives without separate power supplies don't seem to have this problem.
Take any advice for or against particular makes or models with a grain of salt: all makers (of just about anything) can have a "run" of bad components, or a relatively few early failures. Plus, by the time any really good trends are noted, the model has probably been revised or replaced anyway!
Marking solved....thanks again
Great, and thanks for the star!

Backup too large for volume

I have 2 macbook pro's (120GB & 160GB) backing up to a 500GB TM.
both were backing up just fine, however in the past month the 160GB
macbook pro keeps getting this message.....
"backup too large for volume?"
and subsequently the backup fails?
the size of the backup is less than the free space on the TM drive...
any help?

dave,
*_Incremental Backups Seem Too Large!_*
Open the Time Machine Prefs on the Mac in question. How much space does it report you have "Available"? When a backup is initiated how much space does it report you need?
Now, consider the following, it might give you some ideas:
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” [http://discussions.apple.com/thread.jspa?threadID=1209412]
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
If you have recently created a new disk image or burned a DVD, Time Machine will target these files for backup unless they are deleted or excluded from backup.
*Events-Based Backups*
Time Machine does not compare file for file to see if changes have been made. If it had to rescan every file on your drive before each backup, it would not be able to perform backups as often as it does. Rather, it looks for EVENTS (fseventsd) that take place involving your files and folders. Moving/copying/deleting/saving files and folders creates events that Time Machine looks for. [http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14]
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your directories. Every one of these changes is recorded by the OS as an event. Time Machine will backup every file that has an event associated with it since the installation.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer describes this behavior: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*TechTool Pro Directory Protection*
This disk utility feature creates backup copies of your system directories. Obviously these directories are changing all the time. So, depending on how it is configured, these backup files will be changing as well which is interpreted by Time Machine as new data to backup. Excluding the folder these backups are stored in will eliminate this effect.
*Backups WAY Too Large*
If an initial full backup or subsequent incremental backup is tens or hundreds of Gigs larger than expected, check to see that all unwanted external hard disks are still excluded from Time Machine backups.
This includes the Time Machine backup drive ITSELF. Normally, Time Machine is set to exclude itself by default. But on rare occasions it can forget. When your backup begins, Time Machine mounts the backup on your desktop. (For Time Capsule users it appears as a white drive icon labeled something like “Backup of (your computer)”.) If, while it is mounted, it does not show up in the Time Machine Prefs “Do not back up” list, then Time Machine will attempt to back ITSELF up. If it is not listed while the drive is mounted, then you need to add it to the list.
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder if you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.
If none of the above seem to apply to your case, then you may need to attempt to compress the disk image in question. We'll consider that if the above fails to explain your circumstance.
Cheers!

Keyword list in iPhoto is too large for effective searches

Similar Messages

Maybe you are looking for