toasters

toasters@lists.teaparty.net

13514 discussions

RE: Slow write performance
by Mike Ball 06 Feb '02

06 Feb '02

Edward, I not sure I would be concerned about the 0's on disk writes you are seeing. As long as Net KB keeps coming in/out. The Netapp may be recalculating parity and holding the writes in NVRAM before it flushes to disk, etc.. As for the volume being full, I see a lot of customers only add 1 disk at a time when the volumes get full. This causes a problem because you basically do not stripe across disks. You only are writing to one disk. At this point you become disk bound which could very … [View More]well be what is happening here. Make sure you add disks a few at a time when you grow your volume to stripe the data among drives. Mike -----Original Message----- From: Edward Hibbert [mailto:EH@dataconnection.com] Sent: Wednesday, February 06, 2002 8:29 AM To: 'Mike Ball' Subject: RE: Slow write performance Mike, I can send you a couple of the outputs straight away. sysstat doesn't recognise the -u option; what's the difference between that and sysstat 1? I take your point about network settings - we've had problems in this area before - but I don't understand why I would get 0 disk writes for a long time while still getting network traffic in and out. I know that my network traffic during such a period includes write requests (from pktt trace), so what I'm wondering is what causes the writes to hang up and then recover. The disk on /vol/vol0 has previously got very full. Although we've now freed up some space, do you think there might be persistant fragmentation? Edward. nacolt1*> df Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 95328924 54170444 41158480 57% /vol/vol0/ /vol/vol0/.snapshot 0 0 0 ---% /vol/vol0/.snapshot /vol/vol1/ 63552616 60599768 2952848 95% /vol/vol1/ /vol/vol1/.snapshot 0 0 0 ---% /vol/vol1/.snapshot Volume vol0 (root) RAID group 0 RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- parity 8.3 8 0 3 FC:A 34500/70656000 35003/71687368 data 8.4 8 0 4 FC:A 34500/70656000 35003/71687368 data 8.1 8 0 1 FC:A 34500/70656000 35003/71687368 data 8.0 8 0 0 FC:A 34500/70656000 35003/71687368 Volume vol1 RAID group 0 RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- parity 8.2 8 0 2 FC:A 34500/70656000 35003/71687368 data 8.6 8 0 6 FC:A 34500/70656000 35003/71687368 data 8.5 8 0 5 FC:A 34500/70656000 35003/71687368 nacolt1*> -----Original Message----- From: Mike Ball [mailto:MBall@DATALINK.com] Sent: Wednesday, February 06, 2002 1:07 PM To: Edward Hibbert Subject: RE: Slow write performance Edward, Trying forcing the switch you plug into to 100Mb Full duplex. In addition, instead of making e0 auto negotiate, force it to 100Mb full duplex. Your network KB/s is pretty low. Also, how full is your file system? Can you send me the output of the following commands: df sysstat -u 1 (run for 20 seconds) sysconfig -r Thank you, Mike -----Original Message----- From: Edward Hibbert [mailto:EH@dataconnection.com] Sent: Tuesday, February 05, 2002 5:27 PM To: 'Mike Ball' Subject: RE: Slow write performance Here's the sysstat. Interesting that this shows periodic 0 writes. Tue Feb 5 22:22:30 GMT [tn_login_0]: root logged in from host: 192.168.21.16 sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 54% 1012 0 1 393 1494 2430 2446 0 0 1 43% 1012 0 0 431 1549 2302 3947 0 0 1 46% 1278 0 0 471 1787 2708 1116 0 0 1 57% 1080 0 0 611 2019 2078 5177 0 0 1 31% 726 0 0 439 1056 840 1028 0 0 1 37% 962 0 0 388 1872 1561 0 0 0 1 32% 919 0 0 404 1786 1688 0 0 0 1 33% 1050 0 0 407 1815 1529 0 0 0 1 43% 1102 0 0 623 2148 1264 0 0 0 1 43% 857 0 1 347 1585 2154 0 0 0 1 38% 746 0 0 430 1878 1704 0 0 0 1 58% 463 0 1 255 800 2610 3675 0 0 1 52% 997 0 0 517 1544 2840 2084 0 0 1 48% 792 0 0 401 1350 2222 5365 0 0 1 50% 1028 0 0 429 2055 2264 2108 0 0 1 37% 864 0 0 304 1864 1893 2210 0 0 1 39% 1053 0 0 566 2154 988 8 0 0 1 45% 1143 0 0 604 2309 1733 0 0 0 1 35% 1034 0 0 420 2123 1860 0 0 0 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 42% 1000 0 0 550 2016 1264 0 0 0 1 52% 1118 0 1 575 2541 1589 0 0 0 1 30% 791 0 0 327 1648 1880 0 0 0 1 48% 880 0 0 382 1896 2022 1905 0 0 1 47% 745 0 1 354 1354 2196 2828 0 0 1 57% 1287 0 0 581 1772 2366 3583 0 0 1 51% 1136 0 0 595 1929 2488 1168 0 0 1 48% 987 0 0 419 1273 2348 3504 0 0 1 35% 768 0 0 421 1623 1597 720 0 0 1 45% 1237 0 0 624 2465 1869 0 0 0 1 38% 1112 0 0 390 1995 1688 0 0 0 1 44% 1044 0 0 585 1817 1697 0 0 0 1 ifconfig output: e0: flags=240043<UP,BROADCAST,RUNNING,UP_1ARY,LINK_UP> mtu 1500 inet 192.168.21.81 netmask 0xffffff00 broadcast 192.168.21.255 ether 00:a0:98:00:97:67 (auto-100tx-fd-up) lo: flags=240049<UP,LOOPBACK,RUNNING,UP_1ARY,LINK_UP> mtu 1536 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 Regards, Edward. -----Original Message----- From: Mike Ball [mailto:MBall@DATALINK.com] Sent: 05 February 2002 19:58 To: Edward Hibbert; toasters Subject: RE: Slow write performance Edward, Telnet to the netapp and type "sysstat 1". Let it run for about 20 seconds and send us the output. Also, type "ifconfig -a" and send us the output. Mike -----Original Message----- From: Edward Hibbert [mailto:EH@dataconnection.com] Sent: Tuesday, February 05, 2002 2:24 PM To: toasters Subject: Slow write performance We're seeing some performance problems on an F720 which you guys might be able to help with (even though it's not exactly top of the range nowadays). What we see is: - We're driving it over NFS v3. - We get about 1500 ops/sec out of it, of which one third are writes and two thirds are reads. There aren't many file open/close operations. - The operations are to random locations in large (10GB) files. - The CPU is running about 75%, and the network input and output below the throughput of the link we have to it. We've seen both CPU and network go higher if we do simple copy tests. - Looking it it via pktt trace, something approaching 15% of WRITE operations take long enough for the clients to time out and retransmit (so at least 1 second). None of the READ operations do. - The retransmissions appear to come in bunches. For example we'll see a few seconds where the filer doesn't respond, during which time the retransmissions will come in, then it will wake up and send some responses back. - The rest of the time, the WRITES are very fast (sub-ms). This appears to have worsened recently. We tried a couple of things: - We thought that this might be because the disk had got full and fragmented, so we zapped a bunch of data. - We rebooted. Neither of these seemed to help much. sysstat consistently shows a cache age of 1. This, and the bursty nature of the delays, suggest to me that I'm just hitting it too hard, and there's some kind of periodic cache-flushing operation going on, but do any of you folk have any other suggestions? Edward Hibbert Internet Applications Group Data Connection Ltd Tel: +44 131 662 1212 Fax: +44 131 662 1345 Email: eh(a)dataconnection.com Web: http://www.dataconnection.com [View Less]

