toasters December 1997

toasters@lists.teaparty.net

19 participants
19 discussions

Re: More capacity on lower-end filers
by hitz＠netapp.com 10 Feb '98

10 Feb '98

> On Thu, 12 Jun 1997, Dave Hitz wrote: > > > > Although marketing certainly has input, the space restrictions also > > come from engineering droids. During normal operation the smaller > > machines could certainly handle more disk, but the time required for > > something like RAID reconstruction could get dangerously long. > > Is this the reason why the F210 can still only use around 50GB of > disk, even though it can physically accomodate more using 9GB drives? In order for a RAID reconstruction to complete, you have to read all of the data on all of the other disks. So RAID reconstruction time is proportional the the amount of data, not proportional to the number of disks. Dave Hitz hitz(a)netapp.com Network Appliance (408) 367-3106

8 10

Snapshot overhead.
by Gregory Gulik 28 Dec '97

28 Dec '97

I think this has been discussed already, but I can't seen to get to the archive any more. Is there a way to tell how much disk space overhead there is from using snapshots?

3 2

Selective snapshotting
by Brian Tao 14 Dec '97

14 Dec '97

Any plans to offer selective snapshotting per directory tree or quota tree? e.g.: I would love to have snapshots for the /www and /home quota trees, but not for /news and /mail (all four reside on the same filer). -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

2 1

NetApp backup to a Quantum 4700
by rasmus＠bellglobal.com 12 Dec '97

12 Dec '97

I am sure this is documented somewhere, but I haven't run across it yet. The NetApp documentation suggests estimating the number of tapes and then specifying the command-line dump command such that tape handling is done correctly for the number of tapes needed. I'd prefer to let the 4700 do it by itself in auto mode. Can I just use a very large -B value and pretend that my stacker is one big tape or are there other tricks? -Rasmus

1 0

Re: MS-SQL on CIFS shares?
by Rajiv Khemani 10 Dec '97

10 Dec '97

>Oh, it is definitely MS SQL. It wants a real NTFS share with full NTFS >security. Just wondering if anybody has found a way around this. Rasmus, We at NetApp have "found a way" to run SQL server off a NetApp CIFS mounted share. However, it is not yet fully tested or supported by either Microsoft or NetApp. So, we're not promoting this solution and our sales or support people will not be able to help. At the same time, we are interested in hearing from people who like this solution, and your specific reasons for it. Send me an email directly, as this will help Microsoft and us - to justify documenting, testing and supporting it. Regards, Rajiv Khemani At 10:46 AM 12/9/97 -0500, rasmus(a)bellglobal.com wrote: >> On Tue, Dec 09, 1997 at 10:00:47AM -0500, rasmus(a)bellglobal.com had >> written: > Has anybody managed to get Microsoft's SQL server to run nicely >> off of a > NetApp CIFS mounted share? If so, what is the trick? >> >> Good question! >> >> But the problem might be MS SQL since I can't even get it to do it >> over a Samba share and will be trying today from a real NT box to see >> if it works that way. > >Oh, it is definitely MS SQL. It wants a real NTFS share with full NTFS >security. Just wondering if anybody has found a way around this. > >-Rasmus > > ---- Rajiv Khemani Group Marketing Manager Network Appliance, Inc. Direct: 408-367-3758 Fax: 408-367-3151 HTTP: http://www.netapp.com

1 0

NVRAM for a 630
by Wm Kevin Shaw 09 Dec '97

09 Dec '97

Does anyone have a source for 630 NVRAM? Thanks in advance.

1 0

MS-SQL on CIFS shares?
by rasmus＠bellglobal.com 09 Dec '97

09 Dec '97

Has anybody managed to get Microsoft's SQL server to run nicely off of a NetApp CIFS mounted share? If so, what is the trick? -Rasmus

2 2

NVRAM type on F220
by Chris Caputo 09 Dec '97

09 Dec '97

Does anyone have info on or a good source for NVRAM for an F220? Thanks, Chris

3 2

/etc/db/quota.db
by Steve Losen 08 Dec '97

08 Dec '97

Why is the mtime on /etc/db/quota.db set to zero (Dec 31, 1969 EST) ? Is this where the user quotas and disk consumption are stored? This is on a F630 running 4.2a Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

2 1

Re: filesystem and RAID questions
by hitz＠netapp.com 08 Dec '97

08 Dec '97

> > Looks Like it finished rebuilding the disk to me ;) > > I think I've misused the term "degraded mode", but my question is > still the same. What exactly is it going to do if the scrub fails? > I'd rather the filer wasn't stressed until a new spare is in there. I understand your question now. If RAID scrub finds a block it can't read, it reads the corresponding blocks on all the other drives and reconstructs the missing data. Then it re-writes the unreadable block, which remaps the block to a new location. I believe the remapping occurs automatically, because we set an auto-remap flag on the drives, but this may vary from drive to drive. This doesn't require a spare disk. > I guess it still could help with localized media errors, but I've > never seen any reaction to media errors other than a whole disk > failing out. If a WRITE fails, then we do drop the whole disk out. This is because, with auto-reremap, a WRITE should never, ever fail. If it does, there's something seriously wrong. A read failure during normal operation is handled as described above with RAID scrubbing. The block is rebuilt and rewritten so that the drive remaps it. We added RAID scrub because single block failures do occur, and they are nasty. If you've got an undetected bad block, and then a different disk fails entirely, then the stripe with the bad block will be impossible to reconstruct, because it has two missing blocks. In this case we zero both blocks and require the user to run WACK to fix whatever damage that causes. That generally works, unless the lost block is really important, but it's much, much better to find and fix the bad block right away, which is what the scrubbing does. It actually took a year or two before we started seeing this problem in our install base. We figure that it just takes a while before a system sits long enough to have files that never get read, and then for a failure to occur in such a file. Dave

1 0

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 December 1997