* John R. Jackson <[EMAIL PROTECTED]> (Wed, Jan 24, 2001 at 06:50:46PM -0500)
> The only things I can think of to try at this point are a complete rebuild
> of Amanda (blow away all traces of the build area you used before),
> or upgrading to the latest gcc and building that for the specific host
On Wed, 24 Jan 2001, John R. Jackson wrote:
> Huh? What do you mean you're backup up to a disk? Amanda backs up
> to tape. And why would you send all that traffic through the worst file
> protocol in existence, SMB, to one of the worst OS's in existence, NT?
There doesn't seem to be any good
Ben Hyatt wrote:
>
> > If it shows a value of 2 at this point, which is before any Amanda code
> > is run, then it almost has to be a compiler or loader error.
>
> H, gcc version 2.8.1 is what I am using...
>
> > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
Ben and
Johannes Niess wrote:
>
> server:~ # rm /tmp/dattest;mtst -f /dev/nst0 rewind;mtst -f /dev/nst0
> status; echo;dd if=/dev/nst0 of=/tmp/dattest;echo;cat /tmp/dattest
Try specifying the block size in the dd command:
dd if=/dev/nst0 of=/tmp/dattest ibs=32k obs=32k
^
Hi, people
In order to perform my 22GB (level 0) i have to use a SONY DDS3,
but whenever i need to backup everything i have to use that "strategy
nofull" parameter to perferm incremental backups and then i use "admin XXX
force " to force level 0 backups of the filesystem i want, doi
Chris-
> Program received signal SIGSEGV, Segmentation fault.
> 0xff0b6e94 in strlen () from /usr/lib/libc.so.1
> ^^
>
> I am not an expert in all these versions, but I think libc.so.6 is the
> state-of-the-art and everything older is asking for trou
John R. Jackson wrote:
>> amrestore: short file header block: 26624 bytes
>
>
> What do you get if you do this:
>
> mt -f /dev/tape rewind
> dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
> ls -l /tmp/f0.b0
> strings /tmp/f0.b0
#mt rewind
#dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
0+
Hi,
>>... when I try to run amdump,
>>it's done within less than a second, and exits' because it doesn't
>>get
>>any estimates.
>
> What's in /tmp/amanda/sendsize*debug on the client?
Not much, just this:
sendsize: debug 1 pid 7788 ruid 26 euid 26 start time Tue Jan 23
15:45:21 2001
/usr/loca
* Mack Earnhardt <[EMAIL PROTECTED]> (Thu, Jan 25, 2001 at 09:28:31AM -0500)
>> Had you rewound the tape? Amrecover does not do so (or anything else), so
>> if it was at the end (or someplace in the middle), bad things will happen.
> It gives exactly the same messages (including amidxtaped.debu
I was uncertain at first, but I think it's ok. Here's the setup:
mknod /dev/ht0 c 37 0
mknod /dev/nht0 c 37 128
ln -s /dev/nht0 /dev/tape (since /dev/tape is default for mt)
One of my first attempts at this amdump wrote 11 filesystems to tape. I
checked through several that I could use 'mt fs
[EMAIL PROTECTED] (Chris Karakas) writes:
[...]
>
> dd if=/dev/nst0 of=/tmp/dattest ibs=32k obs=32k
> ^^^
> (some implementations of dd may need an explicit setting of input and
> output block sizes, so don't just use bs=32k for the moment).
It's wor
> I could be smoking something here, but I seem to recall seeing this
> (*insecure*) crap on my Solaris 2.6 box here, and my amchecks failed
> until I got rid of the (*insecure*) by fixing my hostname lookups
> for my own host.
The (*insecure*) bit is just part of amanda's .bashrc...
if [ $SHLVL
> Do you have a Sol 2.6 box around ?
Yes
> If so, try building amanda on the 2.6 box.
> 2.6 Amanda works nice and shiny on a Sol 7 box
> (at least it should, I haven't actually tried it yet ;) )
I grabbed, and built the latest gcc from gnu last night.
gcc -v Reading specs from
/usr/local/lib/g
[EMAIL PROTECTED] writes:
> Hi, people
>
> In order to perform my 22GB (level 0) i have to use a SONY DDS3,
> but whenever i need to backup everything i have to use that "strategy
> nofull" parameter to perferm incremental backups and then i use "admin XXX
> force " to force level 0 b
>It's worse. With blocksize 0 I get the data and the error, with bs=32k
>I get just the error and 0 blocks read. This applies to ibs/obs=32k
>and bs=32k. ...
There are several moving parts here that I want to make sure we all are
in sync on.
Some hardware has a blocking size. If you set it to
Hello Folks,
I'm getting this error with the selfcheck routines on Amanda Solaris 2.7
clients:
# more /tmp/selfcheck.debug
selfcheck: debug 1 pid 4232 ruid 20263 euid 20263 start time Thu Jan 25
13:52:26
2001
/opt/amanda-2.4.2/libexec/selfcheck: version 2.4.2
checking disk /home: device /dev/rd
>#mt rewind
>#dd if=/dev/tape bs=32k count=1 > /tmp/f0.b0
>0+1 records in
>0+1 records out
>#ll /tmp/f0.b0
>-rw-r--r--1rootroot26624 Jan 25 09:04 /tmp/f0.b0
>#strings /tmp/f0.b0
>AMANDA: TAPESTART DATE 20010123 TAPE Optivel-01
That's got to be something like:
* A hardware probl
> checking disk /home: device /dev/rdsk/c0t0d0s7: Permission denied
what does ls -la on c0t0d0s7 look like?
For example:
> ls -la ../../devices/pci@1f,4000/scsi@3/sd@0,0:h,raw
crw-r- 1 root sys 32, 7 Jan 22 14:15
../../d
>Not much, just this:
>
>sendsize: debug 1 pid 7788 ruid 26 euid 26 start time Tue Jan 23
>15:45:21 2001
>/usr/local/libexec/sendsize: version 2.4.2
Then it may have died. Do you have any core files in /tmp/amanda? If
so can you get a stack traceback with a debugger?
If not (or even if so), t
> Make sure the user amanda runs as has read permission on the raw device.
Oops... make sure the group of the user that amanda runs as has read
permission.
-Ben
I compiled amanda on a new RH7 server, and did the "make" and "make
install" thing, but now I want to compile it again but with different
options compiled in. How do I completely remove amanda and start over
again with a clean slate?
Thanks for any assistance.
Try retensioning the tape--I find that with Travan tapes you have to
retension them pretty frequently, especially if they've been sitting
around for a few days since you last used them. I usually retension the
tape each time I use it. The command is usually:
mt -f /dev/your-tape-dev retension
I'm sure they would. However, I'd strongly recommend you start with
the main development branch (the main trunk, w/o any -r option), as it
has a new security model that is supposed to make this kind of thing
easier (more modular).
Okay.
Another concern of mine is that, for security,
Hello Ben,
That was it. Geez Amanda installation sure isn't for the faint of heart!
Could this also be why my sendsize wouldn't work either when I used "tar"?
Cheers, Luc.
Ben Hyatt wrote:
> > checking disk /home: device /dev/rdsk/c0t0d0s7: Permission denied
>
>Another concern of mine is that, for security, I'd like to encrypt the data
>going onto tapes for tapes that I want to send off-site. Anyone considered
>something like this before?
Amanda 2.5 (and a special branch of 2.4.2) now contain the "tapeio"
feature which allows new output drivers to be
>... How do I completely remove amanda and start over
>again with a clean slate?
If you're just talking about the binaries, "make distclean" will clobber
everything, then you can start over again with ./configure, etc.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Hello all
I have taken over running Amanda 2.4.1 and backing up about 30-40 servers
and workstations since one of our two Unix system managers moved on to
greener pastures a few months ago. Since then, each time our remaining
system manager has upgraded a sun system to Solaris 8 it has begun fai
I am trying to restore one directory from the archive that was
created using Amanda-2.4.2 and Gnutar however seem to be having
a problem using Amrestore.
Here is what I trying:
amrestore -p /dev/st0 ray hda8 | tar xvf /etc/autorpm.d .
But I get the errors:
tar: etc/autorpm.d: Cannot read: Is a
Hello,
I've just installed amanda 2.4.2 and it's backing up a couple of my
filesystems as expected. I added a another filesystem to be backed up
just yesterday which is timing out on the estimate part.
the problem is that the filesystem is on a Linux software RAID config:
Filesystem
Ray,
The "f" flag to gnutar designates the file you are
attempting to manipulate. In this case, tar is trying to do
a verbose extraction from the file /etc/autorpm.d, and complaining,
as appropriate, that it's a directory. Amanda is then telling
you that the pipe (to the tar command) wa
>Here is what I trying:
>
>amrestore -p /dev/st0 ray hda8 | tar xvf /etc/autorpm.d .
Dan Shauver is correct but left out the most important part, how to
do this right :-). I'm not 100% certain what you were trying to do
(why did you have that '.' on the end?), but on the assumption you were
tryi
>... Since then, each time our remaining
>system manager has upgraded a sun system to Solaris 8 it has begun failing
>out of the backup set. ...
My guess would be some shared library has vanished that amandad is linked
against and so it won't run any more. I have that problem here in the
rever
>... I think it times out because there is over
>100,000 files and it can't create the file list. ...
Does the whole file system has 100,000 files, or just /raid1/production?
Using GNU tar, it would only matter what's under /raid1/production.
>The "production"
>directory isn't even that big, i
> "jrj" == John R Jackson <[EMAIL PROTECTED]> writes:
>> Here is what I trying:
>>
>> amrestore -p /dev/st0 ray hda8 | tar xvf /etc/autorpm.d .
jrj> Dan Shauver is correct but left out the most important part, how to
jrj> do this right :-). I'm not 100% certain what you were trying to do
j
Huh? *blink blink*
Sorry about that.
Apparently, it's time for another cup of coffee.
Dan Shauver
HortResearch UNIX Dude
>Dan Shauver is correct but left out the most important part, how to
>do this right :-). I'm not 100% certain what you were trying to do
>(why did you have that '.' on the
> >... I think it times out because there is over
> >100,000 files and it can't create the file list. ...
>
> Does the whole file system has 100,000 files, or just
> /raid1/production? Using GNU tar, it would only matter what's under
> /raid1/production.
just the /raid/production has the 100,00
It Works! It Works!
I tried experimenting with a short file and found that dd couldn't read
what it wrote. The file was definitely there in some fashion because
'mt eom' followed by 'mt status' said the tape was at block 9, which is
about right (the default phys block is 512 bytes and the fil
On Jan 24, 2001, "Ben Hyatt" <[EMAIL PROTECTED]> wrote:
> H, gcc version 2.8.1 is what I am using...
On Solaris 7? IIRC, GCC 2.8.1 needed some patches to support Solaris 7.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aol
On Jan 24, 2001, Ben Elliston <[EMAIL PROTECTED]> wrote:
> In the case of the full dump only two days into the cycle, it seems that
> dump on that workstation reported an identical size for levels 0 and 1, so
> of course, Amanda decided that level 1 was unwise and did a level 0.
Unless you touch
On Jan 24, 2001, David Wolfskill <[EMAIL PROTECTED]> wrote:
> Per the suggestion, I had built amanda on that client with the
> "--with-udpportrange=850,854" config directive.
Looks like a typo. It's plain (TCP) portrange that should have a
range like this.
--
Alexandre Oliva Enjoy Guarana',
On Jan 25, 2001, Ben Elliston <[EMAIL PROTECTED]> wrote:
> Another concern of mine is that, for security, I'd like to encrypt the data
> going onto tapes for tapes that I want to send off-site. Anyone considered
> something like this before?
A while ago, someone posted patches/scripts to throw
On Jan 25, 2001, [EMAIL PROTECTED] wrote:
> problem is that when i use "strategy nofull" amanda is only performing
> level 1 backups.
As per the documentation :-)
Maybe incronly is what you want?
> I once read something about a patch that could allow me to
> control the backup levels
On Jan 25, 2001, Luc Lalonde <[EMAIL PROTECTED]> wrote:
> Could this also be why my sendsize wouldn't work either when I used "tar"?
Nope. tar doesn't read the disk device directly, so its permission
wouldn't matter.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Re
On Jan 25, 2001, Ajay Sharma <[EMAIL PROTECTED]> wrote:
>> I don't understand. If the CPU usage dropped that much, it implies
>> the GNU tar might have been done. Did you do a "ps" to see what was
>> going on?
> Yeah, the gtar process was the one taking up 70% of the CPU, then after
> 20 minut
On Jan 25, 2001, Harri Haataja <[EMAIL PROTECTED]> wrote:
> Has anyone tried to get amandad to run on NT with the Cygnus stuff?
I believe so. The main difficulty was to get some equivalent of inetd
so that amandad could be fired as a service. That's for the client
part, of course. To get it t
> On Solaris 7? IIRC, GCC 2.8.1 needed some patches to support Solaris 7.
Yes. I built the latest ( I believe ) 2.95.2 and tried compling, making and
install again (fresh build dir)
No luck. Still get amandad looping, and ending up with a segmentation fault
So my next alternative is to fi
On Jan 26, 2001, "Ben Hyatt" <[EMAIL PROTECTED]> wrote:
>> On Solaris 7? IIRC, GCC 2.8.1 needed some patches to support Solaris 7.
> Yes. I built the latest ( I believe ) 2.95.2 and tried compling, making and
> install again (fresh build dir)
> No luck.
What does common-src/version.c look lik
47 matches
Mail list logo
