From: Russell Coker <russell@coker.com.au>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: subvol copying
Date: Wed, 15 May 2013 15:25:27 +1000 [thread overview]
Message-ID: <201305151525.27913.russell@coker.com.au> (raw)
A user of a workstation has a home directory /home/john as a subvolume. I
wrote a cron job to make read-only snapshots of it under /home/john/backup
which was fortunate as they just ran a script that did something like
"rm -rf ~".
Apart from copying dozens of gigs of data back, is there a good way of
recovering it all? Whatever you suggest isn't going to work for this time
(the copy is almost done) but will be useful for next time.
I'm guessing that I can't delete a subvol that has other subvols under it.
Should I have put the backups under /backup instead so that I could just
delete the corrupted subvol and make a read-write snapshot of the last good
one?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2013-05-15 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 5:25 Russell Coker [this message]
2013-05-15 7:40 ` subvol copying Gabriel de Perthuis
2013-05-15 16:43 ` Chris Murphy
2013-05-15 16:44 ` Harald Glatt
2013-05-15 17:28 ` Chris Murphy
2013-05-15 17:30 ` Harald Glatt
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=201305151525.27913.russell@coker.com.au \
--to=russell@coker.com.au \
--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