Re: [PATCH] Btrfs: relocate csums properly with prealloc extents

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Sep 27, 2013 at 09:37:00AM -0400, Josef Bacik wrote:
> A user reported a problem where they were getting csum errors when running a
> balance and running systemd's journal.  This is because systemd is awesome and
> fallocate()'s its log space and writes into it.  Unfortunately we assume that
> when we read in all the csums for an extent that they are sequential starting at
> the bytenr we care about.  This obviously isn't the case for prealloc extents,
> where we could have written to the middle of the prealloc extent only, which
> means the csum would be for the bytenr in the middle of our range and not the
> front of our range.  Fix this by offsetting the new bytenr we are logging to
> based on the original bytenr the csum was for.  With this patch I no longer see
> the csum errors I was seeing.  Thanks,
> 
> Cc: stable@xxxxxxxxxxxxxxx

The patch had the right CC but I don't see it in the mail's CC list (now
added by me). I'm afraid that this never reached stable and explains why
the patch did not end up in 3.12.1.

Stable team, please add this patch to 3.12.x, the commit id is

 4577b014d1bc3db386da3246f625888fc48083a9

thanks,
david
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux