From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org,Zac Medico <zmedico@gentoo.org>
Subject: Re: [gentoo-dev] News Item: Portage rsync hardlink support
Date: Sun, 08 Jul 2018 11:15:05 +0200 [thread overview]
Message-ID: <3F5A2EBD-675B-46D8-8E3A-FBD1CE83DF28@gentoo.org> (raw)
In-Reply-To: <84a41acf-4b39-fca7-aee5-cefe28331d2a@gentoo.org>
Dnia 8 lipca 2018 09:14:06 CEST, Zac Medico <zmedico@gentoo.org> napisał(a):
>On 07/07/2018 11:53 PM, Michał Górny wrote:
>> Dnia 8 lipca 2018 08:08:31 CEST, Zac Medico <zmedico@gentoo.org>
>napisał(a):
>>> Please review.
>>>
>>> Title: Portage rsync hardlink support
>>> Author: Zac Medico <zmedico@gentoo.org>
>>> Posted: 2018-07-11
>>> Revision: 1
>>> News-Item-Format: 2.0
>>> Display-If-Installed: sys-apps/portage
>>>
>>> For users of the rsync tree, beginning with sys-apps/portage-2.3.42,
>>> the default behavior for sync operations will use hardlinks in order
>>> to ensure that a repository remains in a valid state if something
>>> goes wrong [1]. For example, if signature verification fails during
>a
>>> sync operation, the new hardlink behavior will preserve the previous
>>> state of the repository.
>>>
>>> The new behavior may conflict with configurations that restrict the
>>> use of hardlinks, such as overlay filesystems. Therefore, users will
>>> have to set "sync-allow-hardlinks = no" in repos.conf if they have
>>> a configuration that restricts the use of hardlinks, but this should
>>> not be very common:
>>>
>>> [DEFAULT]
>>> sync-allow-hardlinks = no
>>>
>>> [1] https://bugs.gentoo.org/660410 sys-apps/portage: use rsync
>>> --link-dest to implement atomic repository updates (and abort if
>>> signature verification fails)
>>
>> Is safe git syncing implemented already? If not, maybe finish it
>first and cover both with a single news item. Git is going to be more
>efficient here, so people may want to learn they have an alternative.
>
>Yeah there's already a patch for git sync [1] but I'd rather not make
>this news item more complicated than it needs to be. I wouldn't have
>bothered with a news item except that I want to give people some
>warning
>in case they are using overlayfs [2]. I think the efficiency difference
>between rsync and git here are pretty negligible for most people.
Are you sure about that? That might have been the case so far but this hardlink tree may actually tip the balance.
>
>[1] https://bugs.gentoo.org/660372
>[2]
>https://www.brunsware.de/blog/gentoo/portage-tree-squashfs-overlayfs.html
--
Best regards,
Michał Górny (by phone)
next prev parent reply other threads:[~2018-07-08 9:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 6:08 [gentoo-dev] News Item: Portage rsync hardlink support Zac Medico
2018-07-08 6:53 ` Michał Górny
2018-07-08 7:14 ` Zac Medico
2018-07-08 9:15 ` Michał Górny [this message]
2018-07-08 9:21 ` Zac Medico
2018-07-08 9:30 ` M. J. Everitt
2018-07-08 13:02 ` Kristian Fiskerstrand
2018-07-08 13:56 ` Michał Górny
2018-07-08 18:04 ` Zac Medico
2018-07-08 18:42 ` Michał Górny
2018-07-08 18:57 ` Zac Medico
2018-07-08 20:08 ` Michał Górny
2018-07-08 20:18 ` Zac Medico
2018-07-08 21:11 ` Zac Medico
2018-07-08 21:18 ` Michał Górny
2018-07-08 21:38 ` Zac Medico
2018-07-08 21:50 ` Aaron W. Swenson
2018-07-08 21:59 ` Zac Medico
2018-07-09 5:17 ` Zac Medico
2018-07-09 8:04 ` Kristian Fiskerstrand
2018-07-08 22:00 ` Rich Freeman
2018-07-08 17:34 ` Rich Freeman
2018-07-08 17:43 ` M. J. Everitt
2018-07-08 17:50 ` Kristian Fiskerstrand
2018-07-08 18:10 ` Rich Freeman
2018-07-08 18:31 ` Kristian Fiskerstrand
2018-07-08 19:00 ` Rich Freeman
2018-07-08 9:28 ` Toralf Förster
2018-07-08 9:34 ` Zac Medico
2018-07-08 13:00 ` Kristian Fiskerstrand
2018-07-09 3:21 ` [gentoo-dev] News Item: Portage rsync hardlink support [v2] Zac Medico
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=3F5A2EBD-675B-46D8-8E3A-FBD1CE83DF28@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=zmedico@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox