toasters

toasters@lists.teaparty.net

13531 discussions

Restricting given file types from being written to CIFS volumes
by jack.revette＠dowcorning.com 01 Apr '08

01 Apr '08

I've been searching this listserv as well as NOW.NETAPP resources to detemine if there was any easy way to preclude certain file types (e.g., .mp3) from being written to given volumes. It seems the answer was not natively, but it could be done through a business partner product which would be set up as a screening server, much like the AV virus scanning server. I'm thinking maybe it can be done natively by just not implementing the screening servers. My thoughts follow. Comments would be appreciated. display current setup: fpolicy create empy screening profile called restrict_filetypes fpolicy create restrict_filetypes screen limit this profile to volume fre (for my testing) fpolicy vol inc add restrict_filetypes fre limit this profile to filetype xxx (for my testing) fpolicy ext inc add restrict_filetypes xxx limit this profile to activities of create and rename (allow delete) fpolicy monitor add restrict_filetypes -p cifs -f create,rename in absence of screening server, required will deny the access rather than default of permit it fpolicy options restrict_filetypes required on display the profile fpolicy show restrict_filetypes enable the profile, -f forces it because there are no screening servers fpolicy enable restrict_filetypes -f undo it all fpolicy disenable restrict_filetypes fpolicy destroy restrict_filetypes

3 2

Performance impact of in-lined firewalls/IDS
by Tom Yates 01 Apr '08

01 Apr '08

I have a bunch of filers that we use from various hosts for CIFS, NFS and iSCSI. Powers That Be are planning to put both a firewall and an adaptive IDS between my filers and my hosts. Does anyone have any rough and ready (ir ndeed, shiny and precise) numbers about what sort of performance impact this can have, recommendations for how to do it properly, or indeed solid data suggesting not to do it at all? Any experience with this? -- Tom Yates - http://www.teaparty.net

8 9

RAC install on NetApp
by Robert K. Borowicz 01 Apr '08

01 Apr '08

Toasters, My DBA just came to me and complained that a Ora RAC 10g build took 18 hours when using a Filer NFS mount. Seems I've heard of this issue before but forget the fix. Has someone seen this before ? TIA -Rob

6 6

Re: Some thoughts and questions on A-sis
by John Stoffel 31 Mar '08

31 Mar '08

Scott> no symlinks, automounter sub-mount maps. I have 600+ qtrees in Scott> 3 sites with NFS caches in between, in a single name space Scott> using a gory mesh of automount maps and automounter variables Scott> defined on clients. We've done that, but when a single project out grows a volume, then we start needing to shuffle data... it's a pain. If I could have more volumes, then I'd use them over qtrees, but then when an Aggr fills, I need to move volumes. It's a pain. That's why I like the idea of the Acopia product. I wish NetApp would realize that and come out with their own storage virtualization product to put in front of backend NetApps. Would be really nice. Course I'm a mostly NFS only shop. Scott> this is worth doing if the data set is A-sis friendly. >> >> It probably is actually, but hard to know. >> Scott> Future OnTap versions are going to make A-sis an aggregate Scott> behavior, not a volume one, which removes the volume size Scott> limit. >> Scott> and reinforces the silly 16T aggregate limit ;-) >> >> Yeah, that's another silly limit, esp with raid sets and RaidDP >> stuff. They should just let it scale and scale and scale. Scott> really a problem with 1 TB disks; 16 drives, onr Raid-DB group Scott> per aggregate. stinky performance. >> I personally *like* one big volume, with bunches of qtrees. What I'd >> really like is qtrees on multiple levels, or the raising of the number >> of volumes that are supported in an aggregate. That would help. >> >> And speeing up SnapVault. And a pony... :] >> >> John

3 4

"How to" help needed
by Milazzo Giacomo 29 Mar '08

29 Mar '08

Hi I'm going to expand available size to a 980C with only 2 shelves filled with 14 72G FC disks Customer buyed other 28 disks (144) to substitute the old 72. I've only one third shelf available, temporarely. As with the '3 card game' J which is the best way in your opinion to do this job? Could this be correct? 1. Disable cf 2. Attach the temporary shelf to one head, copy in it both 72G shelves content on two different volumes 3. Remove the 72 G disks from the 2nd head shelf and fill it with the 144 ones 4. Install Data Ontap on the 2nd head disks and boot it 5. Copy in this last the content saved at point 2

3 2

Optimal Filesize
by Sebastien Campion 28 Mar '08

28 Mar '08

