Difference between revisions of "Talk:SAN Box used via iSCSI"
From Funtoo Linux
| Line 1: | Line 1: | ||
* Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on. | * Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on. | ||
* Even with tpg defined, a target still listens on all NICs, but the port seems to taken into account....... Bug? | * Even with tpg defined, a target still listens on all NICs, but the port seems to taken into account....... Bug? | ||
| + | * Why format does protest with: | ||
| + | <pre> | ||
| + | WARNING - This disk may be in use by an application that has | ||
| + | modified the fdisk table. Ensure that this disk is | ||
| + | not currently in use before proceeding to use fdisk | ||
| + | </pre> | ||
| + | |||
| + | Thus requiring to manually create a partition with format -> fdisk before being partitioned? ZFS/COMSTAR bug? It does not seems to be a thin provisioning issue at first glance. | ||
Revision as of 22:30, 24 June 2011
- Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on.
- Even with tpg defined, a target still listens on all NICs, but the port seems to taken into account....... Bug?
- Why format does protest with:
WARNING - This disk may be in use by an application that has
modified the fdisk table. Ensure that this disk is
not currently in use before proceeding to use fdisk
Thus requiring to manually create a partition with format -> fdisk before being partitioned? ZFS/COMSTAR bug? It does not seems to be a thin provisioning issue at first glance.
