aufalien
Patron
- Joined
- Jul 25, 2013
- Messages
- 374
Hi,
HW specs to get them out of the way;
12 bay SuperMicro chassis
12 WD Enterprise 3TB drives
32GB ECC ram
E3 1241v3 @3.5Ghz
FreeNAS 9.2.1.7
I've managed to create a device extent for use in FC target mode, worked well, fairly simple to set up once I got my head around concepts etc...
I'd like to create a file extent in seeing how well they work. Based on what I've read, they provide greater flexibility and more efficiency in terms of resource allocation.
However for the life of me I cannot seem to create a file extent on a volume or a data set.
I'm reading and following the 9.2.1 manual pages 192-193 section 8.7.2.1 and following tables 8.7b and 8.7c, the web site version seems to follow the manual word for word on this topic as well.
My RaidZ2 volume is 10.7TB and I've specified 8TB as a file extent size as I wish to stay within 80% usage. Plus I like round even numbers :)
Attached is a pic of what I've done in creating a file extent on top of a volume.
Below are the log messages resulting from trying to start the iSCSI service;
notifier: ctld: error returned from LUN creation request: ctl_be_block_open: error opening /mnt/data3/san.extent
ctld[19851]: error returned from LUN creation request: ctl_be_block_open: error opening /mnt/data3/san.extent
I was under the impression that when specifying a file extent name and its size, that this file would automatically get created. When would it get created, ie; what kicks off the file creation process?
And words of wisdom are appreciated.
HW specs to get them out of the way;
12 bay SuperMicro chassis
12 WD Enterprise 3TB drives
32GB ECC ram
E3 1241v3 @3.5Ghz
FreeNAS 9.2.1.7
I've managed to create a device extent for use in FC target mode, worked well, fairly simple to set up once I got my head around concepts etc...
I'd like to create a file extent in seeing how well they work. Based on what I've read, they provide greater flexibility and more efficiency in terms of resource allocation.
However for the life of me I cannot seem to create a file extent on a volume or a data set.
I'm reading and following the 9.2.1 manual pages 192-193 section 8.7.2.1 and following tables 8.7b and 8.7c, the web site version seems to follow the manual word for word on this topic as well.
My RaidZ2 volume is 10.7TB and I've specified 8TB as a file extent size as I wish to stay within 80% usage. Plus I like round even numbers :)
Attached is a pic of what I've done in creating a file extent on top of a volume.
Below are the log messages resulting from trying to start the iSCSI service;
notifier: ctld: error returned from LUN creation request: ctl_be_block_open: error opening /mnt/data3/san.extent
ctld[19851]: error returned from LUN creation request: ctl_be_block_open: error opening /mnt/data3/san.extent
I was under the impression that when specifying a file extent name and its size, that this file would automatically get created. When would it get created, ie; what kicks off the file creation process?
And words of wisdom are appreciated.