3 2

RE: what disks can i use in an F330?
by Knight, Jason 06 Feb '02

06 Feb '02

Brian, To address your last concern I believe the OS for the F330 goes up to DOT version 5.3.7R3. That is the version we run on our F330. If anyone knows of a later version please let me know. Jason Jason Knight Citadel Investment Group L.L.C. -----Original Message----- From: Brian Hechinger [mailto:wonko@arkham.ws] Sent: Wednesday, February 06, 2002 3:59 AM To: toasters(a)mathworks.com Subject: what disks can i use in an F330? i've got an F330 that i'd like to get online one of these … [View More]

1 0

RE: Slow write performance
by Edward Hibbert 05 Feb '02

05 Feb '02

Here's the sysstat. Interesting that this shows periodic 0 writes. Tue Feb 5 22:22:30 GMT [tn_login_0]: root logged in from host: 192.168.21.16 sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 54% 1012 0 1 393 1494 2430 2446 0 0 1 43% 1012 0 0 431 1549 2302 3947 0 0 1 46% 1278 0 0 471 … [View More]1787 2708 1116 0 0 1 57% 1080 0 0 611 2019 2078 5177 0 0 1 31% 726 0 0 439 1056 840 1028 0 0 1 37% 962 0 0 388 1872 1561 0 0 0 1 32% 919 0 0 404 1786 1688 0 0 0 1 33% 1050 0 0 407 1815 1529 0 0 0 1 43% 1102 0 0 623 2148 1264 0 0 0 1 43% 857 0 1 347 1585 2154 0 0 0 1 38% 746 0 0 430 1878 1704 0 0 0 1 58% 463 0 1 255 800 2610 3675 0 0 1 52% 997 0 0 517 1544 2840 2084 0 0 1 48% 792 0 0 401 1350 2222 5365 0 0 1 50% 1028 0 0 429 2055 2264 2108 0 0 1 37% 864 0 0 304 1864 1893 2210 0 0 1 39% 1053 0 0 566 2154 988 8 0 0 1 45% 1143 0 0 604 2309 1733 0 0 0 1 35% 1034 0 0 420 2123 1860 0 0 0 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 42% 1000 0 0 550 2016 1264 0 0 0 1 52% 1118 0 1 575 2541 1589 0 0 0 1 30% 791 0 0 327 1648 1880 0 0 0 1 48% 880 0 0 382 1896 2022 1905 0 0 1 47% 745 0 1 354 1354 2196 2828 0 0 1 57% 1287 0 0 581 1772 2366 3583 0 0 1 51% 1136 0 0 595 1929 2488 1168 0 0 1 48% 987 0 0 419 1273 2348 3504 0 0 1 35% 768 0 0 421 1623 1597 720 0 0 1 45% 1237 0 0 624 2465 1869 0 0 0 1 38% 1112 0 0 390 1995 1688 0 0 0 1 44% 1044 0 0 585 1817 1697 0 0 0 1 ifconfig output: e0: flags=240043<UP,BROADCAST,RUNNING,UP_1ARY,LINK_UP> mtu 1500 inet 192.168.21.81 netmask 0xffffff00 broadcast 192.168.21.255 ether 00:a0:98:00:97:67 (auto-100tx-fd-up) lo: flags=240049<UP,LOOPBACK,RUNNING,UP_1ARY,LINK_UP> mtu 1536 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 Regards, Edward. -----Original Message----- From: Mike Ball [mailto:MBall@DATALINK.com] Sent: 05 February 2002 19:58 To: Edward Hibbert; toasters Subject: RE: Slow write performance Edward, Telnet to the netapp and type "sysstat 1". Let it run for about 20 seconds and send us the output. Also, type "ifconfig -a" and send us the output. Mike -----Original Message----- From: Edward Hibbert [mailto:EH@dataconnection.com] Sent: Tuesday, February 05, 2002 2:24 PM To: toasters Subject: Slow write performance We're seeing some performance problems on an F720 which you guys might be able to help with (even though it's not exactly top of the range nowadays). What we see is: - We're driving it over NFS v3. - We get about 1500 ops/sec out of it, of which one third are writes and two thirds are reads. There aren't many file open/close operations. - The operations are to random locations in large (10GB) files. - The CPU is running about 75%, and the network input and output below the throughput of the link we have to it. We've seen both CPU and network go higher if we do simple copy tests. - Looking it it via pktt trace, something approaching 15% of WRITE operations take long enough for the clients to time out and retransmit (so at least 1 second). None of the READ operations do. - The retransmissions appear to come in bunches. For example we'll see a few seconds where the filer doesn't respond, during which time the retransmissions will come in, then it will wake up and send some responses back. - The rest of the time, the WRITES are very fast (sub-ms). This appears to have worsened recently. We tried a couple of things: - We thought that this might be because the disk had got full and fragmented, so we zapped a bunch of data. - We rebooted. Neither of these seemed to help much. sysstat consistently shows a cache age of 1. This, and the bursty nature of the delays, suggest to me that I'm just hitting it too hard, and there's some kind of periodic cache-flushing operation going on, but do any of you folk have any other suggestions? Edward Hibbert Internet Applications Group Data Connection Ltd Tel: +44 131 662 1212 Fax: +44 131 662 1345 Email: eh(a)dataconnection.com Web: http://www.dataconnection.com [View Less]

1 0

vol0 question
by Jeff Kennedy 05 Feb '02

05 Feb '02

Now that the R100 has come out I was wondering what people think of the seperate vol0 concept? In the old days it wasn't quite so bad; ok, so you wasted a 4gb drive or maybe even an 18gb drive. But now we're looking at tossing a 136gb drive for what? Squat really. So what's the new thought on this? Do you not waste the disk on a seperate vol0 and just keep tight reigns on qtrees? Or is there still an argument for vol0 on it's own? Thanks. -- ===================== Jeff Kennedy Unix Administrator AMCC jlkennedy(a)amcc.com

4 6

RE: Slow write performance
by Mike Ball 05 Feb '02

05 Feb '02

Edward, Telnet to the netapp and type "sysstat 1". Let it run for about 20 seconds and send us the output. Also, type "ifconfig -a" and send us the output. Mike -----Original Message----- From: Edward Hibbert [mailto:EH@dataconnection.com] Sent: Tuesday, February 05, 2002 2:24 PM To: toasters Subject: Slow write performance We're seeing some performance problems on an F720 which you guys might be able to help with (even though it's not exactly top of the range nowadays). What we see is:… [View More]

