From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Blocket for more than 120 seconds
Date: Sun, 15 Dec 2013 23:08:04 +0000 (UTC) [thread overview]
Message-ID: <pan$9369c$4a56c817$cc0b6bdf$1b4a6541@cox.net> (raw)
In-Reply-To: CAD_cGvHU0yaXj-CzVgNYbeqzu7ZH0mUOiwjT-GmU7F5JTqx=jw@mail.gmail.com
Hans-Kristian Bakke posted on Sun, 15 Dec 2013 15:51:37 +0100 as
excerpted:
> # Regarding torrents and preallocation I have actually turned
> preallocation on specifically in rtorrent thinking that it did btrfs a
> favour like with ext4 (system.file_allocate.set = yes). It is easy to
> turn it off.
> Is the "ideal" solution for btrfs and torrenting (or any other random
> writes to large files) to use preallocation and NOCOW, or use no
> preallocation and NOCOW? I am thinking the first, although I still do
> not understand quite why preallocation is worse than no preallocation
> for btrfs with COW enabled (or is both just as bad?)
I'm not a dev only an admin who follows this list as I run btrfs too, and
thus don't claim to be an expert on the above -- it's mostly echoing what
I've seen here previously.
That said, preallocation with nocow is the choice I'd make here.
Meanwhile, a subpoint I didn't make explicit previously, tho it's a
logical conclusion from the explanation, is that once the writing is
finished and the file becomes like most media files effectively read-
only, no further writes, NOCOW is no longer important. That is, you can
(sequentially) copy the file somewhere else and not have to worry about
it. In fact, that's a reasonably good idea, since NOCOW turns off btrfs
checksumming too, and presumably you're still interested in maintaining
file integrity on the thing.
So what I'd do is setup a torrent download dir (or as I mentioned, a
dedicated partition, since I like that sort of thing because it enforces
size discipline on the stuff I've downloaded but not fully sorted thru...
that's what I do with binary newsgroup downloading, which I've been doing
on and off since well before bittorrent was around), set/mount it NOCOW/
nowdatacow, and use it as a temporary download "cache". Then after a
file is fully downloaded to "cache", I'd copy it off to a final
destination in my normal media partition, ultimately removing my NOCOW
copy.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-12-15 23:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 20:30 Blocket for more than 120 seconds Hans-Kristian Bakke
2013-12-14 21:35 ` Chris Murphy
2013-12-14 23:19 ` Hans-Kristian Bakke
2013-12-14 23:50 ` Chris Murphy
2013-12-15 0:28 ` Hans-Kristian Bakke
2013-12-15 1:59 ` Chris Murphy
2013-12-15 2:35 ` Hans-Kristian Bakke
2013-12-15 13:24 ` Duncan
2013-12-15 14:51 ` Hans-Kristian Bakke
2013-12-15 23:08 ` Duncan [this message]
2013-12-16 0:06 ` Hans-Kristian Bakke
2013-12-16 10:19 ` Duncan
2013-12-16 10:55 ` Hans-Kristian Bakke
2013-12-16 15:00 ` Duncan
2013-12-16 15:18 ` Chris Mason
2013-12-16 16:32 ` Hans-Kristian Bakke
2013-12-16 18:16 ` Chris Mason
2013-12-16 18:22 ` Hans-Kristian Bakke
2013-12-16 18:33 ` Chris Mason
2013-12-16 18:41 ` Hans-Kristian Bakke
2013-12-15 3:47 ` George Mitchell
2013-12-15 23:39 ` Charles Cazabon
2013-12-16 0:16 ` Hans-Kristian Bakke
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='pan$9369c$4a56c817$cc0b6bdf$1b4a6541@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).