From: SourceForge.net <no...@so...> - 2009-11-16 13:16:20
|
Bugs item #2895531, was opened at 2009-11-10 23:34 Message generated for change (Comment added) made by germansalvador You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mkfs.ext3 freezes on scsi disks Initial Comment: I have tryed to make a mkfs.ext3 on /dev/sda1, wich is the only partition crreated on a scsi disk, backed by a plain file. I am using 0.7.5 with the debian lenny root filesystem image. The scsi parameter I am adding to the conf file is just scsi0=disk,j:\test.bin (test.bin is a 8 GB empty file) What happens is that mkfs starts quickly, but soon slows down, and can even freeze colinux. Sometimes it crashes windows also. This also happened on the latest devel snapshot, and also when the scsi backing is a raw device. Tested con Windows XP SP2 ---------------------------------------------------------------------- Comment By: German Salvador (germansalvador) Date: 2009-11-16 14:16 Message: Ok, I have tried with this snapshot, and it "almost" works, it still slows down a lot, but although it eventually seems to complete, there are a lot of errors about "rejecting I/O to a offline device" or something like that, and after the command finishes, the device is not visible any more. This is trying to write to scsi0=disk,\device\harddissk2\partition0,8100 , wich is a USB pen drive attached. Sometimes, even, the windows mouse stops moving and I can see a windows balloon complaining about usb device nor working properly. When the mkfs.ext3 ends, it recovers. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-15 16:48 Message: SVN revision r1293 should fix that bug. There we have limited the worker queue from 73 down to 32 entries, and changed the queue type from Critical into Delayed. Both changes are hints from MSDN. http://msdn.microsoft.com/en-us/library/aa490176.aspx: "Because the pool of system worker threads is a limited resource, ... used only for operations that take a short period of time." http://msdn.microsoft.com/en-us/library/aa490574.aspx: "Drivers must specify DelayedWorkQueue." A new snapshot 'devel' 20091115 is available on http://www.colinux.org/snapshots/ ---------------------------------------------------------------------- Comment By: German Salvador (germansalvador) Date: 2009-11-11 09:48 Message: I have tried with the 20091110 snapshot, downloaded from http://www.henrynestler.com/colinux/testing/stable-0.7.6/20091110-Snapshot/stable-coLinux-20091110.exe, and the bug is still there. About the memory, I tried with several options, but it makes no difference. Now I'm trying with the default debian-lenny.conf, wich has the mem line commented. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-11 01:51 Message: Ok, have seen it with 0.7.6-rc1 scsi0=disk,j:\test.bin,8192 Created primary partition on /dev/sda with fdisk mkfs.ext3 /dev/sda1 ... First coLinux stops doing, no keyboard reaction, The host is idle. Some seconds later, the host is no accessible. The mouse can move, and window-frames (GUI) can move with it. But, can not start taskmanager, and all of the windows-explorer hangs. It seams, that the complete filesystem is locked. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-11-11 00:22 Message: Please try 0.7.6-rc1 from todays build (with kernel 2.6.22.18), or the devel build after 2009-11-05 with kernel 2.6.25.20 - Because a bug #2890857 inside scsi driver was fixed last days. How many memory you have configured or used inside Linux? I ask, because we have fixed an other bug #2893343 this weekend. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2895531&group_id=98788 |