toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

Re: Problems with CIFS and 5.3.1
by Joan Pearson 03 May '99

03 May '99

In 5.3 support for Unicode was added. CIFS can only access directories that have been converted to the new Unicode format. Directories that are not in Unicode format are converted automatically to Unicode format when first accessed by CIFS. But since snapshots are read only, directories in snapshots cannot be converted and are not accessible from CIFS. Before 5.3, there were two directory formats: those accessed by CIFS (cifs format) and those never accessed by CIFS(non-cifs format). The first time CIFS accessed a directory it would be converted to CIFS format. Non-cifs format directories in snapshots were not accessible from CIFS. In 5.3, both cifs-format and non-cifs format directories are converted to unicode format when accessed by CIFS. Directories created by CIFS are created in unicode format. There is an option wafl.create_ucode that can be used to create unicode directories by default from NFS. Refer to the System Administration Guide for more information. Joan Pearson At 11:08 AM 5/3/99 , you wrote: >I upgraded to 5.3.1 this morning. After the upgrade I noticed I was unable >to access any snapshots via CIFS. The snapshots would show up in Explorer >but when I tried to access the snapshots, even logged in as root, I received >a error message "Access is Denied". > >I tried several ideas to resolve the issue without any luck. I then ran >"cifs testdc" and received the following message: > >_______________________________________________________________ >Using Established configuration >Current Mode of NBT is H Mode > >Netbios scope "" >Registered names... > NEWTOASTER < 0> WINS Broadcast > NEWTOASTER < 3> WINS Broadcast > NEWTOASTER <20> WINS Broadcast > OSSRTPPROD < 0> WINS Broadcast > OSSRTPPROD < 3> WINS Broadcast > OSSRTPPROD <20> WINS Broadcast > >Testing Primary Domain Controller >found 1 addresses > >Testing all Domain Controllers >found 3 addresses >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.14...192.168.255.14 is alive >found DC OSSRTPNT40 at 192.168.255.4 >Not able to communicate with DC 192.168.255.4 >found DC OSSRTPBDC at 192.168.255.14 >______________________________________________________ > >Thinking the problem was on my end, I terminated CIFS, deleted the filer on >my PDC and readded the filer. I rebooted the filer and reran "cifs setup" >and kept receiving a error message stating "PDC is not active" and cifs >setup would terminate. > > I finally dropped back to 5.21. > >I reran "cifs testdc" and received the following: >____________________________________________________________________________ >____ >testfiler> cifs testdc >Using Established configuration >Current Mode of NBT is H Mode > >Netbios scope "" >Registered names... > TESTINGFILER < 0> WINS > TESTINGFILER < 3> WINS > TESTINGFILER <20> WINS > OSSRTPPROD < 0> WINS > OSSRTPPROD < 3> WINS > OSSRTPPROD <20> WINS > >Testing Primary Domain Controller >found 1 addresses >trying 192.168.255.4...192.168.255.4 is alive >found PDC OSSRTPNT40 > >Testing all Domain Controllers >found 3 addresses >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.4...192.168.255.4 is alive >trying 192.168.255.14...192.168.255.14 is alive >found DC OSSRTPBDC >found DC OSSRTPNT40 >found DC OSSRTPBDC >____________________________________________________________________________ >____________ > > >Finally, I reran cifs setup without a problem. I was able to get back into >the snapshots. Has anyone else came across a similar issue with 5.3.1 and if >so how did you resolve? >

1 0

Problems with CIFS and 5.3.1
by Mike Ball 03 May '99

03 May '99

