[opensuse] how do I disable snapper?
Hi, yes, I know. I'm a heretic. How do I disable snapper completely? ...why? I am running 5 systems running Leap 15.0, and one VM running tumbleweed. The tumbleweed VM is the only one actually using BTRFS (and I'll have something to say about that later). So on my actual "production" systems, all I get from snapper are log entries telling me that / is not btrfs - which I just happen to know already. On the TW VM, I just had a "zypper up" die on me with out of disk space - snapper snapshots accounting for over half of the filesystem's space (more than 10G). So here I am thinking "maybe these snapshots are a bad idea on a linux flavor that gets almost completely reinstalled sometimes more than once per week?" (tumbleweed snapshots...) So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all". So let me ask again - how can I get rid of snapper? Uninstalling stuff only makes it come back through dependencies... cheers MH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Jul 12, 2019 at 10:56 AM Mathias Homann <Mathias.Homann@opensuse.org> wrote:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
There was recent thread on how to disable them.
So let me ask again - how can I get rid of snapper? Uninstalling stuff only makes it come back through dependencies...
Just delete snapper config for root. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg. Cheers Mathias -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least. For systems without btrfs, taboo snapper and it will not be reinstalled. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least.
For systems without btrfs, taboo snapper and it will not be reinstalled.
snapper was never installed on any of my Leap systems (no btrfs), I have never had to lock it or anything. I think it is dragged in if you install btrfs{progs,maintenance}. (which I don't). -- Per Jessen, Zürich (17.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 12.04, Per Jessen wrote:
Carlos E. R. wrote:
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least.
For systems without btrfs, taboo snapper and it will not be reinstalled.
snapper was never installed on any of my Leap systems (no btrfs), I have never had to lock it or anything. I think it is dragged in if you install btrfs{progs,maintenance}. (which I don't).
No, all systems get snapper installed. In theory XFS can do it. Example: Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 12/07/2019 12.04, Per Jessen wrote:
Carlos E. R. wrote:
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least.
For systems without btrfs, taboo snapper and it will not be reinstalled.
snapper was never installed on any of my Leap systems (no btrfs), I have never had to lock it or anything. I think it is dragged in if you install btrfs{progs,maintenance}. (which I don't).
No, all systems get snapper installed. In theory XFS can do it.
Hmm, snapper is not one of those packages I regularly deselect, I think it was simply not installed.
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed. -- Per Jessen, Zürich (18.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 13.05, Per Jessen wrote:
Carlos E. R. wrote:
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed.
Not by me! Several people have been hit with that bug, posts in this list. Same situation, no btrfs partition at all. They are installed by default on all systems. If they are not on your systems, I wonder why. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 12/07/2019 13.05, Per Jessen wrote:
Carlos E. R. wrote:
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed.
Not by me!
Several people have been hit with that bug, posts in this list. Same situation, no btrfs partition at all. They are installed by default on all systems. If they are not on your systems, I wonder why.
Like I wrote in my first reply, I don't install them. They are on our standard list of installation adjustments. -- Per Jessen, Zürich (18.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 13.16, Per Jessen wrote:
Carlos E. R. wrote:
On 12/07/2019 13.05, Per Jessen wrote:
Carlos E. R. wrote:
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed.
Not by me!
Several people have been hit with that bug, posts in this list. Same situation, no btrfs partition at all. They are installed by default on all systems. If they are not on your systems, I wonder why.
Like I wrote in my first reply, I don't install them. They are on our standard list of installation adjustments.
So you remove them, as I thought. For everybody else that doesn't seek and destroy them on purpose, they are installed. I haven't because I have a thought on the backburner to create a compressed btrfs partition for trying, or to support external media that might get by. Ie, I haven't taken manual action to remove them because "just in case". The default patterns install them. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-12-19 07:25]:
On 12/07/2019 13.16, Per Jessen wrote:
Carlos E. R. wrote:
On 12/07/2019 13.05, Per Jessen wrote:
Carlos E. R. wrote:
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed.
Not by me!
Several people have been hit with that bug, posts in this list. Same situation, no btrfs partition at all. They are installed by default on all systems. If they are not on your systems, I wonder why.
Like I wrote in my first reply, I don't install them. They are on our standard list of installation adjustments.
So you remove them, as I thought. For everybody else that doesn't seek and destroy them on purpose, they are installed. I haven't because I have a thought on the backburner to create a compressed btrfs partition for trying, or to support external media that might get by. Ie, I haven't taken manual action to remove them because "just in case".
The default patterns install them.
just as it does for ntfs and ext2 and fat and ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 13.29, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [07-12-19 07:25]:
On 12/07/2019 13.16, Per Jessen wrote:
Carlos E. R. wrote:
On 12/07/2019 13.05, Per Jessen wrote:
Carlos E. R. wrote:
Example:
Subject: [Bug 1096589] At start of "zypper dup" snapper.py and btrfs-defrag-plugin peg CPU at 100% for minutes when there are no btrfs partitions. <http://bugzilla.suse.com/show_bug.cgi?id=1096589>
Perhaps not the best example, you clearly have e.g. btrfsprogs installed.
Not by me!
Several people have been hit with that bug, posts in this list. Same situation, no btrfs partition at all. They are installed by default on all systems. If they are not on your systems, I wonder why.
Like I wrote in my first reply, I don't install them. They are on our standard list of installation adjustments.
So you remove them, as I thought. For everybody else that doesn't seek and destroy them on purpose, they are installed. I haven't because I have a thought on the backburner to create a compressed btrfs partition for trying, or to support external media that might get by. Ie, I haven't taken manual action to remove them because "just in case".
The default patterns install them.
just as it does for ntfs and ext2 and fat and ...
xfsprogs was not deffault. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Freitag, 12. Juli 2019, 12:04:19 CEST schrieb Per Jessen:
Carlos E. R. wrote:
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least.
For systems without btrfs, taboo snapper and it will not be reinstalled.
snapper was never installed on any of my Leap systems (no btrfs), I have never had to lock it or anything. I think it is dragged in if you install btrfs{progs,maintenance}. (which I don't).
I just removed btrfsprogs and btrfsmaintenance but unless I lock them they come back with "zypper dup"... cheers MH -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Mathias Homann wrote:
Am Freitag, 12. Juli 2019, 12:04:19 CEST schrieb Per Jessen:
Carlos E. R. wrote:
On 12/07/2019 10.29, Mathias Homann wrote:
Am 2019-07-12 09:56, schrieb Mathias Homann:
So then I'm thinking "having a pre and a post snapshot after every single update doesn't put much trust in those updates at all".
Just to illustrate my point: uninstall joe, install it again - four snapshots with a total size of 5 meg.
You simply need a much bigger root partition. 100 gigs at least.
For systems without btrfs, taboo snapper and it will not be reinstalled.
snapper was never installed on any of my Leap systems (no btrfs), I have never had to lock it or anything. I think it is dragged in if you install btrfs{progs,maintenance}. (which I don't).
I just removed btrfsprogs and btrfsmaintenance but unless I lock them they come back with "zypper dup"...
I do usually lock those two, yes. -- Per Jessen, Zürich (19.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Freitag, 12. Juli 2019, 11:24:59 CEST schrieb Carlos E. R.:
You simply need a much bigger root partition. 100 gigs at least.
please read this out loud, slowly, and let it sink in. And anyone who still believes in btrfs: do the same, twice. Cheers MH -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[Sorry for cross post, but I think, this discussion belongs to factory] Am Freitag, 12. Juli 2019, 13:13:58 CEST schrieb Mathias Homann:
Am Freitag, 12. Juli 2019, 11:24:59 CEST schrieb Carlos E. R.:
You simply need a much bigger root partition. 100 gigs at least.
please read this out loud, slowly, and let it sink in.
And anyone who still believes in btrfs: do the same, twice.
What I find ridiculous is, that it's the installation default. Of course, none of the about 100 openSUSE installations, that I care about (and did the installation), have btrfs roots. I use xfs¹. The only systems, that cross my site and use btrfs roots were installed by others, *less* informed users. What's interesting here: those, who are typically not capable of dealing with related issues use it, because they accepted the defaults. In that way, openSUSE becomes a (failed) technology presentation for them, before they go somewhere else. What does openSUSE want to prove with this policy? "We (about to) master a technology, that most probably *will* fall on your feet, or at least provide regular work at moments, where you can afford it fewest at all? Puzzled, Pete ¹) with 2 calculated deficits only: it cannot be shrunken, and dropbox will fail on it (for silly reasons, they insist running on ext4 file systems only. Obviously, they still have too many Linux customers..). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Hans-Peter Jansen <hpj@urpla.net> [07-12-19 13:16]:
[Sorry for cross post, but I think, this discussion belongs to factory]
Am Freitag, 12. Juli 2019, 13:13:58 CEST schrieb Mathias Homann:
Am Freitag, 12. Juli 2019, 11:24:59 CEST schrieb Carlos E. R.:
You simply need a much bigger root partition. 100 gigs at least.
please read this out loud, slowly, and let it sink in.
And anyone who still believes in btrfs: do the same, twice.
What I find ridiculous is, that it's the installation default. Of course, none of the about 100 openSUSE installations, that I care about (and did the installation), have btrfs roots. I use xfs¹.
The only systems, that cross my site and use btrfs roots were installed by others, *less* informed users. What's interesting here: those, who are typically not capable of dealing with related issues use it, because they accepted the defaults. In that way, openSUSE becomes a (failed) technology presentation for them, before they go somewhere else.
What does openSUSE want to prove with this policy? "We (about to) master a technology, that most probably *will* fall on your feet, or at least provide regular work at moments, where you can afford it fewest at all?
the newest install standard unless it has changed since last week was to make the entire install btrfs which, provided your allocated disk space is not very restrictive, should alleviate the full root file system problem. the entire install shares disk space rather than one particular "partition". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 13:40, Patrick Shanahan wrote:
the newest install standard unless it has changed since last week was to make the entire install btrfs which, provided your allocated disk space is not very restrictive, should alleviate the full root file system problem. the entire install shares disk space rather than one particular "partition".
Ah. Didn't I say, some years ago, that the BtrFS attitude was "One File System to Rule Them All" -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mathias Homann wrote:
Hi,
yes, I know. I'm a heretic.
How do I disable snapper completely?
You can disable the zypper-snapper connection via rpm -e snapper-zypp-plugin As an alternative, because the most annoying thing is the small installs that trigger a snapper run, edit /etc/snapper/zypp-plugin.conf and remove the line with the star as match pattern: <?xml version="1.0" encoding="utf-8"?> <snapper-zypp-plugin-conf> <!-- List of solvables. If the zypp commit transaction includes any solvable listed below, snapper will create pre and post snapshots. The match attribute defines whether the pattern is a Unix shell-style wildcard ("w") or a Python regular expression ("re"). If any of the matching solvables is marked as important, the snapshots are also marked as important. --> <solvables> <solvable match="w" important="true">kernel-*</solvable> <solvable match="w" important="true">dracut</solvable> <solvable match="w" important="true">glibc</solvable> <solvable match="w" important="true">systemd*</solvable> <solvable match="w" important="true">udev</solvable> <!-- <solvable match="w">*</solvable> --> </solvables> </snapper-zypp-plugin-conf> Then you'd only get the important ones. If you don't want any, I assume just remove the configuration for your root partition, see man page snapper under 'delete-config' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/12/2019 02:56 AM, Mathias Homann wrote:
Hi,
yes, I know. I'm a heretic.
How do I disable snapper completely?
...why?
I am running 5 systems running Leap 15.0, and one VM running tumbleweed.
The tumbleweed VM is the only one actually using BTRFS (and I'll have something to say about that later).
So on my actual "production" systems, all I get from snapper are log entries telling me that / is not btrfs - which I just happen to know already.
On systems WITHOUT btrfs, simply # zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0 -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2019 18.33, David C. Rankin wrote:
On 07/12/2019 02:56 AM, Mathias Homann wrote:
Hi,
yes, I know. I'm a heretic.
How do I disable snapper completely?
...why?
I am running 5 systems running Leap 15.0, and one VM running tumbleweed.
The tumbleweed VM is the only one actually using BTRFS (and I'll have something to say about that later).
So on my actual "production" systems, all I get from snapper are log entries telling me that / is not btrfs - which I just happen to know already.
On systems WITHOUT btrfs, simply
# zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0
Yes, but I don't remove other filesystem types I don't use, just in case I want to use them one day, or somebody brings a disk in that format. The problem is that btrfs comes with invasive tools. Like causing zypper dup to go 100% cpu and lock for long time doing things btrfs related when there is no btrfs installed. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [07-13-19 08:44]:
On 12/07/2019 18.33, David C. Rankin wrote:
On 07/12/2019 02:56 AM, Mathias Homann wrote:
Hi,
yes, I know. I'm a heretic.
How do I disable snapper completely?
...why?
I am running 5 systems running Leap 15.0, and one VM running tumbleweed.
The tumbleweed VM is the only one actually using BTRFS (and I'll have something to say about that later).
So on my actual "production" systems, all I get from snapper are log entries telling me that / is not btrfs - which I just happen to know already.
On systems WITHOUT btrfs, simply
# zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0
Yes, but I don't remove other filesystem types I don't use, just in case I want to use them one day, or somebody brings a disk in that format.
The problem is that btrfs comes with invasive tools. Like causing zypper dup to go 100% cpu and lock for long time doing things btrfs related when there is no btrfs installed.
that would/should be worthy of a bug report. app should fail if no btrfs fs is present rather than consume unreal amounts of processing time. bug report needed. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/07/2019 16.18, Patrick Shanahan wrote:
* Carlos E. R. <> [07-13-19 08:44]:
On 12/07/2019 18.33, David C. Rankin wrote:
On systems WITHOUT btrfs, simply
# zypper rm btrfsmaintenance btrfsprogs btrfsprogs-udev-rules libbtrfs0
Yes, but I don't remove other filesystem types I don't use, just in case I want to use them one day, or somebody brings a disk in that format.
The problem is that btrfs comes with invasive tools. Like causing zypper dup to go 100% cpu and lock for long time doing things btrfs related when there is no btrfs installed.
that would/should be worthy of a bug report. app should fail if no btrfs fs is present rather than consume unreal amounts of processing time. bug report needed.
There is bug report, on 42.3, which was closed the other day automatically and I reopened it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 07/13/2019 09:35 AM, Carlos E. R. wrote:
There is bug report, on 42.3, which was closed the other day automatically and I reopened it.
Seems the current bug-fix policy regrettably mirrors the whitehouse legal strategy -- delay, run out the clock and hope it goes away... -- David C. Rankin, J.D.,P.E.
Am Samstag, 13. Juli 2019, 20:19:20 CEST schrieb David C. Rankin:
On 07/13/2019 09:35 AM, Carlos E. R. wrote:
There is bug report, on 42.3, which was closed the other day automatically and I reopened it.
Seems the current bug-fix policy regrettably mirrors the whitehouse legal strategy -- delay, run out the clock and hope it goes away...
I didn't know angela merkel was a contributing opensuse member... -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
David C. Rankin -
Hans-Peter Jansen -
Mathias Homann -
Mathias Homann
-
Patrick Shanahan -
Per Jessen -
Peter Suetterlin