Data-corrupting JPEG bug introduced in Lr 3.4, CR 6.4

FYI in case you are unaware.....
I noticed this on the Rob Galbraith web-site ( http://www.robgalbraith.com/bins/content_page.asp?cid=7-11532-11591 ) which is reporting LR 3.4 & CR 6.4 corruption of JPEG metadata in certain (rare) situations.....
"To be susceptible to this problem, the JPEG must contain "an unusually large block of private camera data," says Tom Hogarty, product manager for Lightroom. So far, Adobe has found only one camera that creates a JPEG that can trigger the bug: the HP Photosmart R607.
Hogarty nevertheless suggests that anyone using the affected software to update the metadata in JPEGs to stop doing so until a fix is available. He indicates that will come in Lightroom 3.4.1 and Camera Raw 6.4.1, which Adobe intends to make available by May 27.
More information is a Lightroom Journal post."

As for the preference file, will I lose anything by letting LR rebuild it? Do I just need to jot down my main preferences or also the view options to recreate it?
Thank you both for your help
It affects the general preferences (not the presets, not the catalog settings), and I believe also the view options, but I'm not sure about that.
Beat

Similar Messages

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.

Getting JPEG Library Error for Corrupt JPEG Data using CS5

After recently upgrading to CS5 I am getting JPEG Library Errors for corrupt JPEG data. I have my old PC still in use that uses CS4 and does not generate these errors when accessing the same site. Could someone please assist me in how to get rid of these errors using CS5? I can't find help out there anywhere for this!
Thanks in advance!

You could use Photoshop's Image Processor to open all of your jpegs in a given folder, make a slight tweek and resave them in the hopes of cleaning out any errors that DW is hitting. It's worth a shot maybe.
1. In PS go to File > Scripts > Image Processor
2. For Step 1, browse to a folder in your site with jpeg issues
3. For Step 2, choose save in same location
4. For Step 3, choose Save as JPEG and check Convert File to sRGB
5. Click Run
This will create a sub folder called JPEG with the images resaved there. You can drag them into the parent folder to replace the originals.
If you haven't already, make sure to report the bug here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
At least the right people will be made aware of it then and if it's common enough to trip whatever quantity/user reports system they use, it would get included for repair.
I honestly don't think it's a "bug" per se, since the forum isn't absolutely flooded with the problem.

[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.

Corrupt JPEG Data

Whenever I open the Assets tab in Dreamweaver 8 (am using XP
Pro), I get a one-after-the-other series of the error message:
Corrupt JPEG data: 11 extraneous bytes before marker 0xdb . The
number of extraneous bytes varies (58, 4, etc) and so does the 0x
number (0xd9, 0xc4, etc.)
I don't know which jpg files are causing the problem and
there are hundreds of them listed within Dreamweaver Assets.
How can I determine which jpeg files are corrupt?

> Why does Dreamweaver bother with this error message
about "corrupt jpeg
> data:
> premature end of data segment" if the image, created in
Photoshop, works
> fine
> on the web page, and in any other software??
Most likely because the image has a corrupted data segment
that your limited
test of software chooses to ignore?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"RichR49" <[email protected]> wrote in
message
news:ghr65t$6ep$[email protected]..
> Why does Dreamweaver bother with this error message
about "corrupt jpeg
> data:
> premature end of data segment" if the image, created in
Photoshop, works
> fine
> on the web page, and in any other software?? Since
Adobe/Macromedia hard
> coded
> this error message into Dreamweaver, they should be able
to disable it in
> a
> patch. I would like to see a complete list of
Dreamweaver error messages
> along
> with a solution to fix the problem, in the back of the
manual that comes
> with
> the software. It is currently not documented anywhere.
>

Corrupt JPEG data: 1 extraneous bytes before marker 0xd9

Hello,
Every time when I run the programming with icon and string JList, it shows the following message:
Corrupt JPEG data: 1 extraneous bytes before marker 0xd9
Does any body have any ideas to solve the above problem?
Thank you in advance.
Daniel

Have you tried using an uncorrupted JPEG image?

Library error:corrupt JPEG data:2699 extraneous bytes before marker 0xe2

How can I fix this library error: corrupt JPEG data:2699 extraneous bytes before marker 0xe2
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div id="head-nav">
        <ul>
          <li><a href="../about/contactus.html"> Contact us</a></li>
          <span class="spacer">|</span>
          <li><a href="../news/news.html">News</a></li>
          <span class="spacer">|</span>
          <li><a href="../events/events.html" target="_new">Events</a></li>
          <span class="spacer">|</span>
          <li><a href="../hr/index.html">Careers</a></li>
          <span class="spacer">|</span>
          <li><a href="../volunteer/index.html">Volunteer</a></li>
        </ul>
        <form action="http://www.bancroftneurohealth.org/search.html" id="cse-search-box">
          <div class="search">
            <input type="hidden" name="cx" value="008757697627747439989:fqakzcjmvkq" />
            <input type="hidden" name="cof" value="FORID:9" />
            <input type="hidden" name="ie" value="UTF-8" />
            <input type="text" name="q" size="31" />
            <input type="submit" name="sa" value="Search" />
          </div>
        </form>
        <script type="text/javascript" src="http://www.google.com/cse/brand?form=cse-search-box&lang=en"></script>
      </div>

I think the error is with the marker within the search box. I did not create the search box but need to update the nav list within the div where the search box resides. Anyone have experience with the google cse-search box below?
"cse-search-box">
          <div class="search">
            <input type="hidden" name="cx" value="008757697627747439989:fqakzcjmvkq" />
            <input type="hidden" name="cof" value="FORID:9" />
            <input type="hidden" name="ie" value="UTF-8" />
            <input type="text" name="q" size="31" />
            <input type="submit" name="sa" value="Search" />
          </div>
        </form>
        <script type="text/javascript" src="http://www.google.com/cse/brand?form=cse-search-box&lang=en"></script>
      </div>
    I think the marker within the search box is causing the error. I did not create this search box but need to update the navigation
div which contains this search box.

Corrupt JPEG data causing shutdown issues

I've found the following log entries in system.log, as I am having a problem with shutting down my applications.
System Preferences[266]: Corrupt JPEG data: premature end of data segment
Dec 1 15:22:42 system-name [0x0-0x25025].com.apple.systempreferences[266]: Mon Dec 1 15:22:42 system-name.local System Preferences[266] <Error>: Corrupt JPEG data: premature end of data segment\n
I think it might be related to corrupted wallpaper in JPEG format.
Is there any way of finding out which files are corrupted so that I can remove them?

Thanks.
I figured a way to do determine if a JPEG was corrupt.
It was actually quite visible using the Cover Flow method, the jpeg wasn't showing up properly. I was afraid there was other corruption that wasn't so visible.
What I did was, I opened up my Console from Utilities and watched the logs. As I scrolled through each picture using Cover Flow, an error would show up in the console logs.
That's how I figured it out, thanks for your ideas!

DW Windows claims corrupt JPEGs; Mac doesn't

When I open a certain site in DW 8.0.2 Windows, it complains
that some of the JPEGs are corrupt (it won't say which) by bringing
up a "Corrupt JPEG data" dialog and sometimes an additional dialog
complaining about data after a certain marker.
However, opening the same site in the Macintosh version
reveals no problems at all, even when the site images are exact
copies. No browser has any problems with any file on the site, and
a wide selection of graphics programs on both platforms have no
problem opening any of the files.
Is the Windows version ultra-picky about JPEG conformity? Is
it a bug? And in any event, how do I locate the files that DW Win
dislikes (that's quicker than dismissing a string of dialog boxes,
ie does not involve removing blocks of images until the problem
goes away and then putting them back again)?
Any observations welcome.
Thanks,
--Richard E

If you need to communicate with Macromedia, you need to
contact them
directly, or use the wish form -
http://www.macromedia.com/cfusion/mmform/index.cfm?name=wishform
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"RocDoc7" <[email protected]> wrote in
message
news:ebt8m0$jj4$[email protected]..
>I have been battling the same problem ever since I
installed Dreamweaver 8
>(and
> upgraded to 8.0.2). It is really taxing my patience. Can
someone from
> Macromedia comment on the "jpg error" problem? A simple
addition to the
> Preferences where we can turn off those annoying pop-ups
would be very
> helpful.
>
> RocDoc7
>

[svn] 3149: Fix bugs introduced by the display object sharing optimization.

Revision: 3149
Author: [email protected]
Date: 2008-09-08 16:58:35 -0700 (Mon, 08 Sep 2008)
Log Message:
Fix bugs introduced by the display object sharing optimization. This checkin should fix ordering problems when dynamically adding/removing graphic elements, and ordering problems when changing graphic element properties that require a display object (rotation, alpha, filters, etc).
Bugs:
MXMLG-219: BitmapGraphic component content always rendered from 0, 0 origin.
MXMLG-220: setting visible property of Rect and Ellipse does nothing.
MXMLG-222: setting the alpha of a rectangle changes z-order when there are 3 or more rectangles
SDK-16754: Z-order incorrect when a Group is present
QA: Yes - the test files from these bugs (or something equivalent) should be added to our standard test suite
Reviewer: Deepa
Ticket Links:
http://bugs.adobe.com/jira/browse/MXMLG-219
http://bugs.adobe.com/jira/browse/MXMLG-220
http://bugs.adobe.com/jira/browse/MXMLG-222
http://bugs.adobe.com/jira/browse/SDK-16754
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/flex/core/Group.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/BitmapGraphic.as
flex/sdk/trunk/frameworks/projects/flex4/src/flex/graphics/graphicsClasses/GraphicElement .as

This is the great thread ;-)
My favorite threads are below.
Munky posted great reply :8}
SQL Query Help
order in a connect by

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)

