increased LUN stays same size in FreeNAS

[kalliz]

Hey all,

I'm presenting a LUN (fibre channel) to FreeNAS (11-RC4), which is 4TB.
We now increased this lun to 8TB, but the free space does not change in FreeNAS.
I've tried to reboot and I also tried (probably no use anyway as scsi command?): camcontrol rescan all

Nothing seems to get it to trigger a rescan!

do i need to increase partition manually?

Code:

root@r4-freenas:~ # vi /etc/fstab
freenas-boot/grub	   /boot/grub	  zfs	 rw,noatime	  1	   0
fdescfs /dev/fd fdescfs rw	  0 0
/dev/multipath/disk1p1.eli	  none					swap			sw			  0	   0
~

Thanks for any help!!

 

[Dice]

What do those 4+4TB consists of in terms of drives?
Please provide the output (within code tags) of:
zpool status

 

[kalliz]

Heya,

i found further info:
1. multipathing as such:

Code:

root@r4-freenas:~ # gmultipath status
		   Name   Status  Components
multipath/disk1  OPTIMAL  da2 (ACTIVE)
						  da1 (PASSIVE)

2. from /var/log/messages it looks it can see the full 8TB

Code:

Jun 12 16:15:47 r4-freenas da2: <COMPELNT Compellent Vol Wait> Fixed Direct Access SPC-3 SCSI device
Jun 12 16:15:47 r4-freenas da2: Serial Number 0000557c-0000001f
Jun 12 16:15:47 r4-freenas da2: 400.000MB/s transfers WWNN 0x5000d31000557c02 WWPN 0x5000d31000557c3b PortID 0x30001
Jun 12 16:15:47 r4-freenas da2: Command Queueing enabled
Jun 12 16:15:47 r4-freenas da2: 8388608MB (17179869184 512 byte sectors)

and zpool status gives as such:

Code:

root@r4-freenas:~ # zpool status
  pool: fibre
state: ONLINE
  scan: none requested
config:

		NAME										  STATE	 READ WRITE CKSUM
		fibre										 ONLINE	   0	 0	 0
		  gptid/2f505ef9-4c5f-11e7-8467-0024e8713668  ONLINE	   0	 0	 0

errors: No known data errors

  pool: freenas-boot
state: ONLINE
  scan: none requested
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0
		  da0p2	 ONLINE	   0	 0	 0

errors: No known data errors

i have a feeling i need to increase the partitiopn or something?!
@Dice: no idea what drives are involved. might be any amount of up to 20 disks. storage admin simply increased the LUN that is presented to FreeNAS through FC

 

[kalliz]

here's more (commands taken from other threads)

zpool list shows 4TB

Code:

root@r4-freenas:~ # zpool list
NAME		   SIZE  ALLOC   FREE  EXPANDSZ   FRAG	CAP  DEDUP  HEALTH  ALTROOT
fibre		 3.97T   786G  3.20T		 -	 8%	19%  1.00x  ONLINE  /mnt
freenas-boot  67.5G  1.36G  66.1G		 -	  -	 2%  1.00x  ONLINE  -

camcontrol shows 8TB

Code:

root@r4-freenas:~ # camcontrol readcap da2 -h
Device Size: 8.0 T, Block Length: 512 bytes

gpart show

Code:

root@r4-freenas:~ # gpart show
=>	   34  142081981  da0  GPT  (68G)
		 34	   1024	1  bios-boot  (512K)
	   1058		  6	   - free -  (3.0K)
	   1064  142080944	2  freebsd-zfs  (68G)
  142082008		  7	   - free -  (3.5K)

=>		40  8589934512  multipath/disk1  GPT  (8.0T) [CORRUPT]
		  40		  88				   - free -  (44K)
		 128	 4194304				1  freebsd-swap  (2.0G)
	 4194432  8585740112				2  freebsd-zfs  (4.0T)
  8589934544		   8				   - free -  (4.0K)

 

[kalliz]

from the above I come up with this: https://www.freebsd.org/doc/handbook/disks-growing.html

just surprised there's no autogrow or similar. Just to make sure I'm not doing any daft things here :)

 

[kalliz]

in hindsight: I could have easily created a 2nd lun, present it to FreeNAS and have FreeNAS extend the original 4TB with the new 4TB.
But instead I increased the original LUN.
The effect is the same as if I would have used a virtual FreeNAS and simply increased the virtual disk. So I'm sure there are solutions for it.

Any advise before I take a stab at increasing partition?

 

[SweetAndLow]

You really should not be using this kind of volume with FreeNAS. FreeNAS wants access to the raw disks. You will probably lose the data on this pool eventually. Your ideas of how extending a pool are also incorrect.

To fix your problem I think you can just use gpart to move the 2gb swap to the end of disk then make the zfs partition bigger and zfs should expand into that space.

Sent from my Nexus 5X using Tapatalk

 

[kalliz]

Hey, Thanks for that!!

I was thinking along those lines that FreeNAS needs individual access to disks. In reality my solution is doubled up. A Storage solution (Compellent) that bundles disks in LUNs and then shares it to another storage system. The idea came about since I use FreeNAS with NextCloud at home (access to raw disks) and wanted to replicate the same at work and simply used a free LUN and a free server ... I'll go and re-think it with the team.

I'll still try to fix it up to 8TB anyway just out of interest ... (why not just leave the swap where it is (be happy its ahead of zfs), simply increase the ZFS using gpart)?