On Mon, Nov 24, 2003 at 02:57:56PM -0500, Jean-Francois Malouin wrote: > * Jon LaBadie <[EMAIL PROTECTED]> [20031124 14:15]: > > On Mon, Nov 24, 2003 at 11:59:41AM -0500, Jean-Francois Malouin wrote: > > > Hi, > > > > > > I'm having strange problems with the include thingy in an > > > entry in my disklist: > > > > > > bullcalf /data/nihpd/nihpd1/data/assembly_0 /data/nihpd/nihpd1/data/assembly { > > > include "./0*" > > > exclude "./[1-9]*" > > > high-tar > > > } 1 > > > > > > Looking at what got written to tape (a full backup) I see only > > > directories (no files at all!), and even from the exclude part...ie > > > just the hierarchy structure of /data/nihpd/nihpd1/data/assembly all > > > the way down... > > > > > > > Don't know about your bad backup, but in your DLE you should not > > have both the include and THAT exclude. I.e., the include will > > automatically drop any toplevel dir that does not match "./0*". > > That is want I want! > All subdirs in there have a pattern [0-9]\{6\} , ie, 6 digits. There > are other subdirs but there are not to be backed up. You see, my > problem is that /data/nihpd/nihpd1/data/assembly can contains 100's of > GB and I'm using 4 LTO tape drives, so I have to split that thing in > small chuncks... > > Eventually I'll have 10 DLE's, those starting with ./0* ./1* ... > you get the picture. > > > > > I think the only valid exclude usage would be for things under > > the 0* directories. For example 'exclude "./0*/tmp"'. Though > > I must admit I've never tried that combination. > > Have a look at my other post in this thread. The index file for that > DLE doesn't start with "./" but with "/"...Is my gnutar at fault here? > I thought that v1.13.25 had good karma...
No, the index should start with "/", but it should not start with "/-/" unless you have a top-level directory named "-". -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)