From owner-freebsd-current@FreeBSD.ORG  Sun Oct 13 10:53:44 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 12E2CE7F;
 Sun, 13 Oct 2013 10:53:44 +0000 (UTC)
 (envelope-from etnapierala@gmail.com)
Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com
 [IPv6:2a00:1450:4013:c01::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E9BA2D6E;
 Sun, 13 Oct 2013 10:53:43 +0000 (UTC)
Received: by mail-ea0-f173.google.com with SMTP id g10so2788962eak.4
 for <multiple recipients>; Sun, 13 Oct 2013 03:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=WkDrNhmF459yjh82529uVbYFfgScC6xEpBYRqY6IwyM=;
 b=ZDfH6NHSlNYT1brB+VyuL5hsgu+fPX7oCR7sq/T69Xu/wYQhunlK+EkNbPMBUFIWmH
 BY18t+D0s+VQ/pST3gCV9yzedfZ0NIZLpndCPhyikBOIYZg4hlRkXU06gqZ+2ZvNyJID
 /s1giLiPbXcb9AzmyjHvc77/GDX1GYnAShChy71SW6cracFLrWeBaUuh8nzswHCF7E8V
 myILqUScoTiCe8tUlCgwlLjytnjFlAzrkBPNtH7Gepjy0MHPa2+sQJKaE6qazXaNVv+Y
 MPqrjWButp83Ah3LGAkHyc9mYO4cq3DQlcWcuZtf46zLF+GLUmMRFcGJrPUIiEtq6NZi
 b5qQ==
X-Received: by 10.14.178.67 with SMTP id e43mr2286939eem.59.1381661621715;
 Sun, 13 Oct 2013 03:53:41 -0700 (PDT)
Received: from mini.home (adho211.neoplus.adsl.tpnet.pl. [79.184.170.211])
 by mx.google.com with ESMTPSA id a6sm139049073eei.10.1969.12.31.16.00.00
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sun, 13 Oct 2013 03:53:41 -0700 (PDT)
Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <etnapierala@gmail.com>
Content-Type: text/plain; charset=iso-8859-2
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: New iSCSI stack.
From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@freebsd.org>
In-Reply-To: <CAKYr3zwXwiZWBxwzB2UNVNtoe_N93ogvYdLNihpwgA4HG7GDoQ@mail.gmail.com>
Date: Sun, 13 Oct 2013 12:53:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A782312-6655-489D-927D-C8907C1D9883@freebsd.org>
References: <A758F12B-2798-4A90-8C67-88F78B82434D@FreeBSD.org>
 <522A1C73.9030402@mu.org> <A08A0702-86FF-4F05-B007-CF84F80FF8D5@FreeBSD.org>
 <CAKYr3zxdt3x8dqUN3_QTmjTaVEvZ+8KS4rVkiUPUcJQGiseGPQ@mail.gmail.com>
 <CAKYr3zzLUtdpp1V3LH19d26P1ieH_zc88nhTZJuPePCaO_pg1g@mail.gmail.com>
 <CAKYr3zzXsZi-VP44J9bHEsohc0a+Pw5k_nFAsC423BuC-aYWPA@mail.gmail.com>
 <CAKYr3zxEQRJ+2SD-jMgd7EN7n+adxPgKDnyFOy0dmgmCFGfP4Q@mail.gmail.com>
 <A15BF9C8-1F92-4BC1-8251-2509B242CD7C@freebsd.org>
 <CAKYr3zwXwiZWBxwzB2UNVNtoe_N93ogvYdLNihpwgA4HG7GDoQ@mail.gmail.com>
To: Outback Dingo <outbackdingo@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: freebsd-scsi@freebsd.org,
 "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>,
 Alfred Perlstein <bright@mu.org>,
 "freebsd-current@FreeBSD.org" <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Oct 2013 10:53:44 -0000

Wiadomo=B6=E6 napisana przez Outback Dingo <outbackdingo@gmail.com> w =
dniu 11 pa=BC 2013, o godz. 14:37:
> Quick question, is there a specific reason why ctld doesnt create the =
file / device for iscsi, or fc ?
> the previous iscsi would read the config file and create the file / =
device ... it now appears to be a
> manual process.

You mean, the backing files ("path /dev/zvol/whatever", for example), =
right?

I thought about it.  Problem is, while it makes it somewhat easier in =
very simple
situations, it's not very useful in real life - ctld (or CTL) has no =
information what
the permissions should be, should the file be fully or thin provisioned =
(in other
words, whether it supposed to be filled with zeroes, truncated to a =
correct length,
or perhaps it's a ZVOL with reservation set), etc.  And you don't want =
it to create
files when you make a typo in path name.