>
> no idea, if we can find out what triggered the original message. Without
> doing anything physical, I did an umount storage=LTO4 from bacula and then
> went and did a full btape rawfill without a single problem on the volume:
>
> *status
> Bacula status: file=0 block=1
> Device status: ONLINE IM_REP_EN file=0 block=1
> btape: btape.c:2133 Device status: 641. ERR=
> *rewind
> btape: btape.c:578 Rewound "LTO4" (/dev/nst0)
> *rawfill
> btape: btape.c:2847 Begin writing raw blocks of 2097152 bytes.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++ (...)
> Write failed at block 384701. stat=-1 ERR=No space left on device
> btape: btape.c:410 Volume bytes=806.7 GB. Write rate = 106.1 MB/s
> btape: btape.c:608 Wrote 1 EOF to "LTO4" (/dev/nst0)
> *
>
> zero problems at all.
>
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?
James
------------------------------------------------------------------------------
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
