toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

Changed DLT 4000 for DLT 7000 - how to get new storage density?
by Thomson, Michael (UK, GIS ISM Group for R&D) 05 Nov '98

05 Nov '98

Hi there. Last weekend we upgraded our DLT4700 (single DLT4000, 7 slots) for a Brece-Hill Q2.15 (two DLT 7000, 15 slots). We're reusing the CompacTape IV cartridges, but the new drives seem to recognise the old tapes as being written by a DLT4000, and don't use the higher density that the DLT7000 is capable of. Is there an easy way to re-initialise the tapes that'll allow us to use the maximum storage capacity? Details follow: First we check the status of the drive: Checking pre-dump status with: rsh -n <filer> mt -f nrst0a status Tape drive: Digital DLT7000 Status: ready, write enabled Format: 85937 bpi 70 GB (w/comp) fileno = 0 blockno = 0 resid = 0 This implies that it'll use the high density we're after... Then we do the dump rsh -n <filer> dump 0ufbB urst0a,urst0a,urst0a,nrst0a 63 30000000 / (Yes, I know the block count is low - we're trying to fix the problems without causing any EOT fun & games) Now after the dump is done, we load the tape into the drive, which reports A: Idle C 20.00G This says to me that the tape is still recorded at the DLT4000 density, albeit with compression. Any suggestions? Cheers, Mike -- \\|||// Minds are like parachutes; (@ @) They only work when open. *---oOO-(_)-OOo------------------------------------* * Michael Thomson Email: mt53590(a)ggr.co.uk * * Unix Specialist Internal: 782 2369 * * Glaxo Wellcome External: 01438 762 369 * * Stevenage, UK Fax: 01438 762 461 * * .oooO Oooo. Mobile: 0498 725 047 * *--( )---( )-----------------------------------* \ ( ) / (Quote: Sir James Dewar) \_) (_/

1 0

Dual home fiber
by Algar, Christopher [PAI01:8881:EXCH] 05 Nov '98

05 Nov '98

Greetings. I'm having a bit of difficulty configuring a F760 with two fiber cards on different sub nets. It's been running fine with ifconfig f3 `hostname`-f3 netmask 255.255.240.0 I've tried adding a similar line to etc/rc for f1 explicitly stating the IP address instead of hostname, installing the additional card in slot 1 and rebooting. Also tried installing the card with no changes to rc and rebooting. The result is the same, the system panics and fails to boot. Can anyone help? Regards, Chris Algar UNIX support (amongst other things) Nortel Optoelectronics Paignton UK

1 0

raid scrubbing and hot spares
by Dave Cole 05 Nov '98

05 Nov '98

We have a number of f230's here that seem to have either stopped doing their raid scrubbing or isn't bothering to report it any more. while the /etc/rc file doesn't explicitly ask to turn on scrubbing, doing an 'rsh netapp1 options' returns this: raidtimeout 24 raid.reconstruct_speed 4 raid.scrub.enable on which seems pretty typical. Only 2 out of our 7 operating netapps are actually logging this: Sun Oct 18 01:00:00 EDT [raid_scrub_admin]: Beginning disk scrubbing... Sun Oct 18 02:47:16 EDT [raid_scrub_admin]: Scrub found 0 parity inconsistencies Sun Oct 18 02:47:16 EDT [raid_scrub_admin]: Scrub found 0 media errors Sun Oct 18 02:47:16 EDT [raid_scrub_admin]: Disk scrubbing finished... Of the two that are logging, one is an f210 running ONTAP 4.2a, the other is an f210 running ONTAP 5.1.2 The ones not logging are 4 x f230's, 1 x f220. On a related note, we happen to know that one of our hot spares on one of the f210's is showing a read error. It was discovered during the install. I'm not entirely sure if I have logs of the discovery. But along that line, are there any tests or scrubs done or are they assumed to be healthy? ---------------------------------------------------------------- Dave Cole (DC1110) | dacole(a)netcom.ca Systems Administrator |* dacole(a)rik.net * | office/~dacole/ Netcom Canada |* www.rik.net/~dacole/ * 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725

11 13

RE: can't see ~snapshot directory
by Allison, Bridget 05 Nov '98

05 Nov '98

Firstly, yes, there's a fix - see the man page extract: cifs.show_snapshot By default this option is FALSE. The snapshot directory ~snapshot is no longer shown at the root of a share. This is a change in behavior from previous versions. Setting this to TRUE will restore the old behavior. On Windows NT 4 or Windows 95 clients, the user can access snapshots by entering \\filer\share\.snapshot (or ~snapshot or ~snapsht) in the Start->Run menu. Snapshots can also be accessed lower in the share by providing a path to a lower directory. Snapshots can be accessed through DOS on any system by changing to the ~snapsht directory. We changed the default due to problems with NT backup software handling snapshots badly. > We use NFS and CIFS on our toasters. Since upgrading to 5.1.2, our > PC clients no longer see the ~snapshot directories. (This is the > .snapshot directory on unix clients.) > > Is there a fix? This is disconcerting. Or should I say broken?

