From owner-freebsd-stable@FreeBSD.ORG Sat Aug 20 19:44:46 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E922D106566B for ; Sat, 20 Aug 2011 19:44:46 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 839148FC0C for ; Sat, 20 Aug 2011 19:44:46 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id F29FC153434 for ; Sat, 20 Aug 2011 21:44:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7qEMSDvelXP for ; Sat, 20 Aug 2011 21:44:43 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:c02b:ce62:71ff:9cbc] (unknown [IPv6:2001:4cb8:3:1:c02b:ce62:71ff:9cbc]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id 1BD16153433 for ; Sat, 20 Aug 2011 21:44:43 +0200 (CEST) Message-ID: <4E500EAE.10005@digiware.nl> Date: Sat, 20 Aug 2011 21:44:46 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: "stable@freebsd.org" References: <4E4F973D.9070706@digiware.nl> <4E4F99E4.8060009@digiware.nl> In-Reply-To: <4E4F99E4.8060009@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Remote installing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Aug 2011 19:44:47 -0000 On 20-8-2011 13:26, Willem Jan Withagen wrote: > On 2011-08-20 13:15, Willem Jan Withagen wrote: >> Hi, >> >> Today I liked to live dangerously, and want to upgrade a backups server >> from i386 to amd64. Just to see if we could. >> And otherwise I'd scap it and install from usb-stick. >> >> So I have my server running amd64 build GENERIC. >> export /, /var, /usr on the server to be upgraded. >> >> But upgrading world dus have a snag already early on: >> >> ---- >> empty changed >> flags expected "schg" found "none" not modified: Operation not supported >> ---- >> >> This is probably where some program wants to set immutable flag on >> /var/tmp/empy... >> >> But looks like NFS does not grok that. >> >> Now I seen plenty of sugestions to do it this way, but never saw anybody >> come back with this complaint.... >> >> So I must be ommiting something ?? > > I looked at the work errors. > ----------- > cd /mnt/; rm -f /mnt/sys; ln -s usr/src/sys sys > cd /mnt/usr/share/man/en.ISO8859-1; ln -sf ../man* . > ln: ./man1: Permission denied > ln: ./man1aout: Permission denied > ln: ./man2: Permission denied > ln: ./man3: Permission denied > ln: ./man4: Permission denied > ln: ./man5: Permission denied > ln: ./man6: Permission denied > ln: ./man7: Permission denied > ln: ./man8: Permission denied > ln: ./man9: Permission denied > --------- > > Which comes from the target distrib-dirs in etc > > Why would an ln -sf like that fail.... > the filesystems are exported with -maproot=0 Well turned out that the easiest fix was to run chflags -R noschg / at the client, because certain files are immutable and once you run into those, it is hard to fix it after the fact. Next would be to move /lib and /usr/lib out of the way. So that doesn't cause conflict in near future. Which will cause new programs to start to fail. So better make shure that every thing is set before you start upgrading over NFS. But I did manage to get it "upgraded" from i386 to amd64. --WjW