toasters December 2002

toasters@lists.teaparty.net

80 participants
87 discussions

Tape Jukebox and scsi errors (Overland LXS mini library express)
by Darragh, Stephen J 04 Dec '02

04 Dec '02

Hello, We have a F820 with a lvd scsi card and a Overland Data LXS mini library express (1 dlt7000 and 15 slots) This is directly attached and controlled via ndmp and Veritas NetBackup 3.4.1 We are getting the following errors: Sun Dec 1 12:30:18 EST [isp_timeout:warning]: 1.4(0x015e8ca4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. Sun Dec 1 12:30:24 EST [isp_timeout:warning]: Resetting SCSI adapter 1 (ha #0) Sun Dec 1 12:30:25 EST [isp_timeout:warning]: Resetting SCSI bus 1 (ha #0) to clear outstanding I/O. Sun Dec 1 12:30:39 EST [isp_timeout:warning]: 1.4(0x015e8ca4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. Sun Dec 1 12:30:45 EST [isp_timeout:warning]: Resetting SCSI adapter 1 (ha #0) Sun Dec 1 12:30:45 EST [isp_timeout:warning]: Resetting SCSI bus 1 (ha #0) to clear outstanding I/O. Sun Dec 1 12:31:31 EST [isp_timeout:warning]: 1.4(0x015ea0a4, 0x00): command timeout, quiescing bus to allow outstanding I/O to complete. When we reboot we can use the jukebox, we can use this and it will run fine till we power cycle the jukebox and then we have to bounce the filer. And we can't figure out why we are getting these errors. I have tried swapping cables, terminator, scsi cards, and the jukebox itself. The jukebox is a SE device that is attached to the lvd scsi controller on the filer which should be supported. In fact, if I try to add a 2nd jukebox, the errors are so bad that I can't see either one. I have set the indentification to be DEC TL800, since the filer did not recognize this as a Overland LXS. Does anyone have one of these jukebox's and what Vendor ID and Prodcut ID are you using??? Thanks Stephen Darragh

1 0

backup troubles
by Ambrose_Earle＠shamrockfoods.com 04 Dec '02

04 Dec '02

Does anyone else experience frequent backup failures? We have an F840 cluster and we use NetVault to perform ndmpd backups to an overland tape library. Many times we receive messages like Mon Nov 25 02:43:55 MST [filer: ispfc_main:error]: Tape (switch:0.1L3) hard media error: Sense_Key (3) ASC (c) ASCQ (0) and the backup fails. Our same system is also used by a UNIX server and it never fails, so is DataONTAP more sensitive to these types of issues? Technically, what triggers this? Any help would be much appreciated,

3 2

RE: Network Adapters for Netcache C720
by Alan McLachlan 04 Dec '02

04 Dec '02

Oscar, You'll need to look at the System Configuration Guide on now.netapp.com for a C720 for the version of NetCache you are running to confirm compatability. I just tried to look for you but that part of the site appears to be down at the moment. Having said that, I'm sure any of the adapters you listed will work just fine, if what you are getting at is that you have those in stock and you're not sure which one to use. If you are suggesting using a non-NetApp adaptor, you need to look at the chipset on the NetApp adapter and find another OEM card with the same chipset. i.e. the X1001B is a common Znyx adapter. However, there are two issues with doing this: 1) The firmware on your substitute adaptor may no be the same as the one from NetApp, so it may not work correctly. 2) You will violate your NetApp hardware maintenance contract by using a third-party product inside the box. I do know that the NetApp X1025B gigabit ethernet adaptor is a stock standard Intel Pro1000 which is fully interchangeable, i.e. you can use the NetApp card in a Windows or Linux box and it will work just fine and the regular Intel 8940PWL will work just fine in a Filer (at about a third of the price you would have to pay NetApp for it!). We often use the original Intel card in NetApp boxes in our test labs. However, issue (2) above still applies, so we would never recommend any of our customers do this in a live environment. regards, Alan McLachlan Senior Systems Engineer Storage Management Solutions ASI Solutions www.asi.com.au Ph +61 2 6230 1566 Fax +61 2 6230 5343 Mobile +61 428 655644 e-mail amclachlan(a)asi.com.au -----Original Message----- From: Oscar Rodriguez Hernandez [mailto:orh@satec.es] Sent: Friday, 29 November 2002 8:46 PM To: toasters(a)mathworks.com Cc: Jose Luis Jimenez Fernandez; Jose Sanchez Subject: Network Adapters for Netcache C720 Hello We currently have one C720 Netache unit. We need to have this unit more than one Ethnernet port, and at our local stock we have many different types of Network Adapters, and we would like to know if we could use one of those instead of buying a new one. The network adapters fort C720 are the following NetApp P/N: Single-port 10Base-T/100Base-TX: P/N X1001B* P/N X1001C Quad-port 10Base-T/100Base-TX P/N X1012B* P/N X1012C Does anyone know which network card (manufacturer, model) are those P/N for? Has anyone used succesfully any different network adapter not from NetApp for the NetCache C720 unit? Thanks. Oscar. **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: no_atime_update
by Alan McLachlan 03 Dec '02

03 Dec '02

Ambrose, This article is referring to databases stored on the ext2 linux filesystem, which is a traditional update-in-place fs with fixed locations for metadata. This means that every time a file is read or written the access time (atime) field in the directory entry is updated, causing a seek to the directory inode. Note that actual writes cause the last-modified field to also be changed, you can't do anything about that one. So for transactional read intensive applications (such as databse reporting) on traditional filesystems (ext2/ext3/reiserfs/UFS/NTFS/JFS/AdvFS/XFS etc.), turning off the atime update for those files will cause a substantial reduction in both metadata processing CPU overhead and drive head seeking - hence the performance improvements noted. You would actually see an even greater performance improvement for files held locally on a Windows server due to the NTFS MFT location, so those seeking to optimise a SQL Server installation on a local NTFS filesystem should consider turning off the atime update on their db files. Everything changes however when you move the database to a remote WAFL filesystem on a NetApp Filer. On Network Appliance's WAFL filesytem, we have no fixed locations for metadata and never update-in-place. All required metadata changes for the new consistent image, right back to the root inode, are written at each consistency point. So on NetApp, the access time updata simply causes a few extra blocks to be written at each consistency point (every 10 seconds unless a lot of incoming data writes are received as well). Since we these blocks are written to new locations we aren't seeking back to old spots so there's very little or no head additional head movement, and since the metadata processing is performed by the Filer there is ZERO difference in CPU overhead on the actual Oracle server (i.e. it has no visibility of the atime update setting which is local to the Filer). So the performance benefit to be gained by turning of the atime update on a filer volume hosting an Oracle database is minimal, and being able to track when files have been read may be useful to the administrator, particulary when performing security breach analysis. NetApp do recommend that you turn this off in a limited range of environments, such a read-only library data warehouse where the atime updates are high compared to the regular write load and may cause unnecessary consistency points within the normal 10 second timeout, or add a significant number of blocks to the CP. In these cases you may see a performance improvement but it is still unlikely to be more than a few percent. Note that if you are using the new SnapDrive VLD or LUN block I/O products with your Filer to host the database, you're back to a traditional filesystem managed by the attached Oracle host, so WAFL features don't offload the metadata processing CPU overhead like they do for NFS/CIFS access. However you will still gain some benefit from the block location virtualisation (the head seeks are eliminated because the VLD blocks are not actually overwritten in place, the host just thinks they are.... :o) ) Hope all this helps. Alan McLachlan Senior Systems Engineer Storage Management Solutions NetAppCA, FCNE ASI Solutions www.asi.com.au Ph +61 2 6230 1566 Fax +61 2 6230 5343 Mobile +61 428 655644 e-mail amclachlan(a)asi.com.au -----Original Message----- From: Ambrose_Earle(a)shamrockfoods.com [mailto:Ambrose_Earle@shamrockfoods.com] Sent: Saturday, 30 November 2002 10:19 AM To: toasters(a)mathworks.com Subject: no_atime_update Is anyone using this option with volumes containing Oracle or Lotus Notes files? Have you tested it for any performance improvements? How does this differ from mounting with noatime? I read an article that claimed a nice performance increase when used with Oracle datafiles. Here's the link: http://www.linuxjournal.com/article.php?sid=5840 **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

Change/Notify in a mixed environment ?
by Ketil Kirkerud Elgethun 03 Dec '02

03 Dec '02

I'm currently investigating the possibility of using a filer in a mixed unix/windows environment. Basically, we will have a unix-based ftp server, and various windows based web servers. The way this particular application is built means we could make good use of the cifs mechanism change/notify. As far as I can see, OnTap supports this, more or less, even to the extent of sending notification to cifs clients when an nfs client makes a change to a file. However, the documentation (including bugs online) is unclear on how complete the implementation is. Does anyone know what the current status is ? regards, ---Ketil K. Elgethun

1 0

.snapshot directories
by barrie_spence＠agilent.com 02 Dec '02

02 Dec '02

We make extensive use of automount and each users home directory is mounted separately. With the .snapshot directory enabled, du and find recurse through the snapshot trees and in general this causes too many issues for our users, so we've disabled them. Is there any more sophisticated way of making the snapshots available that won't cause this sort of problem (e.g. can we export the snapshots separately? make them available as a separate CIFS share?). Thanks, Barrie

2 1

未承諾広告※電子メール広告
by hmail22 01 Dec '02

01 Dec '02

<MÒ> dq[LÐ ¡ãALð²ó]µÈ¢ûÍ±±Ö (Kž{¶É ÈœÌ[AhXÌÝðš«º³¢j infoshoppingwave(a)yahoo.co.jp [AhXð²LüµÄŸ³¢B §104-0061 sæâÀ8-19-3 æ2ECOr@3F [}KWs TEL@03-3544-6222 FAX@03-3544-6218 =============================================================== âè€iÎ©èWßÜµœÌÅAÁ³êé°êª èÜ·ÌÅ š\ÝÍšßÉI ================================================================= \\\\\\\\\\\\\\\\\\\\\\\\ rfIÌEÁê_b`CtErlNu @@ `ujDåWEðÛErdwthEA_gObYÈÇ @A_gÖAÌîñÚ@ @@š\ÝE²¶E€iÚ×Í@ @@@@@ºLtqkðNbNµÄ²º³¢B «@@@@«@@@@«@ @@@http://www.ss-koukoku.com/ \\\\\\\\\\\\\\\\\\\\\\\\ @@J^ObYEÉéîñEhÆObYEà×¯îñÈÇ@ @@@@@@@@@@»ÌŒîñÚ@ @@š\ÝE²¶E€iÚ×Í@ @@@@@ºLtqkðNbNµÄ²º³¢B «@@@@«@@@@«@ http://www.pp-koukoku.com/ \\\\\\\\\\\\\\\\\\\\\\\\

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters December 2002