http://bugzilla.kernel.org/show_bug.cgi?id=15025 --- Comment #5 from Steinar H. Gunderson <sgunderson@xxxxxxxxxxx> 2010-01-27 20:23:43 --- On Wed, Jan 27, 2010 at 07:35:11PM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > Sorry for not getting back to you right away; I've been doing a huge amount of > travel right during January. Can you tell me something about the file system > workload on your machine? What does it do? NFS, rsync server, backups, ...? IIRC this was a file system that was mainly used for video storage and transcoding -- I think I was encoding a video with x264 to it when it crashed. Apart from that the machine spends most of its I/O time doing web serving from relatively large (1-2TB) data sets, and occasionally rtorrent. It was recently online expanded, so I thought that might be related, but the problem persisted after a reboot and a forced fsck, so there was no on-disk corruption involved. > And do you know what it might be doing right before it crashed? How easily > can you reproduce this? I take it since you had to stop using 2.6.33-rcX you > could reproduce it easily? It crashed two times in two days or something after I upgraded to 2.6.33-rcX. Not a statistically huge sample, I'm afraid. > If you are willing to try a 2.6.33-rcX kernel, I'd suggest seeing if "echo 0 > > /sys/fs/ext4/<dev>/max_writeback_mb_bump" makes the crashes go away. I'm afraid it's not so easy for me to do reboots into new kernels on this machine; kernel upgrades generally happen when the machine is booted for some other reason. :-/ /* Steinar */ -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
