Pb with tape: processus fbackuprdr blocked

[malki_3]

Hello everybody
I'm sorry I dont find a time for assiging note for my mail of yesterday but I will doing it some time late..
I have another pb:
I hav etiw process blockef
#ps -ef|grep fback
root 16126 1 0 23:05:29 ? 5:56 /usr/sbin/fbackuprdr 270851 1 262144 fr_FR.iso88591 0 0
root 16125 1 0 23:05:29 ? 5:57 /usr/sbin/fbackuprdr 270851 0 262144 fr_FR.iso88591 0 0
Thos tow process oare used for what..? I think there for backup command but Im note sure
I tried to kill them but I can't(with -9 and -24)
I try to force offline my /dev/rmt/0m without sucess..
Have you any idea..?
Thanks for all

[Steve Steel]

Hi

read the man of fbackup and you will see that a certain number of reader processes can be defined in the config file.

These processes read concurrently from disk and send data to a writer program to put it on disk.

I suspect that they are blocked because the parent fbackup is looking for a second tape.

Kill off the fbackup process and the rest should follow eventually but a process will only die when it receives the signal and if waiting on reentrant i/o the kill is ignored.


Steve Steel

[harry d brown jr]

The Internals of fbackup


The fbackup utility consists of three executables: /usr/sbin/fbackup, /usr/sbin/fbackuprdr and /usr/sbin/fbackupwrtr. The fbackup executable is the main controlling program, and it invokes separate processes to do reading and writing during the backup. It is important to note that the reader and writer subprocesses of fbackup (/usr/sbin/fbackuprdr and /usr/sbin/fbackupwrtr) are invoked with their absolute pathnames, regardless of where the fbackup executable resides. Before testing any version of fbackup, make sure that all three updated executables are in the /usr/sbin directory, or they will not be correctly invoked.

Before the subprocesses do any real work, the main process reads the include and exclude options or graph file entries, and searches the included directories recursively to generate a complete listing of all files which are to be backed-up in this session. This list is completely generated and sorted before any backup data is written to tape.

At startup time, the fbackup process sets-up a shared-memory "ring" area and a "pad" area to communicate data and control between processes, and invokes one fbackupwrtr and one or more fbackuprdr processes. The ring is divided into multiple fbackup records that normally correspond to written output records (see the format section, and the Fast Search Mark exception below). The pad section contains groups of status structures which give either the status of each of the reader processes or the status of each of the records in the ring. The number of records stored simultaneously in the ring and the number of reader processes invoked are configurable in the "-c config" file optionally specified to fbackup.

After setting-up shared memory, and invoking the child processes, fbackup searches the included directories for files, and generates the complete list of files which are to be backed-up in this session. After recursively reading all directories, the filename list is sorted, and the excluded files are removed from the list.

The general flow of the data for each file is that the main process finds the next file to backup, finds free space in the next record in the ring, generates and writes header information to the ring, and chooses a reader process to read data to asynchronously fill the in-memory record. Once the main process has set-up the control structure in the pad area to indicate to the reader what to read and where to put the data (the next space sequentially available in the ring), it sends a signal to the chosen reader process to wake it up. The main process can now asynchronously continue this loop for the next file in the list. The signalled reader processes read their data into their designated area in the ring, then send a signal to the main process indicating its completion, and the main process modifies statuses accordingly. The main process also writes a trailer block to the ring to indicate the file's final backup status. It follows this trailer block with the next file's header block (in the same record if there is space), and the algorithm repeats.

Once the main process identifies that an entire ring record has been completely filled with information (header, trailer and file data from the various reader processes), a signal is sent to the writer process indicating that there is work to be done. One entire record is read from the ring and written to the output device, and a signal is sent to the main process to indicate completion. Again, all statuses are checked and acted upon by the main process as appropriate.



http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000046942450

live free or die
harry

[malki_3]

I inform you that I have just 2 backuprdr that are runing on the system but I dont have no fbackup process no fbackupwrt..
I tried to kill them but I can't..
So I looke for a solution to eject tape ot restart killing thes pressess
root 16126 1 0 23:05:29 ?
root 16125 1 0 23:05:29 ?
Thanks more