toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

Start a nNew thread

Net boot Linux SUSE 7.2 from a filer F840 or F230
by Oye 17 Sep '01

17 Sep '01

Does anyone have any idea on how to set up net boot of Suse Linux 7.2 or RedHat on a filer F840 or F230? Thanks, Oye

1 0

Re: Networker "no output" error?
by mcope＠isisph.com 17 Sep '01

17 Sep '01

Try setting the timeout value in the client setup higher - from 30 to 60. I've seen volumes with thousands of small files timeout while Networker "crawled" the directory structure. Bumping the timeout value has ensured successful/complete backups since then. Although I don't recall ever getting the 'no output' error. Michael Cope UNIX/Linux Systems Administrator Isis Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH! On 9/17/2001 6:46:51 AM, "Weng-Kiam Lim" <wklim(a)rand.com>@mathworks.com wrote: > Had been experiencing on unsuccessful saveset since last week, with > "no > output error". It only fails on one particular volume while other > volumes > are fine. Any hints? > > --- Unsuccessful Save Sets --- > > * netapp1:/vol/vol2/pdm 1 retry attempted > * netapp1:/vol/vol2/pdm ! no output > > --- Successful Save Sets --- > > * netapp1:/vol/vol0/etc Warning: unsynchronized client clock detected > netapp1: /vol/vol0/etc level=incr 547 KB 00:00:31 14 files > netapp1: /vol/vol0/db level=incr 537 MB 00:12:17 929 files > server5: /vol5/netapp1 level=9, 1.4 MB > 00:00:14 4 > files > > Regards, > wk >

1 0

Networker "no output" error?
by Weng-Kiam Lim 17 Sep '01

17 Sep '01

Had been experiencing on unsuccessful saveset since last week, with "no output error". It only fails on one particular volume while other volumes are fine. Any hints? --- Unsuccessful Save Sets --- * netapp1:/vol/vol2/pdm 1 retry attempted * netapp1:/vol/vol2/pdm ! no output --- Successful Save Sets --- * netapp1:/vol/vol0/etc Warning: unsynchronized client clock detected netapp1: /vol/vol0/etc level=incr 547 KB 00:00:31 14 files netapp1: /vol/vol0/db level=incr 537 MB 00:12:17 929 files server5: /vol5/netapp1 level=9, 1.4 MB 00:00:14 4 files Regards, wk

1 0

RE: Problem setting access rights for files on a CIFS share progr amatically
by Muhlestein, Mark 15 Sep '01

15 Sep '01

