OVHcloud Private Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#8866 — node-584
Incident
Report for Hosted Private Cloud
Resolved
The service automatically switched onto the slave node following a failure.
A few minutes after the switch, the slave made a kernel panic.
^Mpanic[cpu1]/thread=ffffff6262371c00:
fffffe8005ea6e50 zfs:zfs_nfsshare_inited+437cfe2 ()
fffffe8005ea6e90 zfs:dnode_setdirty+dd ()
fffffe8005ea6f00 zfs:dbuf_dirty+369 ()
fffffe8005ea6f70 zfs:dbuf_dirty+308 ()
fffffe8005ea6fe0 zfs:dbuf_dirty+308 ()
fffffe8005ea7050 zfs:dbuf_dirty+308 ()
fffffe8005ea70c0 zfs:dbuf_dirty+308 ()
fffffe8005ea7130 zfs:dbuf_dirty+308 ()
fffffe8005ea71a0 zfs:dbuf_dirty+308 ()
fffffe8005ea71e0 zfs:dnode_setdirty+ce ()
fffffe8005ea7250 zfs:dbuf_dirty+369 ()
fffffe8005ea7280 zfs:dbuf_will_dirty+62 ()
fffffe8005ea72f0 zfs:dmu_write_uio_dnode+9b ()
fffffe8005ea7320 zfs:dmu_write_uio_dbuf+63 ()
fffffe8005ea7520 zfs:zfs_write+972 ()
fffffe8005ea7530 zfs:zfs_shim_write+c ()
fffffe8005ea7580 genunix:fop_write+31 ()
fffffe8005ea7810 nfssrv:rfs3_write+459 ()
fffffe8005ea7b20 nfssrv:common_dispatch+5b8 ()
fffffe8005ea7b30 nfssrv:rfs_dispatch+21 ()
fffffe8005ea7c00 rpcmod:svc_getreq+209 ()
fffffe8005ea7c50 rpcmod:svc_run+124 ()
fffffe8005ea7c80 rpcmod:svc_do_run+88 ()
fffffe8005ea7ec0 nfs:nfssys+16a ()
fffffe8005ea7f10 unix:brand_sys_sysenter+1f2 ()
The service is still running on the slave.
We are checking the master and will switch the service back onto it.
Update(s):
Date: 2013-06-26 11:02:47 UTC
The service is running on the master again and the HA has been reactivated.
A few minutes after the switch, the slave made a kernel panic.
^Mpanic[cpu1]/thread=ffffff6262371c00:
fffffe8005ea6e50 zfs:zfs_nfsshare_inited+437cfe2 ()
fffffe8005ea6e90 zfs:dnode_setdirty+dd ()
fffffe8005ea6f00 zfs:dbuf_dirty+369 ()
fffffe8005ea6f70 zfs:dbuf_dirty+308 ()
fffffe8005ea6fe0 zfs:dbuf_dirty+308 ()
fffffe8005ea7050 zfs:dbuf_dirty+308 ()
fffffe8005ea70c0 zfs:dbuf_dirty+308 ()
fffffe8005ea7130 zfs:dbuf_dirty+308 ()
fffffe8005ea71a0 zfs:dbuf_dirty+308 ()
fffffe8005ea71e0 zfs:dnode_setdirty+ce ()
fffffe8005ea7250 zfs:dbuf_dirty+369 ()
fffffe8005ea7280 zfs:dbuf_will_dirty+62 ()
fffffe8005ea72f0 zfs:dmu_write_uio_dnode+9b ()
fffffe8005ea7320 zfs:dmu_write_uio_dbuf+63 ()
fffffe8005ea7520 zfs:zfs_write+972 ()
fffffe8005ea7530 zfs:zfs_shim_write+c ()
fffffe8005ea7580 genunix:fop_write+31 ()
fffffe8005ea7810 nfssrv:rfs3_write+459 ()
fffffe8005ea7b20 nfssrv:common_dispatch+5b8 ()
fffffe8005ea7b30 nfssrv:rfs_dispatch+21 ()
fffffe8005ea7c00 rpcmod:svc_getreq+209 ()
fffffe8005ea7c50 rpcmod:svc_run+124 ()
fffffe8005ea7c80 rpcmod:svc_do_run+88 ()
fffffe8005ea7ec0 nfs:nfssys+16a ()
fffffe8005ea7f10 unix:brand_sys_sysenter+1f2 ()
The service is still running on the slave.
We are checking the master and will switch the service back onto it.
Update(s):
Date: 2013-06-26 11:02:47 UTC
The service is running on the master again and the HA has been reactivated.