....
a big problems that is your

if I were you, I would audit the cifs protocol on the filer with some options cifs.audit* in order to know when  and from who (!) the filer would receive some kind of "delete this folder" command
what is your DOT version ?
I also noticed you work with XP. does any client (or the most part of) work with it ?

for reference : (you would try this options with netapp support)
<<
nac3> options cifs
cifs.audit.autosave.file.extension           
cifs.audit.autosave.file.limit 0         
cifs.audit.autosave.onsize.enable off       
cifs.audit.autosave.onsize.threshold           
cifs.audit.autosave.ontime.enable off       
cifs.audit.autosave.ontime.interval           
cifs.audit.enable            off       
cifs.audit.file_access_events.enable on        
cifs.audit.logon_events.enable on        
cifs.audit.logsize           524288    
cifs.audit.saveas            /etc/log/adtlog.evt
>>

il va te falloir du courage

Steve Evans wrote:
I'm sure it wasn't deleted by a user because this happens about once a
month to different people.  Before we migrated to the NetApp filer it
never happened so I doubt it's user error.

We have a CIFS license only, sorry can't check it through NFS.

The llevinson folder is our CFO who's been here for 15+ years but most
importantly her folder was migrated from the old file server last summer
with everyone else.  So it's defiantly not newer than any of the
snapshots. 


Steve Evans
SDSU Foundation
(619) 594-0653 


-----Original Message-----
From: Stephane Bentebba [mailto:stephane.bentebba@fps.fr] 
Sent: Friday, May 02, 2003 8:53 AM
Cc: toasters@mathworks.com

snapshot takes your filesystem state at a moment, what about a directory
you create after the snapshot had been taken ?

if you go into this directory, (after had mapped the cifs shares)
obviously, this directory was not previously catched in a snapshot

for this, the normal operation of the filer is to display snapshot as
files

as I can see your image, I would guess that this directory llevinson was
created after the nightly.3 snapshot was taken and before nightly.2 was
taken.

so, if this is true, then there is no problem with your filer

if it is wrong, then there should be a serious problem with the filer
can you check this snapshot state from any other machines ? (try from
unix)

also, are you absolutly really sure that the directory was not delete
then recreate (by any user or any application) that would explain this
situation

hth

Steve Evans wrote:

  
Look at this screen shot. It's of a users folders snapshot directory.
http://planetevans.com/netapp/snapshot.jpg

You can see that all the snapshots after nightly.3 are regular files.
When I double click on them they want me to choose a program to open it
    

  
with.

This is of the directory \\filer\finance\llevinson\~snapshot

If I go through \\filer\finance\~snapshot\<snapshot>\llevinson I can 
access everything just fine.

Also several days ago (the day that lines up with the bad snapshots) 
everything from \\filer\finance\llevinson (the live data) disappeared 
and we had to pull it from the last snapshot (hourly.0 which was good)

I'm working with NetApp right now.  Originally I had 6.1.3R2 and they 
said there were several CIFS issues with that version of ONTAP, so I 
upgraded to 6.3.1R1.  Unfortunately (or fortunately) it only happens 
once a month or less.  Has anyone seen anything like this before?

Steve Evans
SDSU Foundation
(619) 594-0653


 

    

--
-- jetez un oeil ici http://www.sensiva.com/ --
--  have a look here http://www.sensiva.com/ --






  

-- 
-- jetez un oeil ici http://www.sensiva.com/ --
--  have a look here http://www.sensiva.com/ --