On Wed, Jul 16, 2014 at 1:50 AM, James Harper <james at ejbdigital.com.au> wrote: > Can you offer some comments on what the impact is likely to be to the data in an affected cluster? Should all data now be treated with suspicion and restored back to before the firefly upgrade? I am under the impression that it's not actually a data corruption bug, so much as a "reveal garbage data in sparse files" bug. So far everybody who's run into this has run a repair and not seen any issues, at least. Backups *should* be unnecessary, but we're still nailing down *exactly* what the bug is, so it's possible our suspicions are wrong or my information is out of date. On Wed, Jul 16, 2014 at 2:49 AM, Sylvain Munaut <s.munaut at whatever-company.com> wrote: > On Wed, Jul 16, 2014 at 10:50 AM, James Harper <james at ejbdigital.com.au> wrote: >> Can you offer some comments on what the impact is likely to be to the data in an affected cluster? Should all data now be treated with suspicion and restored back to before the firefly upgrade? > > Yes, I'd definitely like to know that too ... I upgraded a couple > weeks ago to firefly and I run precise with a 3.2 kernel on XFS. I > didn't see any deep scrubs error however. > > Also does this affect RBD only or can also affect radosgw ? RBD-only, and if you haven't seen/don't get deep-scrub errors you won't have any issues. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com
 |