Tino,

> The downside of this is that I cannot easily peek into a backup on
> command line any more. :-( It's been very helpful to quickly figure out
> which files have bee backed up (e.g. to determine unneccessarily backed
> up stuff). Now I'll lose that capability and have to resort to web page
> clicking...

That's true.  Maybe I could add an "ls" facility?

> or us that FUSE FS part of the release?

Not currently planned, but it's a good idea.  The new set up will
make FUSE more faithful (in particular, getting nlinks right).

> Ok, so how do you implement orphan deletion - how are files detected
> which are not needed in pool any more?

That was described in my other posts.  Reference counting is done

> Note that this will blow up if somebody is using ReiserFS since that
> does not have real inode numbers, but invents them on access. It might
> be impossible to implement a sanity check to detect that case...

It shouldn't matter - see below.

> > Inodes attributes (for client hardlinks) are stored in an additional
> > tree of directories below each backup directory.  The attribute hash key
> > is the inode number.  128 directories are used to store up to 128 attrib
> > files.  The lower 14 bits of the inode number are used to determine the
> > directory (bits 13 to 7) and the file name within that directory
> > (bits 0-6).  These two 7 bit values are encoded in hex (XX and YY):
> > 
> >     $TOPDIR/pc/HOST/NNN/inode/XX/attribYY.
> > 
> > where NNN is the backup number.
> 
> Oh, or do you mean: The inode number is made up by BackupPC? Then please
> don't call it inode number, but rather hardlink-ID or so.

Right.  It's made by BackupPC on the server side.  But it would be
the inode number exposed by FUSE, so I'd like to call it that.

Craig

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to