From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: bug#29675: databases should be created with chattr +C Date: Wed, 20 Dec 2017 15:31:12 +0200 Message-ID: <20171220133112.GA16642@macbook41> References: <20171212114608.GB1873@macbook41> <20171213154003.29024f01@scratchpost.org> <87efnpy248.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eReTd-0006nQ-J4 for bug-guix@gnu.org; Wed, 20 Dec 2017 08:32:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eReTa-0003UV-9k for bug-guix@gnu.org; Wed, 20 Dec 2017 08:32:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:34616) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eReTa-0003U9-6N for bug-guix@gnu.org; Wed, 20 Dec 2017 08:32:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eReTa-0007jB-1U for bug-guix@gnu.org; Wed, 20 Dec 2017 08:32:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87efnpy248.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 29675@debbugs.gnu.org --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 20, 2017 at 02:12:39PM +0100, Ludovic Court=C3=A8s wrote: > Hello, >=20 > Danny Milosavljevic skribis: >=20 > > On Tue, 12 Dec 2017 13:46:08 +0200 > > Efraim Flashner wrote: > > > >> We support running GuixSD on top of btrfs, and the prevailing wisdom is > >> to mark databases (sqlite, postgresql, etc.) as 'chattr +C', that is, = as > >> not copy-on-write. It is honored under ext4, but it shouldn't cause any > >> changes. > > > > It sounds reasonable to do that - but I don't think that relational dat= abases are managed by the Guix store. Rather they are in /var or in the ho= me directory. Long story short, it would make sense for Postgres and Sqlit= e upstream to do the chattr +C, if they don't already do it. >=20 > I agree. >=20 > Efraim, unless we have a specific example, I=E2=80=99m inclined to close = it as > =E2=80=9Cnot-a-bug=E2=80=9D, with the understanding that it=E2=80=99s an = upstream issue rather > than something GuixSD-specific. >=20 > How does that sound? >=20 > Ludo=E2=80=99. My intention was that after creating the database in /var that it should get 'chattr +C file', but it actually looks like people are divided between less fragmentation from not CoW for the database or more recovery options from having it CoW and the checksumming, so closing it and leaving it alone for now seems best. --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAlo6Zh4ACgkQQarn3Mo9 g1H7Pw/+NOxEFoq0jPIHF9i3IEdErSo1Z4iS/blFBy6VPk0H2XWty1FsRYIUreJr VTIUI5R57dcNE+2eUR/JH2c5EOvuGdNoQD0FGVEgi8i7SnRsMB09brew9Obo5mj/ kMKsfh+XTxd0Xz2fWXJXxB++8VomzJJXNr8Nxm7LtTq039uyJ6Ez6oqu8a75e5FQ Jrk4NSopM/4se8sncaVo7IaxOaCgGkKynqFYI0oDMUMA0h22C04ZLwCbgxkR6lxs 4ZRVBwkfuG+1KqYTSpIKbzTgb9+Cte4MvCdaIoXsm6wBICMbv566oQbC8eWfORBw 7c8hQ/M9igITYumcxMd7dGgQLD7sewQji8v22LPH9nA8LKUzhi6wnfrEzv4dA7Gt /2lBmtfrBlJkCWbHvOR22NWH8EfOF6HQtqDoSyak0BEkNzGPVN/1kc2dlaQ0KtUO MRfcw+CBXkS+yvof8+Qs1b8ibcGTJPXCj6EVFUGC8DQ/s9HXmOsWIyZb/NfcxYYB Qjdmtccd5HovEYwbogxQG94ngt0Q1CkfXEntq+K/WIlzDGwxtAL1bsNhD+RBuOTd gimeMwcTgFnJH1sxahNKSXX1gBQRlbOX3HlXpAwGuyrRmtMcTecDZvXyva5jWCEa HCffSDYGtZ8fIgeE3WOSpRgFd0ax8Ig7OWk9ndSUq0oFo3qIgwo= =fu5z -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--