toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Re: hooking up laptop to a filer
by Fred Ab 08 Sep '99

08 Sep '99

Oh my, I do not believe I'm the intended recipient for such confidential and high level information. I have destroyed all copies of the original message and wiped my hard drive as well as the mailservers hard drive clean. ===}The information contained in this message is confidential and may be legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. ===} ===}Hello people, ===} ===}I've just received a new F720 and a want to hookup a laptop with hyperterminal to the filer. ===}Can anybody tell me how to configure the laptop/hypertermial to get it started? ===} ===}TIA, ===} ===}Jan & Leonard

1 0

Tedious booting from floppies
by Dave Atkin 08 Sep '99

08 Sep '99

Is there any way to do a maintenance style boot without actually using boot floppies? Maybe by copying the contents of the boot floppies onto a spare disk? The boot command appears to take an argument but I haven't figured out what it is. We just spent a whole day moving data from old F230s to new 740s and we ended up booting from floppies numerous times, partly due to the 740 crashing whenever we tried to put the old volume on line. Waiting for the floppies got very tedious, especially now that the OS has overflowed onto 2 disks. It might then be possible to run WACKY occasionally overnight by dialing in, without having to be physically present to change the floppy. Has Netapp thought of alternative boot methods such as TFTP or LS120 drives? Dave Atkin ------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin(a)york.ac.uk ------------------------------------------------------

6 9

Differential DLT drives in the UK
by Dave Atkin 08 Sep '99

08 Sep '99

Can anyone recommend a source of these in the UK? Our supplier, having now sent us two different single-ended drives by mistake, is saying that the differential versions are only available on special order and it may take up to 12 weeks. Dave Atkin ------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin(a)york.ac.uk ------------------------------------------------------

1 0

Re: Parts source for end of life products?
by Doug Porter 08 Sep '99

08 Sep '99

