Scratch

SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major EVENT-TIME: Thu Mar 5 17:41:00 EST 2009 PLATFORM: SUNW,Netra-240, CSN: -, HOSTNAME: clon10 SOURCE: zfs-diagnosis, REV: 1.0 EVENT-ID: 2f3d5430-2bbb-c8aa-87d5-f79b44f89edf DESC: The ZFS pool has experienced currently unrecoverable I/O failures. Refer to http://sun.com/msg/ZFS-8000-HC for more information. AUTO-RESPONSE: No automated response will be taken. IMPACT: Read and write I/Os cannot be serviced. REC-ACTION:

The pool has experienced I/O failures. Since the ZFS pool property 'failmode' is set to 'wait', all I/Os (reads and writes) are blocked. See the zpool(1M) manpage for more information on the 'failmode' property. Manual intervention is required for I/Os to be serviced. You can see which devices are affected by running 'zpool status -x':

1. zpool status -x

 pool: test
state: FAULTED

status: There are I/O failures. action: Make sure the affected devices are connected, then run 'zpool clear'.

  see: http://www.sun.com/msg/ZFS-8000-HC
scrub: none requested

config:

       NAME        STATE     READ WRITE CKSUM
       test        FAULTED      0    13     0  insufficient replicas
         c0t0d0    FAULTED      0     7     0  experienced I/O failures
         c0t1d0    ONLINE       0     0     0

errors: 1 data errors, use '-v' for a list

After you have made sure the affected devices are connected, run 'zpool clear' to allow I/O to the pool again:

1. zpool clear test

If I/O failures continue to happen, then applications and commands for the pool may hang. At this point, a reboot may be necessary to allow I/O to the pool again.

---

mgetty

Sergey --- does this help you ? Today marked the 3rd week since this case was opened....

Paul

---

Original Message --------

Subject: CASE 66172087 Date: Wed, 28 Jan 2009 12:39:51 -0500 From: Roland 'butch' Morrissette - Sun Microsystems <Roland.Morrissette@sun.com> To: letta@jlab.org

Paul

Received this from engineering. Hopefully this is of some helpfull.

xdm is creating $HOME/.Xauthority file, xauth only reads it. In $HOME/.Xdefaults file try adding the following entry as an alternate location to see if it works.

DisplayManager.DISPLAY.userAuthDir

• /DISPLAY should be the actual display, like

/DisplayManager.host1:0.0.userAuthDir: /path/to/alternate/file

• (If this does not work and still $HOME/.Xauthority file gets written

try changing the permissions on $HOME/.Xauthority file to readonly)

Regards,

--

Roland 'Butch' Morrissette Sun Service OS Support Sun Microsystems, Inc.

phone: (781) 442-7112 email: roland.morrissette@sun.com (800)USA-4SUN (Reference your Case Id #)

My Working Hours : 8am-4pm ET, Monday thru Friday My Manager's Email: dawn.ball@sun.com

5126 303-6644

CLAS12 DC (Mac 14-nov-2007): 2 stereo, +-6 degrees, good resolution (1% dp/p, 1 mrad angle), six 6-layer superlayers, 112 wires per layer; reconstruction improvements: use double hits, use segment angle in road dictionary, early l-r ambig. resolution (now it resolved locally and then corrected after track reconstructed ?), find tracks with no TOF hit and cut off accidental tracks (using residials ?), derive off-diagonal terms in error matrix

SVT readout:

SVX4 - old chip 132ns clock, 40pipeline cells ->5.2us trigger latency; can select readout window like pipeline TDCs (position defined +-132us, window size 132ns fixed) initial part stored upto 4 events, they are rotating internally 32 bits per hit, 128 channels per chip, ... -> 3.2us per chip to get data from the chip to the buffer of 512 full events L2 pipeline 16us L1 latency from Amrit is 3us, Amrit will try to make it 4us Use the same clock as entire CLAS12 trigger system (256MHz)

FSSR 125ns instead of 132ns (built for BTev, never used) self-triggering, do not need L1ACCEPT, L2 pipe 16us can be implemented

SVX4 goes to review !!!

Generic DAQ drawing will be sent to Amrit in April