> NDSU_ITS_Misc:083  0 KB
> NDSU_ITS_Misc:086 1930 KB
> NDSU_ITS_Misc:088  0 KB
> NDSU_ITS_Misc:103 78 GB
> NDSU_SLA:008       0 KB
>
> As you can see, we have quite a few volumes with one or more suspect
> savesets that have not been read since they were last relabelled.

Interesting.  Have these been cloned?

My test box doesn't have any 'suspect' data sets, so I can't really
reproduce this right now.  Maybe if I power cycle the drive... :-)

I must confess though, that the query isn't really specific enough to
completely rule it out yet.

Your first query is listing volumes containing suspect savesets.  Those
savesets may span multiple volumes.  So it would be possible to have a
fragment on one volume with a read error, even though another volume
that has the saveset has not ever been read.  To get more information,
you'd either have to limit the query to savesets that were contained on
only a single volume, or be able to find suspect 'fragments'.

The man page doesn't suggest that the 'fragflags' report would do
anything useful about reporting suspect portions.

Could you redo your first query like this?

 mminfo -q 'suspect' -r 'sumflags,volume' | awk '/^c/ {print $2}'


--
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=