On Wed, Oct 2, 2013 at 2:14 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
Greg Freemyer said the following on 10/02/2013 12:08 PM:
On Wed, Oct 2, 2013 at 9:34 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
I've never heard of that, can you give references please?
As Carlos said the whole thread is worth reading: http://markmail.org/message/b5zmpqluenaq4fi5
The bug in question for failed RPM install is: https://bugzilla.novell.com/show_bug.cgi?id=835695
I don't know about you, but it seems very strange that a filesystem has a feature that has to be "enabled" before ImageMagick's rpm can be installed. It looks like openSUSE is considering that feature stable enough to enable it by default for 13.1, but I doubt 12.3 ever gets that mount option by default.
I'm thinking that some people involved in this thread haven't paid attention.
I've certainly installed ImageMagic * on BtrFS * without having to adjust the parameters
but as Greg goes on to say
Here's a 4-year thread that discusses it. The default limit is around 300 hardlinks in a single directory.
it strikes me as strange that a package needs to set up more than 300 hard links in a single directory.
Note: you can use btrfstune to enable the relatively new extrefs feature.
I didn't know about that when I installed Imagemagick. Why didn't I have that problem? As I said, this was btrFS with 12.3, new drive. This is the 3.6 kernel here, not the 'its in 3.7 already' in the bug report.
The new extrefs feature solves that but at least for now is not a always available filesystem feature.
So why didn't it happen to me? Perhaps because I have this huge single BtrFS partition.
I think ImageMagick for 13.1 is different from the one for 12.3. Only the one for 13.1 fails to install due to the BtrFS lack of functionality. Here's a brand new thread from factory today: http://markmail.org/message/vbfiw6sximwukofc As of that 3 hour old thread, there is not even a recommended upgrade path for people running 12.3 with btrfs as their system drive and having ImageMagick installed. That means you are exactly the person that will see this zypper dup upgrade failure unless you happened to have already setup the new feature. Notice the that 12.3 kernel can't setup the feature with the filesystem mounted, so at least as of this very second the only choice is to boot a rescue CD/DVD and make the filesystem change, then boot back. Trouble is the 12.3 boot CD/DVD doesn't have userland tools that allow the feature to be enabled. I'm guessing a 13.1 boot CD could be used. Thus as of this minute, the only option for this use case is to download the 13.1 boot CD / DVD and use it to do the upgrade. I assume this will be resolved in the next few weeks, but 13.1 is rapidly approaching release, so they don't have a lot of time left to address it. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org