freebsd stable - Jul 2015 - Problems adding Intel 750 to zfs pool

This will almost certainly be due to slow TRIM support on the device.

Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding the 
devices.

On 18/07/2015 05:35, dylan at techtangents.com wrote:
> Hi,
>
> I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running 
> FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. 
> Apologies if this is the wrong mailing list, or if this has been fixed 
> in STABLE since the beta.
>
> Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 
> 357GB for l2arc. Adding the slog partition to the pool takes about 2 
> minutes - machine seems hung during that time. Ping works, but I can't 
> open another ssh session.
>
> Adding the l2arc doesn't seem to complete - it's been going 10
minutes
> now and nothing. Ping works, but I can't log in to the local console 
> or another ssh session.
>
> I'm adding the partitions using their gpt names. i.e.
> zpool add zroot log gpt/slog
> zpool add zroot cache gpt/l2arc
>
> The system BIOS is up-to-date. The OS was a fresh 10.1 install, then 
> freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms.
>
> Root is on zfs.
>
> Device was tested to be working on Windows 8.1 on a Dell T1700 
> workstation.
>
> Any ideas?
>
> Cheers,
>
> Dylan Just
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"

I wonder if this is connected to NVMe?

Our SATA Intel DC S3500 drives (which are not that different to the 750s) TRIM
much more quickly.

What does camcontrol think the secure erase time should be? For a 600GB S3500
camcontrol accurately gives the secure erase time as 4 minutes:

# camcontrol security ada0

erase time                4 min
enhanced erase time       4 min

Trimming drives before addition to a system is definitely worthwhile.

Will
> On 20 Jul 2015, at 10:28, Steven Hartland <killing at
multiplay.co.uk> wrote:
> 
> This will almost certainly be due to slow TRIM support on the device.
> 
> Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding the
devices.
> 
> On 18/07/2015 05:35, dylan at techtangents.com wrote:
>> Hi,
>> 
>> I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320
running FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think.
Apologies if this is the wrong mailing list, or if this has been fixed in STABLE
since the beta.
>> 
>> Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and
357GB for l2arc. Adding the slog partition to the pool takes about 2 minutes -
machine seems hung during that time. Ping works, but I can't open another
ssh session.
>> 
>> Adding the l2arc doesn't seem to complete - it's been going 10
minutes now and nothing. Ping works, but I can't log in to the local console
or another ssh session.
>> 
>> I'm adding the partitions using their gpt names. i.e.
>> zpool add zroot log gpt/slog
>> zpool add zroot cache gpt/l2arc
>> 
>> The system BIOS is up-to-date. The OS was a fresh 10.1 install, then
freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms.
>> 
>> Root is on zfs.
>> 
>> Device was tested to be working on Windows 8.1 on a Dell T1700
workstation.
>> 
>> Any ideas?
>> 
>> Cheers,
>> 
>> Dylan Just
>> 
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"