From: Sage Weil <sage@newdream.net>
To: Igor Fedotov <ifedotov@mirantis.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: uint32_t BlueStore::Extent::logical_offset?
Date: Tue, 22 Nov 2016 21:47:24 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.11.1611222146240.11236@piezo.us.to> (raw)
In-Reply-To: <8e0b5262-32ef-02a6-6812-a3e82369e9aa@mirantis.com>
On Tue, 22 Nov 2016, Igor Fedotov wrote:
> Hi Sage,
>
>
> I'm wondering why BlueStore::Extent::logical_offset is 32-bit wide.
>
> IMHO it's to be uint64_t unless we limit onode size to 4Gb.
>
> Looks like we have implicit truncate when doing set_lextent/new Extent at the
> moment and hence some issues with large onodes are possible.
The max object size enforced in the OSD is ~128 MB (or in that
neighborhood, if I remember correctly). We really shouldn't be storing
individual rados objects that are orders of magnitude larger than that.
sage
next prev parent reply other threads:[~2016-11-22 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 16:58 uint32_t BlueStore::Extent::logical_offset? Igor Fedotov
2016-11-22 17:06 ` Gregory Farnum
2016-11-22 17:15 ` Igor Fedotov
2016-11-22 21:47 ` Sage Weil [this message]
2016-11-22 21:53 ` Somnath Roy
2016-11-22 22:42 ` Matt Benjamin
2016-11-22 22:45 ` Sage Weil
2016-11-22 23:02 ` Matt Benjamin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.11.1611222146240.11236@piezo.us.to \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=ifedotov@mirantis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.