toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

impact of setting snap reserve to 0
by Anna M 07 Apr '08

07 Apr '08

I have a volume with following details: [xxxhost ~yyy/zzz]# rsh xxxfiler df -h /vol/vol_1111_222 Filesystem total used avail capacity Mounted on /vol/vol_1111_222/ 453GB 422GB 31GB 93% /vol/vol_1111_222/ /vol/vol_1111_222/.snapshot 0GB 101GB 0GB ---% /vol/vol_1111_222/.snapshot when I clone a new flexclone volume using this volume and try to get the used space of that newlyc loned volume, I see that used space value changes drastically in couple of seconds We have noticed that with in 17 seconds the used space reported for this newly cloned volume was altered to the tune of 76 GBs (starting from ~387 GB to ~311 GB). Any clue as to why would this be heppening? Can it be because snap reserve is not set properly(we have set it to zero)? -- View this message in context: http://www.nabble.com/impact-of-setting-snap-reserve-to-0-tp16468497p164684… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

8 11

Re: impact of setting snap reserve to 0
by Webster, Stetson 07 Apr '08

07 Apr '08

Hello Anna, I believe your snapshot is indeed zero (0) at first. Then as the data changes, your snapshot is holding on to it's read-only blocks. So it makes sense that the snapshot is growing. The more data you turn over, the bigger thw snapshot will be. A good test: Create a small volume, dump some data into it and then take a snapshot. Examine the snapshot carefully. Now completely overwrite (delete and then re-write) the data and then look at the same snapshot again. Theory: your snapshot keeps changing because your 'active filesystem' is changing. Cheers ...... Sent from my network synchronized laptop running Microsoft Outlook 2003 (www.microsoft.com) -----Original Message----- From: Anna M [mailto:annpurna@gmail.com] Sent: Monday, April 07, 2008 10:18 AM Pacific Standard Time To: toasters(a)mathworks.com Subject: Re: impact of setting snap reserve to 0 Since I am totally new to the world of filers, I would really appreciate if you can just explain me as to why the snapshot size for a newly created flexclone volume is not zero? After all the source for it also was a snapshot. The issues in space calculation for a newly clones volume is actually because of the changes in the snapshot size for this vol. For one of my newly cloned flexclone volume I am seeing that with in 3 minutes, the snapshot size reported is altered from /vol/prod_v/ 475777656KB 400203924KB 75573732KB 84% /vol/prod_v/ /vol/prod_v/.snapshot 0KB 74248140KB 0KB ---% /vol/prod_v/.sn to /vol/prod_v/ 475777656KB 325971708KB 149805948KB 69% /vol/prod_v/ /vol/prod_v/.snapshot 0KB 16112KB 0KB ---% /vol/prod_v/.snapshot Similarly the agg show_space output that I took at the same time as I took above df command output shows change in allocated and Used space values for this volume as: prod_v 75574680KB 32KB volume . ... prod_v 149823776KB 17816KB volume O/p for both these commands are still changing... We have found that values take approx 19 minutes to settle down...19 minutes seems to be a BIG duration :-( Any help in this regard will really be appreciated. -Anna bluezman wrote: > > Anna M wrote: >> snip >> > >> Any clue as to why would this be heppening? Can it be because snap >> reserve >> is not set properly(we have set it to zero)? >> > > i believe that when you take a clone, it takes a snapshot of the src, > since your snapshot space comes out of the actual volume, you will see > the size change > > correct me if i am wrong. > > -- View this message in context: http://www.nabble.com/impact-of-setting-snap-reserve-to-0-tp16468497p165353… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. DISCLAIMER: This email and any attachments are confidential and privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If received in error, do not open, read, copy, disclose, use or store it in any way, or permit others to do so but please notify the sender immediately and delete the original email and attachments from your machine. If you are not the addressee or the intended recipient, any use, disclosure, copying, distribution or action taken in reliance of it, is prohibited and unlawful. The information, attachments, opinions or advice contained in this email are not necessarily the views or opinions of Celtel Nigeria Limited or its affiliates and without more, shall not commit Celtel Nigeria Limited or its affiliates. Celtel Nigeria Limited and its affiliates do not accept liability for claims, losses, or damages caused by the inaccuracy, incorrectness, or lack of integrity of this email or any attachments.

1 0

RE: Restricting given file types from being written to CIFS volumes
by Gupta, Reena 01 Apr '08

01 Apr '08

Hi Jack, Your procedure looks correct, it matches with the example given on the NOW documentation. Check this link: http://now.netapp.com/NOW/knowledge/docs/ontap/rel724/html/ontap/filesag /accessing/task/t_oc_accs_enabling_native_file_blocking.html#t_oc_accs_e nabling_native_file_blocking Thanks, Reena Gupta ________________________________ From: Wu, Linda Sent: Tuesday, April 01, 2008 10:53 AM To: Gupta, Reena Subject: FW: Restricting given file types from being written to CIFS volumes Hi Reena, Could you reply this toaster email thread? I think you've already have the steps to do this procedure. thanks, -linda Linda Wu Sr. Manager, Prod. Mgmt & TME, Windows File Services NetApp Office: (408) 822-3560 Email: wu(a)netapp.com ________________________________ From: jack.revette(a)dowcorning.com [mailto:jack.revette@dowcorning.com] Sent: Tuesday, April 01, 2008 9:17 AM To: toasters(a)mathworks.com Subject: Restricting given file types from being written to CIFS volumes 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

1 0

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

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