OpenFiler - Revision history

Sstrutt: /* Create iSCSI Disk */ Final corrections

2009-11-24T09:11:14Z

Create iSCSI Disk: Final corrections

← Older revision		Revision as of 09:11, 24 November 2009
Line 54:		Line 54:
	## Go to '''Add Volume''', and find the '''Create a volume in ''volgrp''''' section		## Go to '''Add Volume''', and find the '''Create a volume in ''volgrp''''' section
	## Give the volume a name (eg iSCSIvolgrp), select all space, change Filesystem to '''iSCSI''', and hit '''Create'''		## Give the volume a name (eg iSCSIvolgrp), select all space, change Filesystem to '''iSCSI''', and hit '''Create'''
			# Create the iSCSI Target...
			## Go to '''iSCSI Targets''' and click on '''Add''' to create a IQN with the default name
			## Go to the '''LUN Mapping''' tab, and click '''Map''' to map the volume to the IQN
			## Go to the '''Network ACL''' tab, and ensure that connections are allowed
	# Create network share		# Create network share
	## On '''System''' tab, find '''Network Access Configuration'''		## On '''System''' tab, find '''Network Access Configuration'''

Sstrutt: /* Create iSCSI Disk */ Fixed procedure

2009-11-20T14:52:23Z

Create iSCSI Disk: Fixed procedure

← Older revision		Revision as of 14:52, 20 November 2009
Line 41:		Line 41:

	=== Create iSCSI Disk ===		=== Create iSCSI Disk ===

	~~'''Either there is something missing from this proc, or there's a bug in the current version of code, as the iSCSI share never gets mounted, so isn't returned to a SendTargets query'''~~

	# Login to OpenFiler (user/pass openfiler/password)		# Login to OpenFiler (user/pass openfiler/password)
Line 48:		Line 46:
	## Go to '''Volumes''', and to the '''Create a new volume group''' section		## Go to '''Volumes''', and to the '''Create a new volume group''' section
	## Click on the '''create new physical volumes''' link		## Click on the '''create new physical volumes''' link
	## In the resulting '''Block Device Management''' page, edit the disk that we want to create the iSCSI storage on.		## In the resulting '''Block Device Management''' page, edit the disk that we want to create the iSCSI storage on (should have 0 existing partitions).
	## Find the '''Create a partition in /dev/sd''x''''' section and hit '''Create''' (default options)		## Find the '''Create a partition in /dev/sd''x''''' section and hit '''Create''' (default options)
	# Then create a volume group for iSCSI use...		# Then create a volume group for iSCSI use...
Line 61:		Line 59:
	# Enable iSCSI target		# Enable iSCSI target
	## On '''Services''' tab, '''Enable''' iSCSI target server		## On '''Services''' tab, '''Enable''' iSCSI target server
			## Go to '''Volumes''' and '''iSCSI Targets'''
			## Click on add to create the default name IQN

	== Troubleshooting ==		== Troubleshooting ==

Sstrutt: Added "Overview > Terminology"

2009-11-20T11:22:21Z

Added "Overview > Terminology"

← Older revision		Revision as of 11:22, 20 November 2009
Line 1:		Line 1:
			== Overview ==
			=== Terminology ===
			* '''Physical Volume''' - Assigned space on a physical disk, to be used in a Volume Group
			* '''Volume Group''' - Contains the Physical Volumes from which a Logical Volume can be created
			* '''Logical Volume''' - What's presented to the outside world as storage (LUN)

	== Set-up ==		== Set-up ==
	=== Installation ===		=== Installation ===

Sstrutt: /* High Memory Usage */ Expanded slightly

2009-11-12T09:52:44Z

High Memory Usage: Expanded slightly

← Older revision		Revision as of 09:52, 12 November 2009
Line 59:		Line 59:
	=== High Memory Usage ===		=== High Memory Usage ===
	Openfiler will cache all throughput, so as the NAS is used it will fill available memory. This is normal, and to be expected. Physical memory will be freed as required by other processes. If you suspect a problem, login to the console and run the <code>top</code> command. As long as the amount of swap memory in use is low there is no problem.		Openfiler will cache all throughput, so as the NAS is used it will fill available memory. This is normal, and to be expected. Physical memory will be freed as required by other processes. If you suspect a problem, login to the console and run the <code>top</code> command. As long as the amount of swap memory in use is low there is no problem.

			See https://forums.openfiler.com/viewtopic.php?id=1017 for (a little) more info.

			If running OpenFiler on a VM, you may want to minimise the amount of physical memory assigned to the NAS. In which case keep an eye on the swap usage as you decrease the assigned physical memory, once it begins to rise you've gone a little too far.

	=== Failed to get disk partition information ===		=== Failed to get disk partition information ===

Sstrutt: /* Troubleshooting */ Added "High Memory Usage"

2009-11-12T09:48:48Z

Troubleshooting: Added "High Memory Usage"

