[Orca-users] Too many files created

Derek Winkler dwinkler at algorithmics.com
Wed Sep 1 08:44:26 PDT 2004


One of my problem systems has disks with names such as,

orca/lib% format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /ssm at 0,0/pci at 18,600000/scsi at 2/sd at 0,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /ssm at 0,0/pci at 18,600000/scsi at 2/sd at 1,0
       2. c2t3d0 <SEAGATE ST150176 cyl 31270 alt 2 hd 22 sec 142>
          /ssm at 0,0/pci at 18,600000/scsi at 2,1/sd at 3,0
       3. c3t60003BA13E6E60003FF9DEAD0000A38Ed0 <SUN-T4-0300 cyl 34657 alt 2
hd 104 sec 128>
          /scsi_vhci/ssd at g60003ba13e6e60003ff9dead0000a38e
       4. c3t60003BA13E6E60003FFAD056000D7E8Dd0 <SUN-T4-0300 cyl 34400 alt 2
hd 104 sec 128>
          /scsi_vhci/ssd at g60003ba13e6e60003ffad056000d7e8d
       5. c3t60003BA13E6E60003FFAD798000ACD24d0 <SUN-T4-0300 cyl 34657 alt 2
hd 104 sec 128>
          /scsi_vhci/ssd at g60003ba13e6e60003ffad798000acd24
       6. c3t60003BA13E6E60003FFAD249000603D9d0 <SUN-T4-0300 cyl 34402 alt 2
hd 104 sec 128>
          /scsi_vhci/ssd at g60003ba13e6e60003ffad249000603d9
Specify disk (enter its number):

Can Orca not handle the long names?

If I take a look at the orcallator file for that host it repeats the disks
with long names over and over, the current one I'm looking at has 308
columns with each of these disks repeated 42 times as a column.

Thanks for any help.

Using orcallator.se 1.37.

