From: Adam Borowski <kilobyte@angband.pl>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: fsck: to repair or not to repair
Date: Fri, 10 Jun 2016 18:50:46 +0200 [thread overview]
Message-ID: <20160610165046.GA18657@angband.pl> (raw)
In-Reply-To: <87twh1t4xv.fsf@thinkpad.rath.org>
On Fri, Jun 10, 2016 at 08:54:36AM -0700, Nikolaus Rath wrote:
> 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).
Where do you get "never" from?
.--====
cp: invalid argument ‘never’ for ‘--reflink’
Valid arguments are:
- ‘auto’
- ‘always’
Try 'cp --help' for more information.
`----
And, as of coreutils 8.25, the default is no reflink, with "never" not being
recognized even as a way to avoid an alias. As far as I remember, this
applies to every past version with support for reflinks too.
--
An imaginary friend squared is a real enemy.
next prev parent reply other threads:[~2016-06-10 16:50 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
2016-06-10 16:50 ` Adam Borowski [this message]
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=20160610165046.GA18657@angband.pl \
--to=kilobyte@angband.pl \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.