M500/M5x0 QUEUED-TRIM data corruption alert (mostly for Linux users)

The M550 (all released firmware), and the M500 (up to MU04 all released firmware) can cause data corruption when QUEUED TRIM is used. Since Crucial is not urging everyone to update to MU05 and are taking their time with the M550 update, I assume that Windows does not issue QUEUED TRIM by default, and therefore does not trigger the issue (yet). I have no idea about Intel RST enhanced windows drivers, MacOS or FreeBSD. Chances are they cannot trigger the bug, but you might want to check with the vendors.
EDIT: The M500 MU05 firmware still has the QUEUED TRIM data-killer bug, there are no safe firmware versions.EDIT: This is a problem on several outdated versions of the Linux kernel, for the 3.12, 3.13, 3.14 and 3.17 branches. Linux releases older than 3.12 will NOT trigger the bug. Recent releases of the 3.12, 3.13, 3.14 and 3.17 branches have a blacklist in place and will NOT trigger the bug. The 3.15 and 3.16 kernels also have the blacklist, and won't trigger the firmware bug.
Dangerous for use in kernels:3.12 (before 3.12.29);3.13 (before 3.13.7);
3.14 (before 3.14.20);3.17 (before 3.17.1) - regression in the blacklist, fixed in 3.17.1. Safe kernels:anything before 3.12;3.12.29 and later;3.13.7 and later;3.14.20 and later;3.15 (all);3.16 (all);3.17.1 and later.Bug workaround for any kernel version (tanks performance down to a crawl on most workloads): disable NCQ in the kernel command line, by adding the libata.force=noncq parameter in the bootloader. The "uname -r" command will tell you the Linux kernel release you're running on.

