why is my process always killed

SUSE Linux Enterprise Server SLES Configure-Administer
1

Dear all,

OS is SLES 10 SP4,

before I do df -hT here’s my log for /var/log/messages

Jun 16 21:25:11 suse104-10205-ee-si kernel:
Jun 16 21:25:11 suse104-10205-ee-si kernel: Code: 8b 06 48 89 e6 48 89 54 24 24 c7 44 24 20 02 00 00 00 ba 60
Jun 16 21:25:11 suse104-10205-ee-si kernel: RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff81011f0c3cc8>
Jun 16 21:25:11 suse104-10205-ee-si kernel: CR2: 0000000000000000

when I do a df -hT

suse104-10205-ee-si:~ # df -hT
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/system-root
              ext3    7.8G  3.2G  4.2G  44% /
udev         tmpfs    2.0G  212K  2.0G   1% /dev
/dev/sda1     ext2     69M   11M   55M  16% /boot
/dev/mapper/vg_oracle_base-lv_oracle_base
              ext3    6.9G  2.9G  3.8G  43% /u01
/dev/mapper/vg_datafile-lv_datafile
              ext3    3.0G  1.1G  1.8G  39% /u02
/dev/mapper/vg_fra-lv_fra
              ext3    5.9G  347M  5.3G   7% /u03
Killed

I was tailing /var/log/messages while executing df -hT

Jun 16 21:25:11 suse104-10205-ee-si kernel: CR2: 0000000000000000

Jun 16 21:25:59 suse104-10205-ee-si kernel:  <1>Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
Jun 16 21:25:59 suse104-10205-ee-si kernel: <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Jun 16 21:25:59 suse104-10205-ee-si kernel: PGD 108cfd067 PUD 1096c5067 PMD 0
Jun 16 21:25:59 suse104-10205-ee-si kernel: Oops: 0000 [2]
Jun 16 21:25:59 suse104-10205-ee-si kernel: last sysfs file: /devices/system/cpu/cpu0/cache/index0/shared_cpu_map
Jun 16 21:25:59 suse104-10205-ee-si kernel: CPU 0
Jun 16 21:25:59 suse104-10205-ee-si kernel: Modules linked in: raw ipv6 snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd mptctl ehci_hcd usbcore i2c_piix4 i2c_core snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer ide_cd snd cdrom soundcore snd_page_alloc e1000 ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
Jun 16 21:25:59 suse104-10205-ee-si kernel: Pid: 4614, comm: df Tainted: GF    U 2.6.16.60-0.85.1-default #1
Jun 16 21:25:59 suse104-10205-ee-si kernel: RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Jun 16 21:25:59 suse104-10205-ee-si kernel: RSP: 0018:ffff810108109cc8  EFLAGS: 00010282
Jun 16 21:25:59 suse104-10205-ee-si kernel: RAX: 0000000000000001 RBX: ffff810108109d74 RCX: 0000000000000010
Jun 16 21:25:59 suse104-10205-ee-si kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff88293580
Jun 16 21:25:59 suse104-10205-ee-si kernel: RBP: ffff810108109da8 R08: ffff810108109d74 R09: ffff810108109d48
Jun 16 21:25:59 suse104-10205-ee-si kernel: R10: ffff81011e756007 R11: 000000000050c0a0 R12: ffff810108109ed8
Jun 16 21:25:59 suse104-10205-ee-si kernel: R13: 000000000050c080 R14: 0000000000000000 R15: 0000000000000002
Jun 16 21:25:59 suse104-10205-ee-si kernel: FS:  00002ae2d62d06e0(0000) GS:ffffffff8039c000(0000) knlGS:0000000000000000
Jun 16 21:25:59 suse104-10205-ee-si kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 16 21:25:59 suse104-10205-ee-si kernel: CR2: 0000000000000000 CR3: 00000001097b0000 CR4: 00000000000006e0
Jun 16 21:25:59 suse104-10205-ee-si kernel: Process df (pid: 4614, threadinfo ffff810108108000, task ffff810106707850)
Jun 16 21:25:59 suse104-10205-ee-si kernel: Stack: 0000000100000000 0000000500000009 0000000000000001 ffff81011e756000
Jun 16 21:25:59 suse104-10205-ee-si kernel:        ffff810108109e48 ffffffff80186d05 ffff81011f192188 0000000000000000
Jun 16 21:25:59 suse104-10205-ee-si kernel:        ffff81011f765dc0 ffffffff8017c51e
Jun 16 21:25:59 suse104-10205-ee-si kernel: Call Trace: <ffffffff80186d05>{mntput_no_expire+29}
Jun 16 21:25:59 suse104-10205-ee-si kernel:        <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
Jun 16 21:25:59 suse104-10205-ee-si kernel:        <ffffffff8016d074>{vfs_statfs+108} <ffffffff8016d1d5>{vfs_statfs_native+19}
Jun 16 21:25:59 suse104-10205-ee-si kernel:        <ffffffff8016d2a0>{sys_statfs+63} <ffffffff80229694>{tty_write+552}
Jun 16 21:25:59 suse104-10205-ee-si kernel:        <ffffffff8010aba2>{system_call+126}
Jun 16 21:25:59 suse104-10205-ee-si kernel:
Jun 16 21:25:59 suse104-10205-ee-si kernel: Code: 8b 06 48 89 e6 48 89 54 24 24 c7 44 24 20 02 00 00 00 ba 60
Jun 16 21:25:59 suse104-10205-ee-si kernel: RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff810108109cc8>
Jun 16 21:25:59 suse104-10205-ee-si kernel: CR2: 0000000000000000

