ckandreou wrote:
> 
> Craig Barratt wrote:
>> ckandreou writes:
>>
>>
>>> Executing: /usr/local/BackupPC/bin/BackupPC_archiveHost 
>>> /usr/local/BackupPC/bin/BackupPC_tarCreate /usr/bin/split  ccdev10 348 
>>> /usr/bin/bzip2 .bz2 0000000 /dev/sa0  *
>>> Xfer PIDs are now 81631
>>> Writing tar archive for host ccdev10, backup #348 to /dev/sa0
>>> Got unknown type 9 for ./etc/svc/volatile/repository_door
>>> Got unknown type 9 for ./etc/sysevent/piclevent_door
>>> Got unknown type 9 for ./etc/sysevent/sysevent_door
>>> Got unknown type 9 for ./etc/sysevent/syseventconfd_event_channel/reg_door
>>> Got unknown type 9 for ./etc/sysevent/devfsadm_event_channel/1
>>> Got unknown type 9 for ./etc/sysevent/devfsadm_event_channel/reg_door
>>> Got unknown type 8 for ./var/tmp/mapping-emsadmcm
>>> Got unknown type 8 for ./var/tmp/mapping-labadm
>>> Got unknown type 8 for ./var/tmp/mapping-tuxadm
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-410c-0-47179a0e6e3ec
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4118-0-471789141e575
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-411a-0-4717d9ce8b842
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-411c-0-4717a69c1cd75
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4134-0-4717985238546
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4138-0-4717b4d7c9a46
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-413a-0-4717b144d08af
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-413d-0-4717b144d9334
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4141-0-4717ada15334a
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4145-0-4717c89a28c3a
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-414a-0-4717832ec1c7f
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-414c-0-47179fbfd400a
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-414e-0-47179c0c44b35
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-4150-0-4717ac2fb4dba
>>> Got unknown type 8 for ./var/tmp/orbit-labadm/linc-827-0-49b6a0fe2885a
>>> Got unknown type 8 for ./var/run/.inetd.uds
>>> Got unknown type 9 for ./var/run/kcfd_door
>>> Got unknown type 9 for ./var/run/name_service_door
>>> Got unknown type 9 for ./var/run/picld_door
>>> Got unknown type 9 for ./var/run/syslog_door
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/1
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/10
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/11
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/12
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/2
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/3
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/4
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/5
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/6
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/7
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/8
>>> Got unknown type 9 for ./var/run/sysevent_channels/syseventd_channel/9
>>> Got unknown type 9 for 
>>> ./var/run/sysevent_channels/syseventd_channel/reg_door
>>> Got unknown type 9 for ./var/run/rpc_door/rpc_100169.1
>>>
>> Type 8 are socket files and type 9 is unknown (Solaris door files).
>> These are transient files that don't need to be backed up since they
>> can't be restored - they are created by the applications that need
>> them.
>>
>> The warning messages are benign - they simply mean that those files
>> are being skipped.
>>
>> Craig
> 
> 
> Thanks for the info.  I continue to get the same message. BackUpPC web 
> interface for "tape_archive" indicates that the backup failed, with the error 
> message the same as above,
> 
> When I issue the command  
> #tar tvf /dev/sa0  I get a listing of directories on the tape. I am not able 
> to see the contents within directories. For example. 
> #tar tvf /dev/sa0/home 
> I get an an error back

That's the wrong way to ask for something from the tape.  The first 
command should give you the whole listing of files and directories of 
the next tape entry.

> My question then is :
>    Even though that I get the error message on tape_archive web page, I 
> should ignore and with the assumption the tape has the archived contents?
> 
> Thanks in advance

Those 'unknown type' errors aren't responsible for the rest of the 
problem you originally reported:

 > bzip2: I/O or other error, bailing out.  Possible reason follows.
 > bzip2: Inappropriate ioctl for device
 >      Input file = (stdin), output file = (stdout)
 > Executing: /bin/csh -cf -cf 
/usr/local/BackupPC/bin/BackupPC_tarCreate -t -h ccdev10 -n 348 -s \* . 
| /usr/bin/bzip2 >> /dev/sa0
 > Error: /usr/local/BackupPC/bin/BackupPC_tarCreate, compress or split 
failed
 > Archive failed: Error: /usr/local/BackupPC/bin/BackupPC_tarCreate, 
compress or split failed

That part has to do with problems writing to the tape, possibly related 
to the block size - but it could just be that the last block wasn't 
padded out.


-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/