bogdan wrote:
Thanks for clarification uname -r
3.14.5-031405-generic After first reboot I have noticed following entries:[ 25.818233] ata1: log page 10h reported inactive tag 0
[ 25.818242] ata1.00: exception Emask 0x1 SAct 0x50000000 SErr 0x0 action 0x0
[ 25.818244] ata1.00: irq_stat 0x40000008
[ 25.818247] ata1.00: failed command: READ FPDMA QUEUED
[ 25.818252] ata1.00: cmd 60/60:e0:78:d4:15/00:00:09:00:00/40 tag 28 ncq 49152 in
[ 25.818252] res 40/00:f4:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[ 25.818254] ata1.00: status: { DRDY }
[ 25.818256] ata1.00: failed command: SEND FPDMA QUEUED
[ 25.818260] ata1.00: cmd 64/01:f0:00:00:00/00:00:00:00:00/a0 tag 30 ncq 512 out
[ 25.818260] res 40/00:f4:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[ 25.818262] ata1.00: status: { DRDY }
[ 25.818490] ata1.00: supports DRM functions and may not be fully accessible
[ 25.824747] ata1.00: supports DRM functions and may not be fully accessible
[ 25.830741] ata1.00: configured for UDMA/133
[ 25.830754] ata1.00: device reported invalid CHS sector 0
[ 25.830779] sd 0:0:0:0: [sda]
[ 25.830781] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 25.830783] sd 0:0:0:0: [sda]
[ 25.830784] Sense Key : Aborted Command [current] [descriptor]
[ 25.830787] Descriptor sense data with sense descriptors (in hex):
[ 25.830788] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 25.830795] 00 00 00 00
[ 25.830798] sd 0:0:0:0: [sda]
[ 25.830800] Add. Sense: No additional sense information
[ 25.830802] sd 0:0:0:0: [sda] CDB:
[ 25.830804] Write same(16): 93 08 00 00 00 00 02 93 68 38 00 00 00 08 00 00
[ 25.830812] end_request: I/O error, dev sda, sector 43214904
[ 25.830827] ata1: EH complete
[ 25.831278] EXT4-fs (sda1): discard request in group:164 block:27655 count:1 failed with -5Then I have created large files, 1GB, 15GB and 30GB, deleted them and issued fstrim commandsudo fstrim -v /
/: 106956468224 bytes were trimmed Right now I have no more errors in log file except those recorded after first reboot so I guess I should wait for data corruption? It should show up much faster if you have the filesystem mounted with the "discard" option, which enables online discard mode. My best guess is that corruption won't trigger on just every write, likely you want to have pending writes inside the SSD, and maybe cause a trim near them, or something else like that. Running the "mount" command as root should show you the mount options ("sudo mount" might do it in default Ubuntu). "sudo mount -o discard,remount /" might enable it if it isn't already there. Or try "sudo su -" to go root, and issue the commands without "sudo". Now, where the corruption, should it happen, will end up going, I don't know. EDIT: Doing a lot of filesystem work might help, as well. Maybe running bonie++ (warning: will do a lot of writes), or several concurrent file creation/remove workloads. Doing it either in online discard mode, or running fstrim concurrently should do it, I guess.

Corrupt jpeg

I've searched the archives but not much help there. I'm
getting a sporadic corrupt jpeg error. When it happens it occurs
when I'm ABOUT to create a new page from a template. I haven't been
able to determine yet if I've actually selected the dwt (I think it
happens when I get to the asset tab). When it occurs it repeats 3
times.
The dilemma is that it gives no indication which jpeg file is
corrupt and so far I've seen no indication that any jpeg I'm
working with isn't displaying properly.
Any thoughts?
Tom
[EDIT] Did some more testing. The error message is being
displayed when I switch from the files to the asset tab before I
select the template. This is an intermittent problem meaning that
it doesn't happen all the time and I haven't yet figured out how to
recreate it.

The error message is a red herring. It has nothing to do with
JPG images.
I have no idea what causes it, but I do know that Adobe is
interested in
fixing it.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"TCarp" <[email protected]> wrote in message
news:[email protected]...
> Hey Drew
>
> Thanks for keeping an eye on this. If there is a single
image it's more
> basic
> than an individual html page from the site. I think
someone earlier in
> the
> thread mentioned that this may not be what the error
message is implying
> (i.e.
> a corruption in a jpeg).
>
> Let me go over the symptoms again. The error occurs when
I navigate from
> the
> files view to the assets view regardless of whether
there is an individual
> html
> page open at the time. What I'm doing at the time is
copying/pasting data
> from
> one dwt to a new one. It's possible that I could be
doing this conversion
> in a
> more efficient way, but....
>
> During the procedure I go to the assets tab to create a
new page from a
> template. It's when I select the assets tab BEFORE I
select the template
> that
> I get the error. What's frustrating is that it doesn't
occur every time.
> What
> makes it more baffling is that I can recreate the
problem reliably when I
> am
> working with specific pages. For example, the procedure
I used most often
> was
> to open the old html page, switch to assets view to
select the template
> for the
> new page, create the new page, and then start to copy
process. If I have
> a
> failure, I can often go back, re-do the steps, and have
the failure. But
> again, I have seen the failure without opening the old
html page.
>
> The other symptom is, when it occurs, the error always
occurs 3 times
> before
> settling down.
>
> If there is a corrupt jpeg somewhere it doesn't fit the
pattern of errors
> I'm
> seeing.
>
> What I may do next is to focus on the jpegs used on the
site (there are
> quite
> a few). Please don't tell me that opening each one in PS
will not
> reliably
> find the corrupted one.
>
> Thanks for commenting. This is one where other
perspectives can help with
> the
> forest and trees.
>
> Tom
>

