Josh Fisher schrieb: > The only difference that I can see is that the full_write() / > safe_write() functions in tar attempt the write multiple times if need > be and attempt to finish (it seems) partial writes. Btape fails > immediately if the write() system call fails to write the requested > number of bytes. However, btape should be issuing a "Write failed at > block " message if the write fails. That error message contains an error > string corresponding to the errno that was set when the write() failed, > which could be helpful. Christopher Litauer's initial message does not > include such an error message after the "Begin writing raw blocks of " > message, so I don't know if he just didn't include it or if the only > messages he saw were the "bad page state" syslog messages. If there was > no "Write failed at block" message, then the write() system call never > returned, in which case it is a real mystery (to me) as to how tar can > possibly work with the same block size.
No, there definitly is no such message after "Begin writing raw blocks", just one or two '+', nothing more, just the kernel panic messages in /var/log/message -- Regards Christoph ________________________________________________________________________ Christoph Litauer [EMAIL PROTECTED] Uni Koblenz, Computing Center, http://www.uni-koblenz.de/~litauer Postfach 201602, 56016 Koblenz Fon: +49 261 287-1311, Fax: -100 1311 PGP-Fingerprint: F39C E314 2650 650D 8092 9514 3A56 FBD8 79E3 27B2 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
