[57] in The Cryptographic File System users list

home help back first fref pref prev next nref lref last post

Re: Possible Directory Bug in 1.4 Beta 2

daemon@ATHENA.MIT.EDU (Alex Raftis)
Thu Apr 23 21:28:09 1998

From owner-cfs-users@research.att.com Fri Apr 24 01:28:09 1998
Return-Path: <owner-cfs-users@research.att.com>
Delivered-To: cfs-mtg@bloom-picayune.mit.edu
Received: (qmail 5571 invoked from network); 24 Apr 1998 01:28:08 -0000
Received: from unknown (HELO rumor.research.att.com) (192.20.225.9)
  by bloom-picayune.mit.edu with SMTP; 24 Apr 1998 01:28:08 -0000
Received: from research.att.com ([135.207.30.100]) by rumor; Thu Apr 23 21:23:38 EDT 1998
Received: from amontillado.research.att.com ([135.207.24.32]) by research-clone; Thu Apr 23 21:25:17 EDT 1998
Received: from nsa.research.att.com (majordomo@nsa.research.att.com [135.207.24.155])
	by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id VAA12594;
	Thu, 23 Apr 1998 21:25:15 -0400 (EDT)
Received: (from majordomo@localhost) by nsa.research.att.com (8.7.3/8.7.3) id VAA12181 for cfs-users-list; Thu, 23 Apr 1998 21:22:59 -0400 (EDT)
X-Authentication-Warning: nsa.research.att.com: majordomo set sender to owner-cfs-users@nsa.research.att.com using -f
Received: from research.att.com (research-clone.research.att.com [135.207.30.100]) by nsa.research.att.com (8.7.3/8.7.3) with SMTP id VAA12177 for <cfs-users@nsa.research.att.com>; Thu, 23 Apr 1998 21:22:57 -0400 (EDT)
Received: from echidna.doverpacific.com ([207.114.133.4]) by research-clone; Thu Apr 23 21:23:49 EDT 1998
Received: from timewarp.doverpacific.com by echidna.doverpacific.com (NX5.67g/NX3.0M)
	id AA06388; Thu, 23 Apr 98 18:23:48 -0700
Message-Id: <9804240123.AA06388@echidna.doverpacific.com>
Received: by timewarp.doverpacific.com (NX5.67g/NX3.0X)
	id AA08382; Thu, 23 Apr 98 18:23:47 -0700
From: "Alex Raftis" <alex@echidna.doverpacific.com>
Date: Thu, 23 Apr 1998 18:23:46 -0700
To: cfs-users@research.att.com
Subject: Re: Possible Directory Bug in 1.4 Beta 2
Reply-To: "Alex Raftis" <alex@echidna.doverpacific.com>
Disposition-Notification-To: "Alex Raftis" <alex@doverpacific.com>
Received: by NLS.Mailer (0.9.RR)
References: <9804141845.AA24640@echidna.doverpacific.com>
In-Reply-To: <9804141845.AA24640@echidna.doverpacific.com>
Mime-Version: 1.0 (NLS Mail v1)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-cfs-users@research.att.com
Precedence: bulk

On Tuesday, April 14, 1998 you said:
>
> I recently noticed that as I was moving files into a crypted file
> system, the files were "disappearing". I say "disappearing" because
> they don't appear in a directory listing. However, they do exist. Ie,
> if I happen to remember the name, I can open and view the file, even
> though it's not appearing the in the directory listing. Looking into
> the problem futher, I find that the raw disk has 2187 (4293 including
> dot) files in the directory, but the clear text directory only shows a
> 121 files. Obviously, something is a little weird here. 
> 
> Unfortuneately, I can't use cname to try and list the files since I'm
> using the latest version of the file structure. 
> 
> Has anyone else encountered such a problem? Is there someway to get
> my files to show up again in plain text? 
> 
> BTW, I'm using cfs under a OPENSTEP 4.2 (BSD 4.3 filesystem) port of
> the daemon. 

This looks like it was a problem with network byte order. I can't,
for sure, say why it was a problem for me, and hasn't been a problem
for others. All I can think of is that NeXT's (Apple's)
implementation of NFS uses big-endian byte order, but I was running
on a little-endian (Intel) machine. 

Anyways, I added two uses of htonl and ntohl in the readdir portion of
the cfs_nfs.c, and my problem seems to have gone away. 

Alex Raftis
---
alex@doverpacific.com

home help back first fref pref prev next nref lref last post