On Friday 20 August 2004 16:40, Jari Ruusu wrote: > Jari Ruusu wrote: > > David Gümbel wrote: > > > All is running fine, except for the encrypted /home, which shows this > > > error > > > > > > after some time of work (usually 10 to 30 minutes): > > > > Aug 16 19:36:26 [kernel] EXT3-fs error (device loop0): > > > > ext3_readdir: directory # 783444 contains a hole at offset 8192 > > > > Aug 16 19:36:32 [kernel] ext3_abort called. > > > > Aug 16 19:36:32 [kernel] EXT3-fs abort (device loop0): > > > > ext3_journal_start: Detected aborted journal > > > > Aug 16 19:37:04 [kernel] EXT3-fs error (device loop0) in > > > > start_transaction: Journal has aborted > > > > - Last output repeated 4 times - > > > > Aug 16 19:37:22 [su(pam_unix)] session closed for user root > > > > Aug 16 19:37:22 [kernel] EXT3-fs error (device loop0) in > > > > start_transaction: Journal has aborted > > > > - Last output repeated 52 times - > > > > I am unable to reproduce any such errors in my test using kernel > > 2.6.8.1 and loop-AES-v2.1c and ext3 file system on my x86 test box. > > > > > I did not really change the configuration for my kernel (did a make > > > oldconfig); the only "major" thing that is different between my 2.6.7 > > > and my 2.6.8.1 config is the use of mregparm=3 in the latter case. > > > > I have tested loop-AES using mregparm=3 in my earlier tests, and they > > worked ok. gcc version in those tests was 3.3.2 . Today's test kernel > > was compiled with Debian woody gcc-2.95.4, and no mregparm=3 was used. > > I recompiled kernel 2.6.8.1 using gcc-3.3.2 and this time with > mregparm=3. I stress tested ext3 file system on loop-AES-v2.1c, using > AES128 encryption for 8 hours. Again, I was unable to reproduce these > errors. Thanks a lot for your efforts! I shall try to debug the problem further this weekend, after making a full backup of the device and trying to reproduce the error eith the copy. I'll keeep you posted. Regards, David
Attachment:
pgpcbZuRaoQTm.pgp
Description: PGP signature
