ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
Cc: ocfs2-devel ML <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] error message in log: ocfs2_reflink_ioctl:4431 ERROR:	status = -17
Date: Tue, 23 Feb 2021 22:24:06 +0000	[thread overview]
Message-ID: <01866DBC-59D3-4D41-B404-C76FCA6B6221@oracle.com> (raw)
In-Reply-To: <1884783914.58523079.1614110913964.JavaMail.zimbra@helmholtz-muenchen.de>


[-- Attachment #1.1: Type: text/plain, Size: 6491 bytes --]

 #define EEXIST          17      /* File exists */

You may already have the file created from the other node.

wengang

On Feb 23, 2021, at 12:08 PM, Lentes, Bernd <bernd.lentes@helmholtz-muenchen.de<mailto:bernd.lentes@helmholtz-muenchen.de>> wrote:

Hi,

i hope it's ok to ask here, if not tell me.
I know there is a ML ocfs2-user, but it has such low traffic (no E-Mail in the second half of 2020 !) that it doesn't help much.
I have a two-node HA-cluster with pacemaker. My ressources are virtual domains.
The virtual disks of the domains are raw files on an OCFS2 volume on a SAN.
Each evening the domains are shutdown to make a consistent reflink of each raw file which i copy afterwards in the background to a CIFS share.
In my syslog appears quite often the mentioned error:

2021-01-22T00:00:06.655943+01:00 ha-idg-2 kernel: [4191702.116515] (reflink,10881,17):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:06.871000+01:00 ha-idg-2 kernel: [4191702.334649] (reflink,10884,21):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:07.075983+01:00 ha-idg-2 kernel: [4191702.536488] (reflink,10885,17):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:07.791944+01:00 ha-idg-2 kernel: [4191703.255204] (reflink,10888,21):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:08.066327+01:00 ha-idg-2 kernel: [4191703.529930] (reflink,10889,13):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:08.274759+01:00 ha-idg-2 kernel: [4191703.738449] (reflink,10892,1):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:08.475985+01:00 ha-idg-2 kernel: [4191703.938052] (reflink,10893,10):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:08.675990+01:00 ha-idg-2 kernel: [4191704.138467] (reflink,10896,7):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:08.862265+01:00 ha-idg-2 kernel: [4191704.325938] (reflink,10897,23):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.033816+01:00 ha-idg-2 kernel: [4191704.496384] (reflink,10900,19):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.223980+01:00 ha-idg-2 kernel: [4191704.685485] (reflink,10901,9):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.399947+01:00 ha-idg-2 kernel: [4191704.863623] (reflink,10909,15):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.567981+01:00 ha-idg-2 kernel: [4191705.030704] (reflink,10996,7):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.735992+01:00 ha-idg-2 kernel: [4191705.198145] (reflink,10999,1):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:09.971949+01:00 ha-idg-2 kernel: [4191705.435148] (reflink,11000,1):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:10.136051+01:00 ha-idg-2 kernel: [4191705.599029] (reflink,11003,5):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:10.320845+01:00 ha-idg-2 kernel: [4191705.784548] (reflink,11004,17):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:10.528025+01:00 ha-idg-2 kernel: [4191705.990409] (reflink,11007,20):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:10.717251+01:00 ha-idg-2 kernel: [4191706.180929] (reflink,11008,17):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:11.463958+01:00 ha-idg-2 kernel: [4191706.925221] (reflink,11031,1):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:11.655975+01:00 ha-idg-2 kernel: [4191707.117305] (reflink,11037,15):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:13.819013+01:00 ha-idg-2 kernel: [4191709.282582] (reflink,11040,15):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:14.467945+01:00 ha-idg-2 kernel: [4191709.931562] (reflink,11041,19):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:14.683974+01:00 ha-idg-2 kernel: [4191710.144808] (reflink,11052,16):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:14.908012+01:00 ha-idg-2 kernel: [4191710.371273] (reflink,11096,12):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:15.098659+01:00 ha-idg-2 kernel: [4191710.560220] (reflink,11099,20):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:16.271950+01:00 ha-idg-2 kernel: [4191711.735628] (reflink,11104,4):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:16.503952+01:00 ha-idg-2 kernel: [4191711.967347] (reflink,11302,6):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:16.764776+01:00 ha-idg-2 kernel: [4191712.228470] (reflink,11309,10):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:16.972088+01:00 ha-idg-2 kernel: [4191712.431961] (reflink,11312,13):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:17.171988+01:00 ha-idg-2 kernel: [4191712.634809] (reflink,11313,5):ocfs2_reflink_ioctl:4431 ERROR: status = -17
2021-01-22T00:00:17.436011+01:00 ha-idg-2 kernel: [4191712.897895] (reflink,11316,23):ocfs2_reflink_ioctl:4431 ERROR: status = -17

I grepped around in the sources but my last touch with C is 25 years ago.
I "think" the call of the function ocfs2_reflink_ioctl returns a "-17", which indicates clearly that someting is wrong.
But i have no idea what.
My systems are SLES 12 SP5 with kernel 4.12.14-122.46-default and ocfs2-tools-1.8.5-3.3.1.x86_64.

The point is that i have trouble starting some domains after creating the reflinks, some fail occasionally and boot e.g. into emergency mode
and i try to narrow down the problem.

I'd appreciate very much your help.

Thanks.


Bernd

--

Bernd Lentes
System Administrator
Institute for Metabolism and Cell Death (MCD)
Building 25 - office 122
HelmholtzZentrum München
bernd.lentes@helmholtz-muenchen.de<mailto:bernd.lentes@helmholtz-muenchen.de>
phone: +49 89 3187 1241
phone: +49 89 3187 3827
fax: +49 89 3187 2294
http://www.helmholtz-muenchen.de/mcd
Helmholtz Zentrum München

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671


_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel


[-- Attachment #1.2: Type: text/html, Size: 8942 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

  reply	other threads:[~2021-02-23 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 20:08 [Ocfs2-devel] error message in log: ocfs2_reflink_ioctl:4431 ERROR: status = -17 Lentes, Bernd
2021-02-23 22:24 ` Wengang Wang [this message]
2021-02-24  9:11   ` Lentes, Bernd
2021-02-24  9:27     ` Gang He
2021-02-24 21:49     ` Wengang Wang
2021-02-25 12:39       ` Lentes, Bernd
2021-02-25 16:43         ` Wengang Wang
2021-02-25 20:48           ` Lentes, Bernd
2021-02-26  2:41             ` Joseph Qi
2021-02-26 16:42             ` Wengang Wang

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=01866DBC-59D3-4D41-B404-C76FCA6B6221@oracle.com \
    --to=wen.gang.wang@oracle.com \
    --cc=bernd.lentes@helmholtz-muenchen.de \
    --cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).