On Mar 19, 2013, at 6:35 PM, Jeremy Chadwick <j...@koitsu.org> wrote:
> On Tue, Mar 19, 2013 at 06:18:06PM +0100, Michael Landin Hostbaek wrote:
> The kernel panic is happening in NFS-related code. Rick Macklem (and/or
> John Baldwin) should be able to help with this; I've CC'd both here.
OK, thanks.
>
> You're going to need to provide the following details:
>
> 1. Contents of /etc/rc.conf
sshd_enable="YES"
ntpdate_enable="YES"
ntpdate_hosts="xx.xx.xx.xx"
fsck_y_enable="YES"
named_enable="YES"
dumpdev="AUTO"
nfs_client_enable="YES"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
ifconfig_em0="inet xx.xx.xx.xx netmask 255.255.255.0 broadcast xx.xx.xx.xx"
defaultrouter="xx.xx.xx.xx"
hostname="xxxxxxxx"
cloned_interfaces="vlanXXXX"
ifconfig_vlanXXXX="inet xx.xx.xx.xx netmask 255.240.0.0 broadcast xx.xx.xx.xx
vlan XXXX vlandev em0"
apache22_enable="YES"
pureftpd_enable="YES"
revealcloud_enable=YES
> 2. Contents of /etc/sysctl.conf (if modified)
vm.pmap.shpgperproc=250
> 3. Contents of /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/mirror/gm0s1a / ufs rw 1
1
/dev/mirror/gm0s1b none swap sw 0 0
/dev/mirror/gm0s1d /var ufs rw 2
2
/dev/mirror/gm0s1e /logs ufs rw 2
2
/dev/mirror/gm0s1f /extra ufs rw 2
2
/dev/mirror/gm0s1g /usr ufs rw 2
2
proc /proc procfs rw 0 0
xx.xx.xx.xx:/zpool-000xxx/www /mnt/www nfs rw 0 0
xx.xx.xx.xx:/zpool-000xxx/data /mnt/data nfs rw,tcp 0 0
linproc /compat/linux/proc linprocfs rw 0 0
> 4. ifconfig -a
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:25:90:79:a5:ac
inet xx.xx.xx.xx netmask 0xffffff00 broadcast xx.xx.xx.xx
inet6 xxxxxx::a5ac%em0 prefixlen 64 scopeid 0x1
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:25:90:79:a5:ad
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xb
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vlanXXXX: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:25:90:79:a5:ac
inet xx.xx.xx.xx netmask 0xfff00000 broadcast xx.xx.xx.xx
inet6 xxxxx:::5ac%vlanXXXX prefixlen 64 scopeid 0xc
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: XXXX parent interface: em0
> 5. OS used by the NFS server, and all configuration details pertaining
> to that system
This is a hosted service, so I do not have access to this - though I believe
this is a ZFS fs.
Here's more info about the product: http://help.ovh.co.uk/Nas
>
> You may also be asked to upgrade to 9.1-STABLE, as there may be fixes
> for whatever this is in base/stable/9 that are not in -RELEASE, but this
> is speculative on my part.
That is not a problem. I would simply like to confirm the issue, before
upgrading.
Thanks,
/mich
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
