I figured this one out, the file system that I was trying to use
crashed, and was mounted read-only. Sorry about crying wolf
Scott
On Wed, Jul 09, 2003 at 07:09:20PM -0700, Scott Petler wrote:
>
> Amanda was working fine, but now I get the following from amcheck:
> Not sure what
Amanda was working fine, but now I get the following from amcheck:
Not sure what happened, any ideas. I'll also put other relevant files
after. I don't remember changing anything.
Thanks
Amanda Tape Server Host Check
-
amcheck-server: slot 12: chg-multi: slot is em
Thanks for the suggestion. I suppose I would also have to do
this when using my "amcheck" in user backup's crontab.
I'll try this out...
I also saw the previous suggestion to try not even mounting
my /backup disk, that would be cool, but I don't see how I
could set up my tapelist to do this...
Hi,
I am using amanda to back up to a hard disk on my system and would
like to protect the backed up disk from accidental erasure. I thought
one way to do this would be to mount it then run amdump, and then umount it.
The disk is going to be vulnerable during the backup period, but "safe"
when not
-0400, Eric Siegerman wrote:
> On Fri, Jul 04, 2003 at 11:00:26AM -0700, Scott Petler wrote:
> >
> > I am using amanda to back up to a second hard disk. I get the
> > following message:
> >
> > These dumps were to tape DailySet101.
> > ^
I am using amanda to back up to a second hard disk. I get the
following message:
These dumps were to tape DailySet101.
^^^
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flu
, 2003 at 07:18:07PM +0200, Paul Bijnens wrote:
> Scott Petler wrote:
> > I'm trying to configure amanda 2.4.4 to backup to a spare
> > drive, but can't quite get it to work. Where is -1 KB coming from?
>
> Have a look in the debug files in /tmp/amanda.
> There
Hi,
I'm trying to configure amanda 2.4.4 to backup to a spare
drive, but can't quite get it to work. Where is -1 KB coming from?
I've tried changing the length number in the config and don't seem
to be able to make it have any effect on the error message. It seems
that the tape size is 0 o