I upgraded to 5.3.1 this morning. After the upgrade I noticed I was unable to access any snapshots via CIFS. The snapshots would show up in Explorer but when I tried to access the snapshots, even logged in as root, I received a error message "Access is Denied". I tried several ideas to resolve the issue without any luck. I then ran "cifs testdc" and received the following message: _______________________________________________________________ Using Established configuration Current Mode of NBT is H Mode Netbios scope "" Registered names... NEWTOASTER < 0> WINS Broadcast NEWTOASTER < 3> WINS Broadcast NEWTOASTER <20> WINS Broadcast OSSRTPPROD < 0> WINS Broadcast OSSRTPPROD < 3> WINS Broadcast OSSRTPPROD <20> WINS Broadcast Testing Primary Domain Controller found 1 addresses Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPNT40 at 192.168.255.4 Not able to communicate with DC 192.168.255.4 found DC OSSRTPBDC at 192.168.255.14 ______________________________________________________ Thinking the problem was on my end, I terminated CIFS, deleted the filer on my PDC and readded the filer. I rebooted the filer and reran "cifs setup" and kept receiving a error message stating "PDC is not active" and cifs setup would terminate. I finally dropped back to 5.21. I reran "cifs testdc" and received the following: ____________________________________________________________________________ ____ testfiler> cifs testdc Using Established configuration Current Mode of NBT is H Mode Netbios scope "" Registered names... TESTINGFILER < 0> WINS TESTINGFILER < 3> WINS TESTINGFILER <20> WINS OSSRTPPROD < 0> WINS OSSRTPPROD < 3> WINS OSSRTPPROD <20> WINS Testing Primary Domain Controller found 1 addresses trying 192.168.255.4...192.168.255.4 is alive found PDC OSSRTPNT40 Testing all Domain Controllers found 3 addresses trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.4...192.168.255.4 is alive trying 192.168.255.14...192.168.255.14 is alive found DC OSSRTPBDC found DC OSSRTPNT40 found DC OSSRTPBDC ____________________________________________________________________________ ____________ Finally, I reran cifs setup without a problem. I was able to get back into the snapshots. Has anyone else came across a similar issue with 5.3.1 and if so how did you resolve?

1 0

Re: Bypassing rc
by Jason D. Kelleher 03 May '99

03 May '99

In message <Pine.BSF.4.10.9905011132060.249-100000(a)schizo.cdsnet.net>, Jaye Mathisen writes: > > >While I sit on hold at netapp, I'm just wondering if anybody's out there. > >I have a filer running 5.3, and I was trying one of the tips on the Netapp >web page about making one of the interfaces a primary for CIFS, by >rearranging things in /etc/rc, and while all I did was move one of >the 2 ifconfig lines, something is boobered up now, and the filer dies >with: > >Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. >Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. >Sat May 1 11:27:52 PDT [rc]: timed: time daemon started >Sat May 1 11:27:52 PDT [Java Thread]: TimeDaemon: Can't connect to time se >rver >'10.0.1.3' >NFS server is running. >timed not found. Type '?' for a list of commands >quota: vol0: run 'quota off' before 'quota on'. > >PANIC: ../common/nbt/nbns_receive.c:207: Assertion failure. on Sat May 1 1 >8:27: >53 1999 > >version: NetApp Release 5.3: Thu Apr 1 11:18:39 PST 1999 >cc flags: 1 >dumping core: ..................................................Old core pr >esent > on disk --- not dumped. > > > >Anyway, I guess I'll try some floppies, and see how far I get while I >wait... > >Any tips appreciated. Stay away from 5.3 w/out speaking to tech support first. Not sure about 5.3.1, but it took three "D" releases to get 5.3 working properly for me. And since the "Closed Bugs by fix release" for 5.3.1 on NOW looks shorter than the list of bugs fixed in my 5.3Dx release, I'd be real careful. The "Bugs" section in NOW has gotten alot more usable. (In fact, all of NOW has gotten better recently.) But I still want a "Known Bugs by release". jason

1 0

Hardware for F330
by Jay Orr 02 May '99

02 May '99

Hi all! I was wondering if anyone can help. We are a small shop with 2 F330's with 2 disk cabinets on each one. We were looking into adding another tray on each, but were told by NetApps that they are no longer available. All I'm looking for is to upgrade the memory, add another scsi controller, and another tray (is that asking TOO MUCH???). Questions: Can I use off the shelf memory (and what kind)? What about SCSI controllers? Where can I get disk trays? Could we instead replace the drives with 9G or 18G drives (and what model would we use)? NetApps solution is to spend $60k+ to upgrade, and all we need is another 10G - 20G. The current system works fine, isn't overused, and could handle the expansion IF WE CAN FIND THE COMPONENTS... Thanks for the help. By the by, I've been looking for a toaster FAQ, is there one? ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

