Search results

  1. V

    Solved [Solved] I/O fencing. Device not configured

    Re: I/O fencing. Device not configured I found out that this is a firmware issue. The newer disks do not have this issue. From our analysis we see that disk firmware prior to 2004 has this problem. Solution: update the firmware of the disk. Thanks, Vadiraj
  2. V

    PCI driver load is degrading the performance of other device

    Hi, I've ported a NVRAM PCI card driver from Linux to freebsd FreeBSD. The issue I'm facing is, once the driver module is loaded all other related device start performing very bad along with this device. Details below. It's a NVRAM card, hence the storage device is created through the PCI...
  3. V

    Solved [Solved] I/O fencing. Device not configured

    I noticed that the device gets into this if the disks were reserved by another node during bootup. To get around with this is to ensure no reservations are held during a node or a partner bootup. I'm trying to understand which layer and why this happens even when the reservations on the disk are...
  4. V

    Solved [Solved] I/O fencing. Device not configured

    Hi, I'm trying I/O fencing on FreeBSD 9 using sg_persist command. The testing is on ZFS pools. For simplicity I'm trying on a single disk pool. Here is what I'm doing for fencing. Node A: sg_persist --out --register --param-sark=123abc /dev/da1 sg_persist --out --preempt-abort...
  5. V

    vnode_if.h missing from FreeBSD 9.0-BETA1 #0: Thu Jul 28 16:34:16 UTC 2011

    add SRCS+=vnode_if.h I know this is closed, but I think the right answer for this is, add vnode_if.h to your SRCS parameter in your Makefile.
Back
Top