https://bugzilla.novell.com/show_bug.cgi?id=641037 https://bugzilla.novell.com/show_bug.cgi?id=641037#c0 Summary: end_request: I/O error, dev cciss/c0d0, sector 0 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: steffen.neuser@computacenter.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; NET CLR 2.0.50727; .NET CLR 3.0.04506; InfoPath.2) similar to Bug 575697 - end_request: I/O error, dev vda, sector 0 Rhythm is all 5s, 2 times in /var/log/warn, so you'll need a good logrotation Sep 17 13:12:52 ... kernel: [1064270.352326] end_request: I/O error, dev cciss/c0d0, sector 0 DL320 G6 + P212 Smartarray Raid-1 + Hot-Spare + Suse 11.2 using ext4 and LVM, 5 month old installation # rpm -qf /lib/modules/2.6.31.12-0.2-default/kernel/drivers/block/cciss.ko

kernel-default-2.6.31.12-0.2.1.x86_64

could the mentioned kernel patch in Bug 575697 could solve this problem as well? Is this path already out and available by online update? If not I want to ask for an official kernel patch. I contacted a maintainer of cciss at HP and he mentioned, that this kernel patch http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=commit... should fix the problem. His explaination of the problem: "I think it is the block layer complaining about unsupported barriers, but since the smart array turns drive write cache off, and instead has its own battery backed write cache, or else no cache (in other words all write caching is either battery backed or it's not enabled) this means the barriers aren't needed, so the fact that the driver doesn't support them is of no consequence." Reproducible: Always Steps to Reproduce: 1. reproduceable allways with this HW/installation 2. 3. -- 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.