https://bugzilla.novell.com/show_bug.cgi?id=273354 Summary: ext3 problems on cryptofs (updated from 10.2) Product: openSUSE 10.3 Version: Alpha 3plus Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: seife@novell.com QAContact: qa@suse.de CC: lnussel@novell.com, mkoenig@novell.com Since two days, i have lots of problems with my cryptohome, which i installed with 10.2. Filesystem is ext3. I often get things like this in the log: May 10 10:03:28 strolchi kernel: attempt to access beyond end of device May 10 10:03:28 strolchi kernel: sda6: rw=1, want=17592187503960, limit=10490382 May 10 10:03:28 strolchi kernel: Buffer I/O error on device sda6, logical block 8796093751979 May 10 10:03:28 strolchi kernel: lost page write due to I/O error on sda6 May 10 10:03:29 strolchi kernel: Buffer I/O error on device dm-0, logical block 8250 May 10 10:03:29 strolchi kernel: lost page write due to I/O error on dm-0 May 10 10:03:29 strolchi kernel: Aborting journal on device dm-0. May 10 10:03:33 strolchi kernel: ext3_abort called. May 10 10:03:33 strolchi kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal May 10 10:03:33 strolchi kernel: Remounting filesystem read-only After that, i did a fsck, which did find problems, fixed them and re-ran fsck multiple times, until there was no more problem. Later i got: May 10 13:07:56 strolchi kernel: attempt to access beyond end of device May 10 13:07:56 strolchi kernel: sda6: rw=1, want=17592192221596, limit=10490382 May 10 13:07:56 strolchi kernel: Buffer I/O error on device sda6, logical block 8796096110797 May 10 13:07:56 strolchi kernel: lost page write due to I/O error on sda6 May 10 13:07:56 strolchi kernel: Buffer I/O error on device dm-0, logical block 15266 May 10 13:07:56 strolchi kernel: lost page write due to I/O error on dm-0 May 10 13:07:56 strolchi kernel: Aborting journal on device dm-0. May 10 13:07:56 strolchi kernel: journal commit I/O error May 10 13:07:56 strolchi kernel: ext3_abort called. May 10 13:07:56 strolchi kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal May 10 13:07:56 strolchi kernel: Remounting filesystem read-only So i thought "well, e2fsck is just buggy and does not find the corruption", so i backed up the fs to a tarball, did "mkfs -j /dev/mapper/cryptotab_loop0", restored the backup. Now i got: May 10 17:24:55 strolchi kernel: attempt to access beyond end of device May 10 17:24:55 strolchi kernel: sda7: rw=1, want=70368860675912, limit=123652242 May 10 17:24:55 strolchi kernel: Buffer I/O error on device sda7, logical block 8796107584488 May 10 17:24:55 strolchi kernel: lost page write due to I/O error on sda7 May 10 17:25:58 strolchi kernel: attempt to access beyond end of device May 10 17:25:58 strolchi kernel: sda6: rw=1, want=17592189307012, limit=10490382 May 10 17:25:58 strolchi kernel: Buffer I/O error on device sda6, logical block 8796094653505 May 10 17:25:58 strolchi kernel: lost page write due to I/O error on sda6 May 10 17:25:59 strolchi kernel: Buffer I/O error on device dm-0, logical block 3613 May 10 17:25:59 strolchi kernel: lost page write due to I/O error on dm-0 May 10 17:25:59 strolchi kernel: Aborting journal on device dm-0. May 10 17:26:00 strolchi kernel: ext3_abort called. May 10 17:26:00 strolchi kernel: EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal May 10 17:26:00 strolchi kernel: Remounting filesystem read-only May 10 17:59:16 strolchi syslog-ng[3056]: STATS: dropped 0 Which is interesting, because sda7 is a different partition. The machine hung hard some time after that (i was away and when i came back, it was dead, no sysrq). my setup: seife@strolchi:~> cat /etc/fstab /dev/disk/by-id/edd-int13_dev80-part2 /boot ext2 acl,user_xattr 1 2 /dev/disk/by-id/edd-int13_dev80-part5 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/edd-int13_dev80-part7 /local ext3 acl,user_xattr 1 2 /dev/disk/by-id/edd-int13_dev80-part3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /home/seife/local/news /var/spool/news none rw,bind,noauto 0 0 seife@strolchi:~> cat /etc/cryptotab /dev/loop0 /dev/sda6 /home ext3 twofish256 noatime,user_xattr root@strolchi:/# fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 393 3156741 7 HPFS/NTFS /dev/sda2 * 394 399 48195 83 Linux /dev/sda3 400 530 1052257+ 82 Linux swap / Solaris /dev/sda4 531 9729 73890967+ 5 Extended /dev/sda5 531 1379 6819561 83 Linux /dev/sda6 1380 2032 5245191 83 Linux /dev/sda7 2033 9729 61826121 83 Linux Disk /dev/dm-0: 5371 MB, 5371075584 bytes 255 heads, 63 sectors/track, 652 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-0 doesn't contain a valid partition table I am not sure if this is a kernel problem or a problem with the new crypto setup we are using, so i am taking Ludwig and Matthias into cc: -- 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, or are watching someone who is.