From: NeilBrown <neilb@suse.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Sage Weil <sweil@redhat.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [GIT PULL] Ceph fixes for -rc7
Date: Wed, 30 Mar 2016 11:24:44 +1100 [thread overview]
Message-ID: <874mbovmlv.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAOi1vP9j8RCucc9DLoFUOXyBrGuTbN10hnQ0CwOE-PK=_j=k=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
On Fri, Mar 25 2016, Ilya Dryomov wrote:
> On Fri, Mar 25, 2016 at 5:02 AM, NeilBrown <neilb@suse.com> wrote:
>> On Sun, Mar 06 2016, Sage Weil wrote:
>>
>>> Hi Linus,
>>>
>>> Please pull the following Ceph patch from
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
>>>
>>> This is a final commit we missed to align the protocol compatibility with
>>> the feature bits. It decodes a few extra fields in two different messages
>>> and reports EIO when they are used (not yet supported).
>>>
>>> Thanks!
>>> sage
>>>
>>>
>>> ----------------------------------------------------------------
>>> Yan, Zheng (1):
>>> ceph: initial CEPH_FEATURE_FS_FILE_LAYOUT_V2 support
>>
>> Just wondering, but was CEPH_FEATURE_FS_FILE_LAYOUT_V2 supposed to have
>> exactly the same value as CEPH_FEATURE_NEW_OSDOPREPLY_ENCODING (and
>> CEPH_FEATURE_CRUSH_TUNABLES5)??
>
> Yes, that was the point of getting it merged into -rc7.
I did wonder if that might be the case.
>
>> Because when I backported this patch (and many others) to some ancient
>> enterprise kernel, it caused mounts to fail. If it really is meant to
>> be the same value, then I must have some other backported issue to find
>> and fix.
>
> It has to be backported in concert with changes that add support for
> the other two bits.
I have everything from fs/ceph and net/ceph as of 4.5, with adjustments
for different core code.
> How did mount fail?
"can't read superblock".
dmesg contains
[ 50.822479] libceph: client144098 fsid 2b73bc29-3e78-490a-8fc6-21da1bf901ba
[ 50.823746] libceph: mon0 192.168.1.122:6789 session established
[ 51.635312] ceph: problem parsing mds trace -5
[ 51.635317] ceph: mds parse_reply err -5
[ 51.635318] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)
then a hex dump of header:, front: footer:
Maybe my MDS is causing the problem? It is based on v10.0.5 which
contains
#define CEPH_FEATURE_CRUSH_TUNABLES5 (1ULL<<58) /* chooseleaf stable mode */
// duplicated since it was introduced at the same time as CEPH_FEATURE_CRUSH_TUN
#define CEPH_FEATURE_NEW_OSDOPREPLY_ENCODING (1ULL<<58) /* New, v7 encoding */
in ceph_features.h i.e. two features using bit 58, but not
FS_FILE_LAYOUT_V2
Should I expect Linux 4.5 to work with ceph 10.0.5 ??
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-30 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 1:48 Sage Weil
2016-03-25 4:02 ` NeilBrown
2016-03-25 9:34 ` Ilya Dryomov
2016-03-30 0:24 ` NeilBrown [this message]
2016-03-30 2:30 ` Yan, Zheng
2016-03-30 2:40 ` NeilBrown
2016-03-30 8:04 ` Ilya Dryomov
2016-03-30 18:09 ` Gregory Farnum
2016-03-31 2:18 ` NeilBrown
2016-03-28 2:12 ` Yan, Zheng
-- strict thread matches above, loose matches on Subject: below --
2015-01-28 18:55 Sage Weil
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=874mbovmlv.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sweil@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome