linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Schnelle <niklas@komani.de>
To: CACook@quantum-sci.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Backup Command
Date: Fri, 21 Jan 2011 20:15:34 +0100	[thread overview]
Message-ID: <1295637334.8180.1.camel@pluto> (raw)
In-Reply-To: <201101211107.25039.CACook@quantum-sci.com>

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

Kernel 2.6.32.x is to old for snapshot deletion, you will have to use
something more recent
On Fri, 2011-01-21 at 11:07 -0800, CACook@quantum-sci.com wrote:
> Well thanks to some help from you guys I seem to have my backup server almost fully running and functional with rsync.  Amazing functions, this snapshotting and rsync.
> 
> I still don't know why I cannot remove snapshots though. (Debian Testing with 2.6.32-28)
> 
> And I don't know how to reach out from the backup server to the HTPC and stop MythTV there, so I can export the Mysql database safely, from a cron job on the backup server.  Suggestions?
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2011-01-21 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 19:07 Backup Command CACook
2011-01-21 19:14 ` Goffredo Baroncelli
2011-01-21 19:15 ` Niklas Schnelle [this message]
2011-01-21 19:44 ` Freddie Cash
2011-01-21 21:54   ` CACook
  -- strict thread matches above, loose matches on Subject: below --
2011-01-10 13:25 Carl Cook
2011-01-10 13:36 ` Hubert Kario
2011-01-11 13:54   ` Ivan Labáth
2011-01-11 14:19     ` Hubert Kario
2011-01-11 14:33       ` Ivan Labáth
2011-01-11 14:40         ` Hubert Kario
2011-01-11 14:53           ` Ivan Labáth
2011-01-15  1:17 ` Carl Cook
2011-01-15  5:25   ` cwillu

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=1295637334.8180.1.camel@pluto \
    --to=niklas@komani.de \
    --cc=CACook@quantum-sci.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).