My amandad debug file looks like this:
amandad: debug 1 pid 32572 ruid 34 euid 34
start time Thu Jan 6 10:52:00 2005
amandad: version 2.4.2p2
amandad: build:
VERSION=Amanda-2.4.2p2
amandad:
BUILT_DATE=Tue Apr 2 21:24:21 UTC 2002
amandad:
BUILT_MACH=Linux
Hello, Brian,
I thought of your problems this morning ;-)
Just now (on 01/07/2005 at 17:17) you wrote:
BC Oddly trying to dd if=/dev/rmt/tps... read no data
BC samar 85# mt -f /dev/rmt/tps1d4nrns rewind
BC samar 86# dd if=/dev/rmt/tps1d4nrns of=scratch
BC Read error: Invalid argument
Invalid
Stefan,
Yes, will strip more stuff out (didn't realize it had grown so much.
The instruction I was following from Gene where pretty explicite
(not that I follow all that well) and where intended to save the
amanda header, reset the block count, restore the header and flush
the buffers.
Hi, Brian,
on Freitag, 07. Jänner 2005 at 17:59 you wrote to amanda-users:
BC The instruction I was following from Gene where pretty explicite
BC (not that I follow all that well)
;-)
BC and where intended to save the
BC amanda header, reset the block count, restore the header and flush
BC the
On Friday 07 January 2005 11:59, Brian Cuttler wrote:
Stefan,
Yes, will strip more stuff out (didn't realize it had grown so much.
The instruction I was following from Gene where pretty explicite
(not that I follow all that well) and where intended to save the
amanda header, reset the block
Gene,
Humm, are you saying that amlabel works and can read the label
written, but that dd doesn't/cannot? Back to 'man dd' as it exists
on that Irix system would be my next suggestion.
Remembering that I'd set the blocksize on the device and relabeled
yesterday I tried this.
samar 160# mt
Hey Brian,
just now (on 01/07/2005 at 19:20) you wrote:
Humm, are you saying that amlabel works and can read the label
written, but that dd doesn't/cannot? Back to 'man dd' as it exists
on that Irix system would be my next suggestion.
BC Remembering that I'd set the blocksize on the
Stefan,
Good to hear. What size did scratch have?
Much nicer device-name now, BTW, maybe this was the problem ... Do you
use this one (the corresponding non-rewinding device) in amanda.conf
as well ??
I'll have to try to pull it again, I seem to have subsequently
overwritten it with a zero
I'm trying to back up a remote server.
On both machines (FC3) I am loading the ip_conntrack_amanda module for
IPTables.
I have the following in my iptables.
ACCEPT udp -- 192.168.5.0/24 anywhereudp dpt:amanda
ACCEPT tcp -- 192.168.5.0/24 anywhere
On Fri, Jan 07, 2005 at 11:59:54AM -0500, Brian Cuttler wrote:
samar 126# which xfsrestore
/sbin/xfsrestore
samar 127# which xfsdump
/usr/sbin/xfsdump
I suppose the theory must be that anyone can do a restore, but
only root can use [xfs]dump.
--
| | /\
|-_|/ Eric Siegerman, Toronto,
On Fri, Jan 07, 2005 at 02:01:26PM -0500, Eric Siegerman wrote:
On Fri, Jan 07, 2005 at 11:17:21AM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing
On Fri, Jan 07, 2005 at 01:20:42PM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing should this not resolve soon)
Yup, this makes sense. Since
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
samar 7# mt -f /dev/sdlt2 fsf 1
samar 8# dd if=/dev/sdlt2
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 24# mt -f /dev/sdlt2 blksize
Recommended tape I/O size: 131072 bytes (256 512-byte blocks)
Minimum block size: 4 byte(s)
Maximum block size: 16777212 bytes
Current block size: Variable
I am using /dev/sdlt2 link
On Friday 07 January 2005 15:40, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
[likewise with dd bs=32k
--On Friday, January 07, 2005 14:05:19 -0500 Michael J. Pawlowsky [EMAIL
PROTECTED] wrote:
I'm trying to back up a remote server.
On both machines (FC3) I am loading the ip_conntrack_amanda module for
IPTables.
I have the following in my iptables.
ACCEPT udp -- 192.168.5.0/24
17 matches
Mail list logo