1 0

Slow write performance
by Edward Hibbert 05 Feb '02

05 Feb '02

We're seeing some performance problems on an F720 which you guys might be able to help with (even though it's not exactly top of the range nowadays). What we see is: - We're driving it over NFS v3. - We get about 1500 ops/sec out of it, of which one third are writes and two thirds are reads. There aren't many file open/close operations. - The operations are to random locations in large (10GB) files. - The CPU is running about 75%, and the network input and output below the throughput of the … [View More]

1 0

6.2, R100, Where?
by Ambrose_Earle＠shamrockfoods.com 05 Feb '02

05 Feb '02

Where can I find information about the features scheduled for DataONTAP 6.2? and the R100? and other new things?

1 0

Using spare disk shelves
by William Liu 05 Feb '02

05 Feb '02

Question: Suppose I have an additional disk shelf that has data on it, can I just easily add it to the daisy chain of disk shelves on the netapp? So when I do a "sysconfig -r" it will show as spares? Keep in mind that these drives aren't empty. I don't see why not since the source file/directory structure comes from the already configured disk shelves. Can someone shed some light on this? Thanks.

2 1

new bug 60490 cifs and symlinks
by neil lehrer 04 Feb '02

04 Feb '02

has anyone seen this issue? i am going to be using 1 symlink per user for homedirs because our homedir struct is not flat - h/a/aboy, h/b/balbert with dirs a - z. the homedir option will point to the homelinks dir which contains all the symlinks. Description Prolonged heavy access by CIFS clients that involve or cause lookup of Unix absolute symbolic links can affect filer performance. Because the resolution of absolute symlinks depends on Unix mount point information which is not … [View More]available to CIFS clients, a table of translations is kept on the filer (/etc/symlink.translations). The entries in this file are order dependent and are searched sequentially. If a CIFS client is doing symlink lookups frequently, and if the entry to resolve the symlink is near the end of the file, and if the file is large, there can be a great deal of CPU utilization. This can slow operations for other users. For example, a user may be changing files in a directory that contains dozens of absolutes symbolic links. The /etc/symlink.translations file may have 1000s of entries. The user is accessing the files with Windows Explorer. After the target file is updated, the filer notifies Explorer of the file change. This is because Explorer will have posted a "change notify" request with the filer, so that it is alerted when changes occur and can update/redraw its display window. Explorer will touch each file including each of the symbolic links. The access of the symlinks will cause the filer to attempt to resolve them by scanning the /etc/symlink.translations entries. If there are many symlinks, many entries,multiple users with Explorer windows affected by change-notify updates, and if the entries needed to resolve the symlinks are missing or at the end of the /etc/symlink.translations file then filer performance can be affected. Workaround Use the filer's cifs homedir feature (options cifs.home_dir) instead of using a symlink per user when implementing CIFS home directories if there are many users. -- regards +++++++++++++++++++++++++++++++++++++++++++++++++ + Neil Lehrer + + United States International Broadcasting Bureau + System Development Division + + voice 202 619-2524 + fax 202 619-3576 + nlehrer(a)ibb.gov + + " is this crisis an opportunity or just + another grab the fire extinguisher moment?" + +++++++++++++++++++++++++++++++++++++++++++++++++ [View Less]

