amrecover is trying to use restore instead of vrestore.
That doesn't make any sense. The program used by amrecover is determined
by what is recorded in the image header. It does not go through the
getfsent code.
Find out what file on the tape has the image you were going after,
position it
On Apr 10, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
Try this patch, It look at MOUNTED before MNTTAB.
Thanks, I can confirm it works on Tru64 4.0D and GNU/Linux/x86 (Red
Hat Linux 7), with LABEL entries in /etc/fstab.
--
Alexandre Oliva Enjoy Guarana', see
On Apr 9, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
On Mon, Apr 09, 2001 at 02:03:00PM -0300, Alexandre Oliva wrote:
Looks like we need an additional argument in search_fstab, say
check_dev, and get amname_to_devname to call search_fstab first with
check_dev == 1, so as to reject
The patch works for me, what's your /proc/mounts and /etc/mtab entry?
/proc/mounts:
/dev/root / ext2 rw 0 0
/etc/mtab:
/dev/hda1 / ext2 rw 0 0
/etc/fstab:
LABEL=/ / ext2 defaults 1 1
./getfsent /:
device of `/': /dev/root
dirname of `/': /
fstype of `/': ext2
./selfcheck:
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then I'll put together a
On Tue, Apr 10, 2001 at 01:48:13PM -0500, John R. Jackson wrote:
I'm not sure why you asked about /etc/mtab. While it has the right
value, we don't look at it in Amanda (which might be the real problem).
We look at /proc/mounts (which has the wrong /dev value) and MNTTAB,
which is
I have /dev/hda1 in /etc/fstab.
Ahh, I see. So you cheated. :-) :-)
Try this patch, It look at MOUNTED before MNTTAB.
Looks good to me. Alexandre, can you give this a try on Tru64? If it
works for you, then I'll put together a single patch for Walter to try,
and if that works, Jean-Louis
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then I'll put
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
Yeah, this got a little confusing. Sorry 'bout that.
My advice is to wait for Alexandre, Jean-Louis and I to stop publicly
arguing with each other :-) and come to an agreement on the fix.
Then
On Apr 9, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
On Mon, Apr 09, 2001 at 12:22:36PM -0300, Alexandre Oliva wrote:
On Apr 9, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
Here's a patch that fixes the bug. Obviously, the last hunk is enough
to fix the bug, but I'm
Could you try this patch on Tru64.
This is probably a silly question, but did you try the patch on Linux?
I was playing with this too and my version (functionally the same as
yours, I think) put Linux back to trying to use /dev/root.
Here's what I think is happening. Amanda is trying to
Hang on guys,
I'm getting directions from a number of people here. Woe Nelly!
The patch described below and the previous simple patch have not yet been
applied to any of my systems.
I have only done a basic make of getfsent and sent the un modified (or P2
distribution) results of getfsent
On Mon, Apr 09, 2001 at 07:32:43PM -0500, John R. Jackson wrote:
Could you try this patch on Tru64.
This is probably a silly question, but did you try the patch on Linux?
I was playing with this too and my version (functionally the same as
yours, I think) put Linux back to trying to use
On Sun, Apr 08, 2001 at 11:00:06PM -0300, Alexandre Oliva wrote:
On Apr 6, 2001, John R. Jackson [EMAIL PROTECTED] wrote:
The entry in the fstab looks good and looks like this on both
machines:
root_domain#root / advfs rw 1 0
That would seem to be reasonable.
This was working
On Apr 9, 2001, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
Here's a patch that fixes the bug. Obviously, the last hunk is enough
to fix the bug, but I'm posting exactly what I'm about to check in:
2.4.2 branch and mainline.
But your patch break / for linux :-(
You sure? It appears to
On Mon, Apr 09, 2001 at 02:03:00PM -0300, Alexandre Oliva wrote:
Looks like we need an additional argument in search_fstab, say
check_dev, and get amname_to_devname to call search_fstab first with
check_dev == 1, so as to reject any entries whose device names don't
exist, then, if none are
On Apr 6, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote:
The entry in the fstab looks good and looks like this on both
machines:
root_domain#root / advfs rw 1 0
That would seem to be reasonable.
This was working fine in 2.4.2p1 but now that I have upgraded to
2.4.2p2 its not working
I have configured the system so that amcheck is happy, but amdump
reports disk is offline.
I have set the device permissions like so:
brw-r root system /dev/vol/rootvol (logical volume)
Is your Amanda user (the one inetd/xinetd runs amandad as) in group
"system"?
What's in
On Apr 5, 2001, [EMAIL PROTECTED] wrote:
The sendsize*debug file reveals that the client is trying to use dump
instead of vdump upon an advfs file system!
How do I configure the client to use vdump instead?
You get /etc/fstab or equivalent to indicate that directory is mounted
from an
From: Alexandre Oliva [EMAIL PROTECTED]
Date: Fri Apr 6, 2001 3:24am
Subject: Re: LSM - Logical Storage Manager Drives
On Apr 5, 2001, [EMAIL PROTECTED] wrote:
The sendsize*debug file reveals that the client is trying to use
dump
instead of vdump upon an advfs file system!
How do I
The entry in the fstab looks good and looks like this on both
machines:
root_domain#root / advfs rw 1 0
That would seem to be reasonable.
This was working fine in 2.4.2p1 but now that I have upgraded to
2.4.2p2 its not working on any client or even the server anymore.
OK, I can guess which
I have configured the system so that amcheck is happy, but amdump
reports disk is offline.
I have set the device permissions like so:
brw-r root system /dev/vol/rootvol (logical volume)
Is your Amanda user (the one inetd/xinetd runs amandad as) in group
"system"?
What's in
Has anybody any experience with backing up LSM drives using Amanda?
I have configured the system so that amcheck is happy, but amdump
reports disk is offline.
I have set the device permissions like so:
brw-r root system /dev/vol/rootvol (logical volume)
crw-r root system
23 matches
Mail list logo
