From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 10 Oct 2011 09:17:09 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <1dc3dbdc0c9e0ecbc86047c58e0a2d33@hamnavoe.com> <6c0a6fdef3589e5cb13618f19d9ac9fc@chula.quanstro.net> <27cbf24b3414cf47835e99ecbbd97e6d@brasstown.quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] copying fossil filesystem to a bigger disk Topicbox-Message-UUID: 35a1f3be-ead7-11e9-9d60-3106f5b1d025 > su# disk/mkfs -a -s / <{echo +} > arch > processing /fd/7 > mkfs: /fd/7:1: can't open //dev/consctl: '//dev/consctl' permission denied > mkfs: /fd/7:1: can't open //dev/kprint: '//dev/kprint' device or > object already in use > > I guess it wasn't the brightest idea, because the arch file grew much > bigger than all my files put together on the old drive. > > Should I mount the new drive to /n/kfs and not use the -a option? I > was a little confused about these references to kfs while my > filesystem is fossil. you're not the first person to make this mistake, so i should have remembered this problem. sorry. you need to mount both new and old afresh in /n/ and copy using your destination as /n/new and source as /n/old. using / as your source doesn't work because you have many things other than the file server intended mounted. for example, your first error messages are because #c is mounted on /dev. - erik