All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: cancel btrfs delete job
Date: Fri, 27 Jun 2014 10:49:40 +1000	[thread overview]
Message-ID: <61052648.lopAtLMs1F@xev> (raw)
In-Reply-To: <pan$6d335$5c2b9a29$9bcb428d$7e0aa9cc@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Thu, 26 Jun 2014 13:25:09 Duncan wrote:
> properly.  And if you do automated snapshots, use a good thinning script 
> to thin them down so you're well under 500. (I've posted figures where 
> even starting with per-minute snapshots, thinning down to 10 minute, then 
> to half hour within the day, then to say 4/day after two days, 1/day 
> after a week, one a week after four weeks, one every 13 weeks aka 
> quarterly after say six months, and clearing them all and relying on off-
> machine backups after a year or 18 months, runs only 250-ish or so, under 
> 300.)

What scripts are people using for this?

I've attached the latest scripts I use for managing BTRFS, they assume that 
the filesystem is mounted on root.  They use /backup for snapshots of root and 
/backup-$DIR for snapshots of /$DIR.  I've also attached the scrub and 
rebalance script I use.

These aren't the greatest scripts, I'll probably write something better 
eventually if no-one else has done so.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

[-- Attachment #2: btrfs-make-snapshot --]
[-- Type: application/x-shellscript, Size: 516 bytes --]

[-- Attachment #3: btrfs-remove-snapshots --]
[-- Type: application/x-shellscript, Size: 705 bytes --]

[-- Attachment #4: btrfs-scrub --]
[-- Type: application/x-shellscript, Size: 102 bytes --]

  parent reply	other threads:[~2014-06-27  0:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 11:47 cancel btrfs delete job Franziska Näpelt
2014-06-26 13:25 ` Duncan
2014-06-26 13:47   ` Franziska Näpelt
2014-06-27  0:49   ` Russell Coker [this message]
2014-06-27  5:26     ` Duncan
  -- strict thread matches above, loose matches on Subject: below --
2014-06-27  5:00 Franziska Näpelt
2014-06-27  5:58 ` Satoru Takeuchi
2014-06-27  8:09   ` Satoru Takeuchi
2014-06-24  7:50 Franziska Näpelt
2014-06-26  7:17 ` Satoru Takeuchi
     [not found]   ` <1403777123.7657.5.camel@hsew-frn.HIPERSCAN>
     [not found]     ` <53AC013E.5000702@jp.fujitsu.com>
2014-06-26 11:34       ` Franziska Näpelt
2014-06-26 23:29         ` Satoru Takeuchi
2014-06-27  8:55           ` Satoru Takeuchi
2014-06-26 11:06 ` Franziska Näpelt
2014-06-26 11:30   ` Duncan

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=61052648.lopAtLMs1F@xev \
    --to=russell@coker.com.au \
    --cc=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 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.