4gb seg fixup, process zfs-fuse

trispad · 08-02-2011, 04:21 PM

Hello All,

I am running xen on a centos 5.6 box as dom0. I have a domU also running centos 5.6 that is running zfs-fuse. On the domU I am getting the following message when I start the zfs-fuse service:

Code:

4gb seg fixup, process zfs-fuse (pid 1540), cs:ip 73:0804c498

I have done some searching and have found posts suggesting that I do the following:

Code:

echo "hwcap 0 nosegneg" > /etc/ld.so.conf.d/libc6-xen.conf

on domU. But there is already a file in /etc/ld.so.conf.d/ that contains this text.

I have also looked at post suggesting moving /usr/lib/tls to /usr/lib/tls.disabled. There is nothing in the /usr/lib/tls directory, so I do not believe that this is the solution.

Of note is that I only see the message for zfs-fuse and not other process. Also if it helps, this a 32bit machine with low memory, 640Mb total, and the domU gets 512.

Please let me know if I can provide further data.

Thanks,

trispad

trispad · 08-09-2011, 02:39 PM

When I run:

Code:

# ldd /sbin/init
        linux-gate.so.1 =>  (0x0050d000)
        libsepol.so.1 => /lib/libsepol.so.1 (0x00101000)
        libselinux.so.1 => /lib/libselinux.so.1 (0x0084c000)
        libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0x00647000)
        libdl.so.2 => /lib/libdl.so.2 (0x007a5000)
        /lib/ld-linux.so.2 (0x00623000)

it shows that libc.so.6 is pointing to the nosegneg version as does

Code:

# ldd /usr/bin/zfs-fuse 
        linux-gate.so.1 =>  (0x00862000)
        librt.so.1 => /lib/i686/nosegneg/librt.so.1 (0x0086a000)
        libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0x007ac000)
        libfuse.so.2 => /lib/libfuse.so.2 (0x0020a000)
        libdl.so.2 => /lib/libdl.so.2 (0x007a5000)
        libz.so.1 => /usr/lib/libz.so.1 (0x007f3000)
        libaio.so.1 => /usr/lib/libaio.so.1 (0x00206000)
        libcrypto.so.6 => /lib/libcrypto.so.6 (0x00b71000)
        libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0x00647000)
        /lib/ld-linux.so.2 (0x00623000)

I am at a loss here. Any ideas?

Thanks,

Trisapd