linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Roman Mamedov <rm@romanrm.net>, John Stoffel <john@stoffel.org>,
	Mateusz Korniak <mateusz-lists@ant.gliwice.pl>,
	Ron Leach <ronleach@tesco.net>,
	linux-raid@vger.kernel.org
Subject: Re: Recovery on new 2TB disk: finish=7248.4min (raid1)
Date: Mon, 01 May 2017 21:12:54 +0100	[thread overview]
Message-ID: <877f20jpyx.fsf@esperi.org.uk> (raw)
In-Reply-To: <59061BFF.2070503@youngman.org.uk> (Wols Lists's message of "Sun, 30 Apr 2017 18:16:47 +0100")

On 30 Apr 2017, Wols Lists verbalised:

> On 30/04/17 17:10, Nix wrote:
>> This is a one-off with tooling to manage it: from my perspective, I just
>> kick off the autobuilders etc and they'll automatically use transient
>> space for objdirs. (And obviously this is all scripted so it is no
>> harder than making or removing directories would be: typing 'mktransient
>> foo' to automatically create a dir in transient space and set up a bind
>> mount to it -- persisted across boots -- in the directory' foo' is
>> literally a few letters more than typing 'mkdir foo'.)
>
> This sounds like me with tmpfs. Okay, mine don't persist across reboots,
> but if it's in your build scripts, can't they create a tmpfs and do the
> builds in that?

Even though I have 128GiB RAM, I don't want a tmpfs for everything
(though I use it for a lot, oh yes). Some of the transient stuff is
things like QEMU CoW disk images that I don't want to lose on every
reboot (though rebuilding them is not too annoying, it is not totally
ignorable either); other stuff is things like vapoursynth intermediates
which can easily exceed 500GiB, which are only ever read once but
nonetheless just won't fit.

-- 
NULL && (void)

  reply	other threads:[~2017-05-01 20:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 21:57 Recovery on new 2TB disk: finish=7248.4min (raid1) Ron Leach
2017-04-27 14:25 ` John Stoffel
2017-04-27 14:43   ` Reindl Harald
2017-04-28  7:05     ` Ron Leach
2017-04-27 14:54   ` Mateusz Korniak
2017-04-27 19:03     ` John Stoffel
2017-04-27 19:42       ` Reindl Harald
2017-04-28  7:30         ` Mateusz Korniak
2017-04-30 12:04       ` Nix
2017-04-30 13:21         ` Roman Mamedov
2017-04-30 16:10           ` Nix
2017-04-30 16:47             ` Roman Mamedov
2017-05-01 21:13               ` Nix
2017-05-01 21:44                 ` Anthony Youngman
2017-05-01 21:46                 ` Roman Mamedov
2017-05-01 21:53                   ` Anthony Youngman
2017-05-01 22:03                     ` Roman Mamedov
2017-05-02  6:10                       ` Wols Lists
2017-05-02 10:02                         ` Nix
2017-05-01 23:26                   ` Nix
2017-04-30 17:16             ` Wols Lists
2017-05-01 20:12               ` Nix [this message]
2017-04-27 14:58 ` Mateusz Korniak
2017-04-27 19:01   ` Ron Leach
2017-04-28  7:06     ` Mateusz Korniak

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=877f20jpyx.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=antlists@youngman.org.uk \
    --cc=john@stoffel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mateusz-lists@ant.gliwice.pl \
    --cc=rm@romanrm.net \
    --cc=ronleach@tesco.net \
    /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).