<?xml version="1.0" encoding="iso-8859-1" ?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/images/lists/rssstyle2.xsl"?>
<rss version="2.0">
<channel>
<title>Netapp | toasters</title>
<description>Mailing List Archive by Gossamer Threads</description>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/</link>
<language>en-us</language>
<copyright>(c) Gossamer Threads Inc. All rights reserved.</copyright>
<lastBuildDate>08 Nov  2009 15:08:08 -0800</lastBuildDate>
<ttl>120</ttl>
<image>
<title>Gossamer Threads | Netapp | toasters</title>
<width>75</width>
<height>23</height>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/</link>
<url>http://www.gossamer-threads.com/images/lists/rss_logo.jpg</url>
</image>
<item>
<title>SnapDrive 6 &amp;amp; Windows 2008 - can&amp;#039;t see or connect disks in SD but can see them in Disk Management MMC - only mount read-only</title>
<description>Hi, Another question - I have a datawarehouse box - has 4 luns -&amp;gt; SD 6.1 and Server 2k8 both 64bit. I can&amp;#039;t seem to reconnect the LUN&amp;#039;s using the SD</description>
<pubDate>07 Nov  2009 18:26:48 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10441</link>
</item><item>
<title>Re: Controller upgrade complete but . . .</title>
<description>&amp;gt; I believe that happens if you first bring the aggregates online in maintenance mode, &amp;gt; rather than in normal mode. Maintenance mode will strip all</description>
<pubDate>07 Nov  2009 14:01:58 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10440</link>
</item><item>
<title>RE: Controller upgrade complete but . . .</title>
<description>I believe that happens if you first bring the aggregates online in maintenance mode, rather than in normal mode. Maintenance mode will strip all the</description>
<pubDate>07 Nov  2009 10:14:49 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10439</link>
</item><item>
<title>Re: Controller upgrade complete but . . .</title>
<description>Hi Peter, That sounds fairly plausible - the upgrade itself was performed by a vendor and the upgrade steps we used in our change control look like t</description>
<pubDate>07 Nov  2009 09:57:55 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10438</link>
</item><item>
<title>RE: Controller upgrade complete but . . .</title>
<description>It sounds to me like the root volume from the factory was used and the setup routine was run, rather than removing the new drives, connecting the old</description>
<pubDate>07 Nov  2009 09:23:30 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10437</link>
</item><item>
<title>Controller upgrade complete but . . .</title>
<description>Hi all, Hoping you can save me some legwork - We&amp;#039;ve upgraded our 270c to a 2050ha - data looks good. We did run into the lun signaturing issue with</description>
<pubDate>07 Nov  2009 01:40:04 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10436</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>If you don&amp;#039;t get VMWare snapshots in your SMVI process then your backups would be inconsistent. So conceptually the restore would be akin to a tradit</description>
<pubDate>04 Nov  2009 08:47:29 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10435</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>Thanks for all your answers... We made some tests yesterday with esx4 and cloning and snapshotting... It seems that the challenge is not because of</description>
<pubDate>04 Nov  2009 00:59:37 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10434</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>Data ONTap version should read 7.3.1.1p7.  -----Original Message----- From: Ken Williams Sent: Tuesday, November 03, 2009 9:21 AM To: &amp;#039;Steffen Kamme</description>
<pubDate>03 Nov  2009 09:52:05 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10433</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>Yes, we have the same issue. Came down to a few things: 1. Update to 7.3.2p7. There are algorithm changes to WAFL that help with VMFS/VMDK reading/w</description>
<pubDate>03 Nov  2009 09:21:18 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10432</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>Crud. Make sure the partition offset/4096 is an integer, not even. Sorry. And I&amp;#039;m not too certain about the 4096 #, read the TR :) -----Original Mes</description>
<pubDate>03 Nov  2009 07:42:31 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10431</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>If your VMs are Windows it&amp;#039;s relatively simple to do a WMI scan against them for the partition offset and then divide by 4096 (?) and make sure it&amp;#039;s a</description>
<pubDate>03 Nov  2009 07:38:09 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10430</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>This is very commonly an alignment issue. Snapshots exacerbate the already intense I/O caused by misalignment. Essentially, the existence of VMware</description>
<pubDate>03 Nov  2009 07:26:10 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10429</link>
</item><item>
<title>RE: SMVI / VMWare Experiences...</title>
<description>Hi there, We have the same issue with SMVI 2.0 on nfs datastores... on some VMs we get the following error: Cannot create a quiesced snapshot becaus</description>
<pubDate>03 Nov  2009 06:41:04 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10428</link>
</item><item>
<title>SUMMARY: trouble accessing nfs .snapshot dirs via cifs shares</title>
<description>Hi Everyone, First off I&amp;#039;d like to thank everyone whom wrote back to me privately with some suggestions on how to fix this issue. (Original question a</description>
<pubDate>01 Nov  2009 23:34:56 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10427</link>
</item><item>
<title>Re: Controller upgrade - ESX LUN re-signaturing</title>
<description>I wrote a simple little perl script with automates the process of changing the serial numbers on the luns back to their pre-head upgrade serials, whic</description>
<pubDate>30 Oct  2009 03:09:26 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10426</link>
</item><item>
<title>Re: NFS - network read / write throughput per protocol</title>
<description>Steffen,  Here is something I use quite ofter from a unix box. However this is split per volume. If you want the whole system output you need to sdo</description>
<pubDate>29 Oct  2009 19:13:04 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10425</link>
</item><item>
<title>Re: NFS - network read / write throughput per protocol</title>
<description>There&amp;#039;s no specific counter for bytes / sec per protocol in priv set diag. For iops and latency&amp;#039;s and size histograms, but nothing specific. -Blake</description>
<pubDate>29 Oct  2009 14:13:57 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10424</link>
</item><item>
<title>Re: NFS - network read / write throughput per protocol</title>
<description>I don&amp;#039;t see a counter for what you are looking for in 7.3.1.1, but you could add up all the volume stats for nfs_read_data and nfs_write_data and cifs</description>
<pubDate>29 Oct  2009 10:12:21 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10423</link>
</item><item>
<title>RE: NFS - network read / write throughput per protocol</title>
<description>Stats show with the -e will let you use expression matching.   stats show -i 15 -e volume:(nfs|vmware:shares):(nfs)   Would report all of the NFS</description>
<pubDate>29 Oct  2009 10:01:33 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10422</link>
</item><item>
<title>NFS - network read / write throughput per protocol</title>
<description>Hi there, is there a possibility to get the read / write throughput in kilobyte per protocol (separated NFS / CIFS) on a filer? I found only the ope</description>
<pubDate>29 Oct  2009 09:37:57 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10421</link>
</item><item>
<title>Re: Controller upgrade - ESX LUN re-signaturing</title>
<description>Cheers Peter - this looks spot on. I&amp;#039;ll make sure this makes its way into the implementation plan. Raj. On 10/29/09, Learmonth, Peter &amp;lt;Peter.Learmo</description>
<pubDate>28 Oct  2009 23:01:09 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10420</link>
</item><item>
<title>RE: Controller upgrade - ESX LUN re-signaturing</title>
<description>Hi Raj I&amp;#039;d like to refer you to NOW KB33990 (which I wrote). It covers this scenario pretty thoroughly. https://now.netapp.com/Knowledgebase/solutio</description>
<pubDate>28 Oct  2009 22:29:16 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10419</link>
</item><item>
<title>Controller upgrade - ESX LUN re-signaturing</title>
<description>Hi all, We&amp;#039;re planning to upgrade our controller (a 270c to a 2050ha) - my understanding is the iSCSI LUN&amp;#039;s will retain their identity (ie the existi</description>
<pubDate>28 Oct  2009 20:58:49 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10418</link>
</item><item>
<title>RE: Disk runtime</title>
<description>Steffen Kammerer-2 wrote: &amp;gt; &amp;gt; I mean the runtime in hours the disks are running since they are in use... &amp;gt;  This is the runtime since they are in us</description>
<pubDate>27 Oct  2009 01:56:17 -0800</pubDate>
<link>http://www.gossamer-threads.com/lists/netapp/toasters/10417</link>
</item>
</channel>
</rss>
