Coda File System

Re: oddity when restoring a coda client

From: Jan Harkes <>
Date: Tue, 30 Jan 2001 20:28:04 -0500
On Wed, Jan 31, 2001 at 10:21:19AM +1030, Brett Lymn wrote:
> Folks,
>         I have noticed an interesting thing when I went through the
> process of upgrading my hard disks on a couple of machines and noticed
> an oddity with the coda client.  During the change over, I carefully
> shutdown venus and then used dump/restore to copy the files from my
> old hard disk to the new one.  When I brought up coda on the new
> machine everything started fine and /coda was mounted.  I could see
> all the file _names_ and attributes in my coda tree but when I tried
> to access a file it was empty.  The files on the server were ok
> because a different client showed the correct file contents and when I
> did a "venus -init" on the affected client suddenly the files had
> contents.  Why would this be?

The inode number of the container file is stored in RVM. This is passed
down to the kernel. After the switch to the new harddisk the inode
numbers were different so the read/write calls were redirected to
non-existing container files.

Received on 2001-01-30 20:28:12