From owner-freebsd-current@freebsd.org Tue Sep 4 21:27:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BB0FFFCACE; Tue, 4 Sep 2018 21:27:28 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0F4B826C9; Tue, 4 Sep 2018 21:27:27 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f50.google.com with SMTP id j198-v6so15076975ita.0; Tue, 04 Sep 2018 14:27:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=tTJD9sq6mta4u4FctQgnsX6w6gCliPb2+jUnDaDLMl0=; b=PCTzf5rMtbBcz60ZzJru1qFgxU3zIdBv7dNNOlfVsy/Vej+Aq2DV4Z0qqIkp08qNF3 Wsk9ljbM/6U7e+Iux7OUWH2Ev+HfQyKJ0AyzIUMJSHCLHP+HvJvbF48hf8F0Z18NqpQp UsV8UmGetH5xymkLU4Wsf3K6Ux97+rzlaGufRgafRvn2J/n68MM4ab9xLU7EKCuQGxks K9wTeubbhdBuGjiPLh+y+vTKkFtyAQCJkmKsvXDhio2FcMBt7UEpNCN7oJPSHfwVTaG1 UlmtWzlGYuRNiA5fVOanANIIvFrsZz2hQno5nBS2oc57YtT36pQ0oBAw7Vlaz3bIpLcz aajw== X-Gm-Message-State: APzg51BURlV2/zTWMzgA9DDh04+bxYkv16gZhPiJoh3F5068tDvo08i9 lVJ0jiKKHD8Vliw1+u9w+dC3t3FD X-Google-Smtp-Source: ANB0VdbQ/+UN9kCfGoFC2hGturqx1RFfTPNuiEyQEWsdqq2RrmIpIoTpnhFb0AFruNo7mxLyRuJKVA== X-Received: by 2002:a24:2848:: with SMTP id h69-v6mr9444920ith.63.1536096447221; Tue, 04 Sep 2018 14:27:27 -0700 (PDT) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com. [209.85.223.173]) by smtp.gmail.com with ESMTPSA id 68-v6sm215245itx.19.2018.09.04.14.27.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Sep 2018 14:27:27 -0700 (PDT) Received: by mail-io0-f173.google.com with SMTP id e12-v6so4240902iok.12; Tue, 04 Sep 2018 14:27:26 -0700 (PDT) X-Received: by 2002:a5e:9615:: with SMTP id a21-v6mr23473349ioq.53.1536096446818; Tue, 04 Sep 2018 14:27:26 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:9542:0:0:0:0:0 with HTTP; Tue, 4 Sep 2018 14:27:26 -0700 (PDT) In-Reply-To: <774228883.20180905001035@serebryakov.spb.ru> References: <609400979.20180904230820@serebryakov.spb.ru> <1942661439.20180904235514@serebryakov.spb.ru> <774228883.20180905001035@serebryakov.spb.ru> From: Conrad Meyer Date: Tue, 4 Sep 2018 14:27:26 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: newfs silently fails if random is not ready (?) To: Lev Serebryakov Cc: FreeBSD Current , freebsd-fs , Xin LI Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 04 Sep 2018 21:27:28 -0000 On Tue, Sep 4, 2018 at 2:10 PM, Lev Serebryakov wrote: > Wednesday, September 5, 2018, 12:05:43 AM, you wrote: >> I think it is tripping on raise/abort() in one of these routines, but >> nothing is printing that information. See below. > > Maybe, it should be fixed? Yes, it should. > One second after that random is ready to use and > newfs works as intended. It is, really, some race between early init script > (rc.initdiskless) and kernel. I don't think, that newfs must be > killed/aborted in such situation, it could wait! I agree. It looks like it is waiting, in fact, but then Something Bad Happens when the random device is unblocked. >> Ah, thanks. I missed this. mdmfs(8) has a bug in its run() function. >> It treats programs that exit with a signal (KILL, ABRT, ILL, SEGV...) >> the same as programs that exit with success. This is a (major) >> problem and the reason raise/abort is not visible. > > And it is another problem. But if it will be fixed, it doesn't help to init > system properly in my case, only diagnostic will be better. Yep. Best, Conrad