"Shaun T. Erickson" wrote: > sirbruce(a)ix.netcom.com wrote: > > > > On 08/30/99 23:49:43 you wrote: > > >However, the price of RAM from NetApp was 3-5x the price (I forget exactly > > >how much) of the approved Kingston SIMM. So, we just purchased 16 SIMMs > > >from our Kingston supplier, saving significant amounts of cash, and we > > >kept the 4 excess SIMMS in our `hot spare' store. It works like a charm. > > > > A cautionary note - much of the supposedly "in-spec" memory Kingston > > or other vendors sell is not capable of handling the strict timing > > and loading requirements of a Netapp filer. The reason the SIMMs > > you get from Netapp cost more is because they are tested for proper > > tolerance and inoperability. If you decide to use another source, > > you should be prepared for the chance of crashes or spontaneous > > reboots and be prepared to go through several cycles of swapping > > various SIMMs in various combinations to figure out the problem. > > Then NetApp shouldn't certify them. If I buy memory NetApp approved > memory from Kingston (and I have), I expect it to perform as well as > NetApp supplied memory. I don't expect NetApp to recommend sub-standard > memory for me to buy. > Hmm - Anyone ever remember buying single and double density floppy disks? The doubles usually cost a whole lot more (almost double when they first came out) The only difference was in the testing. They all came out of the same production run - some passed the dd tolerance test - some didn't - the ones that didn't became single density. All from the same manufacture. The same is true for memory, disk, and just about anything else that is mass produced. (Kinda like airplane seats - get the most $ that you can - sell the cheap stuff to whoever will buy) dp > > -ste > > -- > Work: (908) 582-7629 Pager: (800) 756-1133 Cell: (908) 672-6456

1 0

Re: Tedious booting from floppies
by Dave Atkin 07 Sep '99

07 Sep '99

Thanks for all the replies. We'll use the "setenv floppy-boot? true" next time. Some people asked about the crashes we had. It was when we moved a set of SCSI disks onto a 740 from a 230, having first renamed the volume on the old 230 to be called "old". The 740 also had some FCAL disks, although it didn't make any difference to the crash whether or not they were connected. We booted the 740 with 5.2.2P1 in maintenance mode (in order to sort out the volume names) from floppy with the old disks plugged into the new differential SCSI shelf. The sequence was: > vol status raid_checklabels(0): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 raid_checklabels(0): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 raid_checklabels(1): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 raid_checklabels(1): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 raid_checklabels(2): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 raid_checklabels(2): disk 8a.0 has serialno 0016784334 but system has serialno 0016792113 No root volume found. You must specify a root volume with "vol options <volname> root" before rebooting the system. Volume State Status Options old offline foreign > vol online old PANIC: MM fault MMCSR=1, type=0, VA=0x128, PC=0xfffffc 00003b967c --- This was quite repeatable. The trick we evenually discovered was to disconnect the FCAL shelf, do a "boot without /etc/rc" so that it gave the message about "discarding the NVRAM contents", and made the volume available instead of labelling it "foreign". Dave Atkin ------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin(a)york.ac.uk ------------------------------------------------------

1 0

Re: Tedious booting from floppies
by alexei＠mindspring.net 07 Sep '99

07 Sep '99

armijo(a)cs.unm.edu writes: > this would be very cool, or better yet: 'boot cdrom', which i have heard > rumored several times , anyone at NetApp want to confirm/deny this may > actually happen? cdrom would be ok, better than floppies, but still limiting in other ways. With floppies, you can make new images as often as you like or need. With cdrom's, you are stuck unless you have a cd burner (which are more common place now) and the time to spend doing so. I think a better solution would be to use the same media the digital cameras of today use. If you use the SmartMedia style, you are limited to the size of images (I think it only goes to 16MB right now). The CompactFlash cards are much sturdier and go to 96MB. The great things with either of these formats are: - cheap media - inexpensive media readers ($70 for a USB version) - good support across most OS'es for the readers - PCMCIA media adapters (so PCMCIA might be a good interface to the filer) and: - I can go to WalMart at 3AM and buy the media and card reader in case of an emergency Including this as a peripheral with every filer is inexpensive (well, cheaper than a ZIP drive or a cdrom burner). I realize there are many competing formats for the next generation of filer boot media, but the digital cameras are pretty wide spread now and the flash card format will be around a while. Alex

2 1

Re: Web Hits per NFS ops/s ?
by sirbruce＠ix.netcom.com 05 Sep '99

05 Sep '99

On 09/04/99 17:00:02 you wrote: >Not sure about the theoretical case but here's some stats from a system of >heavily tuned Apache web servers running Linux 2.0 (NFS V2) mounting a >NetApp for all content. It's only serving plain content - no scripts. > >Average NFS operations per url is 7.96. Why no writes? Do you not keep your log file(s) on the same filer? And what about when you update content? Bruce

2 1

Re: moving stuff among qtrees
by sirbruce＠ix.netcom.com 05 Sep '99

05 Sep '99

On 09/04/99 13:23:47 you wrote: > >On Fri, 3 Sep 1999 sirbruce(a)ix.netcom.com wrote: >> >> So to change the ID requires essentially a recursive chown-type >> operation that is always going to be proportional to the amount of >> data "schlepped". > > If it really was as fast as a recursive chwon, that would be >great, but the Netapp still issues a copy/unlink instead of a rename >when moving files between quota trees. This isn't the fault of the >client either, because the same thing happens if I mount the filer's >root filesystem on the client (so it thinks it is one filesystem), and >do a move from there. Hmm, this doesn't make any sense to me. Shouldn't do that if the client has the root mounted, and in any case I don't know how one would fine out what ops the Netapp is "issueing" to itself. Perhaps it's reported in the NFS ops mix? But if that's the case, then you have an issue as to whether or not those commands should report only what the client is sending (my view) or what operations the Netapp is translating that to internally (your contention that it does now). How about an official "wafl_stat" command? Bruce

2 1

None
by Michael Batterden 04 Sep '99

04 Sep '99

1 0

Re: moving stuff among qtrees
by sirbruce＠ix.netcom.com 04 Sep '99

04 Sep '99

On 09/03/99 10:55:20 you wrote: >Can anybody suggest a way to schlep a hierarchy around that is not >O(n) in this annoying way? A qtree identifier is essentially just a third ID, just like user and group ID, set on each file and inherited from the parent directory. So to change the ID requires essentially a recursive chown-type operation that is always going to be proportional to the amount of data "schlepped". I suppose one could implement a scheme where the changes were not made right away, and instead upon access each parent was checked back to the root to see if the file has the "wrong" qtree ID for the qtree and if so, correct it and then let you access it, but that would be very slow. Bruce

2 1

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