From: Claudius Ellsel <claudius.ellsel@live.de>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: WG: How to properly setup for snapshots
Date: Mon, 21 Dec 2020 16:11:25 +0000 [thread overview]
Message-ID: <AM9P191MB1650A1159D554207CB5D738AE2C00@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM9P191MB165033908B55F8312178D90AE2CB0@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM>
Next try (this time text only activated) after my second try was treated as spam (this time I at least got a delivery failed message stating so).
The original message does not seem to have made it through, so here I try again.
Von: Claudius Ellsel <claudius.ellsel@live.de>
Gesendet: Donnerstag, 10. Dezember 2020 15:37
An: linux-btrfs@vger.kernel.org <linux-btrfs@vger.kernel.org>
Betreff: How to properly setup for snapshots
Hello,
I recently started setting up btrfs on Ubuntu 20.04 LTS for usage as an SMB share mainly. Currently I am at the stage that I have two disks set up with RAID1 and automatically mounting them on boot with a fstab entry. Also I have setup samba and have transferred data on it.
Now I wanted to create snapshots, but am not sure how exactly that works. The wiki does not say much and information on the internet is not really reliable.
The problem might be that I currently don't have any subvolumes set up at all. Am I still be able to create snapshots in this stage or do I have to create a subvolume first from which snapshots can be created afterwards?
Also I learned about snapper from SUSE which sounds nice, but I don't want to break things while trying to use it.
Unfortunately I am already at a somewhat production stage where I don't want to lose any data.
Hopefully somebody can shed some light on this, maybe we can also add info to the wiki so there is a somewhat "official" source to rely on.
PS: I am not subscribed to this list, hopefully replies will reach me anyway.
Kind regards
Claudius Ellsel
next parent reply other threads:[~2020-12-21 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9P191MB165033908B55F8312178D90AE2CB0@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM>
2020-12-21 16:11 ` Claudius Ellsel [this message]
2020-12-21 17:05 ` WG: How to properly setup for snapshots Remi Gauvin
2020-12-21 17:37 ` Roman Mamedov
2020-12-21 18:14 ` Remi Gauvin
2020-12-21 20:14 ` Goffredo Baroncelli
2020-12-21 20:27 ` Remi Gauvin
2020-12-21 20:52 ` Goffredo Baroncelli
2020-12-21 18:26 ` Andrei Borzenkov
2020-12-21 18:35 ` AW: " Claudius Ellsel
2020-12-21 18:40 ` Andrei Borzenkov
2020-12-21 20:51 ` AW: " Claudius Ellsel
2021-01-06 20:07 ` Ulli Horlacher
2020-12-21 20:24 ` WG: " Goffredo Baroncelli
2020-12-21 18:04 ` AW: " Claudius Ellsel
2020-12-21 18:32 ` Remi Gauvin
2020-12-21 18:39 ` AW: " Claudius Ellsel
2020-12-21 20:45 ` Claudius Ellsel
2020-12-21 23:33 ` Graham Cobb
2020-12-22 15:19 ` AW: " Claudius Ellsel
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=AM9P191MB1650A1159D554207CB5D738AE2C00@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM \
--to=claudius.ellsel@live.de \
--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.