Talk:SAN Box used via iSCSI - Revision history

404 Error at 05:22, 15 November 2011

2011-11-15T05:22:24Z

Oleg: Reverted edits by Mpsii (talk) to last revision by 404 Error

2011-11-15T04:27:08Z

Reverted edits by Mpsii (talk) to last revision by 404 Error

Mpsii at 17:40, 14 November 2011

2011-11-14T17:40:13Z

Mpsii: /* Solaris 11 Release */ new section

2011-11-14T17:39:10Z

‎Solaris 11 Release: new section

404 Error at 15:33, 25 June 2011

2011-06-25T15:33:23Z

404 Error: moved Talk:SAN Box to Talk:SAN Box used via iSCSI: Better title :-)

2011-06-24T23:49:31Z

moved Talk:SAN Box to Talk:SAN Box used via iSCSI: Better title :-)

404 Error at 22:30, 24 June 2011

2011-06-24T22:30:27Z

404 Error at 03:52, 22 June 2011

2011-06-22T03:52:37Z

404 Error at 03:32, 22 June 2011

2011-06-22T03:32:25Z

404 Error: Created page with "Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on."

2011-06-19T14:41:08Z

Created page with "Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on."

New page

Explicit device-thresholds seems to be useless, Solaris powers down everything it can. Should try an explicit device-thresholds with system-threshold always-on.

← Older revision		Revision as of 05:22, 15 November 2011
Line 10:		Line 10:
	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.		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.
	* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?		* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?
		+
		+
		+	----
		+
		+
		+	* device-thresholds: Solaris respects power savings requirements so yes if it can it will, my goald here was an attempt to control the delays. Some green drives ignore them.
		+	* tpg: same here, the target listen for connections on all addresses... It sounds like a bug! Functional descriptions are not the same than the seen behaviours.
		+	* I did't use fdisk I give the whole disk to eat to ZFS and it deals nicely with it (a GPT table is created automatically).
		+	* 4k sectors: Solaris seems to handle 4k sectors (at the condition the drive does not lie on the physical sector size). I would say that iSCSI should pay attention ("direct" access), impacts on an access through a zvol on a pool is still a very good question.
		+
		+	--404

← Older revision		Revision as of 04:27, 15 November 2011
Line 10:		Line 10:
	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.		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.
	* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?		* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?
−
−
−	~~Have you updated this box to the Solaris 11 Released version?~~
−
−
−	~~Any other reports of additional/different hardware setups? This setup is about $1,000 US. Though the motherboard is now kinda hard to find.~~

← Older revision		Revision as of 17:40, 14 November 2011
Line 11:		Line 11:
	* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?		* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?

−	~~== Solaris 11 Release ==~~

	Have you updated this box to the Solaris 11 Released version?		Have you updated this box to the Solaris 11 Released version?
		+
		+
		+	Any other reports of additional/different hardware setups? This setup is about $1,000 US. Though the motherboard is now kinda hard to find.

← Older revision		Revision as of 17:39, 14 November 2011
Line 10:		Line 10:
	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.		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.
	* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?		* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?
		+
		+	== Solaris 11 Release ==
		+
		+	Have you updated this box to the Solaris 11 Released version?

← Older revision		Revision as of 15:33, 25 June 2011
Line 9:		Line 9:

	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.		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.
		+	* What about 4k sector alignment required by new hard-drives? iSCSI is transparent for that?

← Older revision		Revision as of 22:30, 24 June 2011
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.

← Older revision		Revision as of 03:52, 22 June 2011
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, Bug?	+	* Even with tpg defined, a target still listens on all NICs, but the port seems to taken into account....... Bug?

← Older revision		Revision as of 03:32, 22 June 2011
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, Bug?