From owner-freebsd-fs@freebsd.org Sun Nov 5 20:43:31 2017 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 31948E50F8D for ; Sun, 5 Nov 2017 20:43:31 +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 1F7406A667 for ; Sun, 5 Nov 2017 20:43:31 +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 vA5KhUaX081296 for ; Sun, 5 Nov 2017 20:43:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 27687] fsck(8) wrapper is not properly passing options to fsck_ Date: Sun, 05 Nov 2017 20:43:31 +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: 5.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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: Sun, 05 Nov 2017 20:43:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D27687 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Open Assignee|ngie@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Nov 6 15:40:30 2017 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 79389E611AD; Mon, 6 Nov 2017 15:40:30 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 0CFD6741DF; Mon, 6 Nov 2017 15:40:29 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id r129so10965674lff.8; Mon, 06 Nov 2017 07:40:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=/CUqSXAa+7aJvdHtKH5SZWVVRFEvEs2nTuXSqHNz5ao=; b=Irdss4zKp0CgtVpOr21ARL2TyPt5W9Y8097bShn/R6gIq7/Ctp/g8Bhm8z68U1o+fw ujURv0zxNREP3RUBIFivwbyMmIdZC5PbSu2x+ApX+Ndf/zVi9hdvPGvFEs6a+bLmGpP4 NCC1otuuTXn5O6b1O0wZES2h08g/cAP79B7f1jMbBXl2G52CKiUt+cuQCK7w2Q56DVcg QIDsiIKCkLnWSDRWjDxsXJ9y8/CbYs/Rt7so7XxWmvafqQN66Yt/tnOKOeWG0/NvxLH4 6PuueK3xQnKJXfJncCLicl7nFhQ49hS7iIAv5qup4P7GkQxsYW7ZwrNbn3i2snXIqA1c BT7w== X-Gm-Message-State: AMCzsaW37dob1IkBDr30sF6O7VKR+MtxRoYJu65Pwa/WXRljUCKznq31 9e0SQlrM8QzxmlooUUIYJLFoYDK12Os= X-Google-Smtp-Source: ABhQp+RHfyOpv0eibAP90keibe6xWz7oUgUqwglSQeIH9HXbmtN5h58zD4iEJWPMvQqeQS6j5fgS0g== X-Received: by 10.46.4.29 with SMTP id 29mr7032020lje.82.1509982822311; Mon, 06 Nov 2017 07:40:22 -0800 (PST) Received: from [192.168.0.197] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z66sm2702207ljb.75.2017.11.06.07.40.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Nov 2017 07:40:21 -0800 (PST) To: freebsd-current@FreeBSD.org, freebsd-fs@FreeBSD.org From: Andriy Gapon Subject: [HEADS UP] posix_fallocate support removed from ZFS, lld affected Message-ID: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org> Date: Mon, 6 Nov 2017 17:40:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Mon, 06 Nov 2017 15:40:30 -0000 >From UPDATING: The naive and non-compliant support of posix_fallocate(2) in ZFS has been removed as of r325320. The system call now returns EINVAL when used on a ZFS file. Although the new behavior complies with the standard, some consumers are not prepared to cope with it. One known victim is lld prior to r325420. >From https://svnweb.freebsd.org/changeset/base/325320 The generic (naive) implementation of posix_fallocate cannot provide the standard mandated guarantee that overwrites would never fail due to the lack of free space. The fundamental reason is the copy-on-write architecture of ZFS. Other features like compression and deduplication can also increase the size difference between the (pre-)allocated dummy content and the future content. So, until ZFS can properly implement the feature it's better to report that it is unsupported rather than providing an ersatz implementation. Please note that EINVAL is used to report that the underlying file system does not support the operation (POSIX.1-2008). illumos and ZoL seem to do the same. lld is affected by the change. That means that any world builds where lld is used are affected as well (if ZFS is involved, of course). One example is the arm64 build (typically a cross build from amd64). The lld issue is fixed in head as of r325420. But other branches are still affected (if you are building them on a head kernel). Other posix_fallocate consumers could be affected too. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Mon Nov 6 17:27:26 2017 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 43A17E63279 for ; Mon, 6 Nov 2017 17:27:26 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 D8D4E7769A for ; Mon, 6 Nov 2017 17:27:25 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 9894adad-c317-11e7-b805-f37e907b5733 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 9894adad-c317-11e7-b805-f37e907b5733; Mon, 06 Nov 2017 17:26:18 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id vA6HQGrn001380; Mon, 6 Nov 2017 10:26:16 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1509989176.99235.79.camel@freebsd.org> Subject: Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected From: Ian Lepore To: Andriy Gapon , freebsd-current@FreeBSD.org, freebsd-fs@FreeBSD.org Date: Mon, 06 Nov 2017 10:26:16 -0700 In-Reply-To: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org> References: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: Mon, 06 Nov 2017 17:27:26 -0000 On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: > From UPDATING: > The naive and non-compliant support of posix_fallocate(2) in ZFS > has been removed as of r325320.  The system call now returns EINVAL > when used on a ZFS file.  Although the new behavior complies with the > standard, some consumers are not prepared to cope with it. > One known victim is lld prior to r325420. > It just popped into my head... does this mean that kernels running r325320+ on systems using ZFS will be unable to host build jails for earlier versions / branches because lld will fail in the jail? I think that will be a big problem for the ports team's package building process, and for anyone using poudriere. -- Ian From owner-freebsd-fs@freebsd.org Tue Nov 7 10:33:49 2017 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 DDF68E54BD6 for ; Tue, 7 Nov 2017 10:33:49 +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 CC70577C5F for ; Tue, 7 Nov 2017 10:33:49 +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 vA7AXnpD014004 for ; Tue, 7 Nov 2017 10:33:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Tue, 07 Nov 2017 10:33:49 +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: wosch@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, 07 Nov 2017 10:33:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 Wolfram Schneider changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Nov 7 18:12:25 2017 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 8CC8CE608D2; Tue, 7 Nov 2017 18:12:25 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f65.google.com (mail-lf0-f65.google.com [209.85.215.65]) (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 1818C7CC5A; Tue, 7 Nov 2017 18:12:24 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f65.google.com with SMTP id l23so96038lfk.10; Tue, 07 Nov 2017 10:12:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2J8zeNUQz37Uoa7k+F5SIaZIhmG9fvH9PbGYYmS05JQ=; b=J9WK30dGRAzOvapDd2ydKi3CRkLJ93pBs2APkEfZ3i+ZoKUB6ohl5yKLbMGWqKvdpx 4ZgzTGEyyiZTWWFnHGr1bZOQQC3fFWGj3wRKJkH1Jz3pifLylAYxrG5l+xc79GRo7Q6S WiwyX5s5tbLNdbXLbG/RaugbDEgd4wtBFUgfqaZVolC9fTmBAIhRYywyTbPdJ+ooqIFh 2KgPnXcNmehzZ2gTNJ3fqW2aXl+qlCRMr3xwLrBpgEmKjcc7L9m/BVbTMJMffhda21yU YNxG9tCc8WfqFtL+PiJM8K5krdQVcFB/5LTi145XBqu0WrYi/Xqi3EuLbGRMPdNFFrRA tHsQ== X-Gm-Message-State: AJaThX6udWuZ3BG0GmlhPzI3U8SplHD0jVyeVjVWopXFsdhj/Nt6JedG urnz1MDv4Dta84XrX+v082oBfa4T X-Google-Smtp-Source: ABhQp+Q44G+eZtFci0M8z32UdMOViVGibX0kL5Aa92W2XPdl1HYn25GPn/HDdh1KS9e1I4tipsvQOg== X-Received: by 10.25.204.211 with SMTP id c202mr6720280lfg.220.1510078336693; Tue, 07 Nov 2017 10:12:16 -0800 (PST) Received: from [192.168.0.197] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id r125sm325317lfr.46.2017.11.07.10.12.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 10:12:15 -0800 (PST) Subject: Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected To: Ian Lepore , freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org> <1509989176.99235.79.camel@freebsd.org> From: Andriy Gapon Message-ID: <153bfe2b-e65e-2036-3391-984c6ba00ffe@FreeBSD.org> Date: Tue, 7 Nov 2017 20:12:13 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <1509989176.99235.79.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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, 07 Nov 2017 18:12:25 -0000 On 06/11/2017 19:26, Ian Lepore wrote: > On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: >> From UPDATING: >> The naive and non-compliant support of posix_fallocate(2) in ZFS >> has been removed as of r325320.  The system call now returns EINVAL >> when used on a ZFS file.  Although the new behavior complies with the >> standard, some consumers are not prepared to cope with it. >> One known victim is lld prior to r325420. >> > > It just popped into my head... does this mean that kernels running > r325320+ on systems using ZFS will be unable to host build jails for > earlier versions / branches because lld will fail in the jail? I am afraid that this is true. > I think that will be a big problem for the ports team's package > building process, and for anyone using poudriere. I hope that lld is not that widely used now. But I admit that I put the cart before the horse. I didn't expect that posix_fallocate is used in the development toolchain and I didn't try to check for it. -- Andriy Gapon From owner-freebsd-fs@freebsd.org Wed Nov 8 00:19:38 2017 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 33109E68695 for ; Wed, 8 Nov 2017 00:19:38 +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 21C157ABE7 for ; Wed, 8 Nov 2017 00:19:38 +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 vA80JbIt050923 for ; Wed, 8 Nov 2017 00:19:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Wed, 08 Nov 2017 00:19:38 +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: cem@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: Wed, 08 Nov 2017 00:19:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cem@freebsd.org --- Comment #1 from Conrad Meyer --- What virtual machine infrastructure? Is the virtual disk lying about flush= ed writes? It seems like this inconsistency could happen if a virtual disk reordered some writes and then the host crashed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Nov 8 04:43:02 2017 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 023C3E6D910 for ; Wed, 8 Nov 2017 04:43:02 +0000 (UTC) (envelope-from youzhong@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 BDFFE68F18 for ; Wed, 8 Nov 2017 04:43:01 +0000 (UTC) (envelope-from youzhong@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id c77so1114830oig.0 for ; Tue, 07 Nov 2017 20:43:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=lPz3V3H06fO3RNysmtGFOLaQKXO8V9JJYn5vpEpOXdY=; b=BleJGBfLCmQQR/+Z6OqZWttfJf4+akUgP8gpANclz4yprfU4QEpIWHORKQXWLDGmia 4h+lXF/1atkorNnIwzw5whbxjvx4eBLSRr203jpYrshn9Z/FWkRAUqtplBKaAv5jAdx3 BBeIWqRyKB1MJ9/ysuzRcix8ldMyQyRI4NgGE0NUeyvOIeH8w0RC4+OCA3cFKqCtEySB Cpzm0aD6qDBYk9S5l7HxJ/5ns1rIafEJVQFfUl6FXkilWqKK9PuzdPykxGCbZKnP/zre Cek3D2sAxBwQPU7RAutwwgMP9/K/9hWk1JafIROoTahDO993wOZUUbubGQGHgRhv8pSu xmvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lPz3V3H06fO3RNysmtGFOLaQKXO8V9JJYn5vpEpOXdY=; b=DS9GMORLYNBddz75CzFgvMt7o4sGQhylJWEpQqQl5/23mFnLVG3HGSiAHtP/G1cYWR vLClaEy8HBRwBszxjxrXt7ZvD2B8/YYfJPCXugkJXXNZyhKE0Ju/utFL3Dxi80Q/mBzV djoueKOMOgJPg6HG/+C2NoOREpqv0hHUAHZSTpPQzFSELHwNksihMtXMBdjBPkslZx9h h1SgPQka6wPB3NHi8+FTVR4rdfbvR1CJ4XPPG3/crK1wXp8dUT6r6cn+iZ/IRNafvaLt 6ilumxcnv34C1X4RPpg0wnsxFX9Bn89JMS1A39V3j2fvpjQUX1BET11X+iXiPcyoc96H 7tRg== X-Gm-Message-State: AJaThX5PQ1uhEXM+mqGMOLwnsIcHcP8RsUmBn5ittZiypeLqYWhawJXc i/sy/e4qN3wTmcLwFVcXL7IpbGMXUP2FL5/02XRcZA== X-Google-Smtp-Source: ABhQp+QmJL7rlCclBw+263sM8sbxz58sr17IytBmxyhkwuWpkDZYWIH7z3WX4K4K4T2c75m18u41fX9fDwhACQPuT+I= X-Received: by 10.202.166.18 with SMTP id p18mr637076oie.192.1510116180712; Tue, 07 Nov 2017 20:43:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.152.233 with HTTP; Tue, 7 Nov 2017 20:43:00 -0800 (PST) From: Youzhong Yang Date: Tue, 7 Nov 2017 23:43:00 -0500 Message-ID: Subject: ls .zfs/snapshot: File name too long 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: Wed, 08 Nov 2017 04:43:02 -0000 Hi, I just saw a strange issue when listing .zfs/snapshot folder: # ls -l /vmgr/Btnas1_c.750842.Bmain.747831.pass/.zfs/snapshot/ total 3 drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass.jobarchive # zfs snapshot clusters/vmgr/Btnas1_c.750842.Bmain.747831.pass@Btnas1_c.750842.release.jobarchive # ls -l /vmgr/Btnas1_c.750842.Bmain.747831.pass/.zfs/snapshot/ ls: Btnas1_c.750842.release.jobarchive: File name too long total 3 drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass.jobarchive No kidding, file name too long? Is this a known issue? By the way, I am new to FreeBSD. The version I am using is 11.1. Thanks, --Youzhong From owner-freebsd-fs@freebsd.org Wed Nov 8 09:04:48 2017 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 5B4E7E71D45 for ; Wed, 8 Nov 2017 09:04:48 +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 0F0FF713FB for ; Wed, 8 Nov 2017 09:04:48 +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 vA894lsI005868 for ; Wed, 8 Nov 2017 09:04:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Date: Wed, 08 Nov 2017 09:04:48 +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: wosch@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: Wed, 08 Nov 2017 09:04:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491 --- Comment #2 from Wolfram Schneider --- It is an Intel 64bit CPU with a shared SSD. I guess the data center is using QEMU/KVM for the virtualization, but I=E2=80=99m not sure about that. $ df -h Filesystem Size Used Avail Capacity Mounted on /dev/vtbd0p2 93G 63G 23G 73% / devfs 1.0K 1.0K 0B 100% /dev sysctl -a kern.geom.label.disk_ident.enable: 1 kern.geom.disk.cd0.flags: 0 kern.geom.disk.cd0.led:=20 kern.geom.disk.vtbd0.flags: 3a kern.geom.disk.vtbd0.led:=20 kern.disks: cd0 vtbd0 SSD write performance ca: 140Mbyte/s=20 SSD read performance ca: 560Mbyte/s FreeBSD 12.0-CURRENT #0 fcca5326804(master): Mon Oct 23 13:24:36 CEST 2017 root@freebsd:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on LLVM 5.0.0svn) CPU: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz (2200.05-MHz K8-class CPU) real memory =3D 8589934592 (8192 MB) FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs virtio_pci0: port 0xc080-0xc0bf mem 0xf2060000-0xf2060fff irq 11 at device 4.0 on pci0 vtblk0: on virtio_pci0 vtblk0: 102400MB (209715200 512 byte sectors) virtio_pci1: port 0xc0c0-0xc0df irq 10 at devi= ce 5.0 on pci0 vtballoon0: on virtio_pci1 ugen0.2: at usbus0 Trying to mount root from ufs:/dev/vtbd0p2 [rw]... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Nov 8 23:15:49 2017 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 C7365E5E145 for ; Wed, 8 Nov 2017 23:15:49 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 7A7CE6B491 for ; Wed, 8 Nov 2017 23:15:49 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-vk0-x231.google.com with SMTP id i133so2839248vke.9 for ; Wed, 08 Nov 2017 15:15:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GCt3IcDCeiJkF3Y+Fwp8PUTv31K3DmPkG52ubDs+HCc=; b=n9B6rFyVpcoIajj4bDNlQYTGUdHIIKybn+Ws5u0ZwgzxgQQr+l+qJie9vHfA7Clx3U ie798GM3FrDXBAXePy8M2fCCSFTGvA8BpTnko1CCIZU6MDk2+VKmsHPK24HUlpDd2ag3 Qdwqo/s+DueefFVC5Y1Eg64Lnm48n69dxvIlyR469M2gN3JPRD/6uvguE9DpI6Fk/yJw B8oIaiWZoTKVF7YNgLMGWc9SzgH0rmPnkyMsz7zp8kx1X18yeoIaoZUvRwn00Xyg17cl E6u7/efUcuZiuILFXy0E3dTuetM/qIkQK3Okf4YtgLCHPpdyq9iZm4IYcGNvgwqOQ+Dj AvQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GCt3IcDCeiJkF3Y+Fwp8PUTv31K3DmPkG52ubDs+HCc=; b=ZDhPF6ndZpKahFKHzyli+9HrVNoCyLlRpYPxZPewlDlDHCAGPQHJRtwaLvBTnw3Eai uf0gwxOUyUwafpCLq5lSbQ6acSFl2GYiX4QO5azfoXhsL6dqhLz+BsN68nR1kkiXg2tm XhFYV2bV/ptFwQTFkazYnPLlRz9I+QYS+WjgMHbXKToaefj5Z3dNeKtrkL8PS3x4hyll FcdEVVEvDK54mYdyUheN39kOjiMVsVO/COITNvEHH0rtbKHi+cSNMWvUy7YJuSezJCBP 1A6PNGcjuz/cGYpkDuJat9rIyH5qFG/NFmcsHddaZx5XypyjFRhzhT+pgY9/lWjnO7fC 2x4Q== X-Gm-Message-State: AJaThX7OzRpFxqoMnWPh5MQSjZo4wXNh1YCtK+VwsT78AiIccKAHOCCx 8bznfgNLx8jhgyAtNLncXY7RXgzJfdCDSxTyjMA= X-Google-Smtp-Source: ABhQp+Sizvq7qSAYBKxfVamhudDkFbv0kXvE97JY4HMpedn4bTN/eY1h7nkGsmBL5m4AQG8sWTw+xLtt9O1eqNfmsMU= X-Received: by 10.31.4.18 with SMTP id 18mr1847879vke.78.1510182948541; Wed, 08 Nov 2017 15:15:48 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ben Woods Date: Wed, 08 Nov 2017 23:15:38 +0000 Message-ID: Subject: Re: ls .zfs/snapshot: File name too long To: Youzhong Yang Cc: 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: Wed, 08 Nov 2017 23:15:49 -0000 On Wed, 8 Nov 2017 at 12:43 pm, Youzhong Yang wrote: > Hi, > > I just saw a strange issue when listing .zfs/snapshot folder: > > # ls -l /vmgr/Btnas1_c.750842.Bmain.747831.pass/.zfs/snapshot/ > total 3 > drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass > drwxrwxr-x 5 root batserve 9 Nov 7 22:48 > Btnas1_c.750842.pass.jobarchive > > # zfs snapshot > > clusters/vmgr/Btnas1_c.750842.Bmain.747831.pass@Btnas1_c.750842.release.jobarchive > > # ls -l /vmgr/Btnas1_c.750842.Bmain.747831.pass/.zfs/snapshot/ > ls: Btnas1_c.750842.release.jobarchive: File name too long > total 3 > drwxrwxr-x 5 root batserve 9 Nov 7 22:48 Btnas1_c.750842.pass > drwxrwxr-x 5 root batserve 9 Nov 7 22:48 > Btnas1_c.750842.pass.jobarchive > > No kidding, file name too long? Is this a known issue? By the way, I am new > to FreeBSD. The version I am using is 11.1. > > Thanks, > > --Youzhong > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Hi Youzhong, This topic has been discussed before here: https://lists.freebsd.org/pipermail/freebsd-fs/2010-March/007964.html In summary, the length limit for a mount points path is 88 characters in all released versions of FreeBSD. This has been increased to 1024 in FreeBSD 12-CURRENT, as it was increased as a part of the 64bit INODE project. Due to the massive amount of changes by that project, it will not be backports to stable branches for FreeBSD 11.2. Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-fs@freebsd.org Wed Nov 8 23:16:56 2017 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 922FDE5E216 for ; Wed, 8 Nov 2017 23:16:56 +0000 (UTC) (envelope-from markham@ssimicro.com) Received: from barracuda.ssimicro.com (barracuda.ssimicro.com [96.46.39.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ssimicro.com", Issuer "RapidSSL SHA256 CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F8F36B55A for ; Wed, 8 Nov 2017 23:16:55 +0000 (UTC) (envelope-from markham@ssimicro.com) X-ASG-Debug-ID: 1510183003-08e717666134e790001-3nHGF7 Received: from mail.ssimicro.com (mail.ssimicro.com [64.247.129.10]) by barracuda.ssimicro.com with ESMTP id 3NqMo7o9ZJCb4Bux (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 08 Nov 2017 18:16:43 -0500 (EST) X-Barracuda-Envelope-From: markham@ssimicro.com X-Barracuda-Effective-Source-IP: mail.ssimicro.com[64.247.129.10] X-Barracuda-Apparent-Source-IP: 64.247.129.10 Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by mail.ssimicro.com (8.15.2/8.15.2) with ESMTPSA id vA8NGgPp098838 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 8 Nov 2017 16:16:42 -0700 (MST) (envelope-from markham@ssimicro.com) To: freebsd-fs@freebsd.org From: markham breitbach Subject: glusterfs volume status not showing online Message-ID: X-ASG-Orig-Subj: glusterfs volume status not showing online Date: Wed, 8 Nov 2017 16:16:42 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Barracuda-Connect: mail.ssimicro.com[64.247.129.10] X-Barracuda-Start-Time: 1510183003 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://barracuda.ssimicro.com:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 11518 X-Virus-Scanned: by bsmtpd at ssimicro.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.50 X-Barracuda-Spam-Status: No, SCORE=0.50 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=BSF_RULE_7582B X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.44642 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.50 BSF_RULE_7582B Custom Rule 7582B 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: Wed, 08 Nov 2017 23:16:56 -0000 Hi There, I hope this is the right place for this question.=A0 I am trying to setup glusterfs on FreeBSD. I originally did some testing a while back with glusterfs 3.9.0_2 on FreeBSD 10.3 and a run through the quickstart seemed to work OK on a couple of small VMs. I am now trying to do some testing on bare metal using FreeBSD 11.1 (and now 10.4). I installed the pkg and ran the "quickstart." but now I find that `gluster volume status` doesn't seem to be working (currently on glusterfs-3.11.1_2) There doesn't seem to be anything particularly telling in glusterd.log, and I can actually mount the volume and use it. Any advice on where to look next? Thanks, -Markham ---- quick start ---- =A0# pkg install glusterfs =A0# zfs create -omountpoint=3D/groot zroot/groot =A0# service glusterd onestart =A0# gluster peer probe gtest4 =A0# gluster volume create apple replica 2 gtest4:/groot/apple gtest3:/groot/apple =A0# gluster volume start apple =A0# gluster volume status Status of volume: apple Gluster process=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 TCP Port=A0 RDMA Port=A0 Online=A0 Pid -------------------------------------------------------------------------= ----- Brick gtest4:/groot/apple=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 N/A=A0=A0=A0=A0=A0=A0 N/A=A0=A0=A0=A0=A0=A0=A0 N=A0=A0=A0=A0=A0=A0= N/A Brick gtest3:/groot/apple=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 N/A=A0=A0=A0=A0=A0=A0 N/A=A0=A0=A0=A0=A0=A0=A0 N=A0=A0=A0=A0=A0=A0= N/A Self-heal Daemon on localhost=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 N= /A=A0=A0=A0=A0=A0=A0 N/A=A0=A0=A0=A0=A0=A0=A0 N=A0=A0=A0=A0=A0=A0 967 Self-heal Daemon on gtest4=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 N/A=A0=A0=A0=A0=A0=A0 N/A=A0=A0=A0=A0=A0=A0=A0 N=A0=A0=A0=A0=A0=A0 97= 0 Task Status of Volume apple -------------------------------------------------------------------------= ----- There are no active volume tasks ----- glusterd.log ----- [2017-11-08 22:29:09.132427] I [MSGID: 100030] [glusterfsd.c:2476:main] 0-/usr/local/sbin/glusterd: Started running /usr/local/sbin/glusterd version 3.11.1 (args: /usr/local/sbin/glusterd --pid-file=3D/var/run/glusterd.pid) [2017-11-08 22:29:09.138608] I [MSGID: 106478] [glusterd.c:1422:init] 0-management: Maximum allowed open file descriptors set to 65536 [2017-11-08 22:29:09.138676] I [MSGID: 106479] [glusterd.c:1469:init] 0-management: Using /var/db/glusterd as working directory [2017-11-08 22:29:09.143727] E [rpc-transport.c:283:rpc_transport_load] 0-rpc-transport: Cannot open "/usr/local/lib/glusterfs/3.11.1/rpc-transport/rdma.so" [2017-11-08 22:29:09.143758] W [rpc-transport.c:287:rpc_transport_load] 0-rpc-transport: volume 'rdma.management': transport-type 'rdma' is not valid or not found on this machine [2017-11-08 22:29:09.143777] W [rpcsvc.c:1660:rpcsvc_create_listener] 0-rpc-service: cannot create listener, initing the transport failed [2017-11-08 22:29:09.143796] E [MSGID: 106243] [glusterd.c:1693:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport [2017-11-08 22:29:09.147373] E [MSGID: 101032] [store.c:433:gf_store_handle_retrieve] 0-: Path corresponding to /var/db/glusterd/glusterd.info. [No such file or directory] [2017-11-08 22:29:09.147414] E [MSGID: 101032] [store.c:433:gf_store_handle_retrieve] 0-: Path corresponding to /var/db/glusterd/glusterd.info. [No such file or directory] [2017-11-08 22:29:09.147416] I [MSGID: 106514] [glusterd-store.c:2215:glusterd_restore_op_version] 0-management: Detected new install. Setting op-version to maximum : 31100 [2017-11-08 22:29:09.147477] E [MSGID: 101032] [store.c:433:gf_store_handle_retrieve] 0-: Path corresponding to /var/db/glusterd/options. [No such file or directory] [2017-11-08 22:29:09.168706] I [MSGID: 106194] [glusterd-store.c:3772:glusterd_store_retrieve_missed_snaps_list] 0-management: No missed snaps list. Final graph: +------------------------------------------------------------------------= ------+ =A0 1: volume management =A0 2:=A0=A0=A0=A0 type mgmt/glusterd =A0 3:=A0=A0=A0=A0 option rpc-auth.auth-glusterfs on =A0 4:=A0=A0=A0=A0 option rpc-auth.auth-unix on =A0 5:=A0=A0=A0=A0 option rpc-auth.auth-null on =A0 6:=A0=A0=A0=A0 option rpc-auth-allow-insecure on =A0 7:=A0=A0=A0=A0 option transport.socket.listen-backlog 128 =A0 8:=A0=A0=A0=A0 option event-threads 1 =A0 9:=A0=A0=A0=A0 option ping-timeout 0 =A010:=A0=A0=A0=A0 option transport.socket.read-fail-log off =A011:=A0=A0=A0=A0 option transport.socket.keepalive-interval 2 =A012:=A0=A0=A0=A0 option transport.socket.keepalive-time 10 =A013:=A0=A0=A0=A0 option transport-type rdma =A014:=A0=A0=A0=A0 option working-directory /var/db/glusterd =A015: end-volume =A016: +------------------------------------------------------------------------= ------+ [2017-11-08 22:29:41.245073] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req gtest4 24007 [2017-11-08 22:29:41.269548] I [MSGID: 106129] [glusterd-handler.c:3623:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: gtest4 (24007) [2017-11-08 22:29:41.310764] W [MSGID: 106062] [glusterd-handler.c:3399:glusterd_transport_inet_options_build] 0-glusterd: Failed to get tcp-user-timeout [2017-11-08 22:29:41.310813] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2017-11-08 22:29:41.310890] W [MSGID: 101002] [options.c:954:xl_opt_validate] 0-management: option 'address-family' is deprecated, preferred is 'transport.address-family', continuing with correction [2017-11-08 22:29:41.317314] I [MSGID: 106498] [glusterd-handler.c:3549:glusterd_friend_add] 0-management: connect returned 0 [2017-11-08 22:29:41.318182] E [MSGID: 101032] [store.c:433:gf_store_handle_retrieve] 0-: Path corresponding to /var/db/glusterd/glusterd.info. [No such file or directory] [2017-11-08 22:29:41.318258] I [MSGID: 106477] [glusterd.c:190:glusterd_uuid_generate_save] 0-management: generated UUID: cee1794a-5e83-415e-88e0-eae018f9e745 [2017-11-08 22:29:41.426904] I [MSGID: 106511] [glusterd-rpc-ops.c:261:__glusterd_probe_cbk] 0-management: Received probe resp from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b3, host: gtest4 [2017-11-08 22:29:41.426950] I [MSGID: 106511] [glusterd-rpc-ops.c:421:__glusterd_probe_cbk] 0-glusterd: Received resp to probe req [2017-11-08 22:29:41.455508] I [MSGID: 106493] [glusterd-rpc-ops.c:485:__glusterd_friend_add_cbk] 0-glusterd: Received ACC from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b3, host: gtest4, port: = 0 [2017-11-08 22:29:41.496977] I [MSGID: 106163] [glusterd-handshake.c:1309:__glusterd_mgmt_hndsk_versions_ack] 0-management: using the op-version 31100 [2017-11-08 22:29:41.521751] I [MSGID: 106490] [glusterd-handler.c:2890:__glusterd_handle_probe_query] 0-glusterd: Received probe from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b3 [2017-11-08 22:29:41.525628] I [MSGID: 106493] [glusterd-handler.c:2953:__glusterd_handle_probe_query] 0-glusterd: Responded to gtest4.ssimicro.com, op_ret: 0, op_errno: 0, ret: 0 [2017-11-08 22:29:41.538527] I [MSGID: 106490] [glusterd-handler.c:2539:__glusterd_handle_incoming_friend_req] 0-glusterd: Received probe from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b= 3 [2017-11-08 22:29:41.557101] I [MSGID: 106493] [glusterd-handler.c:3799:glusterd_xfer_friend_add_resp] 0-glusterd: Responded to gtest4 (0), ret: 0, op_ret: 0 [2017-11-08 22:29:41.574502] I [MSGID: 106492] [glusterd-handler.c:2717:__glusterd_handle_friend_update] 0-glusterd: Received friend update from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b3 [2017-11-08 22:29:41.574567] I [MSGID: 106502] [glusterd-handler.c:2762:__glusterd_handle_friend_update] 0-management: Received my uuid as Friend [2017-11-08 22:29:41.574634] I [MSGID: 106493] [glusterd-rpc-ops.c:700:__glusterd_friend_update_cbk] 0-management: Received ACC from uuid: 2dcbff56-88e8-48c8-814a-101f3d32c2b3 [2017-11-08 22:30:47.866210] W [MSGID: 101095] [xlator.c:162:xlator_volopt_dynload] 0-xlator: Cannot open "/usr/local/lib/glusterfs/3.11.1/xlator/nfs/server.so" [2017-11-08 22:30:55.267120] I [MSGID: 106143] [glusterd-pmap.c:279:pmap_registry_bind] 0-pmap: adding brick /groot/apple on port 49152 [2017-11-08 22:30:55.267548] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2017-11-08 22:30:55.346373] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-snapd: setting frame-timeout to 600 [2017-11-08 22:30:55.346761] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-nfs: setting frame-timeout to 600 [2017-11-08 22:30:55.346875] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: nfs already stopped [2017-11-08 22:30:55.346924] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: nfs service is stopped [2017-11-08 22:30:55.346968] I [MSGID: 106600] [glusterd-nfs-svc.c:82:glusterd_nfssvc_manager] 0-management: nfs/server.so xlator is not installed [2017-11-08 22:30:55.347136] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-glustershd: setting frame-timeout to 600 [2017-11-08 22:30:55.347911] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: glustershd already stopped [2017-11-08 22:30:55.347950] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: glustershd service is stopped [2017-11-08 22:30:55.348012] I [MSGID: 106567] [glusterd-svc-mgmt.c:196:glusterd_svc_start] 0-management: Starting glustershd service [2017-11-08 22:30:56.365516] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-quotad: setting frame-timeout to 600 [2017-11-08 22:30:56.365837] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-bitd: setting frame-timeout to 600 [2017-11-08 22:30:56.366019] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped [2017-11-08 22:30:56.366071] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: bitd service is stopped [2017-11-08 22:30:56.366235] I [rpc-clnt.c:1059:rpc_clnt_connection_init] 0-scrub: setting frame-timeout to 600 [2017-11-08 22:30:56.366372] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped [2017-11-08 22:30:56.366409] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: scrub service is stopped [2017-11-08 22:30:57.707989] E [run.c:190:runner_log] (-->0x803ecad43 at /usr/local/lib/glusterfs/3.11.1/xlator/mgmt/glusterd.so -->0x8008a6504 at /usr/local/lib/libglusterfs.so.0 ) 0-management: Failed to execute script: /var/db/glusterd/hooks/1/start/post/S29CTDBsetup.sh --volname=3Dapple --first=3Dyes --version=3D1 --volume-op=3Dstart --gd-workdir=3D/var/db/gl= usterd [2017-11-08 22:30:57.722114] E [run.c:190:runner_log] (-->0x803ecad43 at /usr/local/lib/glusterfs/3.11.1/xlator/mgmt/glusterd.so -->0x8008a6504 at /usr/local/lib/libglusterfs.so.0 ) 0-management: Failed to execute script: /var/db/glusterd/hooks/1/start/post/S30samba-start.sh --volname=3Dapple --first=3Dyes --version=3D1 --volume-op=3Dstart --gd-workdir=3D/var/db/gl= usterd [2017-11-08 22:31:01.537697] I [MSGID: 106499] [glusterd-handler.c:4302:__glusterd_handle_status_volume] 0-management: Received status volume req for volume apple [2017-11-08 22:31:05.749436] I [MSGID: 106499] [glusterd-handler.c:4302:__glusterd_handle_status_volume] 0-management: Received status volume req for volume apple [2017-11-08 22:31:55.783261] I [MSGID: 106499] [glusterd-handler.c:4302:__glusterd_handle_status_volume] 0-management: Received status volume req for volume apple [2017-11-08 22:34:59.660782] I [MSGID: 106487] [glusterd-handler.c:1484:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req