Talk:Data corruption

message: This article and Integrity (computing) seem to cover the same topic. JonHarder 00:11, 28 January 2006 (UTC)
replies: text: This is no longer true. Badon (talk) 22:15, 21 August 2011 (UTC)
thread_title:  Merge proposal. 

message: hey um I was thinking "hey wouldnt it be fun to make an I Love Bees style web site" so I went looking for software that corrupts data on purpose and I found this: http://www.recyclism.com/corruption/index.php
maybe it should be added as well as maybe links to any other software that does anything similar --207.160.205.13 21:52, 24 September 2007 (UTC)
thread_title:  software for corrupting data? 

message: This google search is loaded with information:
http://www.google.com/search?q=silent+data+corruption
As I get around to adding info, I'll be taking a lot of info from that search. The CERN study of the subject is particularly interesting, as is the widely unrecognized scope of the problem, even in the 2011/2012, when computing technology is commonly thought to be mature - without basic data integrity checks, it is not! 
In particular, the myth that "computers don't make mistakes, people do" originating from the early days (1960's to 1980's?) is completely untrue in the context of a century-long era of unknown, unchecked, unverified, uncorrected data corruption. Badon (talk) 22:19, 21 August 2011 (UTC)
thread_title:  Excellent information to be use as references 

message: I added a bunch of links to the see also section, some of which should be worked into the article prose as the article gets better. Badon (talk) 22:41, 21 August 2011 (UTC)
thread_title:  Added links to see also section 

message: I've been looking for a reliable source overview of this topic as an outline of the article without much success.  CERN is a pretty good overview of the size of the Undetected Data Corruption problem but it really doesn't go into their sources. Most articles point at only one source, typically the HDD.  Silent Data Corruption: Causes and Mitigation Techniques does a good job of listing many sources [all?]:
Unfortunately it is focused on semiconductors in computers and fails to point out that the same errors can occur at any place in the storage hierarchy and that such errors in a file system structure can lead to larger errors due to corruption of pointers to blocks (read or write wrong block).  The latter might be original research unless we can find something.  Still looking :-) Any ideas? Tom94022 (talk) 19:13, 10 January 2014 (UTC)
replies: text: Here's another interesting article, in addition to those listed in the section above, but still nothing providing a required broader coverage: Bitrot and atomic COWs: Inside “next-gen” filesystems. — Dsimic (talk) 03:21, 16 January 2014 (UTC)
replies: text: Thanks for the article; unfortuantely the author seems to think "bit rot" is only an HDD phenomena.  Still looking. Tom94022 (talk) 21:56, 16 January 2014 (UTC)
replies: text:  Here's a quite good talk—although biased toward "Oracle is the best", but not too much—addressing various layers involved into causing data corruption, ways for ensuring end-to-end data integrity etc.: Eliminating Silent Data Corruption in Linux (by Martin Petersen and Sergio Leunissen from Oracle, December 2010).  It could be perceived as being Linux-centric, but the presented material is quite general.  As a huge plus, slides can be linked externally (with no registration required) so they can be used here as references, like this one (slide1_028.png); to obtain URLs of slides, just use Firebug's Net panel to monitor the slides being fetched during the talk, or poke the numbers manually into the above URL, starting with slide1_001.png and ending in slide1_043.png.  Looking usable? — Dsimic (talk) 19:19, 17 January 2014 (UTC)
replies: text:  Great find, here is a pdf of Eliminating Silent Data Corruption with Oracle Linux.  Need to go thru the talk again and then maybe on to the article.  Thanks Tom94022 (talk) 18:07, 18 January 2014 (UTC)

text:  which u linked in on 1 Jan actually has a lot to contribute.  I think at this point we have sufficient reliable sources to craft a good article.  Agree?  Tom94022 (talk) 03:30, 19 January 2014 (UTC)
replies: text:  Totally agreed; these three main references (Cristian-Constantinescu-LANL-talk-2008.pdf, data-integrity-webcast.pdf and jiang.pdf), with some help from other more narrow ones, are providing a very good backing for the article.  Would you like to propose the new article layout, please? — Dsimic (talk) 03:49, 19 January 2014 (UTC)
thread_title:  Content/Layout of article 

message: Merge Data degradation with Data corruption. I don't care which moves where. This page just had a bigger references list. Both pages concern loss of data due to errors in computer systems, with no attempt made to distinguish degradation of data from corruption of data which appear synonymous. Waerloeg (talk) 03:54, 6 October 2016 (UTC)
replies: text: Data degradation is associated with image/photo data loss/change/degradation (i.e. missing or moved 'bits' resulting in missing image 'pixels' or misplaced parts of an image) and usually resulting from intended removal or poorly stored digital image file and thus the loss of file data/'bits' of the digital image information. However, image degradation can also be caused intentionally but not due to corruption of data but rather from intentional re-organising of the image data such as in image compression which results in a degraded image but one of order and with acceptable and expected image quality degradation. JPEG 'artefacts' (jagged image edges) are a resulting visual effect of a 'degraded image' but is accepted and expected.
Data Corruption is associated with the corruption, interference and/or loss of digital information from digital files such as documents not image/photo data information and is usually caused during data file transfer from one source to another (...or intentional, such as sabotage for example).  — Preceding unsigned comment added by Greg Stobie (talk • contribs) 01:14, 14 March 2018 (UTC)

text: Oppose: They really are two different things, one a consequence of normal activity and the other a consequence of failure of some sort; they should remain in two articles. Tom94022 (talk) 06:42, 14 March 2018 (UTC)
replies: text: Closed (given the uncontested objections to the merge). Klbrain (talk) 22:19, 15 May 2018 (UTC)
thread_title:  Merge with Data degradation