how do I resolve such error?

many thanks in advance

2

Which version of the ‘coreutils’ package (from which df originates) do you
have and is it the latest available?

Can you duplicate this on a similar box? On a newer box (SLES 10 is
really old)?

Does it happen if you do not use the -T option with ‘df’?

Does it happen if you put explicitly to /u03 or /u02 or other filesystems
on your system, rather than trying to get information on all of them?

What do you get as output from the ‘mount’ command?

Commands to run:

rpm -q

zypper up coreutils

df -hT /u02

df -hT /u03

df -hT /

mount

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

3 
zypper up coreutils
suse104-10205-ee-si:~ # zypper up coreutils
Restoring system sources...
Parsing metadata for SUSE Linux Enterprise Server 10 SP4...
Parsing RPM database...
Summary:
Nothing to do.
suse104-10205-ee-si:~ # df -hT /u02
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/vg_datafile-lv_datafile
              ext3    3.0G  1.1G  1.8G  39% /u02
suse104-10205-ee-si:~ # df -hT /u03
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/vg_fra-lv_fra
              ext3    5.9G  347M  5.3G   7% /u03

suse104-10205-ee-si:~ # df -hT /
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/system-root
              ext3    7.8G  3.2G  4.2G  44% /
suse104-10205-ee-si:~ #
suse104-10205-ee-si:~ # mount
/dev/mapper/system-root on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda1 on /boot type ext2 (rw,acl,user_xattr)
/dev/mapper/vg_oracle_base-lv_oracle_base on /u01 type ext3 (rw,acl,user_xattr)
/dev/mapper/vg_datafile-lv_datafile on /u02 type ext3 (rw,acl,user_xattr)
/dev/mapper/vg_fra-lv_fra on /u03 type ext3 (rw,acl,user_xattr)
securityfs on /sys/kernel/security type securityfs (rw)
yury on /media/sf_yury type vboxsf (gid=106,rw)

Does it happen if you do not use the -T option with ‘df’?
it happens when I did not specified the device or mount point as can be shown above,

suse104-10205-ee-si:~ # df /
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/system-root
                       8156088   3348132   4393648  44% /
suse104-10205-ee-si:~ # df -T /
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/mapper/system-root
              ext3     8156088   3348132   4393648  44% /
suse104-10205-ee-si:~ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/system-root
                       8156088   3348132   4393648  44% /
udev                   2026836       212   2026624   1% /dev
/dev/sda1                69972     10300     56059  16% /boot
/dev/mapper/vg_oracle_base-lv_oracle_base
                       7216632   2939136   3910904  43% /u01
