Re: Problems with 2.6.8.1, loop-AES and ext3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 20 August 2004 20:07, David Gümbel wrote:
> On Friday 20 August 2004 16:40, Jari Ruusu wrote:
[..]
> > 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.

OK, I recompiled my 2.6.8.1+loop-AES 2.1c without mregparm=3 and tried the 
following:

* updated portage tree (emerge rsync) and started an excessive compile to 
get some load on /var and /usr (both unencrypted ext3) - worked fine
* while the compile had already been running for some time, log into X and 
start KDE. Fire up som konquerors, surf, run some emerge -pv etc. and run 
KMail to check my mails. When writen a response to a mail I recieved, KMail 
died saying someting about insufficient write permissions on its temporary 
file, and voila, the old error had reoccured:

> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 32768
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 90112
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 
> 802557 contains a hole at offset 106496
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 122880
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 151552
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 172032
> Aug 21 15:30:08 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 188416
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 200704
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 212992
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 233472
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 282624
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 303104
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 319488
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 335872
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0): ext3_readdir:
> directory # 802557 contains a hole at offset 348160
> Aug 21 15:30:09 [kernel] ext3_abort called.
> Aug 21 15:30:09 [kernel] EXT3-fs error (device loop0) in
> start_transaction: Jour 
> nal has aborted
>                 - Last output repeated 3 times -

So the problem doesn't seem to be related to register parameters. 


Any ideas?




Regards,



David

Attachment: pgpnyMzSfAVb2.pgp
Description: PGP signature


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux