On 3 September 2013 18:54, Duncan 1i5t5.dun...@cox.net wrote:
In case the data is wrong, there may be a reverse CRC32 algorithm
implemented. Most likely it's only several bytes which got flipped.
...
But... that flips the entire reason for choosing direct-IO in the first
place --
David MacKinnon posted on Tue, 03 Sep 2013 19:26:10 +1000 as excerpted:
On 3 September 2013 18:54, Duncan 1i5t5.dun...@cox.net wrote:
In case the data is wrong, there may be a reverse CRC32 algorithm
implemented. Most likely it's only several bytes which got flipped.
But... that flips the
Hello list,
I was greeted by the following errors in my syslog:
Sep 2 23:06:08 laptop kernel: [ 7340.809551] btrfs: checksum error at
logical 271008116736 on dev /dev/dm-0, sector 540863448, root 442,
inode 1508, offset 10128658432, length 4096, links 1 (path:
Werkstation/Windows 8 x64-cl1.vmdk)
On Mon, Sep 02, 2013 at 11:41:12PM +0200, Rain Maker wrote:
Hello list,
So, I ran a full scrub, and, luckily, it only found 6 csum errors
(these 6). The damage therefore seems to be contained in just 1
file.
Now, I removed the offending file. But is there something else I
should have
First of all, thanks for the quick response. Reply inline.
2013/9/3 Hugo Mills h...@carfax.org.uk:
On Mon, Sep 02, 2013 at 11:41:12PM +0200, Rain Maker wrote:
Now, I removed the offending file. But is there something else I
should have done to recover the data in this file? Can it be
