From: Nikolaus Rath <Nikolaus@rath.org>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fsck: to repair or not to repair
Date: Fri, 10 Jun 2016 08:54:36 -0700 [thread overview]
Message-ID: <87twh1t4xv.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <ec929c7d-079d-8ea5-87d7-fce0ed1c45b7@gmail.com> (Austin S. Hemmelgarn's message of "Fri, 10 Jun 2016 07:05:40 -0400")
On Jun 10 2016, "Austin S. Hemmelgarn" <ahferroin7@gmail.com> wrote:
> JFYI, if you've using GNU cp, you can pass '--reflink=never' to avoid
> it making reflinks.
I would have expected so, but at least in coreutils 8.23 the only valid
options are "never" and "auto" (at least according to cp --help and the
manpage).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-06-10 15:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:10 fsck: to repair or not to repair Nikolaus Rath
2016-05-12 17:02 ` Henk Slager
2016-05-12 17:35 ` Nikolaus Rath
2016-05-12 17:55 ` Ashish Samant
2016-05-13 6:36 ` Duncan
2016-05-13 15:28 ` Nikolaus Rath
2016-05-13 21:35 ` Chris Murphy
2016-05-16 11:17 ` Austin S. Hemmelgarn
2016-05-16 11:34 ` Andrei Borzenkov
2016-05-16 11:48 ` Austin S. Hemmelgarn
2016-06-10 3:40 ` Nikolaus Rath
2016-06-10 11:05 ` Austin S. Hemmelgarn
2016-06-10 15:54 ` Nikolaus Rath [this message]
2016-06-10 16:50 ` Adam Borowski
2016-06-10 16:55 ` Nikolaus Rath
2016-06-10 17:12 ` Austin S. Hemmelgarn
2016-06-10 17:22 ` Adam Borowski
2016-06-10 17:39 ` Austin S. Hemmelgarn
2016-06-10 17:40 ` Henk Slager
2016-06-10 15:55 ` Nikolaus Rath
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=87twh1t4xv.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.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 NNTP newsgroup(s).