Hi, i manage a NetApp Filer for scientific applications and i have to choose an optimal file size to store my data. My range is 4Mo to 40Go. This data must be read by a grid computing based on NFS and Linux. If my NVRAM size is 512Mo, a optimal filesize is < 512 Mo ? Maybe, filesize is not important for filer performance, i don't know. Thanks in advance, Sébastien.

2 1

Re: Some thoughts and questions on A-sis
by John Stoffel 28 Mar '08

28 Mar '08

Scott> 6T on 6070's Heh. I'm running on 960s and 980s now, so this won't help me much, even with an upgrade planned for later this year. Maybe. Scott> in a few cases, I split big volumes into smaller chunks Scott> and stiched them back together with automount maps an DFS Scott> links (my filesystem namespace is already built that way). We've don't this too, but it's a total hassle when one volume has to grow, and I don't want to go down symlink hell again if I can help it. Scott> this is worth doing if the data set is A-sis friendly. It probably is actually, but hard to know. Scott> Future OnTap versions are going to make A-sis an aggregate Scott> behavior, not a volume one, which removes the volume size Scott> limit. Scott> and reinforces the silly 16T aggregate limit ;-) Yeah, that's another silly limit, esp with raid sets and RaidDP stuff. They should just let it scale and scale and scale. I personally *like* one big volume, with bunches of qtrees. What I'd really like is qtrees on multiple levels, or the raising of the number of volumes that are supported in an aggregate. That would help. And speeing up SnapVault. And a pony... :] John

1 0

Some thoughts and questions on A-sis
by Adam McDougall 27 Mar '08

27 Mar '08

I started testing sis on one of our 3040's last weekend. Sorry if theres more extensive information on NOW, but the things I've found so far were fairly rudimentry. Some impressions and questions: I found out quickly that my 5T test volume was too big. Looked up the limits because I had no idea there were volume size limits. 3T for 3040 hmm. I have an existing volume that holds 2.5T, so that is pushing it, and while I would like to split it up, it won't happen overnight. I'm not desperate to use sis on it, although I am almost done copying it and so far have realized 26% savings from dedupe for testing. I wonder why the max size scales with the system model, I haven't thought of a good reason for this yet since you could easily have lots of 3T volumes. I was wondering if you can get sis to shrink say 2.8T to 2.0, is the 2.0 what counts for the sis volume limit size? Even so, would I run into trouble if trying to do a full volume restore and the full data set is over 3.0 but would have shrunk? Once I write over 3T into a volume, it sounds like I cannot run sis on it. I'm not too worried about having to do a full restore of a volume from tape, but I don't want to limit my future options if the short term payoff isn't worth it. I'm pretty sure I'll use it on all or most of all of my other volumes since they are much smaller. I noticed during my data copy, the snapshot reserve was blowing out big time. It seemed like almost any savings from sis went into snapshots for some reason. 100, 200, 400% full, and it started trimming itself back after a while. Since this was a non-production copy, I didn't care, and deleted those snapshots this morning, but I thought that was rather odd, and couldn't think what the snapshots would have to offer since if the data was unmodified at the filesystem level, the snapshot should contain the same data. While not a problem for an initial copy, I would expect the same thing to happen when sis runs during production, and although it wouldn't be as large and would eventually flush out, why am I expending space to store duplicate copies of data that I asked it to deduplicate? :) Maybe its just because wafl identifies them as "changed blocks" and insists on storing them in the snapshot. A 1 gig file of zeros still takes several tens of megabytes after sis. hmm :) And roughly twice as much for a second copy of it.

6 5

vmware on nfs stability issues
by Pascal Dukers 26 Mar '08

26 Mar '08

We have stability issues with vmware esx (3.0.2) on nfs whenever there is a cluster failover. The datastores come back online after the failover is complete (30-40 seconds), but some of the virtual servers (solaris/windows) can crash while the failover takes place. There are probably some timeout settings I need to configure on all esx hosts, but the NetApp best practice guide on vmware/nfs does not mention changes other than the locking parameter. So I hope someone can share if they encountered the same issue and what they changed to improve it. -- View this message in context: http://www.nabble.com/vmware-on-nfs-stability-issues-tp16126353p16126353.ht… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

6 6

cifs.homedir and Microsoft DFS global name space
by Sayla, Mustafa 25 Mar '08

25 Mar '08

Does anyone have experience setting up cifs.homedir feature on FAS3040 (Ontap 7.2) with Microsoft DFS global name space? I have been trying to set this up but permission are causing as issue. Homedir feature works fine without DFS but when we use DFS then users can access other users home drives also as permission needs to be set for everyone to have full access. Mustafa Visit us on the Web at: http://www.mesirowfinancial.com This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product. Please consider the environment before printing this e-mail.

2 1

Jump to page:

2026

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