/dev/mapper/vg_datafile-lv_datafile
                       3088240   1125796   1805568  39% /u02
/dev/mapper/vg_fra-lv_fra
                       6184512    355012   5515340   7% /u03
Killed
suse104-10205-ee-si:~ # df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/mapper/system-root
              ext3     8156088   3348140   4393640  44% /
udev         tmpfs     2026836       212   2026624   1% /dev
/dev/sda1     ext2       69972     10300     56059  16% /boot
/dev/mapper/vg_oracle_base-lv_oracle_base
              ext3     7216632   2939136   3910904  43% /u01
/dev/mapper/vg_datafile-lv_datafile
              ext3     3088240   1125796   1805568  39% /u02
/dev/mapper/vg_fra-lv_fra
              ext3     6184512    355012   5515340   7% /u03
Killed
suse104-10205-ee-si:~ #

Does it happen if you put explicitly to /u03 or /u02 or other filesystems
on your system, rather than trying to get information on all of them?

it will not happen if I specified the device or mount point

My customer is using SLES 10, so I have no choice but to simulate the environment using virutalbox

many thanks in advance

4

I am guessing one of the following is causing the problem, so let’s test them:

On 06/16/2017 09:34 AM, slesmaster wrote:[color=blue]

securityfs on /sys/kernel/security type securityfs (rw)
yury on /media/sf_yury type vboxsf (gid=106,rw)[/color]

df -hT /sys/kernel/security
df -hT /media/sf_yury

The last one is unfamiliar to me, so my money is on that one since I do
not think the security mountpoint will show up at all (pointless for it to
with ‘df’).

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

5

Also, try it without the T

df -h /media/sf_yury

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

6

Dear ab, you are right

/media/sf_yury is causing error

sudo mount -t vboxsf -o rw,uid=1000,gid=1000 yury /media/sf_yury

I got this message from dmesg

 <1>Unable to handle kernel paging request at 00000000406a3cf0 RIP:
<ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
PGD 10c643067 PUD 0
Oops: 0000 [2]
last sysfs file: /devices/system/cpu/cpu0/cache/index0/shared_cpu_map
CPU 0
Modules linked in: raw snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipv6 af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ide_cd cdrom ehci_hcd mptctl i2c_piix4 e1000 i2c_core usbcore ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
Pid: 4951, comm: df Tainted: GF    U 2.6.16.60-0.85.1-default #1
RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
RSP: 0018:ffff810108171cc8  EFLAGS: 00010282
RAX: 0000000000000001 RBX: ffff810108171d74 RCX: 0000000000000010
RDX: 0000000000000000 RSI: 00000000406a3cf0 RDI: ffffffff88293580
RBP: ffff810108171da8 R08: ffff810108171d74 R09: ffff810108171d48
R10: ffff81010460e007 R11: 00007fff2666d48b R12: ffff810108171ed8
R13: 000000000050c120 R14: 000000000050c000 R15: 0000000000000002
FS:  00002aac57c266e0(0000) GS:ffffffff8039c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000406a3cf0 CR3: 0000000107242000 CR4: 00000000000006e0
Process df (pid: 4951, threadinfo ffff810108170000, task ffff810104696040)
Stack: 0000000100000000 0000000500000009 0000000000000001 ffff81010460e000
       ffff810108171e48 ffffffff80186d05 ffff81011f798188 0000000000000000
       ffff81011ed6adc0 ffffffff8017c51e
Call Trace: <ffffffff80186d05>{mntput_no_expire+29}
       <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
       <ffffffff8016d074>{vfs_statfs+108} <ffffffff8016d1d5>{vfs_statfs_native+19}
       <ffffffff8016d2a0>{sys_statfs+63} <ffffffff802c9d8f>{thread_return+0}
       <ffffffff8016e7b4>{sys_write+69} <ffffffff8010aba2>{system_call+126}

Code: 8b 06 48 89 e6 48 89 54 24 24 c7 44 24 20 02 00 00 00 ba 60
RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff810108171cc8>
CR2: 00000000406a3cf0

