From owner-freebsd-current@FreeBSD.ORG Thu Oct 17 01:11:14 2013 Return-Path: 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 AB70AB4E; Thu, 17 Oct 2013 01:11:14 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 65E452704; Thu, 17 Oct 2013 01:11:14 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id vb8so1324596obc.3 for ; Wed, 16 Oct 2013 18:11:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ukFXg9hyM/mVpnmTxymm7E72yqspuyY8FOpqq5IJ9I=; b=vLOevQPjAD/9XahbysPCQ5bzZwDhRQtMMtxsEufUFjq7RMGj+a88S5nY06X6ESJKbu OKudhDkW/9e4TdMVPP8uOcJxklABTK/fmfUpl5kVNaAmJZc/PLukxsOB3xguoq717I0/ v47+8ZXzcmY6BvF0wOvsJnvbXR9B3UpeXYfyygVy8Wc6G4cmrghff42FEu9nmeBxM0Wb NF23fwvwk+vWtRKE4ppbHyQwyRQSVAGx6g62p0vH86JtR3f99X1+7iR/bz5OZ5ys082p nSiQIy3/zubYYNB0qMbcsB1nBPFfLXN3ajZ6o4c3rHsteNAqUvFKy0B0QECuUeKGhRHQ ZorA== MIME-Version: 1.0 X-Received: by 10.182.80.196 with SMTP id t4mr9606568obx.1.1381972273497; Wed, 16 Oct 2013 18:11:13 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Wed, 16 Oct 2013 18:11:13 -0700 (PDT) In-Reply-To: <7c50c939-bfe7-4fcb-b3ef-5c51d4ae8a9c@email.android.com> References: <52571EF6.8010703@gmail.com> <5257DDD1.4070403@gmail.com> <08D4D879-C866-4BEB-BB1D-9579A32F1975@FreeBSD.org> <7c50c939-bfe7-4fcb-b3ef-5c51d4ae8a9c@email.android.com> Date: Wed, 16 Oct 2013 21:11:13 -0400 Message-ID: Subject: Re: [SOLVED] Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 From: Outback Dingo To: "Miguel C." Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current , =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Oct 2013 01:11:14 -0000 On Fri, Oct 11, 2013 at 11:52 PM, Miguel C. wrote: > I updated to alpha5 it is indeed removed. > > Thanks > > > "Edward Tomasz Napiera=B3a" wrote: > >Dnia 11 pa=BC 2013 o godz. 13:15 "Mike C." > >napisa=B3(a): > > > >> > >>> On 10/11/13 09:24, Edward Tomasz Napiera=B3a wrote: > >>>> Wiadomo=B6=E6 napisana przez Mike C. w dniu 10 pa=BC 2013, o godz. 2= 3:41: > >>>> Hi, > >>>> > >>>> I'm running Alpha-2 and wanted to test with iscsi but it seems I > >can't > >>>> start iscsid. > >>>> > >>>> > >>>> $ sudo service iscsid onerestart > >>>> kldload: can't load iscsi: Exec format error > >>>> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi > >>>> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid > >>>> > >>>> > >>>> dmesg shows: > >>>> interface icl.1 already present in the KLD 'kernel'! > >>>> linker_load_file: Unsupported file type > >>> > >>> Do you have "device ctl" in your kernel config? If so, > >>> either remove it (ctl.ko module is automatically loaded > >>> by ctladm), or add "device iscsi". > >> > >> device ctl # CAM Target Layer > >> > >> Seems that GENERIC has it by default! I'll remove and recompile! > > > >Actually, it got removed from GENERIC in 10 some time ago. > Ive actually noticed what i feel is an anomaly with ctladm... i can literally run ctladm create -b block -o file=3D/luns/LUN0 numerous times...... and create a new LUN every time, using the same file. ctladm devlist LUN Backend Size (Blocks) BS Serial Number Device ID san: ~ # ctladm create -b block -o file=3D/mnt/extent6 LUN created successfully backend: block device type: 0 LUN size: 10485760 bytes blocksize 512 bytes LUN ID: 0 Serial Number: MYSERIAL 0 Device ID; MYDEVID 0 san: ~ # ctladm create -b block -o file=3D/mnt/extent6 LUN created successfully backend: block device type: 0 LUN size: 10485760 bytes blocksize 512 bytes LUN ID: 1 Serial Number: MYSERIAL 1 Device ID; MYDEVID 1 san: ~ # ctladm create -b block -o file=3D/mnt/extent6 LUN created successfully backend: block device type: 0 LUN size: 10485760 bytes blocksize 512 bytes LUN ID: 2 Serial Number: MYSERIAL 2 Device ID; MYDEVID 2 san: ~ # ctladm create -b block -o file=3D/mnt/extent6 LUN created successfully backend: block device type: 0 LUN size: 10485760 bytes blocksize 512 bytes LUN ID: 3 Serial Number: MYSERIAL 3 Device ID; MYDEVID 3 san: ~ # ctladm create -b block -o file=3D/mnt/extent6 LUN created successfully backend: block device type: 0 LUN size: 10485760 bytes blocksize 512 bytes LUN ID: 4 Serial Number: MYSERIAL 4 Device ID; MYDEVID 4 san: ~ # ctladm devlist -v LUN Backend Size (Blocks) BS Serial Number Device ID 0 block 20480 512 MYSERIAL 0 MYDEVID 0 lun_type=3D0 num_threads=3D14 file=3D/mnt/extent6 1 block 20480 512 MYSERIAL 1 MYDEVID 1 lun_type=3D0 num_threads=3D14 file=3D/mnt/extent6 2 block 20480 512 MYSERIAL 2 MYDEVID 2 lun_type=3D0 num_threads=3D14 file=3D/mnt/extent6 3 block 20480 512 MYSERIAL 3 MYDEVID 3 lun_type=3D0 num_threads=3D14 file=3D/mnt/extent6 4 block 20480 512 MYSERIAL 4 MYDEVID 4 lun_type=3D0 num_threads=3D14 file=3D/mnt/extent6 notice the same file is used for each LUN...... it appears that ctladm never checks for a LUN using the same file..... or zpool for that matter....... anyway we can "correct" said behavior ?? > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >