From: jf@dockes.org
To: 13601@debbugs.gnu.org
Subject: bug#13601: mv should not silently lose file extended attributes
Date: Thu, 31 Jan 2013 20:06:30 +0100 [thread overview]
Message-ID: <20746.49334.569751.252972@y.dockes.com> (raw)
When moving a file having extended attributes to a target filesystem which
does not support them (e.g. an NFS mount), the attributes are silently
lost.
I think that mv should not complete the move in this case, as the current
behaviour leads to silent and unexpected data loss.
Ideally, this behaviour should be controlled by an option, but I think that
the default should be to refuse to lose data.
mv version: mv (GNU coreutils) 8.13
Checked on Ubuntu 12.04 (probably not relevant).
Regards,
J.F. Dockès
next reply other threads:[~2013-01-31 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 19:06 jf [this message]
2013-02-01 0:25 ` bug#13601: mv should not silently lose file extended attributes Pádraig Brady
2013-02-01 6:59 ` jf
2021-02-21 16:45 ` bug#13601: Joshua Krämer
2023-12-11 20:03 ` bug#13601: mv should not silently lose file extended attributes Abraham S.A.H. via GNU coreutils Bug Reports
2023-12-11 22:38 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20746.49334.569751.252972@y.dockes.com \
--to=jf@dockes.org \
--cc=13601@debbugs.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).