Sebastien Delafond wrote: > On Tue, Nov 29, 2005 at 04:14:17PM -0700, Peter Karbaliotis wrote: > >>I tried with a new FSname but ran into the same problem. However, >>after some more testing, I determined that the problem seems to be >>with the options for the encrypted volume. I had originally set it >>up with the 'pre-configured paranoia' mode. The error went away >>when I tried again with 'standard mode'. > > > I am able to use the 'pre-configured paranoia mode' just fine; using a > new FSname: > > ~ # mount.gmailfs none /home/seb/gmailfs -o [EMAIL > PROTECTED],fsname=TestEncParanoia2 -p -e > Gmail password: > Creating new encrypted volume. > Please choose from one of the following options: > enter "x" for expert configuration mode, > enter "p" for pre-configured paranoia mode, > anything else, or an empty line will select standard mode. > ?> p > > Paranoia configuration selected. > > Configuration finished. > [...] > New Encfs Password: > Verify Encfs Password: > ~ # ls gmailfs > ~ # echo foo >| gmailfs/foo1 > ~ # cat gmailfs/foo1 > foo > ~ # > > >>I did my tests with debugging turned on, so I can provide you with the >>log file if you like. > > > Can you try the same sequence of commands as me, and see if you can > reproduce the problem again ? > > Cheers, > > --Seb >
Ok, I did exactly as you suggested and did not see the error. I then tried again copying the file I had started with and _did_ see the error. I copied files of various sizes and found that the problem only occurs when the file size exceeds 8192 bytes. Peter -- [EMAIL PROTECTED] 780-492-7660 Academic Information and Communications Technology University of Alberta -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