This is bug 50667. Contact support for the fix. Mark -----Original Message----- From: Michael.Kaercher(a)genorz.de [mailto:Michael.Kaercher@genorz.de] Sent: Friday, September 14, 2001 5:39 AM To: toasters(a)mathworks.com Subject: Problem setting access rights for files on a CIFS share programatically Are you an NT administrator? Have you tried to set up user's rights from a script? If so: Please read on! We have implemented a tool to create user accounts for an NT domain. This tools also creates the user's home, group, and profile directories. Of course, these directories must be properly protected from unauthorized access. To this end, we are using Microsoft's ADsSecurity package (found in the ASDI25SDK resource kit). With the graphical tools for setting permissions on a remote file or directory we can modify ACLs on the filer. However using ADSI doesn't work on the filer. (The filer is running 5.3.7R2; ADSI is version 2.5)) We have found that the following (trivial) example program taken from the Microsoft documentation works perfectly well from an NT4 domain controller to another NT4 domain controller, an NT 4 member server, a Windows 2000 member server (of course, all belonging to the same domain), BUT: Setting the new DACL with a NTFS share on the filer does not work (the existing rights are correctly displayed, but setting just doesn't work - without returning an error code!). Const ADS_RIGHT_GENERIC_READ = &H80000000 Const ADS_RIGHT_GENERIC_EXECUTE = &H20000000 Const ADS_ACETYPE_ACCESS_ALLOWED = 0 Set sec = CreateObject("ADsSecurity") Set sd = sec.GetSecurityDescriptor("FILE://\\SERVER\DIR\FILE.TST") Set dacl = sd.DiscretionaryAcl '-- Show the ACEs in the DACL ---- For Each ace In dacl wscript.echo ace.Trustee wscript.echo ace.AccessMask wscript.echo ace.AceType Next '--- Add a new ACE so that the user can read/execute this file Set ace = CreateObject("AccessControlEntry") ace.Trustee = "DOMAIN\user" ace.AccessMask = ADS_RIGHT_GENERIC_READ Or ADS_RIGHT_GENERIC_EXECUTE ace.AceType = ADS_ACETYPE_ACCESS_ALLOWED dacl.AddAce ace sd.DiscretionaryAcl = dacl sec.SetSecurityDescriptor sd BTW: Using the Win32::Perms perl module shows the same behaviour! Thanks, Michael Kärcher

1 0

RE: Problem setting access rights for files on a CIFS share progr amatically
by Nail, Larry 14 Sep '01

14 Sep '01

Do it every day: File level, we use XCACLS. xcacls \\filer01\wts\%1 /c /g administrators:f %1:c "domain\pc gurus":c system:f /t /y xcacls \\filer01\profiles\%1 /c /g administrators:f %1:F "domain\pc gurus":c system:f /t /y Share level, I use a combination of tools between RMTSHARE & "cifs shares access" rsh filer01 cifs shares -add %1 /vol/vol0/wts/%1 rsh filer01 cifs shares -change %1 -comment \"%1 WTS Home Directory\" rmtshare \\filer\%1 /grant domain\%1:c /grant "pc gurus":c /grant vette01\administrators:f /remove everyone Also note that versions of Ontap less than 6 don't support NTFS5 permissions. -----Original Message----- From: Michael.Kaercher(a)genorz.de [mailto:Michael.Kaercher@genorz.de] Sent: Friday, September 14, 2001 7:39 AM To: toasters(a)mathworks.com Subject: Problem setting access rights for files on a CIFS share programatically Are you an NT administrator? Have you tried to set up user's rights from a script? If so: Please read on! We have implemented a tool to create user accounts for an NT domain. This tools also creates the user's home, group, and profile directories. Of course, these directories must be properly protected from unauthorized access. To this end, we are using Microsoft's ADsSecurity package (found in the ASDI25SDK resource kit). With the graphical tools for setting permissions on a remote file or directory we can modify ACLs on the filer. However using ADSI doesn't work on the filer. (The filer is running 5.3.7R2; ADSI is version 2.5)) We have found that the following (trivial) example program taken from the Microsoft documentation works perfectly well from an NT4 domain controller to another NT4 domain controller, an NT 4 member server, a Windows 2000 member server (of course, all belonging to the same domain), BUT: Setting the new DACL with a NTFS share on the filer does not work (the existing rights are correctly displayed, but setting just doesn't work - without returning an error code!). Const ADS_RIGHT_GENERIC_READ = &H80000000 Const ADS_RIGHT_GENERIC_EXECUTE = &H20000000 Const ADS_ACETYPE_ACCESS_ALLOWED = 0 Set sec = CreateObject("ADsSecurity") Set sd = sec.GetSecurityDescriptor("FILE://\\SERVER\DIR\FILE.TST") Set dacl = sd.DiscretionaryAcl '-- Show the ACEs in the DACL ---- For Each ace In dacl wscript.echo ace.Trustee wscript.echo ace.AccessMask wscript.echo ace.AceType Next '--- Add a new ACE so that the user can read/execute this file Set ace = CreateObject("AccessControlEntry") ace.Trustee = "DOMAIN\user" ace.AccessMask = ADS_RIGHT_GENERIC_READ Or ADS_RIGHT_GENERIC_EXECUTE ace.AceType = ADS_ACETYPE_ACCESS_ALLOWED dacl.AddAce ace sd.DiscretionaryAcl = dacl sec.SetSecurityDescriptor sd BTW: Using the Win32::Perms perl module shows the same behaviour! Thanks, Michael Kärcher

1 0

Problem setting access rights for files on a CIFS share programatically
by Michael.Kaercher＠genorz.de 14 Sep '01

14 Sep '01

Are you an NT administrator? Have you tried to set up user's rights from a script? If so: Please read on! We have implemented a tool to create user accounts for an NT domain. This tools also creates the user's home, group, and profile directories. Of course, these directories must be properly protected from unauthorized access. To this end, we are using Microsoft's ADsSecurity package (found in the ASDI25SDK resource kit). With the graphical tools for setting permissions on a remote file or directory we can modify ACLs on the filer. However using ADSI doesn't work on the filer. (The filer is running 5.3.7R2; ADSI is version 2.5)) We have found that the following (trivial) example program taken from the Microsoft documentation works perfectly well from an NT4 domain controller to another NT4 domain controller, an NT 4 member server, a Windows 2000 member server (of course, all belonging to the same domain), BUT: Setting the new DACL with a NTFS share on the filer does not work (the existing rights are correctly displayed, but setting just doesn't work - without returning an error code!). Const ADS_RIGHT_GENERIC_READ = &H80000000 Const ADS_RIGHT_GENERIC_EXECUTE = &H20000000 Const ADS_ACETYPE_ACCESS_ALLOWED = 0 Set sec = CreateObject("ADsSecurity") Set sd = sec.GetSecurityDescriptor("FILE://\\SERVER\DIR\FILE.TST") Set dacl = sd.DiscretionaryAcl '-- Show the ACEs in the DACL ---- For Each ace In dacl wscript.echo ace.Trustee wscript.echo ace.AccessMask wscript.echo ace.AceType Next '--- Add a new ACE so that the user can read/execute this file Set ace = CreateObject("AccessControlEntry") ace.Trustee = "DOMAIN\user" ace.AccessMask = ADS_RIGHT_GENERIC_READ Or ADS_RIGHT_GENERIC_EXECUTE ace.AceType = ADS_ACETYPE_ACCESS_ALLOWED dacl.AddAce ace sd.DiscretionaryAcl = dacl sec.SetSecurityDescriptor sd BTW: Using the Win32::Perms perl module shows the same behaviour! Thanks, Michael Kärcher

1 0

NBU sets filer attached drive down
by Hannes Herret 14 Sep '01

14 Sep '01

anyone knows this behaviour? we're running 6.1.1 on F740 w/ an direct attached ATL L200 (1 Drive) Backupserver is an E450 w/ Solaris 8 and NBU 3.4 DC. NBU always sets the drive in the L200 down. Also i'm upping the drive it lasts bout 30 sec. till the drive is down again. no ndmp backup is possible. a started dump from the filer is working fine. the nbu config seems ok. authorization works, robtest and tldtest from the nbu-server on the L200 also works. could this be a problem cause of missing /etc/dumpdates? who can read an "ndmpd debug 50"-output? thx h -- ------------------------------------------------------------------- Hannes Herret IT-Service / Storage phone : +43 (1) 60 126-34 Bacher Systems EDV GmbH fax : +43 (1) 60 126-555 Wienerbergstr. 11B mailto:hh@bacher.at A-1101 Wien, Austria www : http://www.bacher.at/ Europe

1 0

RAID checksum revert process
by Jeffrey Krueger 14 Sep '01

14 Sep '01

Okay, after creating 16 volumes on 6.1 machines for snapmirror from 5.3 machines, can I say that there really needs to be a "vol create" option to say "-checksums old". It has been a pain to create all these volumes just to wait for checksum reversion. Installing the filer on 5.3 and upgrading after the initial snapmirror isn't an option either - the destination already has other production volumes - besides, thats a kludge. Beyond that, has anyone else noticed that checksum reversions seem to be "single tasked"? For instance: Thu Sep 13 15:46:17 PDT [reactor: worker_thread:error]: A snapmirror transfer from vol0 to vol0 has found that the two volumes have differing checksum states. Data ONTAP is aborting the snapmirror transfer and reverting the checksum state for the destination volume vol0. After Data ONTAP displays a message showing the revert is complete, you can retry the snapmirror transfer. You can use the vol status -c command to see the progress of the reversion. Thu Sep 13 15:46:31 PDT [reactor: worker_thread:error]: A snapmirror transfer from vol0 to vol2 has found that the two volumes have differing checksum states. Data ONTAP is aborting the snapmirror transfer and reverting the checksum state for the destination volume vol2. After Data ONTAP displays a message showing the revert is complete, you can retry the snapmirror transfer. You can use the vol status -c command to see the progress of the reversion. # rsh reactor vol status -c vol0 Volume Checksum style Checksum status vol0 zoned Checksums reverting (98% done) # rsh reactor vol status -c vol2 Volume Checksum style Checksum status vol2 zoned Checksums reverting (0% done) Just an FYI for other folks - this takes a few hours to complete for each volume when the volumes are ~500GB. -- Jeff

1 0

RE: Tape drives revisited (I'm sure...)
by Ting, James 13 Sep '01

13 Sep '01

Jeff http://now.netapp.com/NOW/knowledge/docs/hardware/syscfg/scdot611/index.htm IBM LTO is supported in 6.1.1 Jim -----Original Message----- From: Jeff Kennedy [mailto:jlkennedy@amcc.com] Sent: Thursday, September 13, 2001 3:46 PM To: NDMP List Subject: Tape drives revisited (I'm sure...) According to NetApp, the only dlt-type versions supported are 7k and 8k, no SDLT or LTO. Who out there is using these (particularly SDLT) and how did you get it to work? And do you have support problems? Thanks. -- ===================== Jeff Kennedy Unix Administrator AMCC jlkennedy(a)amcc.com

1 0

Tape drives revisited (I'm sure...)
by Jeff Kennedy 13 Sep '01

13 Sep '01

According to NetApp, the only dlt-type versions supported are 7k and 8k, no SDLT or LTO. Who out there is using these (particularly SDLT) and how did you get it to work? And do you have support problems? Thanks. -- ===================== Jeff Kennedy Unix Administrator AMCC jlkennedy(a)amcc.com

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