On Thu, Jun 18, 2009 at 9:01 AM, John Floren <slawmas...@gmail.com> wrote: > > Our Coraid device recently lost two disks from the RAID5 > configuration; while we were able to rebuild from instructions given > by support, I suspect some small amount of data was corrupted. > > Since rebuilding the device a few days ago, every morning I have > returned to work to find my CPU/auth/file server in a classic "lost my > file system" state--not locked, but trying to run any command causes > it to hang. Also, files have been corrupted--here's the top bit of a > copy of /sys/src/cmd/rio/fsys.c that I was working on: > � > � 4 " �C�/� TEXBASE1ENCODING + DVIPSENCODING TEX-PTMRI8R �H > } m ����� � a a � � �@ �8 � T� > �( �X � � � � � � & 0 ! �� � � � � � � > �< �T � f � P � � � � � * �@ � . �D �Q4 � < > ��t �m> �}E � > J �X ��Q � T � \ � b � e � k ��m �a} ��� > ��� �d ��� �p > > Any ideas? I thought maybe fossil was choking somewhere, maybe bad > info on venti? > > Thanks > > John
Forgot to add that I've only seen one error on the console during all of this: /boot/fossil: could not write super block; waiting 10 seconds /boot/fossil: blistAlloc: called on clean block. John -- "I've tried programming Ruby on Rails, following TechCrunch in my RSS reader, and drinking absinthe. It doesn't work. I'm going back to C, Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba
