> >Right now I am watching a dump:
> >[EMAIL PROTECTED] ~] dump -b64 -5Lau /home
> > DUMP: Connection to big.sibptus.tomsk.ru established.
> > DUMP: Date of this level 5 dump: Sat Aug 18 14:02:16 2007
> > DUMP: Date of last level 0 dump: Sun Aug 12 11:10:56 2007
> > DUMP: Dumping snapshot of /dev/ad0s2f (/home) to /dev/nsa0 on host big
> > DUMP: mapping (Pass I) [regular files]
> > DUMP: mapping (Pass II) [directories]
> > DUMP: estimated 3249348 tape blocks.
> >at the same moment:
> >[EMAIL PROTECTED] ~] snapinfo -v /home
> >/dev/ad0s2f mounted on /home
> > no snapshots found
> >[EMAIL PROTECTED] ~] ll /home/.snap/
> >total 0
> >[EMAIL PROTECTED] ~]
> >Is this normal? Does it mean that dump is not really dumping a
> >snapshot though it says it is?
> man dump (the section regarding -L) says
> "The snapshot is unlinked as soon as the dump starts, and is thus
This explains why there is no visible snapshot file in /home/.snap/
However, I thought that snapinfo should be aware even of unlinked
snapshots. Just like "mdconfig -l" still shows the backingstore file
even if it has been unlinked.
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"