On Fri, 29 Jul 2005, Jesse Keating wrote:
On Fri, 2005-07-29 at 21:49 +0100, Martin Simmons wrote:
Oh, I thought the blockage and mount command is per storage device,
not per
tape.
It does block the storage device. It prevents the storage device from
automounting the next usable tape. I
On Monday 01 August 2005 12:26, Alan Brown wrote:
On Fri, 29 Jul 2005, Jesse Keating wrote:
SO really, all I need to do after marking the tape as full is issue a
update slots command. Easy sleasy. Of course if Kern ever changes how
this works I may be in trouble as this is not the
On Wed, 2005-08-03 at 12:55 -0700, Jesse Keating wrote:
So release does not unload the drive, so I would have to pair that with
an mtx call to unload. This I'd rather not do, but I suppose I should.
Hrm, release doesn't close the /dev/nst0 device either. update slots
leaves the device as
On Wed, 2005-08-03 at 13:15 -0700, Jesse Keating wrote:
Hrm, release doesn't close the /dev/nst0 device either. update slots
leaves the device as closed or non-existent. Will this pose a problem
if I unload the tape out from under bacula-sd while the device is open?
Testing here..
When I
On Wednesday 03 August 2005 21:55, Jesse Keating wrote:
On Sat, 2005-07-30 at 09:32 +0200, Kern Sibbald wrote:
Try the release command. It was designed to release the drive but not
to block it as the unmount command does. You may need to explicitly do
an unload of the drive using mtx
On Friday 29 July 2005 23:01, Jesse Keating wrote:
On Fri, 2005-07-29 at 21:49 +0100, Martin Simmons wrote:
Oh, I thought the blockage and mount command is per storage device,
not per
tape.
It does block the storage device. It prevents the storage device from
automounting the next
On Thu, 2005-07-28 at 15:46 -0700, Jesse Keating wrote:
I'd like to automatically umount the tape in the drive after the last
backup for the week. This way I can come in on Monday and immediately
unload the drive and eject the magazine for tape rotation. However in
the past after I've done a
On Thu, 28 Jul 2005 15:46:13 -0700, Jesse Keating [EMAIL PROTECTED]
said:
Jesse I'd like to automatically umount the tape in the drive after the last
Jesse backup for the week. This way I can come in on Monday and immediately
Jesse unload the drive and eject the magazine for tape
On Fri, 2005-07-29 at 21:05 +0100, Martin Simmons wrote:
Yes, this is normal behaviour. You could try adding an admin job that
mounts the tape.
hrm... problem is that I don't know which tape is needed next. I was
just hoping to clear the block flag so that Bacula could mount whatever
tape
On Fri, 2005-07-29 at 21:49 +0100, Martin Simmons wrote:
Oh, I thought the blockage and mount command is per storage device,
not per
tape.
It does block the storage device. It prevents the storage device from
automounting the next usable tape. I have automated marking the last
tape as
On Fri, 29 Jul 2005 14:01:38 -0700, Jesse Keating [EMAIL PROTECTED]
said:
Jesse On Fri, 2005-07-29 at 21:49 +0100, Martin Simmons wrote:
Oh, I thought the blockage and mount command is per storage device,
not per
tape.
Jesse It does block the storage device. It prevents the
On Fri, 2005-07-29 at 23:15 +0100, Martin Simmons wrote:
Ah, that's what I was missing. Maybe you can run the mtx script to load slot
1 into the drive and keep Bacula's mount command happy?
Actually I think I found a good work around. update slots will umount
any mounted drive and unload it
I'd like to automatically umount the tape in the drive after the last
backup for the week. This way I can come in on Monday and immediately
unload the drive and eject the magazine for tape rotation. However in
the past after I've done a umount in bconsole, backups wouldn't continue
due to
13 matches
Mail list logo
