From: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
To: ocfs2-devel <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] error message in log: ocfs2_reflink_ioctl:4431 ERROR: status = -17
Date: Wed, 24 Feb 2021 10:11:27 +0100 (CET) [thread overview]
Message-ID: <834203578.59367045.1614157887078.JavaMail.zimbra@helmholtz-muenchen.de> (raw)
In-Reply-To: <01866DBC-59D3-4D41-B404-C76FCA6B6221@oracle.com>
----- On Feb 23, 2021, at 11:24 PM, Wengang Wang wen.gang.wang@oracle.com wrote:
> #define EEXIST 17 /* File exists */
> You may already have the file created from the other node.
> wengang
Hi Wengang,
thanks for your help.
The reflink is created via:
reflink -fv /path/to/domain.raw /mnt/ocfs2/reflink
Of course this file exists already because the skript ran also one day before.
But from which node the previous one was created is unpredictable, it might be the same
but also the other one.
Is the message severe or don't i have to bother about it ?
Thanks.
Bernd
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
next prev parent reply other threads:[~2021-02-24 9:11 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
2021-02-24 9:11 ` Lentes, Bernd [this message]
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=834203578.59367045.1614157887078.JavaMail.zimbra@helmholtz-muenchen.de \
--to=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).