Date Corruption in iPhoto 9, other bugs (possibly from migration?)

Just upgraded to iPhoto 9 and upgraded my library, then imported some new photos. I'm seeing the following problems:
- Some photos from my old library that were rotated are reverted to their original position. Not sure yet if I also lost any other edits.
- All movies have had their dates changed by +3 days. Maybe +2. Even the movies I imported after upgrading have this problem.
- When I uploaded photos to Flickr (via Flickr uploader, the integrated thing is not working) several dates were corrupted in Flickr. But they're still okay in iPhoto.
Any idea how to fix this?

launch iPhoto while depressing the option (alt) and command (apple) keys and rebuild your library
LN

Similar Messages

Aperture cannot import anything from iPhoto and other bugs!!

Aperture is buggy. Recently, I just updated Mac OS X to 10.4.5 and also updated iLife 06. Now I cannot import anything from iPhoto. I tried import images from iphoto or import iphoto library, both not working. I can import images from other directories but jut could not see anything display under iphoto library directory. Trying to use import iphoto library, click choose and then nothing happens.
If you create a smart web gallery, all photos will be automatically duplicated.

I used Pacifist.app to find iPhoto in the iLife '06 install package and then installed the app in the default location replacing the bundle that was there.
the normal method gave me an install error.
Thank you to the person who discovered this.
I was going nuts trying. I have 6 iphoto libraries with 30,000 photos in total and some would import fine and others would not. couldn't tell the difference between them and had forgotten the update. just got a new iMac intel and wasn't paying attention. Causality

Corrupted Library6.iPhoto file. New Library from ext. drive?

My Library6.iPhoto file is corrupted. How do I create a new 'Library' when all the 'original' stills are on an external drive and will not fit on my 'desktop'?
Ben

TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Do you Twango?

[SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

Be careful
EXT4 Data Corruption Bug Hits Stable Linux Kernels
http://www.phoronix.com/scan.php?page=n … px=MTIxNDQ
https://lkml.org/lkml/2012/10/23/779
Edited: Removed the [ALERT] label.
Last edited by ontobelli (2012-11-01 04:58:43)

headkase wrote:
Even though it is a severe bug the chances of it happening to you are low. You have to unmount and immediately remount an EXT4 partition twice in a row for it to happen. On a normally operating system that is not a normal thing to happen. Just wait on your desktop for 5 minutes before rebooting again.
Arch, as a general rule, tends to stick as close to upstream as possible. I'm sure the devs are very competent people but a quick hack or branch revert has the possibility of introducing issues of its own. With the chance of the bug occurring low on a normally operating system I think it is better to wait for a fix from upstream.
Well maybe i am a bit over stressed about this since with this computer i have quite a lot of troube which i cannot find solutions to. Also a kernel panic after a reboot this morning -probably not related to this- got me in a bad mood.
Anyway.

How can I preserve the date and time of photos when moving them from iPhone to iPhoto and then to other folders on my computer?

In the past I’ve had no problem moving photos from my iPhone 4 into various folders on my computer while retaining their original date and time. I would import into iPhoto, then drag the photos from iPhoto into other folders via the Finder or Adobe Bridge (which is my principal image organizer). The original date and time of the photo would always travel with the jpeg into iPhoto and then into other folders. However, sometime during a recent session transferring photos in this way, the dates of the photos started to change at the point when I copied them out of iPhoto. Within iPhoto itself, the various original dates of the photos are retained. But in Finder and Bridge, copies of those same photos all carry the same (worthless) date: the date and time that they were imported from my iPhone. I can’t figure out what would have changed on my Mac to make it start re-dating my photos. I was happily dragging and dropping photos, and suddently I started to lose the original dates. Did I inadvertently change some settings? (I am running OS 10.6.8 and using iPhoto 8.)

(I use iPhoto only to import from my iPhone; I organize all my images, including thousands of RAW files, in folders on a big external drive.)
Why are you using iPhoto at all? use image capture or drag and drop the photos
The problem is that the files I am copying are getting stripped of the EXIF metadata
eliminating iPhoto from your work flow will eliminate one oppertunity to have this happen For photos in iPhoto it is best to export them rather than drag an drop them - this assures your EXIF and IPTC data is correct and uptodate
Why would I be able, over many years, to retain EXIF metadata in photos imported from an iPhone--then one day find that the same workflow strips such photos of EXIF data?
Because exporting is the supported way to "export" photos - I never drag and drop photos out of iPhoto and I never use thrid party programs on the photos in the iPhoto library - try exporting as suggested above and see if that is the solution
LN

How can I minimise data corruption?

Mac OS X is great, and one of the greatest things it has achieved is an environment so stable that it almost never crashes.
However, for me the next BIG problem with using computers is data corruption. Data corruption problems bug my life as much now as system freezes/crashes did 5 years ago.
For some reason, it often seems to be preferences files that become corrupt. I don't know why, or whether other files are becoming corrupt too and I've not discovered it yet. Sometimes I wonder whether it's just because of all the junk I install, or the length of time it's been since doing a clean format. However, with my recent purchase of a Macbook, and within a couple of months having all my preference files becoming corrupt, this goes against those theories. My macbook has minimal amounts of software installed, and is generally kept quite simple.
Obviously backing up is an important strategy, but that leads to a whole load of decisions like, how often to backup, do you keep incremental backups, do you restore absolutely everything when you discover 1 or 2 corrupt files (how do you know if others have become corrupt?).
Correct shutting down is something I always do - unless something prevents me from doing so, like power cuts. I've also often had a problem with the sccreen remaining blank after macbook has slept or had the screensaver on. On occasion I've had to hold down the power button to shut it down and get it going again.
I've looked into uninterruptible power supplies. Unfortunately, the ideal setup with additional battery to provide a few hours of power are very expensive. Also, should the macbook not be immune from problems caused by power fluctuations because of the battery? I certainly did get a system crash recently when there was a power cut - but at the time I just wondered if it was due to the wireless router going off.
.mac and idisk seem to cause their share of problems. Again, I'm not sure if these are the cause or a consequence of the problems. I have iDisk syncing switched on, and on a few occasions it's vanished and I've had to reboot to get things back to normal. Recently there have been warnings of clashes between .mac and the local idisk.
Filevault is another possible cause of problems. I've read people advising against it's use. However, if someone is willing to steal my macbook, I don't want that sort of person having access to anything, whether it's address book contacts, calendars, word documents or anything financial. OK, people suggest creating an encrypted disk image, but that doesn't solve the problem of preventing people accessing address book or ical.
What I'd really like to know is, what are the main causes of data corruption. If I can identify the causes I might be better prepared for trying to prevent it. For example, if 99% of data corruption is due to power fluctuation then I might accept that I need to spend the money on a UPS.
Once identifying the possible causes, what can be done to prevent them. Would a RAID 1 configuration protect against data corruption, or is it only good in cases of catastrophic drive failure? I've just purchased a 500GB external Firewire 800 drive, which raises the option of creating a RAID 1 with my 2 built in drives.
Sorry for so many questions, but I just really need to get this sorted. Since moving from OS 9 to OS X this has regularly been my biggest cause of troubles.

Hi, bilbo_baggins.
You wrote: "What I'd really like to know is, what are the main causes of data corruption..."You've already identified them, but you seem reluctant to implement the procedures needed to mitigate or avoid those causes that can be mitigated or avoided, in particular:• Power outages or power problems.
• Improper shutdowns.
• Hardware problems or failures, e.g. hard drive failures, bad sectors, bad RAM, etc.
• Bad programming.I can understand your position since:• Not everything one needs to run their computer comes in the box: additional money must be spent.
• The solutions often seem more complex to implement than they really are. One needs some guidance, which again it does not come in the box, and few books address preventing problems before they occur.Here's my advice:
1. Implementing a comprehensive Backup and Recovery Solution and using it regularly is essential to assure against data loss in the event of a hard drive failure or other problems. For advice on the backup and recovery solution I employ, see my "Backup and Recovery" FAQ. Using a personal computer without backup and recovery is like driving without auto insurance. Likewise, without a Backup and Recovery solution, you are accepting the risk of potentially losing all of your data at some point.
2. Perform the little bit of required, regular maintenance: see my "Maintaining Mac OS X" FAQ. It covers my advice on "regular maintenance" and dispels some common "maintenance myths."
3, If you use a desktop Mac, you need an Uninterruptible Power Supply: power outages and other power problems —surges, spikes, brownouts, etc. — can not only cause data corruption but damage your hardware. I have complete advice on selecting a UPS in the "Protecting Against Power Problems" chapter in my book. Don't simply walk into a store and by the first UPS recommended by a clerk: the UPS needs to be configured and sized to match your computer setup. You don't need hours of battery run time: 10-15 minutes is sufficient to save your work and perform a proper shutdown, or for a modern UPS to perform an automatic shutdown if your computer is running in your absence.
4. If you regularly "solve" problems by performing a hard restart (pressing and holding the power button or, on Macs so equipped, the restart button), then go back to work without first troubleshooting the cause of the problem, you risk letting a small problem compound into a larger problem. At a minimum, after a hard restart your should:• Run the the Procedure specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ.
• Then troubleshoot the cause of the problem that led to the hard restart.My book also has an entire chapter on methods for troubleshooting "Freezes and Hangs."
5. Likewise, hoping that by installing a Mac OS X Update will fix a problem, or simply reinstalling one, without first checking for other problems, can make a bad problem worse. Before installing software updates, you may wish to consider the advice in my "Installing Software Updates" FAQ. Taking the steps therein before installing an update often helps avert problems and gives you a fallback position in case trouble arises.
6. FileVault does not corrupt data, but it, like any hard drive or disk imge, doesn't respond well to the causes cited above. This is why it is essential to regularly backup your encrypted Home folder using a comprehensive Backup and Recovery solution. FileVault is an "all your eggs in one basket" solution: if bad sectors develop on the hard drive in the area occupied by your encrypted Home folder, you could lose all the data therein without a backup.
7. RAID: IMO, unless one is running a high-volume transaction server with a 99.999% ("Five Nines") availability requirement, RAID is overkill. For example, unless you're running a bank, a brokerage, or a major e-commerce site, you're probably spending sums of time and money with RAID that could be applied elsewhere.
RAID is high on the "geek chic" scale, low on the "average user" practicality scale, and high on the "complex to troubleshoot" scale when problems arise. The average user is better served by implementing a comprehensive Backup and Recovery solution and using it regularly.
8. I don't use .Mac — and hence, don't use an iDisk — so I can't advise you there. However, I suspect that if you're having problems with these, and the causes are unrelated to issues of Apple Server availability, then I'd suspect they are related to the other issues cited above.
9. You can't completely avoid problems caused by bad programming, but you can minimize the risk by not installing every bit of shareware, freeware, or beta code you read about just to "try it out." Stick to reliable, proven applications — shareware or freeware offerings that are highly rated on sites like MacUpdate and VersionTracker — as well as commercial software from major software houses. LIkewise, a Backup and Recovery solution can help here.
10. Personal computers today are not much more advanced than automobiles were in the 1920's and '30s: to drive back then, you had to be part mechanic as well as driver. Cars today still require regular maintenance. It's the same with personal computers today: you need to be prepared for troubleshooting them (mechanic) as well as using them (driver). Computer hardware can fail, just as autos can break down, usually at the worst possible moment.
People whose homes or offices have several Macs, a network, and the other peripherals normally associated with such setups — printers, scanners, etc. — are running their own data centers but don't know it. Educating yourself is helpful: my "Learning About Mac OS X" FAQ has a number of resources that you will find helpful including books, online training, and more. My book focuses exclusively on troubleshooting, with a heavy emphasis on preventing problems before they occur and being prepared for them should they arise.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Corrupt Library6.iphoto - empty albums

Hello, guys, hope someone out there is smarter than I (and smarter than "I-Photo").
I have a corrupt library6.iphoto here. About 100 of my albums show zero pictures (only one is populated). But all 40Gb of photos are still intact in the 'Original' and 'Modified' folders. I believe the problem is a corrupt slideshow I just created. I think that because when I try to click that slideshow, iPhoto quits abruptly (i.e. no obvious way to delete it).
I read this thread (and many similar) http://discussions.apple.com/thread.jspa?messageID=9861491&#9861491
and the three options described there will cause a lot of work:
Option 1. "Back-Up": My latest backup is about 15Gb ago (yes, that's a human error), and I've modified a lot of pictures since then, so I estimate I would lose about 20 to 30 hours of work.
Option 2. "Rebuild": I'm in the process of rebuilding another 40Gb Library, but I guess it won't work since the corrupt Library6 file is a fraction of the size of my last backed up library6 file.
Option 3. "Re-Populate": Not all the Rolls correspond to Albums, so there isn't an easy way to re-create my albums (another, 5 to 10 hours of work).
My questions:
A) Since I see the empty Album-structure intact in the corrupt library, is it possible that the album-data is still stored somewhere (despite the fact that the Library6 file is a fraction of what it was)?
B) Is it possible to rebuild the libraries using all available photos in the Pictures folder? (i.e. using both folders 'Modified' and 'Originals'?)
C) Is it possible to kick that slideshow out of the database, thereby leaving the empty Album-structure for me to re-populate?
A thousand thanks to anyone who can help.
-Stuart

Stuart
That library6.iphoto file is toast. There is no going back to it. Even if you could “repopulate” it somehow, you would be bringing data into an entity known to unstable - nothing too wise there
As you don’t have an up-to-date- back up your choices are two:
The first attempts to leverage the data about your albums mentioned here:
A) Since I see the empty Album-structure intact in the corrupt library, is it possible that the album-data is still stored somewhere (despite the fact that the Library6 file is a fraction of what it was)?
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
or
Rebuild from Scratch.
B) Is it possible to rebuild the libraries using all available photos in the Pictures folder? (i.e. using both folders 'Modified' and 'Originals'?)
Yes, simply import the photos from both Folders. But you will have massive duplication as each will be treated as a new photo in itself. If you don’t have a working back up and/or if rebuilding with iPhoto Library Manager fails there is +no way+ to re-construct the relationship between the Original and Modified versions.
C) Is it possible to kick that slideshow out of the database, thereby leaving the empty Album-structure for me to re-populate?
No.
To create and populate a new *iPhoto 6* library:
Note this will give you a working library with the same Rolls and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
Move the iPhoto Library to the desktop
Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
Go into the iPhoto Library on your desktop and find the Originals folder. From the Originals folder drag the individual Roll Folders to the iPhoto Window and it will recreate them in the new library.
When you're sure all is well you can delete the iPhoto Library on your desktop.
In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
Regards
TD

Data corrupt block

os Sun 5.10 oracle version 10.2.0.2 RAC 2 node
alert.log 내용
Hex dump of (file 206, block 393208) in trace file /oracle/app/oracle/admin/DBPGIC/udump/dbpgic1_ora_1424.trc
Corrupt block relative dba: 0x3385fff8 (file 206, block 393208)
Bad header found during backing up datafile
Data in bad block:
type: 32 format: 0 rdba: 0x00000001
last change scn: 0x0000.98b00394 seq: 0x0 flg: 0x00
spare1: 0x1 spare2: 0x27 spare3: 0x2
consistency value in tail: 0x00000001
check value in block header: 0x0
block checksum disabled
Reread of blocknum=393208, file=/dev/md/vg_rac06/rdsk/d119. found same corrupt data
Reread of blocknum=393208, file=/dev/md/vg_rac06/rdsk/d119. found same corrupt data
Reread of blocknum=393208, file=/dev/md/vg_rac06/rdsk/d119. found same corrupt data
Reread of blocknum=393208, file=/dev/md/vg_rac06/rdsk/d119. found same corrupt data
Reread of blocknum=393208, file=/dev/md/vg_rac06/rdsk/d119. found same corrupt data
corrupt 발생한 Block id 를 검색해 보면 Block id 가 검색이 안됩니다.
dba_extents 로 검색
corrupt 때문에 Block id 가 검색이 안되는 것인지 궁금합니다.
export 받으면 데이타는 정상적으로 export 가능.

다행이네요. block corruption 이 발생한 곳이 데이터가 저장된 블록이
아닌 것 같습니다. 그것도 rman백업을 통해서 발견한 것 같는데
맞는지요?
scn이 scn: 0x0000.00000000 가 아닌
0x0000.98b00394 인 것으로 봐서는 physical corrupt 가 아닌
soft corrupt인 것 같습니다.
그렇다면 버그일 가능성이 높아서 찾아보니
Bug 4411228 - Block corruption with mixture of file system and RAW files
의 버그가 발견되었습니다. 이것이 아닐 수도 있지만..
이러한 block corruption에 대한 처리방법 및 원인분석은
오라클(주)를 통해서 정식으로 요청하셔야 합니다.
metalink를 통해서 SR 요청을 하십시오.
export는 high water mark 이후의 block corruption을 찾아내지 못하고 이외에도
아래 몇가지 경우에서도 찾아내지 못합니다.
db verify( dbv)의 경우에는 physical corruption은 찾아내지 못하고
soft block corruption만 찾아낼 수 있습니다.
경험상 physical corruption 이 발생하였으나 /dev/null로
datafile copy가 안되는데도 dbv로는 이 문제를 찾아내지
못하였습니다.
그렇다면 가장 좋은 방법은 rman 입니다. rman은 high water mark까지의
데이터를 백업해주면서 전체 데이터파일에 대한 체크를 하기도 합니다.
physical corruption뿐만 아니라 logical corruption도 체크를
하니 점검하기로는 rman이 가장 좋은 방법이라 생각합니다.
The Export Utility
# Use a full export to check database consistency
# Export performs a full scan for all tables
# Export only reads:
- User data below the high-water mark
- Parts of the data dictionary, while looking up information concerning the objects being exported
# Export does not detect the following:
- Disk corruptions above the high-water mark
- Index corruptions
- Free or temporary extent corruptions
- Column data corruption (like invalid date values)
block corruption을 정상적으로 복구하는 방법은 restore 후에
복구하는 방법이 있겠으나 이미 restore할 백업이 block corruption이
발생했을 수도 있습니다. 그러므로 다른 서버에 restore해보고
정상적인 datafile인 것을 확인 후에 실환경에 restore하는 것이 좋습니다.
만약 백업본까지 block corruption이 발생하였거나 또는 시간적 여유가
없을 경우에는 table을 move tablespace 또는 index rebuild를 통해서
다른 테이블스페이스로 데이터를 옮겨두고 문제가 발생한 테이블스페이스를
drop해버리고 재생성 하는 것이 좋을 것 같습니다.(지금 현재 데이터의
손실은 없으니 move tablespace, rebuild index 방법이 좋겠습니다.
Handling Corruptions
Check the alert file and system log file
Use diagnostic tools to determine the type of corruption
Dump blocks to find out what is wrong
Determine whether the error persists by running checks multiple times
Recover data from the corrupted object if necessary
Preferred resolution method: media recovery
Handling Corruptions
Always try to find out if the error is permanent. Run the analyze command multiple times or, if possible, perform a shutdown and a startup and try again to perform the operation that failed earlier.
Find out whether there are more corruptions. If you encounter one, there may be other corrupted blocks, as well. Use tools like DBVERIFY for this.
Before you try to salvage the data, perform a block dump as evidence to identify the actual cause of the corruption.
Make a hex dump of the bad block, using UNIX dd and od -x.
Consider performing a redo log dump to check all the changes that were made to the block so that you can discover when the corruption occurred.
Note: Remember that when you have a block corruption, performing media recovery is the recommended process after the hardware is verified.
Resolve any hardware issues:
- Memory boards
- Disk controllers
- Disks
Recover or restore data from the corrupt object if necessary
Handling Corruptions (continued)
There is no point in continuing to work if there are hardware failures. When you encounter hardware problems, the vendor should be contacted and the machine should be checked and fixed before continuing. A full hardware diagnostics should be run.
Many types of hardware failures are possible:
Bad I/O hardware or firmware
Operating system I/O or caching problem
Memory or paging problems
Disk repair utilities
아래 관련 자료를 드립니다.
All About Data Blocks Corruption in Oracle
Vijaya R. Dumpa
Data Block Overview:
Oracle allocates logical database space for all data in a database. The units of database space allocation are data blocks (also called logical blocks, Oracle blocks, or pages), extents, and segments. The next level of logical database space is an extent. An extent is a specific number of contiguous data blocks allocated for storing a specific type of information. The level of logical database storage above an extent is called a segment. The high water mark is the boundary between used and unused space in a segment.
The header contains general block information, such as the block address and the type of segment (for example, data, index, or rollback).
Table Directory, this portion of the data block contains information about the table having rows in this block.
Row Directory, this portion of the data block contains information about the actual rows in the block (including addresses for each row piece in the row data area).
Free space is allocated for insertion of new rows and for updates to rows that require additional space.
Row data, this portion of the data block contains rows in this block.
Analyze the Table structure to identify block corruption:
By analyzing the table structure and its associated objects, you can perform a detailed check of data blocks to identify block corruption:
SQL> analyze table_name/index_name/cluster_name ... validate structure cascade;
Detecting data block corruption using the DBVERIFY Utility:
DBVERIFY is an external command-line utility that performs a physical data structure integrity check on an offline database. It can be used against backup files and online files. Integrity checks are significantly faster if you run against an offline database.
Restrictions:
DBVERIFY checks are limited to cache-managed blocks. It’s only for use with datafiles, it will not work against control files or redo logs.
The following example is sample output of verification for the data file system_ts_01.dbf. And its Start block is 9 and end block is 25. Blocksize parameter is required only if the file to be verified has a non-2kb block size. Logfile parameter specifies the file to which logging information should be written. The feedback parameter has been given the value 2 to display one dot on the screen for every 2 blocks processed.
$ dbv file=system_ts_01.dbf start=9 end=25 blocksize=16384 logfile=dbvsys_ts.log feedback=2
DBVERIFY: Release 8.1.7.3.0 - Production on Fri Sep 13 14:11:52 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Output:
$ pg dbvsys_ts.log
DBVERIFY: Release 8.1.7.3.0 - Production on Fri Sep 13 14:11:52 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = system_ts_01.dbf
DBVERIFY - Verification complete
Total Pages Examined : 17
Total Pages Processed (Data) : 10
Total Pages Failing (Data) : 0
Total Pages Processed (Index) : 2
Total Pages Failing (Index) : 0
Total Pages Processed (Other) : 5
Total Pages Empty : 0
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Detecting and reporting data block corruption using the DBMS_REPAIR package:
Note: Note that this event can only be used if the block "wrapper" is marked corrupt.
Eg: If the block reports ORA-1578.
1. Create DBMS_REPAIR administration tables:
To Create Repair tables, run the below package.
SQL> EXEC DBMS_REPAIR.ADMIN_TABLES(‘REPAIR_ADMIN’, 1,1, ‘REPAIR_TS’);
Note that table names prefix with ‘REPAIR_’ or ‘ORPAN_’. If the second variable is 1, it will create ‘REAIR_key tables, if it is 2, then it will create ‘ORPAN_key tables.
If the thread variable is
1 then package performs ‘create’ operations.
2 then package performs ‘delete’ operations.
3 then package performs ‘drop’ operations.
2. Scanning a specific table or Index using the DBMS_REPAIR.CHECK_OBJECT procedure:
In the following example we check the table employee for possible corruption’s that belongs to the schema TEST. Let’s assume that we have created our administration tables called REPAIR_ADMIN in schema SYS.
To check the table block corruption use the following procedure:
SQL> VARIABLE A NUMBER;
SQL> EXEC DBMS_REPAIR.CHECK_OBJECT (‘TEST’,’EMP’, NULL,
1,’REPAIR_ADMIN’, NULL, NULL, NULL, NULL,:A);
SQL> PRINT A;
To check which block is corrupted, check in the REPAIR_ADMIN table.
SQL> SELECT * FROM REPAIR_ADMIN;
3. Fixing corrupt block using the DBMS_REPAIR.FIX_CORRUPT_BLOCK procedure:
SQL> VARIABLE A NUMBER;
SQL> EXEC DBMS_REPAIR.FIX.CORRUPT_BLOCKS (‘TEST’,’EMP’, NULL,
1,’REPARI_ADMIN’, NULL,:A);
SQL> SELECT MARKED FROM REPAIR_ADMIN;
If u select the EMP table now you still get the error ORA-1578.
4. Skipping corrupt blocks using the DBMS_REPAIR. SKIP_CORRUPT_BLOCK procedure:
SQL> EXEC DBMS_REPAIR. SKIP_CORRUPT.BLOCKS (‘TEST’, ‘EMP’, 1,1);
Notice the verification of running the DBMS_REPAIR tool. You have lost some of data. One main advantage of this tool is that you can retrieve the data past the corrupted block. However we have lost some data in the table.
5. This procedure is useful in identifying orphan keys in indexes that are pointing to corrupt rows of the table:
SQL> EXEC DBMS_REPAIR. DUMP ORPHAN_KEYS (‘TEST’,’IDX_EMP’, NULL,
2, ‘REPAIR_ADMIN’, ‘ORPHAN_ADMIN’, NULL,:A);
If u see any records in ORPHAN_ADMIN table you have to drop and re-create the index to avoid any inconsistencies in your queries.
6. The last thing you need to do while using the DBMS_REPAIR package is to run the DBMS_REPAIR.REBUILD_FREELISTS procedure to reinitialize the free list details in the data dictionary views.
SQL> EXEC DBMS_REPAIR.REBUILD_FREELISTS (‘TEST’,’EMP’, NULL, 1);
NOTE
Setting events 10210, 10211, 10212, and 10225 can be done by adding the following line for each event in the init.ora file:
Event = "event_number trace name errorstack forever, level 10"
When event 10210 is set, the data blocks are checked for corruption by checking their integrity. Data blocks that don't match the format are marked as soft corrupt.
When event 10211 is set, the index blocks are checked for corruption by checking their integrity. Index blocks that don't match the format are marked as soft corrupt.
When event 10212 is set, the cluster blocks are checked for corruption by checking their integrity. Cluster blocks that don't match the format are marked as soft corrupt.
When event 10225 is set, the fet$ and uset$ dictionary tables are checked for corruption by checking their integrity. Blocks that don't match the format are marked as soft corrupt.
Set event 10231 in the init.ora file to cause Oracle to skip software- and media-corrupted blocks when performing full table scans:
Event="10231 trace name context forever, level 10"
Set event 10233 in the init.ora file to cause Oracle to skip software- and media-corrupted blocks when performing index range scans:
Event="10233 trace name context forever, level 10"
To dump the Oracle block you can use below command from 8.x on words:
SQL> ALTER SYSTEM DUMP DATAFILE 11 block 9;
This command dumps datablock 9 in datafile11, into USER_DUMP_DEST directory.
Dumping Redo Logs file blocks:
SQL> ALTER SYSTEM DUMP LOGFILE ‘/usr/oracle8/product/admin/udump/rl. log’;
Rollback segments block corruption, it will cause problems (ORA-1578) while starting up the database.
With support of oracle, can use below under source parameter to startup the database.
CORRUPTEDROLLBACK_SEGMENTS=(RBS_1, RBS_2)
DB_BLOCK_COMPUTE_CHECKSUM
This parameter is normally used to debug corruption’s that happen on disk.
The following V$ views contain information about blocks marked logically corrupt:
V$ BACKUP_CORRUPTION, V$COPY_CORRUPTION
When this parameter is set, while reading a block from disk to catch, oracle will compute the checksum again and compares it with the value that is in the block.
If they differ, it indicates that the block is corrupted on disk. Oracle makes the block as corrupt and signals an error. There is an overhead involved in setting this parameter.
DB_BLOCK_CACHE_PROTECT=‘TRUE’
Oracle will catch stray writes made by processes in the buffer catch.
Oracle 9i new RMAN futures:
Obtain the datafile numbers and block numbers for the corrupted blocks. Typically, you obtain this output from the standard output, the alert.log, trace files, or a media management interface. For example, you may see the following in a trace file:
ORA-01578: ORACLE data block corrupted (file # 9, block # 13)
ORA-01110: data file 9: '/oracle/dbs/tbs_91.f'
ORA-01578: ORACLE data block corrupted (file # 2, block # 19)
ORA-01110: data file 2: '/oracle/dbs/tbs_21.f'
$rman target =rman/rman@rmanprod
RMAN> run {
2> allocate channel ch1 type disk;
3> blockrecover datafile 9 block 13 datafile 2 block 19;
4> }
Recovering Data blocks Using Selected Backups:
# restore from backupset
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 19 FROM BACKUPSET;
# restore from datafile image copy
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 19 FROM DATAFILECOPY;
# restore from backupset with tag "mondayAM"
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 199 FROM TAG = mondayAM;
# restore using backups made before one week ago
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 19 RESTORE
UNTIL 'SYSDATE-7';
# restore using backups made before SCN 100
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 19 RESTORE UNTIL SCN 100;
# restore using backups made before log sequence 7024
BLOCKRECOVER DATAFILE 9 BLOCK 13 DATAFILE 2 BLOCK 19 RESTORE
UNTIL SEQUENCE 7024;
글 수정:
Min Angel (Yeon Hong Min, Korean)

Data corruption with SSD after hard reset

Hi, I'm using a Mac Mini for a car product and I MUST shut it down each time the hard way, i.e. by cutting the power.
I am perfectly aware that this is definitely NOT the recommended way to shut down OSX because it might lead to data corruption but at the moment there are NO other options. So please don't simply suggest to shut it down the "good way", i.e. via software, because it simply isn't an option.
Now, in the past I did lots of ON/OFF tests with conventional drives and had no problems. Recently I moved to SSD drives and it looks like I get more frequent boot problems (apple logo with the wheel spinning forever). Using DiskWarrior in these cases fixes the problem and repairs the folder structure of the drive. After that the drive boots again.
Given the constraints for the application, i.e. shutdown==powercut, is there any way I can ensure better data integrity? If I disable write caching would that help? Any other trick I could do to make the system more resilient? And finally, are actually SSD more prone to crashes of this kind or was that just a coincidence?
Thanks a lot for the help, I hope some of you has experienced this problem in a similar situation (and found a good solution)
cheers
Emanuele

There are OSX compatible UPSs that send status information to the computer via USB. This enables the computer to do a normal shutdown before the UPS battery runs out. Here's an example of the system preference that will show when a compatible UPS is connected:
<http://www.cyberpowersystems.com/support/faqs/faqOSXUPS.html>
Do you think disabling write caching would help at all?
It might, but the problem may be entirely in the SSD. Do you have journaling enabled on the SSD? That could make a big difference.
Finally, I'm using OCZ Solid 2. Do you have any comment on that or do you recommend something different? I doubt that SLC drives would help in this matter.
You would have to contact the SSD makers and ask them how well they handle power failures. It should be possible to make them no worse than a normal hard drive, but there may be some compromises they have to make for performance reasons.

Photo corruption post iPhoto 6.0.5 update

Recently downloaded iPhoto 6.0.5 update via software update and multiple photos in the library appear to be corrupted or have a portion missing. Some but not all of these photos have been modified and appear fine in the "Original" folder and in their thumbnail view but appear corrupted in the full screen view. By corrupted, I mean that a portion of the photo from the top down to a certain point appears as it should and then objects in the photo are shifted, color distorted, and sometimes overwritten with colorful vertical bands from that point down. In slideshow view, these pictures are all black. I have backup copies of the originals but can't work on any of the current projects without encountering these problems.
Is it possible to remove the 6.0.5 update if it is, indeed, the cause? Thanks
mac mini (Intel 1.66 GHz Core Duo) Mac OS X (10.4.7) Base model: 1.66 Intel Core Duo, 512 Ram, Combo Drive, 60 GB HD - external FW HD, recent software update to OSX 10.2.8, iphoto 6.0.5

I tried the instructions to rebuild the iPhoto library. Not knowing exactly what the problem was, I checked all the boxes to rebuild all thumbnails, find orphans, etc. The process executed in less than 10 seconds. Now, iPhoto only shows 6 photos in my library (there were several hundred before). One has the colors all messed up in certain parts of the photo, one is about 3/4 of the picture and the bottom 1/4 is blank, one only appears as a grey, dashed outline, and 3 appear as they should until I try to view them full screen and I get an infinite rolling beach ball.
To answer your question, TD, when using Finder to navigate to my iPhoto library and opening jpgs from the "Modified" folder, the files appear incomplete. Some are normal and continuous from the top down to a certain point - a different point in each file - where they go blank from there down. Others appear completely black in Preview. Still others appear completely normal, as they should. Even the jpgs that show as normal in Preview, however, no longer appear in my library when I open iPhoto.
The beach ball started rolling before I started this post. Its still rolling...
mac mini (Intel 1.66 GHz Core Duo) Mac OS X (10.4.7) Base model: 1.66 Intel Core Duo, 512 Ram, Combo Drive, 60 GB HD - external FW HD, recent software update to OSX 10.2.8, iphoto 6.0.5

New to iPhoto: Database Corruption and iPhoto Package

Coming from the PC I'm used to individual files with Picasa and Photoshop and I'm confused about a few things:
1. Is the iPhoto database separate from the iPhoto package file that stores all of the images?
2. And if you were to lose your database because of corruption, do you lose all of your individual photos?
3. Or if the package somehow became corrupted, do you lose your original images?
4. Slightly off-topic -- does Aperture store the images separately or does it use the same "database package" concept as iPhoto?

1. Is the iPhoto database separate from the iPhoto package file that stores all of the images?
Yes and No. It depends on the settings you choose. In the default setting both the photos and the database are contained within the Library Package. For more see below*.
A Package File is simply a folder that looks like a file in the Finder. The change was made to the format of the iPhoto library because many users were inadvertently corrupting their library by browsing through it with other software or making changes in it themselves.
Want to see inside? Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Standard Warning: Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
2. And if you were to lose your database because of corruption, do you lose all of your individual photos?
No. The db is a couple of files inside the Library. The photos are at no more risk that when a file goes bad in any folder.
3. Or if the package somehow became corrupted, do you lose your original images?
There's no way for a package to become corrupted. Like I say, it's just a folder.
Of course, the protection for any data on your computer is a good up-to-date back up.
4. Slightly off-topic -- does Aperture store the images separately or does it use the same "database package" concept as iPhoto?
Yes and no. Depends on the settings you choose.
* And this is the below piece to see:
There are two kinds of Library: Managed and Referenced.
A +Managed library+, is the default setting, and iPhoto copies files into the iPhoto Library when Importing. In this scenario iPhoto is responsible for File Management.
A +Referenced Library+ is when iPhoto is NOT copying the files into the iPhoto Library when importing because you made a change at iPhoto -> Preferences -> Advanced. In this scenario you are responsible for the File Management.
*How to do it:*
Simply go to iPhoto Menu -> Preferences -> Advanced and uncheck 'Copy Files to the iPhoto Library on Import'.
*What Happens:*
Now iPhoto will not copy the files, but rather simply reference them on your HD. To do this it will create an alias in the Originals Folder that points to your file. It will still create a thumbnail and, if you modify the pics, a Modified version within the iPhoto Library Folder.
*Some things to consider:*
1. Importing and deleting pics are more complex procedures. You have to to put the files where they will be stored before importing them. When you delete them you'll need to remove the files from the HD yourself.
2. You cannot move or rename the files on your system or iPhoto will lose track of them on systems prior to 10.5 and iPhoto 08. Even with the later versions issues can still arise if you move the referenced files to new volumes or between volumes.
3. Most importantly, migrating to a new disk or computer can be much more complex.
4. Because iPhoto has no tools for managing Referenced Files, if, for some reason, the path to the photos changes then you could find yourself resolving aliases for +each photo in the Library+ one by one.
My own opinion:
I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organiser
If disk space is an issue, you can run an entire iPhoto Library from an external disk:
1. Quit iPhoto
2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
If you're concerned about accessing the files, There are many, many ways to access your files in iPhoto:
You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Command-Click for selecting multiple pics.
Uploaded with plasq's Skitch!
You can access the Library from the New Message Window in Mail:
Uploaded with plasq's Skitch!
Many internet sites such as Flickr and SmugMug have plug-ins for accessing the iPhoto Library.
If you're using Gmail you can use iPhoto2GMail
If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
*If you want to access the files with iPhoto not running*:
For users of 10.6 and later:
You can download a free Services component from MacOSXAutomation which will give you access to the iPhoto Library from your Services Menu. Using the Services Preference Pane you can even create a keyboard shortcut for it.
Other options include:
1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
*Using iPhoto with Photoshop*
You can set Photoshop (or any image editor) as an external editor in iPhoto. (Preferences -> General -> Edit Photo: Choose from the Drop Down Menu.) This way, when you double click a pic to edit in iPhoto it will open automatically in Photoshop or your Image Editor, and when you save it it's sent back to iPhoto automatically. This is the only way that edits made in another application will be displayed in iPhoto.
Note that iPhoto sends a copy+ of the file to Photoshop, so when you save be sure to use the Save command, not Save As... If you use Save As then you're creating a new file and iPhoto has no way of knowing about this new file. iPhoto is preserving your original anyway.
Aperture - which is somewhat more expensive that iPhoto - has much better tools for running Referenced Libraries. I have no reservations about running Aperture in that mode.
Regards
TD

Avoid multiple start of VM on different servers ? (data corruption)

Hello,
we are using OracleVM without manager.
Setup: 2 servers connected to one SAN device. The SAN device is connected with 2 FC links, handles by device mapper multipath. The file system /OVS is located on OCFS2 filesystem which is located in SAN. Both nodes have /OVS mounted to make live migration possible.
When testing this setup, we found that it is possible to start VM1 on both servers at the same time. This IS GOING TO lead to data corruption for sure.
Is there a way to avoid that is is possible to start the same VM on multiple servers at the same time ? Any hints ?
Regards,
Robert

I was investigating this issue some more and found the very useful DLMFS coming with OCFS2 (see http://oss.oracle.com/projects/ocfs2/src/branches/ocfs2-1.2/dlmfs.txt)
I played around with it and found the following:
1) The O_NONBLOCK operating mentioned is not working (open always fails)
2) Locks are cleared if a machine leaves the cluster (disconnected or failes)
3) open call waits until a log is cleared
So I was thinking about the following solution:
Write a wrapper for "xm" that calls "xm.orig". This wrapper creates a daemon process along with the virtual machine that holds a lock file /dlm/xen/MachineName open as long as the machine is running. When you shutdown the virtual machine, this daemon is ending and the lock is released now the machine can be started on a another machine and this machine is locking again.
The problem is a crashing machine. If a machine crashes, the lock is not cleared because the deamon is still running.
Is there a way to get notified of a crashing machine in OracleVM or is there some way to "hook" into the "oncrash" routines of Xen ?

How is the Raw data used in iPhoto. I currently shoot both jpeg and raw and import them both into iPhoto.

How is the Raw data used in iPhoto? I currently shoot both jpeg and raw and import them both into iPhoto. What do I gain by collecting Raw data?
Thanks

You get more parameters for making adjustments to the image. This is not really an iPhoto question but more a general photography one. In rather simple terms here's how a digital camera works:
You expose an image. A lot of data is gathered in by the sensor. But it's just a bug lump of data and not very useful in that form.
In cameras that shoot jpeg that mass of data is interpreted/processed into an actual image, and the image is stored in a jpeg file. (that's a process broadly analogous to developing a film). The decisions that go into making that interpretation are all made by an engineer somewhere, back when the camera was developed.
If you shoot Raw, then what you do is take that mass of data, and rather than working to the decisions made by that engineer, you develop the shot - you run the digital darkroom.
Why would you do this? Take on all this extra work? Well one of three reasons: a: you think you can do a better job than that engineer. b: you just prefer the result you get when you develop yourself or c: you're a hopeless shooter and raw means you have more options to fix the mistakes you made in the camera. (That's why I do it.)
Here endeth the two dollar tour. So, basically, if you're happy with what your camera produces in Jpeg then there's really no need to shoot Raw.
There's no need at all to shoot Raw+Jpeg as iPhoto creates a jpeg preview when you import, so you're just wasting space.

? Corrupted Library6.iPhoto file?

I updated iPhoto to 7.1.2 a few days ago. On opening iPhoto the next AM I noticed that all my pictures from summer 2006 to present are missing when running iPhoto; those before summer 2006 remain. It was a few days since I had looked at pictures before the upgrade. Fortunately, all my pictures appear to be in the correct place and are viewable with Preview when I click on the photo file (user/Pictures/iPhoto Library/) on the internal hard drive. Whew!
I've reviewed the forum for the last 2 hours and assume that I have a corrupted database file. Not sure if it is the Library6.iPhoto file or albumData.xml file. I have tried copying both of these from my SuperSuper backup volume (done last Sunday evening automatically before I knew I had a problem) on my external hard drive without correction of the problem. Should I also try to copy over the Library.iPhoto file? I didn't see this recommended elsewhere.
Prior posts recommended copying over the Library6.iPhoto file if a backup was available, and if no improvement, to rebuild the library using iPhoto Library Manager. Before jumping into this, I want to make sure that is what others would recommend. I've got the program downloaded and see the command to rebuild. It will save the new library as "rebuilt library" in the pictures folder. Is this my best action?
If I rebuild, shouId I then throw away my old "iPhoto Library", then change the name of the rebuilt library to "iPhoto Library"?
What are the ramifications of rebuilding the library? Although I have a lot of albums, I only have a couple slideshows, only 1 web gallery item, and no cards. I assume I'll have to rename events; no big deal.
I am a little surprised rebuilding the library is not built into iPhoto somewhere. Good thing someone wrote a program.
Given this corrupted file, should I be checking my drive for other problems? Permissions are correct and the disk verified fine with disk utility.
Thanks,
Justin

jcgraff
Try these in order - from best option on down...
1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
2. Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums back.
3. If neither of these work then you'll need to create and populate a new library.
To create and populate a new library:
Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
Move the iPhoto Library to the desktop
Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
When you're sure all is well you can delete the iPhoto Library on your desktop.
In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.
Regards
TD

SATA - Registry and data corruption

Hey guys... I thought I'd pass these on, because the information contained therein is very solid, if not somewhat incomplete.
Summary of the issue:
Users are experiencing random data corruption or outright registry errors when the computer is powered on. These errors are not happening with reboots, only with cold starts.
The problem? It appears that Windows is shutting down too quickly. With the registry being the last thing to get written to, a shut-down midway through can be devastating. There are also indications that drives with 8mb buffers are being negatively effected by 48-bit LBA.
The cuplrit? The VIA SATA Driver, and possibly one of the Windows Service Packs... I would read though these two threads and see if they help. I'm still sketchy on solutions (the second thread is mainly WinXP oriented, and I run Win2K), but at least I now know what is happening and that a solution MAY pop up... A solution other than buying a seperate SATA controller with a different chipset.
http://forums.viaarena.com/messageview.cfm?catid=20&threadid=47963
http://forums.pcper.com/showindex.php?s=890ec3c36a77b696a1ab7bedc364cce0&threadid=268684&perpage=15&pagenumber=1

I had this board before I RMA-ed it because it was in my opinion just plain "flaky"! I understand that the majority of the "issues" with this board are #1 PSU and #2 Memory...However, quite frankly MSI should be "up front" on the box and in advertising what the recommended PSU minimum requirements are for this board and they should ensure that retailers and OEM builders like Alienware and Cybertron that build custom AMD-64 systems that utilize this board are completely cognizant of the PSU requirements and recommended power supply vendors. In the same fashion as they do when for recommended memory modules that have been tested with this board.
"Frysign" the originator of this thread was simply posting some information about SATA corruption that he felt was important to get out and I Thank him for that information. After all isn't this the purpose of this forum to share information to try and enlighten and Help each other ?
I hope so ! The follow on threads to Frysign's post seemed less interested in learning something about possible reasons for SATA drive corruption and more interested in cutting him off with the instinctual reply that "it's your power supply dude".
The wealth of information that exists by the users of this board deserves better
Cheers
Saphire

Date Corruption in iPhoto 9, other bugs (possibly from migration?)

Similar Messages

Maybe you are looking for