1 0

can't see ~snapshot directory
by Tom Reingold 04 Nov '98

04 Nov '98

We use NFS and CIFS on our toasters. Since upgrading to 5.1.2, our PC clients no longer see the ~snapshot directories. (This is the .snapshot directory on unix clients.) Is there a fix? This is disconcerting. Or should I say broken?

1 0

Re: Quota initialization speed on F230
by mds＠ns.gbnet.net 03 Nov '98

03 Nov '98

Sounds bad - does this pertain to 5.1.2 or 5.1.2D1?

1 0

Quota initialization speed on F230
by Brian Tao 03 Nov '98

03 Nov '98

Is it just me, or is quota initialization on an F230 running 5.1.2 excruciatingly slow? I don't remember our other F230's being this slow at redoing tree quotas with 4.2a, especially when the filer is basically empty (only the /etc directory is populated). It's been 15 minutes since a "quota on", and the filer only reports 39% done. I'm sure it was faster in 4.2a. # rsh toast quota vol0: quotas are initializing (39% done). # rsh toast df Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 33007568 1212560 31795008 4% /vol/vol0/ /vol/vol0/.snapshot 11002520 0 11002520 0% /vol/vol0/.snapshot # rsh toast df -i Filesystem iused ifree %iused Mounted on /vol/vol0/ 1161 8709169 0% /vol/vol0/ # rsh toast sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 37% 0 0 0 0 0 1211 0 0 0 6 72% 0 0 0 1 0 76 0 0 0 6 22% 0 0 0 0 0 244 0 0 0 6 30% 0 0 0 1 0 1234 0 0 0 6 79% 0 0 0 2 0 56 0 0 0 6 ^C -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

2 1

Changing which volume is the root volume W/O losing data?
by Larry Rosenman-CyberRamp System Administration 02 Nov '98

02 Nov '98

Is it possible on 5.1D14 to change which of 2 volumes is the root volume of a F520-110? I have a filer that has 14 disks (100GB), and 2 volumes: 30gb Mail 70gb News. Mail is the current root volume. I want to make the news volume the root volume, but not lose the data on news. I then want to destroy mail (it's moving to a new filer), and add it's disks to the news volume. How would I go about this? Thanks! LER -- Larry Rosenman, Sr. System Administrator, CyberRamp Internet Services E-Mail: ler(a)cyberramp.net, http://www.cyberramp.net Voice: (214) 343-3333/(817) 461-8484 (Metro)/Fax: (214) 343-3727 Tech Support: (214) 340-2020/(817) 226-2020 (Metro) 7AM-Midnight, 7 Days U.S. Mail: 11350 Hillguard Rd, Dallas, TX 75243-8311

3 3

Re: SMTP MIB (was Re: raid scrubbing and hot spares)
by mds＠ns.gbnet.net 29 Oct '98

29 Oct '98

Has anyone thought of adding a counter for the number of NVRAM flushes for a given rolling period? My understanding is that one of the issues in achieving excellent performance on writes is avoiding, or dealing with, back-to-back consistency points. It strikes me that a simple metric based on the number of NVRAM flushes-to-disk over the last 60-seconds, updated every 5 seconds say, would give people a handle on whether there's a bottleneck happening there. It might be even more interesting to keep track of in the clustered-filer environment.

2 1

Re: ndmpcopy question
by sirbruce＠ix.netcom.com 29 Oct '98

29 Oct '98

On 10/28/98 17:49:05 you wrote: >NOW BEWARE! Once you test a few times and discover that ndmpcopy tends to >hang, you can get into the habit of just interrupting it whenever you see >that message. DON'T. If you are copying a very large amount of data, the >restore will probably finish well after the dump. This is because the >restore does a final pass (after all data has transferred) to set the >correct owner and permissions on all directories. If you interrupt >ndmpcopy while this is going on, you are left with a bunch of dirs owned >by root, with permissions 777 on the restore filer. Can you guess how >I found this out?? :-) This should be entered as a bug. Even though interrupting a restore isn't something you should do, having it create potential security issues as a result isn't really necessary. It's probably nice to have that as a with ndmpcopy as a shortcut in the code (you can probably rely letting the requests go through a higher level, since they have "permission"), though, so it's not surprising it's there. May not be something that can be fixed easily. Bruce

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