Hot answers tagged zfs
Ok so it turns out this is a bug with the bxe driver in FreeBSD 10.0-Release specifically The bxe(4) driver can cause packet corruption when TSO (TCP Segmentation Offload) feature is enabled. This feature is enabled by default and can be disabled by using a -tso parameter of ifconfig(8). It can be specified in rc.conf(5) like the following: ...
Ok, never mind what I said in my other answer. You won't be able to boot into single-user mode if you are having problems with ZFS partitions anyway. What's funny is after I posted my answer, I had a problem with power again and I couldn't boot into my system, just like your problem. So here is what I did to get back in. I used a FreeBSD 10.0-RELEASE Live ...
It's better to use whole-disks with ZFS, when possible. There's no need to partition in your use case.
try with: zpool import -nfF rpool if you don't see any critical error, try to use the previous command without n option zpool import -fF rpool
Ok, so this is definitely due to my inexperience with ZFS. Unlike a traditional file system where you can reference a particular partition from any context, ZFS seems to retain the exact information used to reference the data location no matter where it is loaded from. For example, I created the zpool and referenced the device by from OSX by "/dev/disk0s6" ...
Looks to me more like a net-snmp problem. More specifically, a 32 bit limit in the MIB. Look for some details in http://sourceforge.net/p/net-snmp/patches/959/. There are a few other pages relating to this problem, easily googled. I have a similar graph problem with a server running ext4, with a 12TB disk (used for Bacula backups). Still searching for a ...
iozone will operate in the current directory by default. If you wish to test your ZFS pool, change directories to the relevant directory containing the pol or child filesystems, then execute iozone.
Only top voted, non community-wiki answers of a minimum length are eligible