This is now fixed after addding allow_other in the fstab
--
View this message in context:
http://bacula.10910.n7.nabble.com/backup-sd-JobId-36-Error-dev-c-130-Unable-to-stat-device-mnt-s3-consi-it-backup-ERR-Permission-denie-tp85594p85626.html
Sent from the Bacula - Users mailing list archive a
> On Wed, 12 Apr 2017 08:03:32 +0100 (BST), Tom Yates said:
>
> I've got a fairly big filesystem (3TB, 15M files) of which I want to
> (test) restore a part. I know that if the backend DB is slow the
> "Building file list" stage can take some time, but I have it striped over
> a 5-SAS-disc
Yes, I have.
I was upload on pasterbin:
http://pastebin.ca/3794414
Log is contionous with same error.
*—*
*Petar Kozić*
System Administrator
On April 12, 2017 at 11:03:51 AM, Josip Deanovic (djosip+n...@linuxpages.net)
wrote:
On Wednesday 2017-04-12 01:07:41 Petar Kozić wrote:
> @Josip Dean
On Wed, 12 Apr 2017, Francisco Javier Funes Nieto wrote:
The missing question, which Database Catalog are you using ?
The catalogue database is on MySQL, again using the version that comes
with CentOS 6 (5.1.73).
--
Tom Yates - http://www.teaparty.net-
On Wednesday 2017-04-12 01:07:41 Petar Kozić wrote:
> @Josip Deanovic
> Are you using spooling?
> If yes, is your spool directory on the same file system as your database
> data?
>
> No, I don’t spooling Data, only Attributes
>
> My config:
> Spool Data = no
> Spool Attributes = yes
>
>
> I was
@Josip Deanovic
Are you using spooling?
If yes, is your spool directory on the same file system as your database
data?
No, I don’t spooling Data, only Attributes
My config:
Spool Data = no
Spool Attributes = yes
I was increase innodb_timewait_lockout = 150 but error appears again.
Some ideas ?
The missing question, which Database Catalog are you using ?
El 12 abr. 2017 9:26 a. m., "Tom Yates" escribió:
> I've got a fairly big filesystem (3TB, 15M files) of which I want to
> (test) restore a part. I know that if the backend DB is slow the
> "Building file list" stage can take some tim
I've got a fairly big filesystem (3TB, 15M files) of which I want to
(test) restore a part. I know that if the backend DB is slow the
"Building file list" stage can take some time, but I have it striped over
a 5-SAS-disc RAID-0, and this step takes only about eight minutes.
The problems start
