Re: [Gnu-arch-users] Corrupt pristine tree

[John Meacham]

On Mon, Mar 15, 2004 at 08:01:29AM -0500, Aaron Bentley wrote:
> Peter Conrad wrote:
> 
> >Hi,
> >
> >On Sat, Mar 13, 2004 at 06:26:29PM -0500, Aaron Bentley wrote:
> > 
> >
> >>C. R. Oldham wrote:
> >>   
> >>
> >>>I upgraded my Linux box and moved my home directory onto a new disk.  I
> >>>also upgraded to ext3.  Now on my trees I get
> >>>
> >>>corrupt pristine (failed inode signature validation)
> >>>
> >>>Whenever I try to commit.  The message recommends "You should remove
> >>>this pristine from your tree."  How do I do that?  
> >>>     
> >>>
> >>"rm -Rf {arch}/++pristine-trees" in the tree root
> >>   
> >>
> >
> >Is there any particular reason why tla doesn't do that by itself? I'm
> >getting that message fairly often (on a device mounted via cryptoloop)
> >and I find it pretty annoying.
> >
> tla doesn't remove corrupt pristines automatically because there should 
> never be any.
> 
> Corrupt pristines are serious; they usually indicate a configuration 
> problem or a problem with the way we check for corruption.  I suspect in 
> your case, your device number is changing, and that's not currently 
> permitted.  Covering up the problem would be counter-productive.

I also have to regularly delete the ++pristine-trees dir. I know why,
(funky distributed filesystem setup) but it is still anoying. 

Why not use a cryptographic hash? that seems like a much nicer way to
verify the integrity of the pristine trees and doesn't suffer from the
device/inode issues that people have with any slightly unusual setup.
plus, they are a lot more trustworthy than device/inode numbers with the
multitude of filesystems modern unix systems support.
        John


-- 
---------------------------------------------------------------------------
John Meacham - California Institute of Technology, Alum. - address@hidden
---------------------------------------------------------------------------