From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: util-linux-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:36629 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751389AbaFPOAw (ORCPT ); Mon, 16 Jun 2014 10:00:52 -0400 Date: Mon, 16 Jun 2014 16:00:47 +0200 From: Karel Zak To: Eric Rannaud Cc: util-linux@vger.kernel.org, Dave Reisner Subject: Re: Using findmnt in the presence of a stale NFS mount Message-ID: <20140616140047.GL30975@x2.net.home> References: <20140616132816.GK30975@x2.net.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20140616132816.GK30975@x2.net.home> Sender: util-linux-owner@vger.kernel.org List-ID: On Mon, Jun 16, 2014 at 03:28:16PM +0200, Karel Zak wrote: > > As it is, it is impossible to upgrade an Arch Linux install when there > > is a stale NFS mount anywhere on the system (and listed in fstab). > > You can try to exclude NFS at all by --types nonfs, but maybe we can > add option --nocanonicalize. I'll try to play with that tomorrow. OK, tomorrow is now ;-) (the option added) The problem is that this is not commonly usable solution, because it very significantly affects the way how libmount search in fstab, mountinfo etc. The option disallow to reliable compare symlinks, tags etc. It would be better to have NFS specific solution, or in the update/install script use --types nonfs and when only if not found required directories try fallback solution with --nocanonicalize or so. Karel -- Karel Zak http://karelzak.blogspot.com