https://bugzilla.novell.com/show_bug.cgi?id=478482 User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=478482#c10 --- Comment #10 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2009-02-27 00:44:22 MST --- I have some news on this issue: Yesterday I installed the new kernel, and things look better now. In the boot messages I noticed a difference regarding "reiserfs: using flush barriers". After a little while (when beagle became active?), I noticed these messages in syslog: kernel: REISERFS warning (device dm-2): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) associated with [1919251317 1634026030 0x656c67 UNKNOWN] kernel: REISERFS warning (device dm-2): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) associated with [1919251317 1634026030 0x656c67 UNKNOWN] [...] So I conclude that there is some type of data corruption on ReiserFS mounted via cryptotab_loop0. That could mean: 1) The data got corrupted, but undetected in openSUSE 11.0 (unlikely IMHO) 2) The data got corrupted, causing a freeze in openSUSE 11.1 (which would be bad) 3) The data got corrupted as a consequence of the freeze (which would be also bad) 4) The old kernel did not detect (or report) this type of corruption, but froze instead I don't know if the problem was really fixed in the new kernel, but obviously the problem is related to beagle-index, reiserfs, and cryptotab_loop My /home is mounted as: /dev/mapper/cryptotab_loop0 on /home type reiserfs (rw,acl,user_xattr) In reply to comment #8: I'll have to see whether the current kernel (2.6.27.19-3.2-pae #1 SMP 2009-02-25 15:40:44 +0100 i686 i686 i386 GNU/Linux) still freezes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.