We could conceivably mark the PG for backfill, but to do this correctly
we have to do the log rollback, which uses various methods in PG to update
snap metadata that we simply don't have access to from this tool.
Signed-off-by: Sage Weil <sage@redhat.com>
Move all PG metadata (info, biginfo, epoch, and log) to a single per-PG
object. This should make it easier for ObjectStore implementations to
avoid lock contention in the write path.
Signed-off-by: Sage Weil <sage@redhat.com>
This way we properly create the pgmeta object and set the infokey attr on
it. Break it into two steps, one part before split, one after.
Disable the collection_empty() check in split so that it doesn't trip over
this object.
Signed-off-by: Sage Weil <sage@redhat.com>
There will be exactly one of these per PG. It slots into the flat
(pool, hash, name...)
namespace but is not a legal rados name (since it is the empty string).
Signed-off-by: Sage Weil <sage@redhat.com>
From FileStore's perspective, nothing changed from v3 to v4. However, we
need to pass the do_upgrade flag to DBOjectMap open to trigger it's
upgrade process.
Signed-off-by: Sage Weil <sage@redhat.com>
This ensures that we exercise the large xattr handling paths in the OSD.
(Specifically, we want to trigger DBObjectMap usage on EC objects so that
we can test the fix for #10171).
Signed-off-by: Sage Weil <sage@redhat.com>
We were inadvertantly dropping the hash portion of the header key for EC
objects. This is usually not noticeable, but turns up quite quickly with
the new pgmeta objects, which share the same name ('') across PGs with
different hash values
Fixes: #10171
Signed-off-by: Sage Weil <sage@redhat.com>
ReplicatedPG: Make recovery using fiemap and fix perf counter
sage-2014-12-16_08:43:28-powercycle-wip-sage-testing-distro
Reviewed-by: Sage Weil <sage@redhat.com>
add osdmap checksums
sage-2014-12-16_06:27:10-rados:singleton-wip-sage-testing2-distro-basic-multi
sage-2014-12-15_13:18:23-rados:thrash-wip-sage-testing2-distro-basic-multi
Reviewed-by: Samuel Just <sjust@redhat.com>
osd: reenable fadvise; use it more often
sage-2014-12-16_06:27:10-rados:singleton-wip-sage-testing2-distro-basic-multi
sage-2014-12-15_13:18:23-rados:thrash-wip-sage-testing2-distro-basic-multi
Reviewed-by: Sage Weil <sage@redhat.com>
A restriction that the w parameter of the cauchy technique is limited to
8, 16 or 32 was added incorrectly while refactoring parameter parsing in
the jerasure plugin and must be relaxed.
http://tracker.ceph.com/issues/10325Fixes: #10325
Signed-off-by: Loic Dachary <ldachary@redhat.com>
In the source code of cephfs there is no reference to it anymore,
but it's still in the man page. Leave it there for now, but make
it more clear that it is deprecated and unsupported.
It was possible for an image to be closed while aio operations
were still outstanding. Now all aio operations are tracked and
completed before the image is closed.
Fixes: #10299
Backport: giant, firefly, dumpling
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
buffer::list::c_str does not actually provide a C-style, NULL
terminated string. As a result, its use for console output
resulted in stray garbage characters being printed.
Fixes: #9405
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
Otherwise we may trigger the timeout while waiting for the work to be
committed to the store -- and it would only take the write to take a bit
longer than 10 seconds (default accept timeout).
We do wait for the work to be properly committed to the store before
extending the lease though.
Fixes: #10220
Signed-off-by: Joao Eduardo Luis <joao@redhat.com>
