Hello,
On 27.10.2005 12:03, Tracy R Reed wrote:
has this been answerded already?
I am running Bacula from cvs as of yesterday on a dual-core AMD64 box
running FC4. And I am having a lot of problems. Sometimes when I try to
label a disk I get a strange error:
*label
Using default Catalog name=MyCatalog DB=bacula
Automatically selected Storage: DVD
Enter new Volume name: 21
Automatically selected Pool: Default
Connecting to Storage daemon DVD at home:9103 ...
Sending label command for Volume "21" Slot 0 ...
3000 OK label. Volume=21 Device="DVDWriter" (/dev/hda)
Catalog record for Volume "21", Slot 0 successfully created.
Requesting to mount DVDWriter ...
3907 Device "DVDWriter" (/dev/hda) cannot be mounted. ERR=mount: wrong
fs type, bad option, bad superblock on /dev/hda,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Do not forget to mount the drive!!!
I just labelled a second volume and it did not give me that erorr this
time. Not sure what the difference would be. Maybe the first media was
bad or something.
Well, that message is the output of the system's mount command, I assume.
I notice when trying to purge a volume it says:
Enter MediaId or Volume name:
But it seems to only accept MediaID. I name my volumes by numbers which
can cause confusion with this prompt also. I had a volume named 2 and a
MediaID 2 but they weren't the same physical media.
Right, this is indeed sort of a problem - as long as Bacula allows IDs
and names you should avoid using names consisting of digits only.
Quite often in bconsole that if I ctrl-z it the command line becomes
very confused. And I often find myself stuck at a prompt with no way out
except to ctrl-z and kill bconsole if I do not wish to proceed. An
example of this is in the label command.
Ever tried entering "." without qoutes at a prompt? But in fact bconsole
doesn't like C-z or c-c. Well, I can live without it, because I usually
can leave the bconsole properly.
Otherwise it seems to be doing a backup now. Haven't tried a restore yet
but that will be the real test.
Also, when I turn on software compression of backups is is incredibly
slow. I'm not sure it is working properly at all. I see the spool file
in my spool directory increasing in size at a rate of 1M/minute. That is
WAY slow! A tail -f on that file shows it is writing the same 16 bytes
to the file over and over again. bacula-fd is chewing up all of the cpu
time. Anyone know what is going on with that?
No, but keep in mind that the compression is done by the FD and that
gzip can use lots of CPU time, depending on the compression setting, the
data to compress, and of course the machine it's running on.
I have around 40G of data on this machine to backup. I just tried the
estimate command:
*estimate
The defined Job resources are:
1: Client1
2: home
3: BackupCatalog
4: RestoreFiles
Select Job resource (1-4): 2
Connecting to Client home-fd at home:9102
2000 OK estimate files=611104 bytes=1,295,324,281,965
Am I reading that right? Nearly 1.3 TERABYTES? Something is quite wrong.
Re-check your fileset. Use the estimate listing command. Other than
that, you would need to show us your fileset definition.
Also, is there any way to see what files it is backing up in real time?
You can query the FD, but this only gives a snapshot of what it's doing.
Try the status client=xxx-fd command.
I just tried to do a backup again. It ran for a while, running growisofs
judging by top, then it said this:
27-Oct 02:58 home-sd: Remaining free space 4,689,526,784 on "DVDWriter"
(/dev/hda)
27-Oct 02:58 home-sd: Recycled volume "22" on device "DVDWriter"
(/dev/hda), all previous data lost.
*
*home-sd: dvd.c:376 dvd.c:375 Error while writing current part to the
DVD: Running /usr/bin/growisofs -use-the-force-luke=notray -quiet
-use-the-force-luke=4gms -A 'Bacula Data' -input-charset=default
-iso-level 3 -pad -p 'dvd-handler / growisofs' -sysid 'BACULADATA' -R -Z
/dev/hda /home/backup/22
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Error trying to open /dev/hda exclusively ... retrying in 1 second.
Trying to open without locking.
FATAL: /dev/hda already carries isofs!
27-Oct 02:59 home-sd: Marking Volume "22" in Error in Catalog.
Overall I am getting very weird and inconsistant behavior. :(
Yes, that's what happens sometimes when you use beta software :-)
To help improving the DVD writing code, you should try to understand the
reactions of your system to the commands involved. Bacula relies on
external programs, currently simple scripts, to do the actual work of
writing to DVD. You can run these scripts fromthe shell, and you can
read them and try the commands by hand.
Concerning your last problem, I suppose that some other software
accesses your DVD writer. The different flavours of auto mounting can be
a little annoying... Basic suggestion: The DVD writer should be used by
Bacula only.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
