On Tue, Oct 25, 2005 at 02:01:00PM +1000, tim shimmin wrote:
> tim shimmin wrote:
> > Hi Alex,
> >
> > Alexander Fisher wrote:
> >> Hi again.
> >>
> >> I've mounted my snapshots readonly, but I occasionally get warnings
> >> from xfsdump during the backups. I get two different types of
> >> warning.
> >>
> >> xfsdump: WARNING: failed to get bulkstat information for inode 10485897
> >> and
> >> xfsdump: WARNING: could not stat dirent .viminfo ino 10485896: No such
> >> file or directory: using null generation count in directory entry
> >>
> >> What's causing these? Can they be ignored?
They can be ignored - they are inodes that were previously unlinked,
but are still partially there on the snapshot volume, and visible
to the by-handle interfaces that xfsdump is using to extract all of
the inodes in the snapshot.
> >> Thanks,
> >> Alex
> >>
> >>
> Rereading.
> Hmmm, I wouldn't have expected these msgs from readonly snapshots.
>
We don't process the unlinked lists on a snapshot atm (no recovery
is done, as we don't leave a dirty log on the snapshot, on Linux).
We probably should be doing that, then these unlinked inodes would
not still be visible to bulkstat.
cheers.
--
Nathan
|