toasters

toasters@lists.teaparty.net

13514 discussions

RE: Snapshot Cheats?
by Traitel, Eyal 16 Aug '01

16 Aug '01

You can do: snap create before_delete delete files snap delete before_delete But this will not bring you into any better situation than the beginning one... Usually I view it like a cake - you cannot eat it and expect it to be still complete - if you want to be able to restore files you will have to keep the snapshot. If disk space is more important at this point, just delete old snapshots OR change snap reserve. ----------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! Filer Escalation Engineer CNA, MCSE, CSA, LCA, NetApp CA Network Appliance BV Hoofddorp, The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Get answers NOW! - NetApp On the Web - http://now.netapp.com ----------------------------------------------------------------- -----Original Message----- From: Kennard, Dave M SITI-ISEL-31 [mailto:Dave.M.Kennard@is.shell.com] Sent: Thursday, August 16, 2001 10:19 To: 'toasters(a)mathworks.com' Subject: Snapshot Cheats? List, Is there any way to cheat with snapshots so that data in them can be deleted? I have stupidly let a volume on my filer grow to capacity and want to free up space my moving files to another volume, if I just move the files I will get no gain in free disk space because the files will exist in the snapshot right? Could I cheat this by taking a snapshot of the volume before I delete the files then delete the snapshot after the file are deleted? Regards Dave Kennard

3 3

RE: What happenned to the archive?
by Joe Luchtenberg 16 Aug '01

16 Aug '01

It's back up now (or at least I'm able to get to it again). Thanks, K. The archive page is a pretty huge download. If this presents any probelms for you, then you may want to try the search page at http://teaparty.mathworks.com:1999/toasters/Search.html. HTH. Joe > -----Original Message----- > From: John Stoffel [mailto:stoffel@casc.com] > Sent: Thursday, August 16, 2001 12:32 PM > To: Joe Luchtenberg > Cc: 'toasters' > Subject: Re: What happenned to the archive? > > > > Joe> For several days I have been unable to pull up > Joe> http://teaparty.mathworks.com:1999/toasters. Help? > > I have *never* been able to access the archive. I wish I could... > > John >

1 0

RE: NetBackup problem logs
by Rudie, Tony 16 Aug '01

16 Aug '01

that's a Veritas bug, and there's a patch for it. get the latest patches for NetBackup from Veritas tech support. -----Original Message----- From: Fayek, Ahmed [mailto:ahmed_fayek@mentorg.com] Sent: Thursday, August 16, 2001 3:15 AM To: NDMP mailing list (E-mail); toasters (NetApp) mailing list (E-mail); Veritas mailing list (E-mail) Subject: Netbackup problem logs Hello All I'm using Netbackup to backup Netapp servers ( NDMP). After first time backup i received the following error in the Netbackup problem logs email : TIME SERVER/CLIENT TEXT 08/14/2001 16:03:33 alpha toast1 put_ino: file 4M5TTVH.iccel_1 name cannot begin with name array terminator character 08/14/2001 16:03:33 alpha toast1 ndmp_bpfsmap_dir: put_ino returned -1 alpha = Netbackup server toast1 = Netapp filer Anybody got idea about this error ? is it serious ? Nice day All Ahmed

1 0

Snapshot Cheats?
by Kennard, Dave M SITI-ISEL-31 16 Aug '01

16 Aug '01

List, Is there any way to cheat with snapshots so that data in them can be deleted? I have stupidly let a volume on my filer grow to capacity and want to free up space my moving files to another volume, if I just move the files I will get no gain in free disk space because the files will exist in the snapshot right? Could I cheat this by taking a snapshot of the volume before I delete the files then delete the snapshot after the file are deleted? Regards Dave Kennard

2 1

Netbackup problem logs
by Fayek, Ahmed 16 Aug '01

16 Aug '01

Hello All I'm using Netbackup to backup Netapp servers ( NDMP). After first time backup i received the following error in the Netbackup problem logs email : TIME SERVER/CLIENT TEXT 08/14/2001 16:03:33 alpha toast1 put_ino: file 4M5TTVH.iccel_1 name cannot begin with name array terminator character 08/14/2001 16:03:33 alpha toast1 ndmp_bpfsmap_dir: put_ino returned -1 alpha = Netbackup server toast1 = Netapp filer Anybody got idea about this error ? is it serious ? Nice day All Ahmed

1 0

resizing boot volume
by neil lehrer 15 Aug '01

15 Aug '01

i am going to redo my boot volume. no data to save. steps: create new volume /vol/vol1 vol create /vol/vol1 2 export /vol/vol1 copy /etc from vol0 to vol1 make vol1 the root volume vol options /vol/vo11 root reboot if vol1 shows as the root volume then vol offline /vol/vol0 reboot vol destroy /vol/vol0 rename back to default root vol name vol rename /vol/vol1 /vol/vol0 add some disks back to the new vol0 vol add /vol/vol0 3 am i missing anything? thanks. -- regards

2 2

RE: /net/filer/blah vs. /net/filer/vol/vol0/blah
by Mike Sphar 15 Aug '01

15 Aug '01

I'm only running 6.0, so it's possible something changed in 6.1, but I've been able to adjust those paths simply by editing the /etc/exports file to export the paths without the vol0. -----Original Message----- From: Jim Davis [mailto:jdavis@cs.arizona.edu] Sent: Wednesday, August 15, 2001 9:46 AM To: toasters Subject: /net/filer/blah vs. /net/filer/vol/vol0/blah After upgrading from 5.3.4-mumble to 6.1.1, it seems that clients can't access pathnames like /net/filer/whatever, but rather have to use /net/filer/vol/vol0/whatever. I think before both seemed to work more or less interchangeably, and unfortunately we have some symlinks that use the old form to point to various things that now are missing. I'm probably just missing something obvious, but is there a way to get the old behavior without using '/vol/vol0' in those pathnames?

2 1

RE: resizing boot volume
by Fox, Adam 15 Aug '01

15 Aug '01

Actually you can offline vol0 before you reboot. It won't actually offline the volume until you reboot but it will mark it to be offlined. Or if you are running 6.x, you can do it as you want but you won't need the 2nd reboot because you can offline non-root volumes without a reboot on 6.x. If you are running pre-6.x, you can do the first method and only have 1 reboot. Just a thought. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: neil lehrer [mailto:nlehrer@ibb.gov] > Sent: Wednesday, August 15, 2001 1:04 PM > To: toasters > Subject: resizing boot volume > > > i am going to redo my boot volume. no data to save. > > steps: > create new volume /vol/vol1 > vol create /vol/vol1 2 > > export /vol/vol1 > > copy /etc from vol0 to vol1 > > make vol1 the root volume > vol options /vol/vo11 root > > reboot > > if vol1 shows as the root volume then > vol offline /vol/vol0 > reboot > vol destroy /vol/vol0 > > rename back to default root vol name > vol rename /vol/vol1 /vol/vol0 > > add some disks back to the new vol0 > vol add /vol/vol0 3 > > > am i missing anything? > > thanks. > > > > -- > > > regards >

1 0

RE: ndmpcopy - dir size changes
by Link, Bill (OTS-EDH) 15 Aug '01

15 Aug '01

Over time as files are deleted directories get more and more deleted entries which are essentially holes in the directory file. NDMPCOPY or even extracting a tar archive will compress the directory files by deleting the unused dirents. Bill -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Wednesday, August 15, 2001 9:38 AM To: toasters Subject: ndmpcopy - dir size changes Hi, I just performed a ndmpcopy on my filer. I ran an ls -lR on the original location and on the new location. The files and sizes were identical, the directory sizes differed. Anyone have any ideas why? Thanks Manny Notice: This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system. Thank you.

2 1

RE: boot volume with no data
by Fox, Adam 15 Aug '01

15 Aug '01

Okay, I've heard lots of debates on this, here's my opinion and I'm sure others will disagree. I'm not a big fan of root-only volumes. I think that overall they are a big waste of space for very little gain. However, there are some good reasons to do it depending on your scenario. 1. SnapMirror. If you are SnapMirroring all of your data then it is a good idea to have your root volume on a separate volume. This allows you to offline your data volumes at will which is good for initial transfers or resynching back to a source. 2. SnapRestore. If your application or dataset makes regular use of SnapRestore..yes I've seen this in a case where customers like to snapshot a known good dataset, have their users mess with it, then SnapRestore back to the known good dataset afterwards. If this is your scenario, then yes, a root volume is a good idea. 3. Lots of vol copy'ing. If you do lots of vol copy commands in your dataset, then for the same reason as SnapMirror, the offline ability is a good one. There may be others out there in the world, but these are the most common. But in my opinion, for the 50-60MB that /etc typically takes up, is it worth dedicating 2 36GB or 72GB drives? Maybe so, but most of my customers don't think so. Just one geek's opinion. There isn't really a single right or wrong answer on this one. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: neil lehrer [mailto:nlehrer@ibb.gov] > Sent: Tuesday, August 14, 2001 11:56 AM > To: toasters > Subject: boot volume with no data > > > are there any particular advantages or disadvantages to just > having ontap on > vol0 and data on other volumes? > -- > > > regards >

6 5

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