> -----Original Message-----
> From: Derek Winkler [mailto:dwinkler at algorithmics.com]
> Sent: Friday, July 09, 2004 1:23 PM
> To: 'orca-users at orcaware.com'
> Subject: RE: [Orca-users] Too many files created
> 
> 
> Here's one of the recent headers...
> 
> timestamp  locltime   uptime state_D state_N state_n state_s 
> state_r state_k
> state_c state_m state_d state_i state_t DNnsrkcmdit  usr%  
> sys%  wio% idle%
> 1runq  5runq 15runq #proc  #runque #waiting  #swpque scanrate #proc/s
> #proc/p5s  smtx smtx/cpu ncpus mntC_/ mntU_/ mntA_/ mntP_/ 
> mntc_/ mntu_/
> mnta_/ mntp_/ mntC_/usr mntU_/usr mntA_/usr mntP_/usr 
> mntc_/usr mntu_/usr
> mnta_/usr mntp_/usr mntC_/var mntU_/var mntA_/var mntP_/var mntc_/var
> mntu_/var mnta_/var mntp_/var mntC_/local3 mntU_/local3 mntA_/local3
> mntP_/local3 mntc_/local3 mntu_/local3 mnta_/local3 mntp_/local3
> disk_runp_c0t0d0 disk_runp_c1t0d0 disk_runp_c1t1d0 disk_runp_ssd34.fp2
> disk_runp_ssd33.fp2 disk_runp_ssd32.fp2 disk_runp_ssd31.fp2
> disk_runp_ssd34.fp3 disk_runp_ssd33.fp3 disk_runp_ssd32.fp3
> disk_runp_ssd31.fp3 disk_runp_c2t3d0
> disk_runp_c3t60003BA13E6E60003FFAD056000D7E8Dd0
> disk_runp_c3t60003BA13E6E60003FFAD798000ACD24d0
> disk_runp_c3t60003BA13E6E60003FF9DEAD0000A38Ed0
> disk_runp_c3t60003BA13E6E60003FFAD249000603D9d0
> disk_runp_c3t60003BA13E6E60003FFAD056000D7E8Dd0
> disk_runp_c3t60003BA13E6E60003FFAD798000ACD24d0
> disk_runp_c3t60003BA13E6E60003FF9DEAD0000A38Ed0
> disk_runp_c3t60003BA13E6E60003FFAD249000603D9d0 disk_peak disk_mean
> disk_rd/s disk_wr/s disk_rK/s disk_wK/s tape_rd/s tape_wr/s tape_rK/s
> tape_wK/s swap_avail page_rstim   freememK free_pages   ce0Ipkt/s
> ce0Opkt/s   ce0InKB/s   ce0OuKB/s   ce0IErr/s   ce0OErr/s   ce0Coll%
> ce0NoCP/s   ce0Defr/s   ce1Ipkt/s   ce1Opkt/s   ce1InKB/s   ce1OuKB/s
> ce1IErr/s   ce1OErr/s   ce1Coll%   ce1NoCP/s   ce1Defr/s tcp_Iseg/s
> tcp_Oseg/s tcp_InKB/s tcp_OuKB/s tcp_Ret% tcp_Dup% tcp_Icn/s tcp_Ocn/s
> tcp_estb tcp_Rst/s tcp_Atf/s tcp_Ldrp/s tcp_LdQ0/s tcp_HOdp/s 
> nfs_call/s
> nfs_timo/s nfs_badx/s nfss_calls nfss_bad  v2reads v2writes  v3reads
> v3writes dnlc_ref/s dnlc_hit% inod_ref/s inod_hit% inod_stl/s 
> pp_kernel
> pagesfree pageslock pagestotl
> 
> Anyone know what's going on with disk_runp_c3t6?
> 
> For the last run the headers alone were 50K.
> 
> Thanks.
> 
> > -----Original Message-----
> > From: Blair Zajac [mailto:blair at orcaware.com]
> > Sent: Wednesday, July 07, 2004 8:19 PM
> > To: Derek Winkler
> > Cc: 'orca-users at orcaware.com'
> > Subject: Re: [Orca-users] Too many files created
> > 
> > 
> > Derek Winkler wrote:
> > 
> > > Some of my systems create a new file in 
> > ~/orca/var/orca/orcallator every 5
> > > minutes...
> > > 
> > > -rw-r--r--   1 root     other        3900 Jul 07 16:40
> > > orcallator-2004-07-07-200.gz
> > > -rw-r--r--   1 root     other        3918 Jul 07 16:45
> > > orcallator-2004-07-07-201.gz
> > > -rw-r--r--   1 root     other        3939 Jul 07 16:50
> > > orcallator-2004-07-07-202.gz
> > > -rw-r--r--   1 root     other        3936 Jul 07 16:55
> > > orcallator-2004-07-07-203.gz
> > > -rw-r--r--   1 root     other        3941 Jul 07 17:00
> > > orcallator-2004-07-07-204.gz
> > > -rw-r--r--   1 root     other        3955 Jul 07 17:05
> > > orcallator-2004-07-07-205.gz
> > > -rw-r--r--   1 root     other       64052 Jul 07 17:10
> > > orcallator-2004-07-07-206
> > 
> > You probably have a mount point or something else that's 
> > changing pretty 
> > consistently.
> > 
> > Take a look at the first line of each of these files and see 
> > what changes there are.
> > 
> > Every time orcallator.se sees the addition or removal of a 
> > mount point, ethernet 
> > card, etc, it will start a new file.  This is to work around 
> > a bug in Orca.
> > 
> > Best,
> > Blair
> > 
> > -- 
> > Blair Zajac <blair at orcaware.com>
> > Plots of your system's performance - http://www.orcaware.com/orca/
> > 
> 
> This email and any files transmitted with it are confidential and
> proprietary to Algorithmics Incorporated and its affiliates
> ("Algorithmics").  If received in error, use is prohibited.  
> Please destroy,
> and notify sender.  Sender does not waive confidentiality or 
> privilege.
> Internet communications cannot be guaranteed to be timely, 
> secure, error or
> virus-free.  Algorithmics does not accept liability for any errors or
> omissions.  Any commitment intended to bind Algorithmics must 
> be reduced to
> writing and signed by an authorized signatory.
> _______________________________________________
> Orca-users mailing list
> Orca-users at orcaware.com
> http://www.orcaware.com/mailman/listinfo/orca-users
> 

This email and any files transmitted with it are confidential and
proprietary to Algorithmics Incorporated and its affiliates
("Algorithmics").  If received in error, use is prohibited.  Please destroy,
and notify sender.  Sender does not waive confidentiality or privilege.
Internet communications cannot be guaranteed to be timely, secure, error or
virus-free.  Algorithmics does not accept liability for any errors or
omissions.  Any commitment intended to bind Algorithmics must be reduced to
writing and signed by an authorized signatory.



More information about the Orca-users mailing list