Re: Error 0

Daniel Grund <[email protected]> wrote:

> Hi!
>
> I call star-1.5a87 like this:
>
> star c -silent -no-statistics -M -multivol new-volume-script="/usr/local/bin/yacdbak.cdrecord root 1 noburn" VOLHDR="FreeBSD 7.0-RC1 2008-01-08 03:20+0100 Level 1" -dump level=1 -dumpmeta tardumps=/var/db/yacdbak/root.snapshots -wtardumps -p -match-tree -tsize=66534 -no-fifo -nodump artype=e xustar -sparse file=/var/tmp/yacdbak.image fs-name=/ dumpdate=/var/tmp/timestamp -dodesc -not .snap -not lost+found -C=/.snap/backupmount .

First some notes:


-	You are not using star correctly.

	-	You use two -not arguments where one is sufficient

	-	You use -not but no related pattern option

-	it is _highly_ recommended _not_ to use options to tell star 
	to scan only parts of the filesystem if in incremental mode
	as this could result in inconsistent archives.

-	You found a bug: star should not allow you to specify more than
	one start directory.

-	I recommend to first clean up the command line and check whether
	the incorrect command line is the reason for the problem.


> The output is:
>
> star: Error 0. Error moving extended header '././@PaxHeader'.
> Segmentation fault
>
>
> What does that error message mean?

This cannot really happen as it would imply that star tries to create an 
extended header with size < 0.

Without debugging, I cannot help. I need the information on what star
tries to archive with size < 0 and why star tries to do this.



> I've already tried to unlimit core file size and to recompile with: 
> smake COPTX=-g LDOPTX=-g
>
> star still does not dump core.

Did you install star suid root and not call it as root?

You will get help from the kernel people first. After the kernel is able again 
to create a core file. 

Jörg

-- 
 EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
       [email protected]                (uni)  
       [email protected]     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily