From owner-freebsd-amd64@freebsd.org Mon Nov 28 09:12:55 2016 Return-Path: Delivered-To: freebsd-amd64@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 D25C8C58A36 for ; Mon, 28 Nov 2016 09:12:55 +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 B8D041A87 for ; Mon, 28 Nov 2016 09:12:55 +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 uAS9CtD0036866 for ; Mon, 28 Nov 2016 09:12:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 214898] mount -a will remount a partition if it's a ramdisk by incrementing mdX Date: Mon, 28 Nov 2016 09:12:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bjornr@iceland2000.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2016 09:12:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214898 Bug ID: 214898 Summary: mount -a will remount a partition if it's a ramdisk by incrementing mdX Product: Base System Version: 10.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: bjornr@iceland2000.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Before mount -a: /var/run and /tmp are mounted as ramdisk: md /tmp mfs rw,-s512M,noatime 0= =20=20=20=20=20 0 md /var/run mfs rw,-s32M,noatime 0= =20=20=20=20=20=20 0 df -h |grep md /dev/md0 on /tmp (ufs, local, noatime, soft-updates) /dev/md1 on /var/run (ufs, local, noatime, soft-updates) After mount -a: df -h |grep md /dev/md0 496M 52K 456M 0% /tmp /dev/md1 31M 128K 28M 0% /var/run /dev/md2 496M 8,0K 456M 0% /tmp /dev/md3 31M 8,0K 28M 0% /var/run Executing commands in /usr/local/bin will now fail: # bash Shared object "libintl.so.8" not found, required by "bash" Does not happen on FreeBSD 10.2, will also happen on FreeBSD 11.0-RELEASE Affects: 11.0-RELEASE-p3 10.3-RELEASE-p12 Temporary resolution: umount the filesystems and for /var/run, execute: ldconfig /usr/local/lib This does not happen when the md devices are explicitly named in fstab: md0 /tmp mfs rw,-s512M,noatime 0= =20=20=20=20 0 md1 /var/run mfs rw,-s32M,noatime 0= =20=20=20=20=20 0 But mount -a returns: mount -a mount_mfs: mdconfig (attach) exited with error code 1 mount_mfs: mdconfig (attach) exited with error code 1 According to the man page: # UFS file system on a swap-backed md(4). /dev/md10 is # automatically created. If it is "md", a unit number # will be automatically selected. md10 /scratch mfs rw,-s1g 0 0 But at some time, after 10.3-RELEASE it will not re-use, but create new md devices? --=20 You are receiving this mail because: You are on the CC list for the bug.=