Re: One error/warning message after upgrade 5.11 -> 6.8

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

 



On May 11, 2020 7:59:00 AM GMT+03:00, Hu Bert <revirii@xxxxxxxxxxxxxx> wrote:
>Hi,
>
>no problem. Output is identical for all 3 bricks (1 x 3 = 3)
>
>:xfs_info /gluster/md4
>meta-data=/dev/md4               isize=512    agcount=32,
>agsize=152598400 blks
>         =                       sectsz=4096  attr=2, projid32bit=1
>      =                       crc=1        finobt=1, sparse=0, rmapbt=0
>         =                       reflink=0
>data     =                       bsize=4096   blocks=4883148800,
>imaxpct=5
>         =                       sunit=128    swidth=256 blks
>naming   =version 2              bsize=8192   ascii-ci=0, ftype=1
>log      =internal log           bsize=4096   blocks=521728, version=2
>        =                       sectsz=4096  sunit=1 blks, lazy-count=1
>realtime =none                   extsz=4096   blocks=0, rtextents=0
>
>Best Regards,
>Hubert
>
>Am Fr., 8. Mai 2020 um 21:47 Uhr schrieb Strahil Nikolov
><hunter86_bg@xxxxxxxxx>:
>>
>> On April 21, 2020 8:00:32 PM GMT+03:00, Amar Tumballi
><amar@xxxxxxxxx> wrote:
>> >There seems to be a burst of issues when people upgraded to 5.x or
>6.x
>> >from
>> >3.12 (Thanks to you and Strahil, who have reported most of them).
>> >
>> >Latest update from Strahil is that if files are copied fresh on 7.5
>> >series,
>> >there are no issues.
>> >
>> >We are in process of identifying the patch, and also provide an
>option
>> >to
>> >disable 'acl' for testing. Will update once we identify the issue.
>> >
>> >Regards,
>> >Amar
>> >
>> >
>> >
>> >On Sat, Apr 11, 2020 at 11:10 AM Hu Bert <revirii@xxxxxxxxxxxxxx>
>> >wrote:
>> >
>> >> Hi,
>> >>
>> >> no one has seen such messages?
>> >>
>> >> Regards,
>> >> Hubert
>> >>
>> >> Am Mo., 6. Apr. 2020 um 06:13 Uhr schrieb Hu Bert
>> ><revirii@xxxxxxxxxxxxxx
>> >> >:
>> >> >
>> >> > Hello,
>> >> >
>> >> > i just upgraded my servers and clients from 5.11 to 6.8; besides
>> >one
>> >> > connection problem to the gluster download server everything
>went
>> >> > fine.
>> >> >
>> >> > On the 3 gluster servers i mount the 2 volumes as well, and only
>> >there
>> >> > (and not on all the other clients) there are some messages in
>the
>> >log
>> >> > file of both mount logs:
>> >> >
>> >> > [2020-04-06 04:10:53.552561] W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-2: remote operation failed [Permission
>denied]
>> >> > [2020-04-06 04:10:53.552635] W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-1: remote operation failed [Permission
>denied]
>> >> > [2020-04-06 04:10:53.552639] W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-0: remote operation failed [Permission
>denied]
>> >> > [2020-04-06 04:10:53.553226] E [MSGID: 148002]
>> >> > [utime.c:146:gf_utime_set_mdata_setxattr_cbk]
>0-persistent-utime:
>> >dict
>> >> > set of key for set-ctime-mdata failed [Permission denied]
>> >> > The message "W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-2: remote operation failed [Permission
>denied]"
>> >> > repeated 4 times between [2020-04-06 04:10:53.552561] and
>> >[2020-04-06
>> >> > 04:10:53.745542]
>> >> > The message "W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-1: remote operation failed [Permission
>denied]"
>> >> > repeated 4 times between [2020-04-06 04:10:53.552635] and
>> >[2020-04-06
>> >> > 04:10:53.745610]
>> >> > The message "W [MSGID: 114031]
>> >> > [client-rpc-fops_v2.c:851:client4_0_setxattr_cbk]
>> >> > 0-persistent-client-0: remote operation failed [Permission
>denied]"
>> >> > repeated 4 times between [2020-04-06 04:10:53.552639] and
>> >[2020-04-06
>> >> > 04:10:53.745632]
>> >> > The message "E [MSGID: 148002]
>> >> > [utime.c:146:gf_utime_set_mdata_setxattr_cbk]
>0-persistent-utime:
>> >dict
>> >> > set of key for set-ctime-mdata failed [Permission denied]"
>repeated
>> >4
>> >> > times between [2020-04-06 04:10:53.553226] and [2020-04-06
>> >> > 04:10:53.746080]
>> >> >
>> >> > Anything to worry about?
>> >> >
>> >> >
>> >> > Regards,
>> >> > Hubert
>> >> ________
>> >>
>> >>
>> >>
>> >> Community Meeting Calendar:
>> >>
>> >> Schedule -
>> >> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
>> >> Bridge: https://bluejeans.com/441850968
>> >>
>> >> Gluster-users mailing list
>> >> Gluster-users@xxxxxxxxxxx
>> >> https://lists.gluster.org/mailman/listinfo/gluster-users
>> >>
>>
>> Hi,
>>
>> Can you provide the xfs_info for the bricks from the volume ?
>>
>> I have a theory that I want to confirm or reject.
>>
>> Best Regards,
>> Strahil Nikolov

Hi Hubert,

Thanks for the reply.
The theory that the brick was created with the default inode size is 'rejected'.
I guess  it's something else.

Best Regards,
Strahil Nikolov
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux