Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Dec 2013 11:25:25 +0100 (CET)
From:      Richard Kojedzinszky <krichy@cflinux.hu>
To:        krad <kraduk@gmail.com>
Cc:        FreeBSD FS <freebsd-fs@freebsd.org>
Subject:   Re: ssd for zfs
Message-ID:  <alpine.BSF.2.00.1312021124580.52215@pi.nmdps.net>
In-Reply-To: <CALfReyegX_8UarSQMsPo8wvwN_99pRMaQA_Q3bX=sfZubwbGMw@mail.gmail.com>
References:  <alpine.BSF.2.00.1311270946260.70091@pi.nmdps.net> <03CB6E4FFD454EBA9E416813A5187C9F@multiplay.co.uk> <CALfReyegX_8UarSQMsPo8wvwN_99pRMaQA_Q3bX=sfZubwbGMw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Dear,

I also have a separate cache device for the pool. Thanks. I would like to 
use this only for log.

Regards,

Kojedzinszky Richard

On Mon, 2 Dec 2013, krad wrote:

> you also want to look at your workloads on the pool, if you are not doing lots of async writes, you may well be better off using it as an l2arc device. Ideally you should have separate devices, but you could partition the ssd and use
> it as l2arc and zill, but that isnt best practice, but there are many people who do that out there with varying mileage depending on their workloads.
> 
> 
> On 28 November 2013 12:51, Steven Hartland <killing@multiplay.co.uk> wrote:
>       FreeBSD has TRIM support and some disks have very slow TRIM support.
>
>       Try disabling TRIM support in /boot/loader.conf
>       vfs.zfs.trim.enabled=0
>
>       Also check to see if your seeing ashift 12 as I suspect thats actually
>       a 4k not 512b device. This can be confirmed by looking at the boot
>       output.
>
>          Regards
>          Steve
>       ----- Original Message ----- From: "Richard Kojedzinszky" <krichy@cflinux.hu>
>       To: <freebsd-fs@freebsd.org>
>       Sent: Wednesday, November 27, 2013 8:51 AM
>       Subject: ssd for zfs
> 
>
>             Dear fs developers,
>
>             Probably this is not the best list to report my issue, but please forward it to where it should get.
>
>             I bought an SSD for my ZFS filesystem to use it as a ZIL. I've tested it under linux, and found that it can handle around 1400 random synchronized write IOPS. Then I placed it into my freebsd 9.2 box, and after
>             attaching it as a ZIL, my zpool only performs 100 (!) write iops. I've attached it to an AHCI controller and to an LSI 1068 controller, on both it behaves the same. So I expect that something in the scsi layer
>             is different, FreeBSD is handling this device slower, but actually it can handle the 1400 iops as tested under linux.
>
>             Please give some advice where to go, how to debug, and how to improve FreeBSD's performance with this drive.
>
>             The device is:
>             # camcontrol identify ada3
>             pass4: <STEC MACH16 M16SD2S-50UI 00000299> ATA-8 SATA 2.x device
>             pass4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes)
>
>             protocol              ATA/ATAPI-8 SATA 2.x
>             device model          STEC MACH16 M16SD2S-50UI
>             firmware revision     00000299
>             serial number         STM0001680E8
>             WWN                   5000a7203006f8e5
>             media serial number   STEC MACH16 M16SD2S-50UI STM00
>             cylinders             16383
>             heads                 15
>             sectors/track         63
>             sector size           logical 512, physical 512, offset 0
>             LBA supported         97696368 sectors
>             LBA48 supported       97696368 sectors
>             PIO supported         PIO4
>             DMA supported         WDMA2 UDMA6
>             media RPM             non-rotating
>
>             Feature                      Support  Enabled   Value           Vendor
>             read ahead                     yes yes
>             write cache                    yes yes
>             flush cache                    yes yes
>             overlap                        no
>             Tagged Command Queuing (TCQ)   no no
>             Native Command Queuing (NCQ)   yes 32 tags
>             SMART                          yes yes
>             microcode download             yes yes
>             security                       yes no
>             power management               yes yes
>             advanced power management      no no
>             automatic acoustic management  no no
>             media status notification      no no
>             power-up in Standby            yes no
>             write-read-verify              no no
>             unload                         no yes
>             free-fall                      no no
>             Data Set Management (DSM/TRIM) yes
>             DSM - max 512byte blocks       yes              8
>             DSM - deterministic read       yes              any value
>             Host Protected Area (HPA)      yes      no      97696368/97696368
>             HPA - Security                 no
>
>             Regards,
>
>             Kojedzinszky Richard
>             _______________________________________________
>             freebsd-fs@freebsd.org mailing list
>             http://lists.freebsd.org/mailman/listinfo/freebsd-fs
>             To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
> 
> 
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise
> disseminating it or any information contained in it.
> In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
> or return the E.mail to postmaster@multiplay.co.uk.
> 
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
> 
> 
> 
>
From owner-freebsd-fs@FreeBSD.ORG  Mon Dec  2 11:06:31 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5BBF2A42
 for <freebsd-fs@freebsd.org>; Mon,  2 Dec 2013 11:06:31 +0000 (UTC)
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com
 [209.85.160.49])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 28F11191D
 for <freebsd-fs@freebsd.org>; Mon,  2 Dec 2013 11:06:30 +0000 (UTC)