4 7

RE: adding cifs users homedirs and setting ownership
by jwitham＠takedapharm.com 02 Feb '02

02 Feb '02

We did the migration from an NT fileserver about a year ago. Granted, we didn't go from NFS to CIFS, but maybe our experience will help a little. The way we define the user's homedir is by throwing the UNC in the Home Directory field in User Mangler, then do a 'net use H: /home' in the logon script. When we migrated, we had our webmaster take 5 seconds out of his busy day to write a quick ADSI script that tore through the SAM of the DCs and simply changed \\NTfileserver\username$ to \\… [View More]filer\username. Then we used robocopy (NT Res kit) to move everything and their permissions to the new filer. If you're going from NFS to NTFS, you'll probably have to script something. For quotas, we use this line in /etc/quotas: * user@/vol/volX/users 3G (Yeah, I know, 3G for every user is huge.) I think this feature requires ONTAP 6.1, so buyer beware. If you have multiple NT domains, you might want to look at caveats of using the CIFS HOMEDIR option. It's nice not to have 1500 separate shares, but may be prohibitive if you have the same username for different users in multiple domains. Good luck! -john John Witham Sr. Data Networking Engineer Takeda Pharmaceuticals North America, Inc. A computer lets you make more mistakes faster than any invention in human history, with the possible exceptions of handguns and tequila. -Mitch Ratcliffe -----Original Message----- From: neil lehrer [mailto:nlehrer@yahoo.com] Sent: Friday, February 01, 2002 11:30 PM To: toasters(a)mathworks.com Subject: adding cifs users homedirs and setting ownership hi, we are going from nfs, unix on solaris to cifs, ntfs on filer. how do folks do the normal creation of new users homedir[we currently map our h: drive from the login script, we don't set the homedir in the users domain account]. from nt gui, from cmdline, using script? and, for quota purposes, how do you set the new users's homedir ownership and acl, in ntfs? na_chown and some other util? i need to set this up for our user support folks and am looking for best ways. thanks ===== neil lehrer ******************************************** * is this crisis an opportunity for growth * or just another fire extinguisher moment? ******************************************** __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com This message is for the designated recipient only and may contain privileged or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. [View Less]

1 0

Jump to page:

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