Messages in this thread | | | From | Ray_Van_Tassle-CRV004@email ... | Date | 22 Mar 96 10:43:03 -0600 | Subject | loop fs lockup (1.3.72) |
| |
Using 1.3.72, there is a bug/interaction between umsperf and loop device. No panic, no Oops, no Aiee, just total disk seizure. shift/scroll and ctrl/scroll both give their printouts. can shift VT's, just no disk access.
I did "umsperf -i1 -m4 -e0 -c [filename]" 1) filename = "/i/xxx" -- msdos fs on msdos disk-------works ok 2) filename = "/tmp/xxx" ext2 fs in a linux partition ---- works ok.
-with loop devices, using losetup & mount from mount-2.5g.tgz 3) filename = "/mnt0/xxx" /dev/loop0 (ext2). loop file on /tmp (ext2) ------- works ok 4) filename = "/mnt1/xxx" /dev/loop1 (ext2). loop file on /i (msdos) ------- hangs after umsperf prints "allocating new blocks .. 0/1"
Any ideas???? BTW, doing cp and cat to/from /mnt1 and /mnt0 (mounted as above), all seems to work ok, but I havn't tested with heavy load.
Thanks, Ray Van Tassle rayvt@comm.mot.com
| |