Received: by mail-pb0-f49.google.com with SMTP id jt11so18422331pbb.8
 for <freebsd-fs@freebsd.org>; Mon, 02 Dec 2013 03:06:24 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=Zw5f6IJzb9ZFXi1IlFV7gsxrhgyt5gZTOrjcDILFZz4=;
 b=aIXzrzMnCEJNWrn4ED3ZRMnn2cMsp2SsTu4GoFy6jHzoXe+h1bugX8iCmCX+RSw1Pq
 YSJhBs8DeEg72samJQwIpqPD1mtjPTfMblXSQpyGzVP3NfNVV44krkXMU8gLaJj5W41X
 QOuWSO77JEKGHdm1Zb5IRdoizQ6YtlT//4mb00l0ibSWSMyX3newwbqyKuvQAKExvhVq
 P4vuODaBjjHycID4NtBzhtEUeqkUluMsfFO6wlUPjZoHn1Rxu6uogsbPq3SL4T++T9bd
 FO8Qznnc6k0/xDTIy7UscSj44KPAv/+wzh5FfwHPEaSr2u6Zs2HVvWm2iFyOR/eR+UAL
 hyYQ==
X-Gm-Message-State: ALoCoQlaXcYe9fukdqIJDjyxzxZAckCqRiBzQpT0JkvXkPxjzcvllB4wJ8r7Arsq/M+HV9u3comD
MIME-Version: 1.0
X-Received: by 10.66.146.199 with SMTP id te7mr67612193pab.106.1385982076296; 
 Mon, 02 Dec 2013 03:01:16 -0800 (PST)
Received: by 10.68.111.100 with HTTP; Mon, 2 Dec 2013 03:01:16 -0800 (PST)
Date: Mon, 2 Dec 2013 12:01:16 +0100
Message-ID: <CAHvs-HVUC_GYrUMzTD_jV0Kyri8iyj_JV=PJdj1ucDeGzwM1=A@mail.gmail.com>
Subject: ZVOL/istgt wrong placed on disk
From: Johan Kooijman <mail@johankooijman.com>
To: freebsd-fs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>;
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 11:06:31 -0000

Hi all,

The issue I'm having is the same as discussed over here:
http://freebsd.1045724.n5.nabble.com/zvol-and-zfs-send-no-file-on-the-receiving-side-td5024476.html
.

I've added the zfs path to my istgt.conf config and are now stuck with this
setup:

[root@san-head1 ~]# zfs list
NAME        USED  AVAIL  REFER  MOUNTPOINT
tank       25.6T  4.74T  3.93T  /tank
tank/fish  21.7T  26.4T    16K  -

[root@san-head1 ~]# grep LUN0 /usr/local/etc/istgt/istgt.conf
    LUN0                     Storage /tank/fish 21T

[root@san-head1 ~]# ls -lh /tank/fish
-rw-r--r--  1 root  wheel    21T Dec  2 11:57 /tank/fish

Now.. it works, it exports to my virtualized setup, but I can't snapshot or
anything. Is there a way to get this situation restored to the way it
should be?

-- 
Met vriendelijke groeten / With kind regards,
Johan Kooijman

T +31(0) 6 43 44 45 27
E mail@johankooijman.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1312021124580.52215>