• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 357
  • Last Modified:

Remove clone fileset failure when Unmounting fileset (umount error/failure)

Every night our backups run by doing the following:-
   1. Create clones of filesets
   2. Dump to tape using vdump
   3. Removing cloned filesets

This has been working fine until a couple of weeks ago when an additional 6Gb of space was added to the system. Now after the dumping to tape the fileset gets an error while trying to unmount. When I come into work the next day I unmount the fileset manually without an issue. Do you think that the vdump command may still be accessing the cloned fileset when the unmount is issued?

There is more than the require 5% free space on the system for cloning as can bee seen below:-

Filesystem                  1024-blocks          Used   Available Capacity  Mounted on
root_domain#root             131072         72482       52600    58%    /
/proc                                        0                0              0   100%    /proc
usr_domain#usr               716800        451229     249040    65%    /usr
oracle_domain#u01       24762368    17058083   7211552    71%    /u01

Machine is a HP Alpha running Tru64 Unix version 4.0.

Command that is causing the error:-
   /sbin/umount /u01_clone

Our backup log file. Errors are at the end:-
Exporting databases 23:05
Shutting down databases 23:25
Databases shut down 23:26
Creating clones of filesets 23:26
Finished creating clones of filesets 23:26
Restarting Oracle databases 23:26
Databases restarted 23:26
Dumping filesets to tape 23:26
Starting dumping to tape of u01_clone 23:26
Finished dumping to tape of u01_clone 01:15
Starting dumping to tape of root_clone 01:15
Finished dumping to tape of root_clone 01:16
Starting dumping to tape of usr_clone 01:16
Finished dumping to tape of usr_clone 01:25
Dumping filesets Finished 01:25
Removing Clones 01:25
Error unmounting clone fileset for u01 01:26
Error removing clone fileset for u01 01:26
Error removing the u01 clone directory 01:26
Finished removing Clones 01:26
0
craigstewart
Asked:
craigstewart
1 Solution
 
GnsCommented:
Dunno, perhaps some cronjob or similar has started... Assuming the extra 6 GiB to Oracle add some significant amount of time... Perhaps around 01:00:-)... Would prevent the clone and "magically" be gone in the morning.
If it was Linux I'd guess at slocate/updatedb (which do some more or less wellbehaved finds), but I've got _very_ limited True64 experience, so best if you look for yourself for possible "culprits":-).
One "troublesooting aid" could be to list the processes running just prior to the (failed) umount (just dump it to the log or to a separate file.... after all, it is a backup _script_, right?-)

HtH

-- Glenn
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now