Re: cfs reports Input/Output error

2006-09-25 Thread Franz Schenk
Hi Sergio, I cannot provide any help, sorry, but i can give you my own experiences. I used to be in exactly the same situation some time ago (I also posted to this list, check the archives for details). In the end I gave up, as far as i know cfs simply does not work on amd64. I now use an

Re: cfs reports Input/Output error

2006-09-24 Thread Sergio Mendoza
Hi, I'm still in the same situation. Can a few of you install cfs and try to create an encrypted directory ( $ cmkdir somedir ) and then mount it ( $ cfssh somedir) and check whether you can ls on the mounted directory (cffsh will put you on the right mounted dir). I can't live without the

cfs reports Input/Output error

2006-09-22 Thread Sergio Mendoza
Hi, I'm using cfs on an amd64 (sid). The Cryptographic File System (cfs) deb package used to work fine. Haven't used it for a while on amd64 (only on i386) and now... it doesn't work. I can manage to mount the encrypted directory by doing: $ cfssh directory The problem is when I try to

cfs reports Input/Output error

2006-09-21 Thread Sergio Mendoza
Hi, I'm using cfs on an amd64 (sid). The Cryptographic File System (cfs) deb package used to work fine. Haven't used it for a while on amd64 (only on i386) and now... it doesn't work. I can manage to mount the encrypted directory by doing: $ cfssh directory The problem is when I try to

Re: cfs reports Input/Output error

2006-09-21 Thread Hamish Moffatt
On Thu, Sep 21, 2006 at 11:30:57PM -0500, Sergio Mendoza wrote: $ ls ls: reading directory .: Input/output error My guess is that this is a problem with the way things are mounted, not ls. I've tried to do an strace on this, but didn't get anything. Any ideas on how to fix this.

Re: cfs reports Input/Output error

2006-09-21 Thread Sergio Mendoza
Hi, On Fri, Sep 22, 2006 at 03:07:47PM +1000, Hamish Moffatt wrote: On Thu, Sep 21, 2006 at 11:30:57PM -0500, Sergio Mendoza wrote: $ ls ls: reading directory .: Input/output error My guess is that this is a problem with the way things are mounted, not ls. I've tried to do an