Re: [vserver] hashify

From: Herbert Poetzl <herbert_at_13thfloor.at>
Date: Tue 20 Mar 2018 - 22:14:03 GMT
Message-ID: <20180320221403.GE11055@MAIL.13thfloor.at>

On Tue, Mar 20, 2018 at 03:03:30PM -0600, Sandino Araico Snchez wrote:
> On 18/03/18 10:10, Tor Rune Skoglund wrote:

>> If nothing is there in the code today to handle such issues,
>> what is the right way to deal with it:

>> 1) Don't care, as any problems arising from any possibly
>> broken in-vm hardlinks are so rare that side-effects of it
>> "never" happens?

>> 2) Patch the vhashify code so that files that are already
>> hardlinks inside a vm will not be hashified? (As suggested
>> above)

I think that is already done to some degree ...
(Daniel for sure has all the details :)

>> 3) Patch the CoW code so that it handles files that was
>> originally hardlinked in the vm to be restored as hardlinked
>> also when CoW does its work?

> Patch de CoW code so that it breaks the hard link only when
> the hard-linked other file is outside the VM.

Good luck with finding the 'other' file(s) ...

> Hard links inside the VM should be preserved as such.

Best,
Herbert

>> 4) Don't use hashify?

>> What do you suggest? Anyone with any experiences to share?

>> BR, Tor Rune Skoglund, trs@swi.no

> --
> Sandino Araico Snchez
> http://sandino.net
Received on Tue Mar 20 22:10:09 2018

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Tue 20 Mar 2018 - 22:10:09 GMT by hypermail 2.1.8