From owner-freebsd-stable@freebsd.org Mon Jan 4 12:33:25 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 78D624D4966; Mon, 4 Jan 2021 12:33:25 +0000 (UTC) (envelope-from ali.abdallah@suse.com) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp2.suse.de", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D8ZmN5zBKz4fN0; Mon, 4 Jan 2021 12:33:24 +0000 (UTC) (envelope-from ali.abdallah@suse.com) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id AD724AD1E; Mon, 4 Jan 2021 12:33:22 +0000 (UTC) Date: Mon, 4 Jan 2021 13:33:21 +0100 From: Ali Abdallah To: techyNotes Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Consistency of pkg db on UFS Message-ID: <20210104123321.nvjambhslmvzmiac@Fryzen495> References: <20201211165713.syvzamtdtrbrgx44@frix230> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4D8ZmN5zBKz4fN0 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.20 / 15.00]; MID_RHS_NOT_FQDN(0.50)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[suse.com:s=susede1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.135.220.15]; MIME_GOOD(-0.10)[text/plain]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DWL_DNSWL_MED(-2.00)[suse.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[195.135.220.15:from]; DKIM_TRACE(0.00)[suse.com:+]; DMARC_POLICY_ALLOW(-0.50)[suse.com,quarantine]; RWL_MAILSPIKE_GOOD(0.00)[195.135.220.15:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29298, ipnet:195.135.220.0/22, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-fs,freebsd-stable] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2021 12:33:25 -0000 On 12.12.2020 09:44, techyNotes wrote: > Hi Ali Hi > > I had a similar problem with my HP Elitebook couple of days ago with UFS option. I had been experimenting with various modes and setup options including the file system ZFS and UFS. I would have installed and reinstalled Freebsd 12.2 more than 20 times! > > I guess the issue lies in the Installation process. Just before the final step of rebooting it takes sometime (more than when installing with ZFS option) to complete the installation closure tasks. This was not completed or you did not wait until the point the message popped up to reboot the system! > > To verify if this is the case, check your loader.conf and/or rc.conf it would be empty. The options you selected during the install process would not be recorded in these files. > > SOLUTION: I just reinstalled again with the option of UFS and waited on the last before step patiently and then finally rebooted upon the alter message of REBOOT option from the installer. I'm no speaking about the installer, but an already installed system. I don't believe there is a solution to the described issue, the blocks of a newly installed package can make it to the disk and to the fs metadata, but the information about it written by the package manager to its database/plain file might not make it to the disk in case of power failure/panic, so you would end up with an installed package that the package manager itself doesn't know about! The issue can happen on any filesystem, not only on UFS. Regards, Ali