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

Re: Problems with 2.6.8.1, loop-AES and ext3

hi *,

>>>>> "DG" == David Gümbel <david.guembel@xxxxxx> writes:

DG> OK, I recompiled my 2.6.8.1+loop-AES 2.1c without mregparm=3 and

>> 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

i can confirm this. i also run into this problem while upgrading the
kernel. but let me explane. 

my fileserver is running fedora-core 2 + loopAES on a hardware raid5
(3ware 7506-4LP). this box worked like a charm until i upgraded to the
latest fedora-kernel 2.6.7-1.494.2.2 (of course custom with loopAES
2.1c as a module). there where _no_ errors in the past. i am running
this for 1 year now starting with something like 2.4.13 and loopAES
1.6X.

last kernel before the error occured: 2.6.6-1.435.2.3custom with
loopAES 2.1b and loopAES 2.1c (running fine for weeks)

then with 2.6.7-1.494.2.2custom:

Aug 16 08:53:06 gk kernel: EXT3-fs error (device loop2):
ext3_readdir: directory #917516 contains a hole at offset 503808
Aug 16 08:53:06 gk kernel: Aborting journal on device loop2.
Aug 16 08:53:06 gk kernel: ext3_abort called.
Aug 16 08:53:06 gk kernel: EXT3-fs abort (device loop2):
ext3_journal_start: Detected aborted journal
Aug 16 08:53:06 gk kernel: Remounting filesystem read-only

Aug 17 21:35:58 gk kernel: EXT3-fs error (device loop2):
ext3_find_entry: reading directory #458753 offset 2
Aug 17 21:35:58 gk kernel:
Aug 17 21:35:58 gk kernel: Aborting journal on device loop2.
Aug 17 21:35:58 gk kernel: ext3_abort called.
Aug 17 21:35:58 gk kernel: EXT3-fs abort (device loop2):
ext3_journal_start: Detected aborted journal
Aug 17 21:35:58 gk kernel: Remounting filesystem read-only


both errors were easy to repair but i switched back to the "old"
kernel because i like my data:). again no problems. 

i have no idea how to reproduce/force this error, it was very rare (2
times in 3 days.) 


DG> Any ideas?

i also have no idea.



best regards,

     alex

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/