Re: cfs reports Input/Output error
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 encrypted
partition (using the loop device), which, in the end, does the same
thing, and i do not see any disadvantages compared to cfs.
Sergio Mendoza wrote:
> 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 cryptographic file system... Please let me know if you manage to get
> rid of the error I mentioned on my previous postings.
> On Fri, Sep 22, 2006 at 12:17:51AM -0500, Sergio Mendoza wrote:
>> 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 strace on this, but didn't get anything. Any
>>>> ideas on how to fix this.
>>> Run dmesg or check /var/log/kern.log to see if there is any explanation
>>> as to why.
>> The error is:
>> Sep 22 00:14:49 izta kernel: RPC call_verify: retry failed, exit EIO
>> Sep 22 00:14:50 izta kernel: call_verify: server accept status: 5
>> Sep 22 00:14:50 izta last message repeated 2 times
>>> Is this amd64-specific?
>> Yes, this is amd64-specific.
>>> Hamish Moffatt VK3SB <email@example.com> <firstname.lastname@example.org>
>>> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact email@example.com
>> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org