> Just had a quick look... the "read-only" message is this in stored/block.c: > > if (!dev->can_append()) { > dev->dev_errno = EIO; > Jmsg1(jcr, M_FATAL, 0, _("Attempt to write on read-only Volume. dev=%s\n"), > dev->print_name()); > return false; > } > >And can_append() is: > >int can_append() const { return state & ST_APPEND; } > >so it does seem pretty basic unless there is a race somewhere in getting the >value of 'state'. > >Are there any kernel messages that might indicate a problem somewhere at that >time?
Nothing related to bacula/tape modules. I am running zfsonlinux for the file system here and there is a known bug with that causing soft lockups for 60-120 seconds: [121423.079640] BUG: soft lockup - CPU#5 stuck for 61s! [z_wr_iss/5:5354] Though the system recovers. This normally happens at delete time (txg_sync) which as this was a new tape mount that would/could be close to the time when an old spool was being deleted (spool sizes are 800G which is the same size as the LTO4 tape). Though I did not see anything like that happen at the time, when it normally happens there is a complete system 'freeze' for a couple seconds and then recovery, I was in via ssh and did not see that and was able to umount & run btape commands. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users