Andrey Borzenkov said the following on 02/25/2013 09:20 AM:
On Mon, Feb 25, 2013 at 5:30 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
The articles I find on BtrFS snapshots all tell me how great this mechanism is and how to use it and set it up. But it seems already set up and working even without me doing anything to initiate it. There are hundreds of sub-directories under /.snapshot and they are filling up.
I believe .snapshot directory is used by snapper. Do you have it installed and enabled?
Its installed, yes, but I don't know what you mean by 'enabled'. I see # grep -R snapper /etc/*cron* /etc/cron.daily/suse.de-snapper:# get information from /etc/sysconfig/snapper /etc/cron.daily/suse.de-snapper:if [ -f /etc/sysconfig/snapper ] ; then /etc/cron.daily/suse.de-snapper: . /etc/sysconfig/snapper /etc/cron.daily/suse.de-snapper:# run snapper for all configs /etc/cron.daily/suse.de-snapper: . /etc/snapper/configs/$CONFIG /etc/cron.daily/suse.de-snapper: snapper --config=$CONFIG --quiet cleanup number /etc/cron.daily/suse.de-snapper: snapper --config=$CONFIG --quiet cleanup timeline /etc/cron.daily/suse.de-snapper: snapper --config=$CONFIG --quiet cleanup empty-pre-post /etc/cron.hourly/suse.de-snapper:# get information from /etc/sysconfig/snapper /etc/cron.hourly/suse.de-snapper:if [ -f /etc/sysconfig/snapper ] ; then /etc/cron.hourly/suse.de-snapper: . /etc/sysconfig/snapper /etc/cron.hourly/suse.de-snapper:# run snapper for all configs /etc/cron.hourly/suse.de-snapper: . /etc/snapper/configs/$CONFIG /etc/cron.hourly/suse.de-snapper: snapper --config=$CONFIG --quiet create --description="timeline" --cleanup-algorithm="timeline" Oh My! I'm ovverwhelmed! I wans't aware of all that! The hourly create ... WOW!
They are even filling up with stuff that comes from the NFS mounted stuff under /home !
Not sure about NFS, but on btrfs snapshots are point in time view of the whole filesystem (subvolume). They do not actually take up as much space as it seems.
Two points: Yes, I understand COW, but they ARE taking up space! Yes, they are taking images of the NFS mounted. So far as I can read the config, that seems to be what the config allows. But I'm still confused/unenlightened about what some of the config CAN do. I've got some reseaching to do ...
I'm concerned because this is eating away at my small disk. Every time I do an zypper update this grows.
That supports my idea that you have snapper active.
Agreed. A side note: We have a large AIX setup. I used to administer it. (I still get lookins but its not my full time job any more.) I was glad when Linux acquired the LVM type of management I had grown used to ;-) One thing I liked was the way that the patches and updates could be rolled back so easily or 'committed'. It seems this is now part of what snapper lets us do with Linux ... if I can only figure out how....
If I try to delete I get a message telling me that the files are on a write-protected file system!
btrfs snapshots can be both read-only and writable. Probably snapper creates RO snapshots (makes sense in this case).
You probably should use snapper to manage those snapshots in this case.
So this isn't really a BtrFS issue as such ... -- Vegetables are not food; vegetables are what food eats. Fruit are vegetables that fool you by tasting good. Fish are fast-moving vegetables. Mushrooms are what grows on vegetables when food's done with them. -- Meat Eater's Credo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org