6 5

restore annoyance
by kg 01 May '99

01 May '99

Anyone notice that restore operations will fail if there isn't a /etc/tmp on the destination volume? Fine most of the time, but rather annoying to have to create a /etc on non-root volumes.... ..kg..

1 0

Bypassing rc
by Jaye Mathisen 01 May '99

01 May '99

While I sit on hold at netapp, I'm just wondering if anybody's out there. I have a filer running 5.3, and I was trying one of the tips on the Netapp web page about making one of the interfaces a primary for CIFS, by rearranging things in /etc/rc, and while all I did was move one of the 2 ifconfig lines, something is boobered up now, and the filer dies with: Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. Sat May 1 11:27:51 PDT [rc]: de_main: e10 : Link down. Sat May 1 11:27:52 PDT [rc]: timed: time daemon started Sat May 1 11:27:52 PDT [Java Thread]: TimeDaemon: Can't connect to time server '10.0.1.3' NFS server is running. timed not found. Type '?' for a list of commands quota: vol0: run 'quota off' before 'quota on'. PANIC: ../common/nbt/nbns_receive.c:207: Assertion failure. on Sat May 1 18:27: 53 1999 version: NetApp Release 5.3: Thu Apr 1 11:18:39 PST 1999 cc flags: 1 dumping core: ..................................................Old core present on disk --- not dumped. Anyway, I guess I'll try some floppies, and see how far I get while I wait... Any tips appreciated.

1 0

NOW profile 'Protocol Licenses'
by kg 01 May '99

01 May '99

Any chance that cluster licenses could get listed as well? http://now.netapp.com/cgi-bin/profile/protlicenses ..kg..

2 1

Re: Hardware for F330
by Jay Orr 01 May '99

01 May '99

Ok, so if you can humor a newbie for a few more questions I'd appreciate it. I have a similar configuration with a tray off each slot. I can dasy-chain on more trays? Also, could I use a generic hot-swap SCSI cabinet? And if I put 9 gig drives in them, any special ones? Also, I notice on the sysconfig that both slot0 and 9 use Qlogic ISP 1020A scsi controllers. As best as I can see those are discontinued, but they're standard PCI scsi controllers -- anyone dropped in another PCI scsi controller and see what it does? And what's with your CPU speed? On Fri, 30 Apr 1999, Luke Gain wrote: > I think the scsi card was made by netapp. so your only option may be the > slot0 controller. > > Here is my 330 config fwiw.. > (check out the cpu speed :) > -Luke > > > sysconfig -v > NetApp Release 4.3.4: Wed Apr 22 16:25:06 PDT 1998 > System ID: 0016781651 > slot 0: System Board 192 MHz (NetApp System Board I rev-b) > Firmware release: 1.6_i > Memory Size: 256 MB > slot 0: SCSI Host Adapter 0 (QLogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > slot 0: Ethernet Controller e0 > MAC Address: 00:a0:98:00:08:ce (100tx-fd) > slot 6: NVRAM (NetApp NVRAM I) > Revision: D1 > Serial Number: 4435 > Memory Size: 8 MB > Battery 1 Status: 100% (3.18v) > Battery 2 Status: 100% (3.18v) > slot 9: Dual SCSI Host Adapter (NetApp SCSI Adapter I) > SCSI Host Adapter 9a (Qlogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > SCSI Host Adapter 9b (Qlogic ISP 1020A) > Firmware Version 2.13 Clock Rate 40MHz. > 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) > In-Band Enclosure Services > 0 Swap Events, 0 Enclosure Events > > > > > > Yes, that helps alot! Any idea on adding another scsi card? > > > > > > On Fri, 30 Apr 1999, Luke Gain wrote: > > > > > Jay, > > > > > > I have found that standard Kingston 72pin parity memory works fine in > > > both my 220 and 330. You should be able to string a 3rd shelf > > > off of the controller on the motherboard. Don't know where to obtain the > > > Digital Storageworks shelf (Tech Data used to sell them). > > > Corprate Systems is normally a good source for drives. (www.corpsys.com) > > > > > > Hope this helps. > > > > > > -Luke > > > > > > > > > > > > > > Hi all! > > > > > > > > I was wondering if anyone can help. We are a small shop with 2 F330's with > > > > 2 disk cabinets on each one. We were looking into adding another tray on > > > > each, but were told by NetApps that they are no longer available. > > > > > > > > All I'm looking for is to upgrade the memory, add another scsi controller, > > > > and another tray (is that asking TOO MUCH???). Questions: Can I use off > > > > the shelf memory (and what kind)? What about SCSI controllers? Where can I > > > > get disk trays? Could we instead replace the drives with 9G or 18G drives > > > > (and what model would we use)? > > > > > > > > NetApps solution is to spend $60k+ to upgrade, and all we need is another > > > > 10G - 20G. The current system works fine, isn't overused, and could handle > > > > the expansion IF WE CAN FIND THE COMPONENTS... > > > > > > > > Thanks for the help. By the by, I've been looking for a toaster FAQ, is > > > > there one? > > > > > > > > ----------- > > > > Fujitsu - Nexion, St. Louis, MO > > > > Jay Orr (314) 579-6517 > > > > > > > > > > > > > > > > > > ----------- > > Fujitsu - Nexion, St. Louis, MO > > Jay Orr (314) 579-6517 > > > > > > ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

