Date: Mon, 19 Jun 1995 21:37:54 -0700 From: "Russell L. Carter" <rcarter@geli.com> To: freebsd-bugs@freebsd.org Cc: rcarter@geli.com Subject: more on st cataclysmic error 8-) Message-ID: <199506200437.VAA00321@geli.clusternet>
next in thread | raw e-mail | index | archive | help
Ok, I've got some more data on the /dev/rst0 bug. There still remains the possibility that it is my drive. Careful watching showed the following output from ncrcontrol: 24 456 4 256 0 0 20 200 19456 6 1 24 1 19 260 5 120 0 0 14 140 14013 7 0 19 0 22 380 4 200 0 0 18 180 17687 6 2 22 2 18 288 2 128 0 0 16 160 16384 3 0 18 0 11 218 2 128 0 0 9 90 20294 3 0 11 0 23 392 3 192 0 0 20 200 17453 5 1 23 1 16 268 2 128 0 0 14 140 17152 3 0 16 0 16 268 2 128 0 0 14 140 17152 3 1 16 1 12 228 2 128 0 0 10 100 19456 3 1 12 1 10 154 1 64 0 0 9 90 15770 3 0 10 0 18 342 3 192 0 0 15 150 19456 6 1 18 1 36 576 4 256 0 0 32 320 16384 5 1 36 1 13 238 2 128 0 0 11 110 18747 3 1 13 1 16 252 2 112 0 0 14 140 16128 3 0 16 0 32 544 8 304 0 0 24 240 17408 11 0 32 0 12 228 2 128 0 0 10 100 19456 4 0 12 0 16 268 2 128 0 0 14 140 17152 3 1 16 1 total ST32550N CD-ROM C 4326XX 2 transf. disconn interru t/s kb/s t/s kb/s t/s kb/s t/s kb/s length exp une fly brk 5 50 0 0 0 0 5 50 10240 0 0 5 0 12 228 2 128 0 0 10 100 19456 2 0 12 0 10 154 1 64 0 0 9 90 15770 2 0 10 0 7 124 1 64 0 0 6 60 18139 2 1 7 1 18 274 9 184 0 0 9 90 15588 17 0 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 154 1 64 0 0 9 90 15770 1 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 28 496 4 256 0 0 24 240 18139 5 1 28 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 1024 2 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12 157 2 57 0 0 10 100 13397 2 1 12 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 32 544 8 304 0 0 24 240 17408 9 1 32 1 total ST32550N CD-ROM C 4326XX 2 transf. disconn interru t/s kb/s t/s kb/s t/s kb/s t/s kb/s length exp une fly brk 0 0 0 0 0 0 0 0 0 0 0 0 0 39 660 5 320 0 0 34 340 17329 6 0 39 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 154 1 64 0 0 9 90 15770 2 1 10 1 28 496 4 256 0 0 24 240 18139 4 0 28 0 At the very start the throughput is about 2x better than what you see at the top of the ncrcontrol output. This, allowed to complete the progression, hangs my system every time. An immediate ^C on the pax process gave: /usr/local/pkg/numerics/medusa/medusa/examples/sphere/grid.uu /usr/local/pkg/numerics/medusa/medusa/examples/sphere/headdp /usr/local/pkg/numerics/medusa/medusa/examples/sphere/grid.fmt^C pax: Signal caught, cleaning up. pax: Waiting for tape drive close to complete...done. pax: ustar vol 1, 21573 files, 0 bytes read, 380528640 bytes written. geli# I ejected the tape, reinserted it, and then tried: geli# pax -rvf /dev/rst0 windocs.tar.gz windocs.tar.gz.1Jun 19 21:23:52 geli /kernel: in getcc reselect by t1. Jun 19 21:23:52 geli /kernel: in getcc reselect by t1. Jun 19 21:24:23 geli last message repeated 118 times Jun 19 21:24:23 geli last message repeated 118 times windocs.tar.gz.2^C pax: Signal caught, cleaning up. pax: Waiting for tape drive close to complete...done. pax: ustar vol 1, 3 files, 6563840 bytes read, 0 bytes written. I'm using pax because it's more verbose about it's problems. Tar is much less verbose about the exact same problem. After this, the regular file systems are ok, and there is nothing detected by fsck. What's up? Nothing interesting is output to either the console or /var/log/messages at this stage. Russell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506200437.VAA00321>