> the response were: > check tag PC=12336 w"/dev/sdC0/fscache"(0) tag/path=<badtag> /15.....36: > expected <nil> > and then returned back to the selection prompt. > > why tag/path in fscache is the problem in recovering? > they must be cleaned based on fsworm.
on the real file server, the command is
recover main
note the fs name. and one would expect a stream of
"dump %lld is good; %lld next\n" messages.
peeking at the source, i would expect similar from
cwfs.
- erik