tailing /var/log/messages before df

suse104-10205-ee-si:~ # tail -f /var/log/messages
Jun 20 07:30:52 suse104-10205-ee-si kernel:        ffff81011ed6adc0 ffffffff8017c51e
Jun 20 07:30:52 suse104-10205-ee-si kernel: Call Trace: <ffffffff80186d05>{mntput_no_expire+29}
Jun 20 07:30:52 suse104-10205-ee-si kernel:        <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
Jun 20 07:30:52 suse104-10205-ee-si kernel:        <ffffffff8016d074>{vfs_statfs+108} <ffffffff8016d1d5>{vfs_statfs_native+19}
Jun 20 07:30:52 suse104-10205-ee-si kernel:        <ffffffff8016d2a0>{sys_statfs+63} <ffffffff802c9d8f>{thread_return+0}
Jun 20 07:30:52 suse104-10205-ee-si kernel:        <ffffffff8016e7b4>{sys_write+69} <ffffffff8010aba2>{system_call+126}
Jun 20 07:30:52 suse104-10205-ee-si kernel:
Jun 20 07:30:52 suse104-10205-ee-si kernel: Code: 8b 06 48 89 e6 48 89 54 24 24 c7 44 24 20 02 00 00 00 ba 60
Jun 20 07:30:52 suse104-10205-ee-si kernel: RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff810108171cc8>
Jun 20 07:30:52 suse104-10205-ee-si kernel: CR2: 00000000406a3cf0
suse104-10205-ee-si:~ # df /media/sf_yury
Filesystem           1K-blocks      Used Available Use% Mounted on
Killed

after df here’s the log

Jun 20 07:37:34 suse104-10205-ee-si kernel:  <1>Unable to handle kernel paging request at 00000000406a3cf0 RIP:
Jun 20 07:37:34 suse104-10205-ee-si kernel: <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Jun 20 07:37:34 suse104-10205-ee-si kernel: PGD 10c65e067 PUD 0
Jun 20 07:37:34 suse104-10205-ee-si kernel: Oops: 0000 [3]
Jun 20 07:37:34 suse104-10205-ee-si kernel: last sysfs file: /devices/system/cpu/cpu0/cache/index0/shared_cpu_map
Jun 20 07:37:34 suse104-10205-ee-si kernel: CPU 0
Jun 20 07:37:34 suse104-10205-ee-si kernel: Modules linked in: raw snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipv6 af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ide_cd cdrom ehci_hcd mptctl i2c_piix4 e1000 i2c_core usbcore ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
Jun 20 07:37:34 suse104-10205-ee-si kernel: Pid: 4954, comm: df Tainted: GF    U 2.6.16.60-0.85.1-default #1
Jun 20 07:37:34 suse104-10205-ee-si kernel: RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Jun 20 07:37:34 suse104-10205-ee-si kernel: RSP: 0018:ffff81011fe85cc8  EFLAGS: 00010282
Jun 20 07:37:34 suse104-10205-ee-si kernel: RAX: 0000000000000001 RBX: ffff81011fe85d74 RCX: 0000000000000010
Jun 20 07:37:34 suse104-10205-ee-si kernel: RDX: 0000000000000000 RSI: 00000000406a3cf0 RDI: ffffffff88293580
Jun 20 07:37:34 suse104-10205-ee-si kernel: RBP: ffff81011fe85da8 R08: ffff81011fe85d74 R09: ffff81011fe85d48
Jun 20 07:37:34 suse104-10205-ee-si kernel: R10: ffff81010460e007 R11: 00007ffffce9348b R12: ffff81011fe85ed8
Jun 20 07:37:34 suse104-10205-ee-si kernel: R13: 000000000050c120 R14: 000000000050c000 R15: 0000000000000002
Jun 20 07:37:34 suse104-10205-ee-si kernel: FS:  00002b43e6f476e0(0000) GS:ffffffff8039c000(0000) knlGS:0000000000000000
Jun 20 07:37:34 suse104-10205-ee-si kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jun 20 07:37:34 suse104-10205-ee-si kernel: CR2: 00000000406a3cf0 CR3: 000000010c436000 CR4: 00000000000006e0
Jun 20 07:37:34 suse104-10205-ee-si kernel: Process df (pid: 4954, threadinfo ffff81011fe84000, task ffff8101057e1040)
Jun 20 07:37:34 suse104-10205-ee-si kernel: Stack: 0000000100000000 0000000500000009 0000000000000001 ffff81010460e000
Jun 20 07:37:34 suse104-10205-ee-si kernel:        ffff81011fe85e48 ffffffff80186d05 ffff81011f798188 0000000000000000
Jun 20 07:37:34 suse104-10205-ee-si kernel:        ffff81011ed6adc0 ffffffff8017c51e
Jun 20 07:37:34 suse104-10205-ee-si kernel: Call Trace: <ffffffff80186d05>{mntput_no_expire+29}
Jun 20 07:37:34 suse104-10205-ee-si kernel:        <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
Jun 20 07:37:34 suse104-10205-ee-si kernel:        <ffffffff8016d074>{vfs_statfs+108} <ffffffff8016d1d5>{vfs_statfs_native+19}
Jun 20 07:37:34 suse104-10205-ee-si kernel:        <ffffffff8016d2a0>{sys_statfs+63} <ffffffff802c9d8f>{thread_return+0}
Jun 20 07:37:34 suse104-10205-ee-si kernel:        <ffffffff8016e7b4>{sys_write+69} <ffffffff8010aba2>{system_call+126}
Jun 20 07:37:34 suse104-10205-ee-si kernel:
Jun 20 07:37:34 suse104-10205-ee-si kernel: Code: 8b 06 48 89 e6 48 89 54 24 24 c7 44 24 20 02 00 00 00 ba 60
Jun 20 07:37:34 suse104-10205-ee-si kernel: RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff81011fe85cc8>
Jun 20 07:37:34 suse104-10205-ee-si kernel: CR2: 00000000406a3cf0
7

