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

Re: thelma disk errors

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: Re: thelma disk errors
  • Date: Tue, 23 May 2000 13:43:16 -0600 (MDT)
Mike,

That's great, how about we do it tomorrow morning. I'm sure that will make
the ldm more stable.

Robb...


On Tue, 23 May 2000, Mike Schmidt wrote:

> Robb,
> 
> Since the beginning of April, thelma has consistently logged disk errors
> on six distinct bad blocks -- those are;
> 
>   152146
>   383922
>   383951
>   420892
>   423612
>   424715
> 
> I have removed all except the first from the active block list.  It turns
> out that block 152146 is actively used by the ldm;
> 
> % xfs_check -b 152146 /dev/root
> setting block 4/21074 to data
> setting inode to 568960 for block 4/21074
> inode 568960 block 152146 at offset 6697
> 
> % xfs_ncheck -i 568960 /dev/root
>      568960 export/local/ldm/data/ldm.pq
> 
> so we'll need to stop the ldm, remove the product queue, remove the block
> from the active block list, and restart the ldm.  Let me know when you
> want to do this.
> 
> mike
> 
> 
> 
> 
> 
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================