From owner-freebsd-fs@freebsd.org Sun Sep 18 07:27:57 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD49FBDD337 for ; Sun, 18 Sep 2016 07:27:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC39BDB6 for ; Sun, 18 Sep 2016 07:27:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8I7RugY049324 for ; Sun, 18 Sep 2016 07:27:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212608] nfsd(8) listens on UDP port 2049, but it is reported incorrectly in sockstat(1) and lsof(8) Date: Sun, 18 Sep 2016 07:27:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: woodsb02@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 07:27:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212608 --- Comment #2 from Ben Woods --- (In reply to nowak from comment #1) So the TCP socket is opened by userspace, but the UDP socket is opened by t= he kernel? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Sep 18 21:00:52 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61952BE038B for ; Sun, 18 Sep 2016 21:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5608A9C2 for ; Sun, 18 Sep 2016 21:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8IL01aK043760 for ; Sun, 18 Sep 2016 21:00:52 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201609182100.u8IL01aK043760@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 18 Sep 2016 21:00:52 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 21:00:52 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 203419 | solaris assert: (dn->dn_phys->dn_nlevels == 0 && Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Tue Sep 20 17:49:13 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE334BE24E9 for ; Tue, 20 Sep 2016 17:49:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E04AB08 for ; Tue, 20 Sep 2016 17:49:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8KHnDtO075456 for ; Tue, 20 Sep 2016 17:49:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212861] [tmpfs] uchg files can be removed by root Date: Tue, 20 Sep 2016 17:49:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 17:49:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212861 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --- Comment #1 from Ngie Cooper --- Sidenote: $ uname -a FreeBSD fbsd12 12.0-CURRENT FreeBSD 12.0-CURRENT #3 r305956: Sun Sep 18 21:40:02 PDT 2016 ngie@fbsd11:/usr/obj/usr/src/svn/sys/GENERIC-NODEBUG= =20 amd64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Sep 22 09:43:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC653BE48A8 for ; Thu, 22 Sep 2016 09:43:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC69AEA7 for ; Thu, 22 Sep 2016 09:43:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8M9hOXK003113 for ; Thu, 22 Sep 2016 09:43:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 212861] [tmpfs] uchg files can be removed by root Date: Thu, 22 Sep 2016 09:43:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: trasz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 09:43:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212861 Edward Tomasz Napierala changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trasz@FreeBSD.org --- Comment #2 from Edward Tomasz Napierala --- Could you do the same "sudo" thing in the UFS case? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Sep 22 12:49:13 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 364ABBE5CC2 for ; Thu, 22 Sep 2016 12:49:13 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 992B8395 for ; Thu, 22 Sep 2016 12:49:09 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id u8MCfJVS073091 for ; Thu, 22 Sep 2016 15:41:20 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Thu, 22 Sep 2016 15:41:19 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-fs@FreeBSD.org Subject: ZFS: tuning for flash-only pool Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Thu, 22 Sep 2016 15:41:20 +0300 (MSK) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 12:49:13 -0000 Dear colleagues, are there any special tunings that would be useful for pool of raidz2 of 6 SSDs? usage pattern is like rrd and/or database, so IOPS in mix read-write situation it the primary target (ashift is automatically set as 12). -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-fs@freebsd.org Thu Sep 22 17:35:46 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 641F6BE6627 for ; Thu, 22 Sep 2016 17:35:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 538D2CA8 for ; Thu, 22 Sep 2016 17:35:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8MHZj8h082043 for ; Thu, 22 Sep 2016 17:35:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 211013] Write error to UFS filesystem with softupdates panics machine Date: Thu, 22 Sep 2016 17:35:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-BETA1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: op@hardenedbsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: flagtypes.name cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 17:35:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211013 op@hardenedbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |mfc-stable10? CC| |op@hardenedbsd.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Sep 22 20:15:32 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46123BE5399 for ; Thu, 22 Sep 2016 20:15:32 +0000 (UTC) (envelope-from aaronkmiller@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11B5C8E9 for ; Thu, 22 Sep 2016 20:15:32 +0000 (UTC) (envelope-from aaronkmiller@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id e66so8057377iod.1 for ; Thu, 22 Sep 2016 13:15:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=m8B4aVz8nQ8h1wgCA07gJbFdro3SfbMppHjhZ+LsuCM=; b=T8R4lk4WvQiH1a2o5udoRJESMi6CJ/Wv45yqnYMxTwYPKw1d1I5grkfAXOuC9PtUj4 9+PCX2Gtvwk7DTRMVz0ihlAWpbc+4qlJDWkXvh3La1y7OPSPXRA9tpHkedX+02e+fkDC klx3NBrrlyuAEg1CYaD56rxohWC57+TDXZH3M5g6uIXtQh0M8L/LQQX550eL6uVIJSqy s0+9Y1MlWZX8S2ORRtd/KRURW7flSSFFA5ZAlCZQ5Jp1Qbyg8kqaF22JoRNtB/Rl4asC Pao3EiRnfnimSjUaYOBl/q1eMvsg43S8+9v8oxhYYsMVr2aEnbJxWQ14QDreoXj4EbIf z/8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=m8B4aVz8nQ8h1wgCA07gJbFdro3SfbMppHjhZ+LsuCM=; b=IOJwu1URaFBwSbmOdWcZCus+zEyOnyEX+dA8xlHv3pRcgQ2Lpn80gJU0uxbqBsNy9F r/ktlpSMPIo6x6ZOnvf3pl5coHJrz8vpOPyTAtUhOjcFmJGAz9t7rXn9V8TdNXG9nIbK +nCWI2cRlafyYyIah0/0exAg3H2XW7qMu5QJ/dOrPS5SHfmzUnUUSLxd/h8tbpHRccop CTSOgFnLK/90GjtkG4VFOb34PgHAay8ihM5oH24vRUmhOXslBdWwch0/z1cGs1o/I06f u0ngtJPr8iriUpkPJUFUZBtbmKFluwH1+r3p3/VFURmiFSrYeeSSNoBjozmEoeuof7s3 GjUQ== X-Gm-Message-State: AE9vXwOU1ri086ywmQ+0jUn/HoEn2a6e2fgwv+tt7mGSy7gAqAClGrFado2JIQq2gxP+f0d6eMAvh+77ItK2Ww== X-Received: by 10.107.17.216 with SMTP id 85mr5508604ior.96.1474575331254; Thu, 22 Sep 2016 13:15:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.71.209 with HTTP; Thu, 22 Sep 2016 13:14:50 -0700 (PDT) From: Aaron Miller Date: Thu, 22 Sep 2016 13:14:50 -0700 Message-ID: Subject: Logical unit not ready, manual intervention required To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 20:15:32 -0000 Hello all, I hope I'm posting to the right list and someone can help me. After rebooting my FreeBSD 10.3 machine the iSCSI LUN it is hosting is no longer accessible on my SAN. The underlying zpool and zvol seem fine: root@freebsd:~ # zpool status pool: spool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM spool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 mirror-4 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 mirror-5 ONLINE 0 0 0 da10 ONLINE 0 0 0 da11 ONLINE 0 0 0 root@freebsd:~ # zfs list NAME USED AVAIL REFER MOUNTPOINT spool 3.16T 0 19K /spool spool/volume1 3.16T 3.15T 5.18G - root@freebsd:~ # zfs get all spool/volume1 NAME PROPERTY VALUE SOURCE spool/volume1 type volume - spool/volume1 creation Tue Sep 6 8:23 2016 - spool/volume1 used 3.16T - spool/volume1 available 3.15T - spool/volume1 referenced 5.18G - spool/volume1 compressratio 1.00x - spool/volume1 reservation none default spool/volume1 volsize 3.06T local spool/volume1 volblocksize 8K - spool/volume1 checksum on default spool/volume1 compression off default spool/volume1 readonly off default spool/volume1 copies 1 default spool/volume1 refreservation 3.16T local spool/volume1 primarycache all default spool/volume1 secondarycache all default spool/volume1 usedbysnapshots 0 - spool/volume1 usedbydataset 5.18G - spool/volume1 usedbychildren 0 - spool/volume1 usedbyrefreservation 3.15T - spool/volume1 logbias latency default spool/volume1 dedup off default spool/volume1 mlslabel - spool/volume1 sync standard default spool/volume1 refcompressratio 1.00x - spool/volume1 written 5.18G - spool/volume1 logicalused 5.15G - spool/volume1 logicalreferenced 5.15G - spool/volume1 volmode default default spool/volume1 snapshot_limit none default spool/volume1 snapshot_count none default spool/volume1 redundant_metadata all default The LUN seems to start okay? root@freebsd:/var/log # ctladm start 0 (7:0:0/0): LUN started successfully I do have some errors in the log but I'm not sure if they are related: Sep 22 19:12:03 freebsd kernel: GEOM: da0: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da0: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da1: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da1: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da2: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da2: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da3: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da3: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da4: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da4: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da5: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da5: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da6: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da6: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da7: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da7: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da8: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da8: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da9: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da9: using the secondary instead -- recovery strongly advised. Sep 22 19:12:03 freebsd kernel: GEOM: da10: the primary GPT table is corrupt or invalid. Sep 22 19:12:03 freebsd kernel: GEOM: da10: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: da11: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: da11: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZY8NW1L%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZY8NW1L%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WV8UEL%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WV8UEL%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRVTEL%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRVTEL%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN71J%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN71J%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXYHAKJ%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXYHAKJ%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZB4PJ%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZB4PJ%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN7HJ%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN7HJ%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKHP0J%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKHP0J%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKJB9J%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKJB9J%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WT1S8L%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WT1S8L%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRD6PL%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRD6PL%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZYD0VWM%20%20%20%20%20%20%20%20: the primary GPT table is corrupt or invalid. Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZYD0VWM%20%20%20%20%20%20%20%20: using the secondary instead -- recovery strongly advised. There's a lot of this noise when an initiator is online and trying to connect: Sep 22 19:40:49 freebsd ctld[6983]: 10.33.80.62: read: connection lost Sep 22 19:40:49 freebsd ctld[659]: child process 6983 terminated with exit status 1 Sep 22 19:40:49 freebsd ctld[6984]: 10.33.80.62: read: connection lost Sep 22 19:40:49 freebsd ctld[659]: child process 6984 terminated with exit status 1 Sep 22 19:40:49 freebsd ctld[6985]: 10.33.80.62 (iqn.1993-08.org.debian:01:46952f23d3e): read: connection lost Sep 22 19:40:49 freebsd ctld[659]: child process 6985 terminated with exit status 1 Sep 22 19:40:57 freebsd ctld[6987]: 10.33.80.62 (iqn.1993-08.org.debian:01:46952f23d3e): read: connection lost On the initiator which is running debian-based proxmox there is a lot of this in the log: Sep 22 12:49:53 proxmox kernel: [ 136.579835] sd 1:0:0:0: [sdb] Add. Sense: Logical unit not ready, manual intervention required Sep 22 12:49:53 proxmox kernel: [ 136.580246] sd 1:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 22 12:49:53 proxmox kernel: [ 136.580250] sd 1:0:0:0: [sdb] Sense Key : Not Ready [current] Which after some googling sounds like I need to run 'ctladm start 0 -o', right? Well for some reason that doesn't work: root@freebsd:~ # ctladm start 0 -o ctladm: illegal option -- o ctladm: illegal option -- o (7:0:0/0): LUN started successfully No idea why it's saying illegal option here? It's listed in the command help: root@freebsd:~ # ctladm Usage: Primary commands: ctladm start [dev_id][general options] [-i] [-o] But that option is missing from 'man ctladm'? Folks on #freebsd have suggested that maybe it was added after freebsd 10.3 but I've found man pages online from 9.x that have it. Any assistance greatly appreciated! Thanks! From owner-freebsd-fs@freebsd.org Thu Sep 22 23:39:29 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50010BE67E3 for ; Thu, 22 Sep 2016 23:39:29 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from mail.quorumlabs.com (mail.quorum.net [64.74.133.216]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.quorumlabs.com", Issuer "Go Daddy Secure Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4174C238 for ; Thu, 22 Sep 2016 23:39:28 +0000 (UTC) (envelope-from Shiva.Bhanujan@Quorum.net) Received: from QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc]) by QLEXC01.Quorum.local ([fe80::fcc3:c03f:ab83:3cfc%14]) with mapi id 14.02.0318.001; Thu, 22 Sep 2016 16:38:17 -0700 From: Shiva Bhanujan To: "freebsd-fs@freebsd.org" Subject: HP smart HBA H241 Thread-Topic: HP smart HBA H241 Thread-Index: AdIVKmTLLCcSvc07Sj2DBThja9Mn7A== Date: Thu, 22 Sep 2016 23:38:17 +0000 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC07013044D4B1@QLEXC01.Quorum.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.7.61] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 23:39:29 -0000 Hello all, Does anybody know if the HP smart HBA H241 is supported in FreeBSD? I have= one installed in a Dell Poweredge R730, and the H241 is being connected to= a JBOD, but I don't see the disks. 'camcontrol devlist' doesn't show the = H241 either. Regards, Shiva From owner-freebsd-fs@freebsd.org Fri Sep 23 00:21:35 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81EF5BE5C54 for ; Fri, 23 Sep 2016 00:21:35 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id BF5381B96 for ; Fri, 23 Sep 2016 00:21:34 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Fri, 23 Sep 2016 02:21:22 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 8C808477-A7C8-4AE6-A724-D1C3FA9D5F96.1 envelope-from (authenticated bits=0); Fri, 23 Sep 2016 02:21:15 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HP smart HBA H241 From: Rainer Duffner In-Reply-To: <3A5A10BE32AC9E45B4A22F89FC90EC07013044D4B1@QLEXC01.Quorum.local> Date: Fri, 23 Sep 2016 02:20:16 +0200 Cc: "freebsd-fs@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <2FC349E0-84D3-4273-B27E-074F06C49010@ultra-secure.de> References: <3A5A10BE32AC9E45B4A22F89FC90EC07013044D4B1@QLEXC01.Quorum.local> To: Shiva Bhanujan X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=12 total_conn=1 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 1127, bad: 1, connections: 1435, history: 1126, asn_score: 608, asn_connections: 691, asn_good: 608, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 00:21:35 -0000 > Am 23.09.2016 um 01:38 schrieb Shiva Bhanujan = : >=20 > Hello all, >=20 > Does anybody know if the HP smart HBA H241 is supported in FreeBSD? I = have one installed in a Dell Poweredge R730, and the H241 is being = connected to a JBOD, but I don't see the disks. 'camcontrol devlist' = doesn't show the H241 either. What version of FreeBSD? I have a couple of H240 (IIRC) and they are recognized as of FreeBSD = 10.1 ciss0: port 0x3000-0x30ff mem = 0x92e00000-0x92efffff,0x92f00000-0x92f003ff at device 0.0 on pci3 ciss0: PERFORMANT Transport ciss1: port 0x2000-0x20ff mem = 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 on pci5 ciss1: PERFORMANT Transport (DL380-Gen9 - the H24x series is the only (HP-supported) JBOD HBA) The PCI-ids were added later. From owner-freebsd-fs@freebsd.org Fri Sep 23 22:48:44 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A5DBBE8B0D for ; Fri, 23 Sep 2016 22:48:44 +0000 (UTC) (envelope-from aaronkmiller@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2433BBFE for ; Fri, 23 Sep 2016 22:48:44 +0000 (UTC) (envelope-from aaronkmiller@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id r145so132682921ior.0 for ; Fri, 23 Sep 2016 15:48:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=mGAAKZsgV6GZ2Tqp4PnKgMmtm9nxXHcKwOKg/e/T/rw=; b=UW5raAQ4rZUeez1ppYWQxBH8eKNeGawkkTy3KKRltCGLW3HiQo5EV1TjpTApJEjYn8 FBsNJuZ/5++2vtgDYo09ge76Weq/4780SyG6uPKvMLlTmJd55H8jK6olObsywpHY7izS rtivZ/E2Yr/PL2Tq+FlHoEClB7z5N5fboV3C0H76XjoDxfFczqzx7K3k64votCtu+0q/ UhRSURTosBDGl6mURkQwYw/UIcJ6NBsWCwlBgR3Qg5hbSXENTmjeoyDdz3+U2fScJS/2 y2ZJapfazbZZ2gES5f6qaUM8Cd+VvdNuE510kK6N/I6KiUzqGUOg2h2JL18H6KdZTTZ/ Jttw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=mGAAKZsgV6GZ2Tqp4PnKgMmtm9nxXHcKwOKg/e/T/rw=; b=UjvQ5TK86UbXT5mv1WrFLi4UqarSjFzXsnikgawVx345GXWKVKVr2zTw9xyhXWgTRJ YLdTEpYoQZIHxg+vuNn+S5oAi9aivdeEbncmlEns9kX8t/Oaz9ev+dzqKehfhD3cFw1K qeCuzY6tJ5vvXI4a+b/RLug4LY2ktBlM3P/JaNPQd7BdQIZTmJGjClWB9LvV/evACKAZ k67NKZQfxmoDBogP9C6Wa81HYXRaIQJYxYD2iUJnGEpyQnJL2n082FBxNIDr6FBYadel LZCkd8DvLeQ3KaoHCBEKr4ryGfWEog9YXJHCRh8b79NJ5h+dJXXqlifttQcDtCgrpOXc 6/gA== X-Gm-Message-State: AE9vXwO0Hia1RRmtLjmhrdHJOqveQzLIQuqIF/5jsCMjl7/ma7LxmBy2SgAgwf7K5D0wYWSw7aTzb1mrNJL1hQ== X-Received: by 10.107.17.216 with SMTP id 85mr13265425ior.96.1474670923309; Fri, 23 Sep 2016 15:48:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.71.209 with HTTP; Fri, 23 Sep 2016 15:48:02 -0700 (PDT) In-Reply-To: References: From: Aaron Miller Date: Fri, 23 Sep 2016 15:48:02 -0700 Message-ID: Subject: Re: Logical unit not ready, manual intervention required To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 22:48:44 -0000 I figured it out. I did not have a size defined for my LUN in /etc/ctl.conf. Added that, restarted ctld and now it's working. On Thu, Sep 22, 2016 at 1:14 PM, Aaron Miller wrote: > Hello all, I hope I'm posting to the right list and someone can help me. > After rebooting my FreeBSD 10.3 machine the iSCSI LUN it is hosting is no > longer accessible on my SAN. > > The underlying zpool and zvol seem fine: > > root@freebsd:~ # zpool status > pool: spool > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > spool ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > da0 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > mirror-1 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > mirror-2 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > mirror-3 ONLINE 0 0 0 > da6 ONLINE 0 0 0 > da7 ONLINE 0 0 0 > mirror-4 ONLINE 0 0 0 > da8 ONLINE 0 0 0 > da9 ONLINE 0 0 0 > mirror-5 ONLINE 0 0 0 > da10 ONLINE 0 0 0 > da11 ONLINE 0 0 0 > > root@freebsd:~ # zfs list > NAME USED AVAIL REFER MOUNTPOINT > spool 3.16T 0 19K /spool > spool/volume1 3.16T 3.15T 5.18G - > > root@freebsd:~ # zfs get all spool/volume1 > NAME PROPERTY VALUE SOURCE > spool/volume1 type volume - > spool/volume1 creation Tue Sep 6 8:23 2016 - > spool/volume1 used 3.16T - > spool/volume1 available 3.15T - > spool/volume1 referenced 5.18G - > spool/volume1 compressratio 1.00x - > spool/volume1 reservation none default > spool/volume1 volsize 3.06T local > spool/volume1 volblocksize 8K - > spool/volume1 checksum on default > spool/volume1 compression off default > spool/volume1 readonly off default > spool/volume1 copies 1 default > spool/volume1 refreservation 3.16T local > spool/volume1 primarycache all default > spool/volume1 secondarycache all default > spool/volume1 usedbysnapshots 0 - > spool/volume1 usedbydataset 5.18G - > spool/volume1 usedbychildren 0 - > spool/volume1 usedbyrefreservation 3.15T - > spool/volume1 logbias latency default > spool/volume1 dedup off default > spool/volume1 mlslabel - > spool/volume1 sync standard default > spool/volume1 refcompressratio 1.00x - > spool/volume1 written 5.18G - > spool/volume1 logicalused 5.15G - > spool/volume1 logicalreferenced 5.15G - > spool/volume1 volmode default default > spool/volume1 snapshot_limit none default > spool/volume1 snapshot_count none default > spool/volume1 redundant_metadata all default > > > The LUN seems to start okay? > > root@freebsd:/var/log # ctladm start 0 > (7:0:0/0): LUN started successfully > > > I do have some errors in the log but I'm not sure if they are related: > > Sep 22 19:12:03 freebsd kernel: GEOM: da0: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da0: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da1: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da1: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da2: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da2: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da3: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da3: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da4: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da4: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da5: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da5: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da6: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da6: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da7: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da7: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da8: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da8: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da9: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da9: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:03 freebsd kernel: GEOM: da10: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:03 freebsd kernel: GEOM: da10: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: da11: the primary GPT table is > corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: da11: using the secondary instead -- > recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZY8NW1L%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZY8NW1L%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WV8UEL%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WV8UEL%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRVTEL%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRVTEL%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN71J%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN71J%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXYHAKJ%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXYHAKJ%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZB4PJ%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZB4PJ%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN7HJ%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZXZN7HJ%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKHP0J%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKHP0J%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKJB9J%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZWKJB9J%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WT1S8L%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WT1S8L%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRD6PL%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-J9WRD6PL%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZYD0VWM%20%20%20%20%20%20%20%20: > the primary GPT table is corrupt or invalid. > Sep 22 19:12:04 freebsd kernel: GEOM: diskid/DISK-JZYD0VWM%20%20%20%20%20%20%20%20: > using the secondary instead -- recovery strongly advised. > > > There's a lot of this noise when an initiator is online and trying to > connect: > > Sep 22 19:40:49 freebsd ctld[6983]: 10.33.80.62: read: connection lost > Sep 22 19:40:49 freebsd ctld[659]: child process 6983 terminated with exit > status 1 > Sep 22 19:40:49 freebsd ctld[6984]: 10.33.80.62: read: connection lost > Sep 22 19:40:49 freebsd ctld[659]: child process 6984 terminated with exit > status 1 > Sep 22 19:40:49 freebsd ctld[6985]: 10.33.80.62 (iqn.1993-08.org.debian:01:46952f23d3e): > read: connection lost > Sep 22 19:40:49 freebsd ctld[659]: child process 6985 terminated with exit > status 1 > Sep 22 19:40:57 freebsd ctld[6987]: 10.33.80.62 (iqn.1993-08.org.debian:01:46952f23d3e): > read: connection lost > > > On the initiator which is running debian-based proxmox there is a lot of > this in the log: > > Sep 22 12:49:53 proxmox kernel: [ 136.579835] sd 1:0:0:0: [sdb] Add. > Sense: Logical unit not ready, manual intervention required > Sep 22 12:49:53 proxmox kernel: [ 136.580246] sd 1:0:0:0: [sdb] Read > Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > Sep 22 12:49:53 proxmox kernel: [ 136.580250] sd 1:0:0:0: [sdb] Sense Key > : Not Ready [current] > > > Which after some googling sounds like I need to run 'ctladm start 0 -o', > right? Well for some reason that doesn't work: > > root@freebsd:~ # ctladm start 0 -o > ctladm: illegal option -- o > ctladm: illegal option -- o > (7:0:0/0): LUN started successfully > > > No idea why it's saying illegal option here? It's listed in the command > help: > > root@freebsd:~ # ctladm > Usage: > Primary commands: > > ctladm start [dev_id][general options] [-i] [-o] > > > But that option is missing from 'man ctladm'? Folks on #freebsd have > suggested that maybe it was added after freebsd 10.3 but I've found man > pages online from 9.x that have it. > > > Any assistance greatly appreciated! Thanks! >