Hello,

I rented a new machine a couple of days ago,
and it happens:

Test: Transfer some 5GB of files to the machine

Works fine as long as I use one of the drives individually.

If I gmirror the drives
        gmirror label gm0 ada0
        gmirror insert gm0 ada1
        ...wait for rebuild

the machine reliably locks up on the file transfer,
with a frozen systat screen showing both drives at 100% busy:


   10 users    Load  0,41  0,44  0,20                   6 Jul 18:47

Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out
Act   23496    6036   600772    12252 1361840  count
All   71680    6632 1074428k    28264          pages
Proc:                                                            Interrupts
  r   p   d   s   w   Csw  Trp  Sys  Int  Sof  Flt        cow     121 total
28 199 2 121 4 67 zfod atkbd0 1 ozfod 4 re0 16 0,4%Sys 0,0%Intr 0,0%User 0,0%Nice 99,6%Idle %ozfod atapci0 20 | | | | | | | | | | | daefr 94 cpu0:timer prcfr 23 cpu1:timer
                                      1333 dtbuf        4 totfr
Namei     Name-cache   Dir-cache    111358 desvn          react
   Calls    hits   %    hits   %      1009 numvn          pdwak
       3       3 100                    32 frevn          pdpgs
                                                          intrn
Disks  ada0  ada1 pass0 pass1                      302680 wire
KB/t  16,00 16,00  0,00  0,00                       14716 act
tps       1     1     0     0                      334260 inact
MB/s   0,02  0,02  0,00  0,00                             cache
%busy   100   100     0     0                     1361840 free
                                                   217488 buf

While the network stays responsive, i. e. I can ping the machine and _connect_ via ssh,
I can't actually log in (or, in already open shell, execute anything).
System requires a hardware reset. Nothing in the logs whatsoever (no surprise here).

I have no KVM access to this system.

OS is generic 9.0 stable from two days ago.

I run 8.2-R on an identical machine without trouble.
I run 9.0 stable as of May 4th on an similiar (other CPU and NIC) machine without trouble.
On both machines, the drives are recognized as ``ad''.
(Why btw? ``man ada'' says ``device ada'', but there is no such option in the GENERIC config. Do I get ``ada'' with ``device ATA_CAM ''? I'm going to try this next, kick ata_cam from the kernel, see if drives are ``ad'' and system doesn't crash.)


I'd appreciate suggestions on what I could do.

Thanks,

Michael
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to