savevg stuck on file

[MoeTr]

Hi I'm running a savevg cmd and it seems to be hung up on a file.
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)..............................
4322124 of 7603568 files (56%)............................

I found this link with someone with a similar problem and it turned out to be a failing disk -

http://www.experts-exchange.com/OS/Unix/Q_26759973.html.

I am getting no reporting from my SAN that there are any issues and I think its just a corrupt file.

Is there someway I can find out what file savevg is trying to backup before I kill the script. It's backing up to tape using this cmd:
/usr/bin/savevg -b $BLOCK_SIZE_512 -ixf /dev/rmt0.1 $VGNAME
Its part of a script that loops and stacks savevg's. I know the script is ok because it's been tested with smaller test filesystems and it already completed one savevg and is not hung on the 2nd loop.
This is production system, so I can't take it off line and do an fsck right now.
I would also prefer not to have to run savevg again with debug or more verbose options to try to find the problem file. I'm hoping I can find the file savevg is trying to touch with another method before killing this script and then maybe just exclude that file until I can take the FS down and do an fsck.

 

[TSch]

Hi MoeTr,

you could try "ps -ef" but I'm not sure whether this is going to list the file being processed or not.
Some processes do, some don't ...

Regards,
Thomas

 

[trifo]

Few tips, just shooting blindly:

* what happens when you create the backup into /dev/null ?

* you can run fsck on a running system, in "no modify" mode. This might help to filter out some fs problems.

* if the filename is known, you can use the /etc/exclude.<YOURVG> file to exclude it from the backup, but this is obvious, sorry.

* if you do not know which file is the problem, get the lsof command and run it against your backup process to see which files are kept open by it

--Trifo