On Thu, Oct 3, 2013 at 3:03 AM, Petr Gajdos
On Wed, Oct 02, 2013 at 03:11:58PM -0300, Cristian Rodríguez wrote:
El 02/10/13 15:04, Tomáš Chvátal escribió:
Also possibility is to revert the %fdupes call on the imagemagick to ensure the dup works and just put it in effect later on which should not deem trouble.
I just tried to correct this with btrfstune but can't be issued to a mounted root filesystem.. -_- I suggest to omit the %fdupes call in the package instead.
bnc#841472
%fdupes -s seems to work?
Petr
I assume you don't want to make that change for all packages. How could it be assured that every package with too many hardlinks is converted to use symbolic links? Considering users will sometimes use zypper dup to update from M to M+2 or M+3, how long would you have to leave that workaround in place? Obviously I don't like the approach. I'd rather see "zypper dup" patched to error out if: btrfs is in use for / or /usr, the current kernel is < 3.11 and the repositories it will pull from are >= 13.1. It could just tell the user that "zypper dup" upgrade is not supported for that and they need to download the DVD and upgrade that way. That has the advantage of being a permanent "fix" that won't need to be undone in the future. Then if the kernel is >= 3.11 zypper could check the filesystem and ensure it supports large numbers of hardlinks prior to starting the upgrade. After all, having these users download a DVD is not the end of the world and I would hope anyone running btrfs for / or /usr knew they were taking a risk of not having it go perfectly smoothly. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org