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

[Jon N. B. <ma...@nv...>]

	Yeah.  I did use the -f option.  I think you may be right about
the file contents though.  The file in question was generated by some
simulation software we use, and after some digging, I found that it is a
standard naming convention for the files it generates.  I am chalking this
one up to a fluke, but appreciate the helpful diagnostic tips.  I am sure
they will come in handy in the future.

Thanks again.

~Jon.




On Fri, 14 May 2004, Stelian Pop wrote:

> 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.
> 

-- 



*******************************

 Jon N. Brelie
 Information Systems Manager
 NVE Corp.

*******************************