On Thu, May 17, 2012 at 03:17:32PM +0300, Toomas Aas wrote: > Thu, 17 May 2012 kirjutas "Christopher X. Candreva" <[email protected]>: > > >One file system means just that. Unless /storage/lists is a separate > >partition mounted at that point, /storage is one file system, as you say > >above. You need the explicit exclude. > > That was exactly my point. Until day before yesterday, > /storage/lists was just a subdirectory on /storage filesystem. Then > I created a new filesystem, moved the contents of /storage/lists to > that filesystem and mounted it under /storage/lists. So it is a > separate filesystem, but it was still backed up as part of /storage. > > $ df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 254546 212474 55% / > devfs 1 1 0 100% /dev > /dev/md0 31470 7764 21190 27% /phpramdisk > /dev/da0s1f 8119342 4804070 2665726 64% /usr > /dev/da0s1e 4058062 2732312 1001106 73% /var > /dev/da0s1d 126702 22014 94552 19% /var/tmp > /dev/da0s2.journal 54576856 17684592 32526116 35% /storage > devfs 1 1 0 100% /var/named/dev > /dev/da1s1a 34425972 9515844 22156052 30% /storage/lists >
Grasping at straws, any chance you also left the original files in the directory "lists" after copying them to the new partition. After mounting the new partition on /storage/lists they would be "masked" and would not be accessible using file system semantics. But dump-like programs could still see, and back-up, the masked files. Tar should be using file system semantics, but like I said, "grasping". jl -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
