Re: [Dump-users] Dump hangs on specific inode.

[Stelian P. <st...@po...>]

On Thu, May 13, 2004 at 02:37:43PM -0500, Jon N. Brelie wrote:

> 
> 	Thanks.  Turns out the problem file was a 67MB .csv file with two
> "#"'s in the path.  I cleaned it up and the dump performed flawlessly.
> 
> ~jon.

Strange, two '#' in the pathname is not a problem to dump:
	# touch /tmp/aaa##aaa
	# dump 1uf tmp.1 /tmp
	... (no problem)

I'd say the problem was more in the file contents than in its
name. But, since I suppose you don't have a copy of that file
(and anyway a logical copy of the file contents would probably 
show no problem, the problem probably was in the inode metadata),
it is probably to late to try to find out what happened. 

Just for the record, you say you had checked the filesystem. 
Did you use the -f flag when you ran fsck ?

Stelian.
-- 
Stelian Pop <st...@po...>