4 4

Re: Hardware for F330
by sirbruce＠ix.netcom.com 01 May '99

01 May '99

On 04/30/99 18:53:15 you wrote: > >On Fri, Apr 30, 1999 at 12:34:30PM -0500, Jay Orr wrote: >> And what's with your CPU speed? > >Luke has bumped up his CPU speed using an overdrive processor. This is >pretty simple to do, but NetApp claims that bus bandwidth, not CPU speed is >the limiting factor in the F330/230/220 series of filers. It's not simply a claim; it's true. >NetApp says that >there is no benefit to an overdrive, I don't think they would claim _no_ benefit. Just that the benefit will be very minor in the majority of cases, and not worth the extra cost. Plus, since there are all sorts of reliability and timing issues that are changed by changing the processor speed, there configuration is likely to be less reliable. That being said, if your environment frequently experiences an NFS ops mix that is CPU-heavy and bus-light, a faster CPU could provide slightly better response times and peak operations. But this is a very unlikely situation. I suppose RAID reconstruction in the event of failure is probably noticeably faster, although you're probably hitting limits on the bus bandwidth as well once you exceed 90-120 MHz. The extra CPU might help the filer be a little more responsive to regular ops during reconstruction. >and I suspect that support is likely to >blame it for any trouble you have in the future. I suspect you're right. I'm surprised there haven't been any firmware problems already. Bruce

1 0

netapp meets bugtraq. again.
by fubar＠mathworks.com 01 May '99

01 May '99

Ok, so I don't have the docs handy.. but if you have an "-access" options, it just seems kinda intuitive to me that you might actually *USE IT*. But maybe it's just me. ------- Start of forwarded message (RFC 934 encapsulation) ------- From: pashdown(a)XMISSION.COM (Pete Ashdown) Subject: Network Appliance NFS filer root hole Date: 28 Apr 1999 15:58:45 -0400 Organization: Bugtraq List Message-ID: <199904281658.KAA14944(a)slack.xmission.com> Reply-To: Pete Ashdown <pashdown(a)XMISSION.COM> For Network Appliance NFS filer release: NetApp Release 5.2.1: Thu Dec 31 12:56:45 PST 1998 Following "Example 1" on page 136 of the "System Administrator's Guide" for the Network Appliance results in a gaping hole. In this example, they explain that "the following line exports the root directory of the default filter volume to the administration host with root privileges." /vol/vol0 -root=adminhost This is all fine and good, but it also exports to the WORLD with root privileges. You have to specify either "-access", or "-rw", or "-ro" in addition to "-root" for this not to happen. When I mentioned this to my NetApp SE, I was met with quizzical looks, but no code-update or patch. Thusly, I sent it to bugtraq. ------- End -------

4 6

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