[svn] 1388: Fixing a bug introduced for DefineFont3 equality testing.

Revision: 1388
Author: [email protected]
Date: 2008-04-24 10:19:44 -0700 (Thu, 24 Apr 2008)
Log Message:
Fixing a bug introduced for DefineFont3 equality testing. DefineFontAlignZones already checks its DefineFont3 for equality and so this goes back to the old behavior and avoid an infinite equality check.
Doc: No
QA: Yes, also please add a test case that makes use of two, duplicated embedded fonts with advanced anti-aliasing to the automated mxunit testsuite.
Bug: SDK-15378
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15378
Modified Paths:
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tags/DefineFont3.java

I just posted something about this too, and while I feel that its wrong to "bump" an old post, this issue has still stayed unresolved and my frustration is peaking. In my thread my problem is i can't even use the KXdrivers on an x64 operating system, so this things an expensi've paper weight. Great.
Creative makes good sound cards, NO DOUBT about that. Their customer service on the other hand however, is absolute trash. I have read that "statement" as well, and it seems an easy way out to just say "yeah we addressed it, so please, shut up about it already". And I agree, it is NOT a fix, for all of us. If one would take the time to read the forum, its not only ABIT motherboards. Even in that one thread, one if the first couple of replies a guy says "but I have a gigabyte motherboard". Surprise surprise, he was ignored by the mod who posted that (she answered some other poster's question with "read the instructions please" . Please creative, give us some faith back in your company by helping out the many of us with this problem. Only then will I reccomend and buy your products.

[svn] 3780: Fix for bug introduced yesterday when adding clipContent to FxContainer and FxDataContainer .

Revision: 3780
Author: [email protected]
Date: 2008-10-21 10:51:40 -0700 (Tue, 21 Oct 2008)
Log Message:
Fix for bug introduced yesterday when adding clipContent to FxContainer and FxDataContainer. The default value needs to be true.
Also fixing a bug in SystemManager since application isn't always an IRawChildrenContainer anymore. This was previously fixed and got clobbered in a merge.
QE Notes: None
Doc Notes: None
Bugs: SDK-17423, SDK-17697
Reviewer: Hans
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17423
http://bugs.adobe.com/jira/browse/SDK-17697
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxContainer.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxDataContainer.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/SystemManager.as

The network admin solved the problem:
“When I recreated the User Profile Service, I did not enable “NetBIOS Name” on the service, so all user accounts did not have the proper domain, which is why none of the targeting worked.
All users were listed as corp\username instead of rcd\username.”, Network Admin.
Further information: http://www.windowsclever.com/sharepoint/netbios-name-is-different-domain-name-user-profie-service-sharepoint-2010.html

Data-corrupting JPEG bug introduced in Lr 3.4, CR 6.4

Similar Messages

Maybe you are looking for