On Wed, 2009-09-02 at 12:32 -0400, jim owens wrote:
@@ -2895,7 +2895,7 @@ again:
multi-num_stripes = num_stripes;
multi-max_errors = max_errors;
}
- if (raid_map_ret) {
+ if (raid_map) {
sort_parity_stripes(multi,
On Tue, Sep 08, 2009 at 10:15:29AM +0100, David Woodhouse wrote:
On Wed, 2009-09-02 at 12:32 -0400, jim owens wrote:
@@ -2895,7 +2895,7 @@ again:
multi-num_stripes = num_stripes;
multi-max_errors = max_errors;
}
- if (raid_map_ret) {
+
On Tue, Sep 08 2009, Markus Trippelsdorf wrote:
On Tue, Sep 08, 2009 at 10:00:42PM +0200, Jens Axboe wrote:
On Mon, Sep 07 2009, Markus Trippelsdorf wrote:
Just got this error today in my dmesg:
btrfs csum failed ino 1483065 off 158482432 csum 4283543305 private
43905798
linux
Thanks! I have a follow up question: Are back references reference
counted? If so, this should mean that after the file system COWs an
inode, it must increase the reference counts of its file extent back
references. Do we know what is the overhead? In the case they are not
reference counted,
On Mon, Sep 07 2009, Markus Trippelsdorf wrote:
Just got this error today in my dmesg:
btrfs csum failed ino 1483065 off 158482432 csum 4283543305 private 43905798
linux % find . -inum 1483065
./.git/objects/pack/pack-f9251bcc6a8afe3c92193e14d1d742f2f0182ce5.pack
It's the main pack file
On Tue, Sep 08, 2009 at 10:00:42PM +0200, Jens Axboe wrote:
On Mon, Sep 07 2009, Markus Trippelsdorf wrote:
Just got this error today in my dmesg:
btrfs csum failed ino 1483065 off 158482432 csum 4283543305 private 43905798
linux % find . -inum 1483065