Date: Wed, 7 Apr 2021 20:26:44 +0200 From: <driesm.michiels@gmail.com> To: "'George Mitchell'" <george+freebsd@m5p.com>, "'freebsd ports'" <freebsd-ports@freebsd.org> Subject: RE: Begone, accursed poudriere partitions! Message-ID: <002401d72bdb$901115f0$b03341d0$@gmail.com> In-Reply-To: <d81f6c2c-c08b-5e61-42a3-5a7e84d31aaf@m5p.com> References: <d81f6c2c-c08b-5e61-42a3-5a7e84d31aaf@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-ports@freebsd.org = <owner-freebsd-ports@freebsd.org> > On Behalf Of George Mitchell > Sent: Wednesday, 7 April 2021 20:18 > To: freebsd ports <freebsd-ports@freebsd.org> > Subject: Begone, accursed poudriere partitions! >=20 > On one occasion, probably a couple of years ago, I tried poudriere = out. > I decided it was too heavy for my use case and uninstalled it. Ever = since, > though, every time my build machine reboots, *something* recreates a = whole > poudriere tree on my ZFS file system, with a total of ten mountpoints = littering > my daily report (though apparently only 139K of actual data). Then I = have to > repeat a ritual of "chflags -R noschg", "rm -r", "zfs umount $x" for = each of the > mount points. So what you happen to do is manually unmount each ZFS dataset. That does not mean the ZFS datasets are gone or wont be mounted on the = next (re)boot. As long as the datasets exist and canmount=3Don, it will get mounted = every time. The easiest fix is to delete the zfs datasets that poudriere created. You can find the correct dataset with # zfs list And then most probably # zfs destroy -r zroot/poudriere >=20 > How do I stop them from coming back from the dead? -- = George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002401d72bdb$901115f0$b03341d0$>