[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20041205: LDM for the SURA SCOOP project and bigbird

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20041205: LDM for the SURA SCOOP project and bigbird
  • Date: Sun, 05 Dec 2004 10:08:38 -0700
>From:  Gerry Creager N5JXS <address@hidden>
>Organization:  Texas A&M University -- AATLT
>Keywords:  200412031403.iB3E3olI004347 LDM NEXRAD Level II SURA SCOOP

Hi Gerry,

>Matt and I were on the same conference call.  Sorry for the multiple 
>contacts.

No worries.

>My recommendation on that call was to use EXP (somehow I thought it was 
>EXPER) for now and seek an additional product name formally in the future.

This is a good place to start.

>Please take a look at the Bird sometime.  We're up running FC2, the 
>3Ware and 8 drives in RAID 10.  3Ware thinks the problems I've been 
>seeing are a combination driver code problem of theirs with the 2.6 
>kernel, and the slower transfer rate of P-ATA drives in RAID5.  They've 
>offered a real deal I'll be ordering up tomorrow, on the SATA 
>controller, and I think I can leverage something on getting 10 SATA 
>drives for the Bird.

After seeing your message this morning, I jumped onto bigbird and took
a quick look around.  Since I saw that there were more than 30 days of
Level II data under /data/ldm/gempak/nexrad/craft_all, I decided to
look harder to see what was going on.  I found that a number of the
directories were owned by 'root', so the scour processes running under
ldm's cron were not working:

drwxr-xr-x  103 root root 4096 Dec  3 00:08 20041119
drwxr-xr-x  103 root root 4096 Dec  3 00:06 20041118
drwxr-xr-x  102 root root 4096 Dec  2 23:59 20041117
drwxr-xr-x  102 root root 4096 Dec  2 23:56 20041116
drwxr-xr-x  102 root root 4096 Dec  2 23:55 20041115
drwxr-xr-x   98 root root 4096 Dec  2 23:50 20041114
drwxr-xr-x  100 root root 4096 Dec  2 23:46 20041113
drwxr-xr-x  102 root root 4096 Dec  2 23:40 20041112
drwxr-xr-x  102 root root 4096 Dec  2 23:35 20041111
drwxr-xr-x  102 root root 4096 Dec  2 23:26 20041110
drwxr-xr-x  103 root root 4096 Dec  2 23:20 20041109
drwxr-xr-x  102 root root 4096 Dec  2 23:16 20041108
drwxr-xr-x  102 root root 4096 Dec  2 23:11 20041107
drwxr-xr-x  102 root root 4096 Dec  2 23:08 20041106
drwxr-xr-x  103 root root 4096 Dec  2 23:03 20041105
drwxr-xr-x  126 root root 4096 Dec  2 22:57 20041104
drwxr-xr-x  125 root root 4096 Dec  2 22:48 20041103
drwxr-xr-x  125 root root 4096 Dec  2 22:38 20041102
drwxr-xr-x  124 root root 4096 Dec  2 22:26 20041101

I changed the ownership to ldm:ldm and am running scourBYday.tcl to
scour back to 30 days.  Since it is taking some time to run (as
expected), I will stay logged on for awhile.

Other than that, I didn't see anything majorly wrong.  I will look
some more after breakfast.

>Things are back to looking good...

Excellent news!

Cheers,

Tom

>From address@hidden  Sun Dec  5 19:06:05 2004

Argh.  I remembered last evening, after going to bed, that I'd forgotten 
to change back the permissions.  Of course, I didn't get right up and 
fix it!

I'll be up your way 24-28 JAN, after AMS.  MM5 training.

Later, gerry