Hi! I'm still having these strange "ufsdump return 3" errors being reported
for one drive. It isn't accounting restrictions -- I checked that. It
isn't compression -- turning that off also didn't help (it was server side
compression anyways...)
So, in order to check from the lowest level, I just went to the machine,
su'd to amanda, and ran:
/usr/sbin/ufsdump 2f - /dev/rdsk/c0t2d0s4 > /dev/null
This ran completely correctly. So now, I'm thinking that it must be the
index creation that's causing the problem. The problem is, I don't exactly
understand how the index is being created -- I know it has something to do
with ufsrestore -- but I don't exactly understand how to call dump/restore
as it is being called by sendbackup.
What is the command that I need to use to run the dump|restore|sed manually?
Or, better yet, how do I get this info from the sendbackup*debug file?
(I've included what I think are the relevent lines below)
Thanks,
Ricky
-----------------------------------------------------------------
sendbackup: spawning /usr/sbin/ufsdump in pipeline
sendbackup: argument list: dump 2usf 1048576 - /dev/rdsk/c0t2d0s4
sendbackup: started index creator: "/usr/sbin/ufsrestore -tvf - 2>&1 | sed
-e '
s/^leaf[ ]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'"
-----------------------------------------------------------------
-----------------------------------------------------
Richard Morse System Administrator
MGH Biostatistics Center 50 Staniford St. Rm 560
[EMAIL PROTECTED] 617/724-9830
