Hi,
11.10.2007 08:56,, Jean-Michel Caricand wrote::
> Hi,
>
> I have a litlle question. I have a server with theses mount point :
>
> # cat /etc/fstab
> ...
> /dev/mapper/myvg-home /home ext3
> defaults,usrquota,grpquota,acl0 2
> /dev/mapper/myvg-public /home/publi
Hi,
I have a litlle question. I have a server with theses mount point :
# cat /etc/fstab
...
/dev/mapper/myvg-home /home ext3defaults,usrquota,grpquota,acl
0 2
/dev/mapper/myvg-public /home/public ext3defaults
0
On Thu, 23 Nov 2006 09:09:13 +0100
Manuel Staechele <[EMAIL PROTECTED]> wrote:
> Hello List,
>
> i do not understand the message:
>
> server-fd: Filesystem change prohibited. Will not descend into /home
>
> did bacula save this directory or not? It came only this message, the
> job it self is
On 11/23/06, Manuel Staechele <[EMAIL PROTECTED]> wrote:
Hello List,
i do not understand the message:
server-fd: Filesystem change prohibited. Will not descend into /home
did bacula save this directory or not? It came only this message, the
job it self is OK without warnings, so i think it do
Hello List,
i do not understand the message:
server-fd: Filesystem change prohibited. Will not descend into /home
did bacula save this directory or not? It came only this message, the
job it self is OK without warnings, so i think it doesn't matter.
If bacula did not save the directory, how ca
> On Tue, 22 Aug 2006 21:29:20 -0700, Robert W Hartzell said:
>
> Martin Simmons wrote:
> >> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
>
> I think the simplest and best solution is to suppress these messages as
> I
> wrote above if they are in fact backe
Martin Simmons wrote:
>> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
I think the simplest and best solution is to suppress these messages as I
wrote above if they are in fact backed up somewhere else in the backup.
This
will ensure that the messages are
On Tuesday 22 August 2006 11:39, Martin Simmons wrote:
> > On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
> >
> > Martin Simmons wrote:
> > >> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said:
> > >> On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
> > On Tuesday 0
> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
>
> Martin Simmons wrote:
> >> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said:
> >> On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
> On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> It's worth noting,
Martin Simmons wrote:
>> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said:
>> On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> It's worth noting, that the messages above don't necessarily mean
> that the
> filesys
On Wednesday 16 August 2006 18:29, Martin Simmons wrote:
> > On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said:
> >
> > On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
> > > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> > > >> It's worth noting, that the messages above don't
> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said:
>
> On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
> > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> > >> It's worth noting, that the messages above don't necessarily mean
> > >> that the
> > >> filesystem mentioned wou
On Wednesday 16 August 2006 00:33, Jo Rhett wrote:
> > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> >> It's worth noting, that the messages above don't necessarily mean
> >> that the
> >> filesystem mentioned wouln't be backed up at all.
> >>
> >> The message is generated, when a mount
> On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
>> It's worth noting, that the messages above don't necessarily mean
>> that the
>> filesystem mentioned wouln't be backed up at all.
>>
>> The message is generated, when a mounted filesystem is met, but the
>> filesystem may be backed up an
I have a question relating to this one:
Shannon: Filesystem change prohibited. Will not descend into /dev
Don't you need the (link) files in this directory in order to restore your
system? Is it a problem to back it up?
I guess you also need boot?
On Tuesday 08 August 2006 16:47, Marco S
On Mon, 14 Aug 2006, Kern Sibbald wrote:
Unfortunately it also doesn't backup the mountpoint as a directory, which
makes restoration a bit messy at times.
>>>
>>> Bacula has backed up mount points for quite some time now, though I don't
>>> remember what version it was first implemented
On Monday 14 August 2006 11:29, Alan Brown wrote:
> On Sun, 13 Aug 2006, Kern Sibbald wrote:
>
> >> Unfortunately it also doesn't backup the mountpoint as a directory, which
> >> makes restoration a bit messy at times.
> >
> > Bacula has backed up mount points for quite some time now, though I don
On Sun, 13 Aug 2006, Kern Sibbald wrote:
>> Unfortunately it also doesn't backup the mountpoint as a directory, which
>> makes restoration a bit messy at times.
>
> Bacula has backed up mount points for quite some time now, though I don't
> remember what version it was first implemented in.
It's
On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote:
> > Marco Strullato wrote:
> > > hi all,
> > > do you know why I get Filesystem change prohibited when I run bacula?
> > >
> > >
> > > 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> > > Job=BackupShannon.2006-08-08_16.39.58
> > > 08-Aug 1
On Tuesday 08 August 2006 18:13, Alan Brown wrote:
> On Tue, 8 Aug 2006, Michel Meyers wrote:
>
> > Those are mounted filesystems. Bacula will not descend into mounted
> > filesystems unless you specifically tell it to.
>
> Unfortunately it also doesn't backup the mountpoint as a directory, which
> Marco Strullato wrote:
> > hi all,
> > do you know why I get Filesystem change prohibited when I run bacula?
> >
> >
> > 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> > Job=BackupShannon.2006-08-08_16.39.58
> > 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written,
> > mov
> On Tue, 8 Aug 2006 17:13:22 +0100 (BST), Alan Brown said:
>
> On Tue, 8 Aug 2006, Michel Meyers wrote:
>
> > Those are mounted filesystems. Bacula will not descend into mounted
> > filesystems unless you specifically tell it to.
>
> Unfortunately it also doesn't backup the mountpoint as a
On Tue, 8 Aug 2006, Michel Meyers wrote:
> Those are mounted filesystems. Bacula will not descend into mounted
> filesystems unless you specifically tell it to.
Unfortunately it also doesn't backup the mountpoint as a directory, which
makes restoration a bit messy at times.
AB
---
>From the bacula manual:
onefs=yes|no
If set to yes (the default), Bacula will remain on a single file
system. That is it will not backup file systems that are mounted on a
subdirectory. If you are using a *nix system, you may not even be
aware that there are several different filesystems as t
In response to "Marco Strullato" <[EMAIL PROTECTED]>:
> hi all,
> do you know why I get Filesystem change prohibited when I run bacula?
>
>
> 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> Job=BackupShannon.2006-08-08_16.39.58
> 08-Aug 16:40 StorageServer: Volume "centroservizi" previousl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Strullato wrote:
> hi all,
> do you know why I get Filesystem change prohibited when I run bacula?
>
>
> 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> Job=BackupShannon.2006-08-08_16.39.58
> 08-Aug 16:40 StorageServer: Volume "centroservi
hi all,
do you know why I get Filesystem change prohibited when I run bacula?
08-Aug 16:40 DirectorServer: Start Backup JobId 95,
Job=BackupShannon.2006-08-08_16.39.58
08-Aug 16:40 StorageServer: Volume "centroservizi" previously written,
moving to end of data.
Shannon: Filesystem change pro
Hi I am backing up a linux box and I see the following in the messages.
< snip >
frigg-fd: Filesystem change prohibited. Will not descend into /home
< /snip >
in my fileset I have the following
< snip /etc/bacula/bacula-dir.conf >
FileSet {
Name = "frigg-full"
Include {
Options
On Mon, Dec 19, 2005 at 10:19:08AM +0200, Timo Neuvonen wrote:
> Is there any way to disable warning "Filesystem change prohibited", that
> appears in 1.38.x while onefs=yes is in use?
Just to show that needs vary, I wish that there were a way to get a
similar warning when a directory tree is omit
Is there any way to disable warning "Filesystem change prohibited", that
appears in 1.38.x while onefs=yes is in use?
While this message can be very informational during debugging, I would
prefer this kind of warnings not to appear in regular production run -now it
may be more tough to notice "rea
30 matches
Mail list logo