I find the following

suse104-10205-ee-si:~ # dmesg | grep vboxsf
vboxsf: module not supported by Novell, setting U taint flag.
vboxsf: no version for "VBoxGuest_RTMemTmpFree" found: kernel tainted.
vboxsf: Successfully loaded version 5.1.12 (interface 0x00010004)
<ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Modules linked in: raw snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipv6 af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ide_cd cdrom ehci_hcd mptctl i2c_piix4 e1000 i2c_core usbcore ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
       <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff81011fe85cc8>
<ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Modules linked in: raw snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipv6 af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ide_cd cdrom ehci_hcd mptctl i2c_piix4 e1000 i2c_core usbcore ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
       <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff810108171cc8>
<ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
Modules linked in: raw snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipv6 af_packet vboxsf vboxguest dock button battery ac apparmor usbhid loop ohci_hcd snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc ide_cd cdrom ehci_hcd mptctl i2c_piix4 e1000 i2c_core usbcore ext3 jbd ata_piix ahci libata dm_snapshot edd dm_mod fan thermal processor sg mptspi mptscsih mptbase scsi_transport_spi piix sd_mod scsi_mod ide_disk ide_core
RIP: 0010:[<ffffffff8828db81>] <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45}
       <ffffffff8017c51e>{link_path_walk+214} <ffffffff8828c111>{:vboxsf:sf_get_volume_info+52}
RIP <ffffffff8828db81>{:vboxsf:VbglR0SfFsInfo+45} RSP <ffff81011fe85cc8>
suse104-10205-ee-si:~ #
8

If your VirtualBox version (I presume you’re using that anyway) is
anything new at all, its inability to work on SLES 10 is probably not
that surprising. Have you tried SLES 12 SP2, or even SLES 11 SP4?
Alternatively, don’t let ‘df’ work on just any filesystem but instead ask
it explicitly for what you care about.

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

9

Dear ab, it does not have any issue with SuSe 11 SP4. I guest we have to be realistic about too old software. There bound to be a lot of problems.

thanks