Date: Mon, 20 Jul 2015 12:06:18 +0100 From: Will Green <will@sundivenetworks.com> To: freebsd-stable@freebsd.org Subject: Re: Problems adding Intel 750 to zfs pool Message-ID: <8BB8F0CB-70D4-4663-AE3C-ECA3ECA99AAD@sundivenetworks.com> In-Reply-To: <55ACBF3C.2020208@multiplay.co.uk> References: <55A9D79E.3070601@techtangents.com> <55ACBF3C.2020208@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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@multiplay.co.uk> = wrote: >=20 > This will almost certainly be due to slow TRIM support on the device. >=20 > Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding = the devices. >=20 > On 18/07/2015 05:35, dylan@techtangents.com wrote: >> Hi, >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> I'm adding the partitions using their gpt names. i.e. >> zpool add zroot log gpt/slog >> zpool add zroot cache gpt/l2arc >>=20 >> 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. >>=20 >> Root is on zfs. >>=20 >> Device was tested to be working on Windows 8.1 on a Dell T1700 = workstation. >>=20 >> Any ideas? >>=20 >> Cheers, >>=20 >> Dylan Just >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8BB8F0CB-70D4-4663-AE3C-ECA3ECA99AAD>