← Older revision		Revision as of 09:48, 12 November 2009
Line 57:		Line 57:

	== Troubleshooting ==		== Troubleshooting ==
			=== High Memory Usage ===
			Openfiler will cache all throughput, so as the NAS is used it will fill available memory. This is normal, and to be expected. Physical memory will be freed as required by other processes. If you suspect a problem, login to the console and run the <code>top</code> command. As long as the amount of swap memory in use is low there is no problem.

	=== Failed to get disk partition information ===		=== Failed to get disk partition information ===
	To fix "Failed to get disk partition information" error when mounting iSCSI partition, see [http://ict-freak.nl/2009/03/14/vmware-failed-to-get-disk-partition-information/ this fix].		To fix "Failed to get disk partition information" error when mounting iSCSI partition, see [http://ict-freak.nl/2009/03/14/vmware-failed-to-get-disk-partition-information/ this fix].

Sstrutt: /* Create iSCSI Disk */ Added "proc don't work" note

2009-11-12T08:42:20Z

Create iSCSI Disk: Added "proc don't work" note

← Older revision		Revision as of 08:42, 12 November 2009
Line 35:		Line 35:

	=== Create iSCSI Disk ===		=== Create iSCSI Disk ===

			'''Either there is something missing from this proc, or there's a bug in the current version of code, as the iSCSI share never gets mounted, so isn't returned to a SendTargets query'''

	# Login to OpenFiler (user/pass openfiler/password)		# Login to OpenFiler (user/pass openfiler/password)
	# First create a partition...		# First create a partition...

Sstrutt: /* Set-up */ Addded "Create NFS Disk"

2009-11-12T08:05:47Z

Set-up: Addded "Create NFS Disk"

@@ Line 9: / Line 9: @@
 ## Change line 94 of <code> /opt/openfiler/var/www/includes/network.inc </code> to
 ## <code> exec("sudo ifconfig -a | grep  'eth'",$output); </code>
 === Create iSCSI Disk ===

Sstrutt: /* Create iSCSI Disk */ Minor proc correction

2009-11-11T14:56:27Z

Create iSCSI Disk: Minor proc correction

← Older revision		Revision as of 14:56, 11 November 2009
Line 25:		Line 25:
	# Create network share		# Create network share
	## On '''System''' tab, find '''Network Access Configuration'''		## On '''System''' tab, find '''Network Access Configuration'''
	## Add in the ~~OpenFiler's~~ IP address, etc, and hit '''Update'''		## Add in the local network address, or specify individual iSCSI client IP address, etc, and hit '''Update'''
	# Enable iSCSI target		# Enable iSCSI target
	## On '''Services''' tab, '''Enable''' iSCSI target server		## On '''Services''' tab, '''Enable''' iSCSI target server



	== Troubleshooting ==		== Troubleshooting ==

Sstrutt: Initial creation

2009-11-09T10:27:56Z

Initial creation

New page

== Set-up ==
=== Installation ===
# Download the appropriate appliance from [http://www.openfiler.com/community/download/ OpenFiler]
# Extract, upload to your ESX and '''Add to Inventory''', and start
# The machine will attempt use DHCP to assign an IP
# Browse to the machine, and login using openfiler/password
# If change IP option doesn't appear on '''System''' page, attempt following fix
## Login to console of VM (root, no password)
## Change line 94 of <code> /opt/openfiler/var/www/includes/network.inc </code> to
## <code> exec("sudo ifconfig -a | grep 'eth'",$output); </code>

=== Create iSCSI Disk ===
# Login to OpenFiler (user/pass openfiler/password)
# First create a partition...
## Go to '''Volumes''', and to the '''Create a new volume group''' section
## Click on the '''create new physical volumes''' link
## In the resulting '''Block Device Management''' page, edit the disk that we want to create the iSCSI storage on.
## Find the '''Create a partition in /dev/sd''x''''' section and hit '''Create''' (default options)
# Then create a volume group for iSCSI use...
## Go to '''Volume Groups''' (right-hand menu) and find the '''Create a new volume group''' section
## Give the volume group a name (eg volgrp1), select the partition/physical volume and hit '''Add volume group'''
## Click on the '''create new physical volumes''' link
## Go to '''Add Volume''', and find the '''Create a volume in ''volgrp''''' section
## Give the volume a name (eg iSCSIvolgrp), select all space, change Filesystem to '''iSCSI''', and hit '''Create'''
# Create network share
## On '''System''' tab, find '''Network Access Configuration'''
## Add in the OpenFiler's IP address, etc, and hit '''Update'''
# Enable iSCSI target
## On '''Services''' tab, '''Enable''' iSCSI target server

== Troubleshooting ==
=== Failed to get disk partition information ===
To fix "Failed to get disk partition information" error when mounting iSCSI partition, see [http://ict-freak.nl/2009/03/14/vmware-failed-to-get-disk-partition-information/ this fix].

<pre>
[root@labesx-1 /]# fdisk -l

Disk /dev/sda: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 140 1124518+ 83 Linux
/dev/sda2 141 154 112455 fc VMware VMKCORE
/dev/sda3 155 2610 19727820 5 Extended
/dev/sda5 155 2610 19727788+ fb VMware VMFS

Disk /dev/sdb: 7973 MB, 7973371904 bytes
255 heads, 63 sectors/track, 969 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 76 610438+ 82 Linux swap / Solaris
/dev/sdb2 77 331 2048287+ 83 Linux
/dev/sdb3 332 969 5124735 5 Extended
/dev/sdb5 332 969 5124703+ 83 Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdc: 217.9 GB, 217968541696 bytes
256 heads, 63 sectors/track, 26396 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 26397 212860927+ ee EFI GPT
[root@labesx-1 /]# fdisk /dev/sdc

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.

The number of cylinders for this disk is set to 26396.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdc: 217.9 GB, 217968541696 bytes
256 heads, 63 sectors/track, 26396 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 26397 212860927+ ee EFI GPT

Command (m for help): d
Selected partition 1

Command (m for help): p

Disk /dev/sdc: 217.9 GB, 217968541696 bytes
256 heads, 63 sectors/track, 26396 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System

Command (m for help): p

Disk /dev/sdc: 217.9 GB, 217968541696 bytes
256 heads, 63 sectors/track, 26396 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-26396, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-26396, default 26396):
Using default value 26396

Command (m for help): p

Disk /dev/sdc: 217.9 GB, 217968541696 bytes
256 heads, 63 sectors/track, 26396 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 26396 212857312+ 83 Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): fb
Changed system type of partition 1 to fb (VMware VMFS)

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
</pre>