Re: Bad pattern match on disklist
On Thu, Feb 15, 2001 at 02:54:58AM -0200, Alexandre Oliva wrote: On Feb 15, 2001, Mario Obejas [EMAIL PROTECTED] wrote: amadmin ssm1 info hostx / See `man amdmin'. disk is a regular expression in 2.4.1p1; use `/$'. In 2.4.2, a new pattern matching scheme was introduced. `/' should no longer match other disks in 2.4.2. The new pattern matching scheme is not available in 2.4.2, it is only available in the 2.5.0 branch. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Bad pattern match on disklist
Using Solaris 8 based server, amanda_2.4.1p1. Same results appear with Solaris 2.5.1 based server. Summary: amrestore and amadmin act on the wrong filesystem when the disklist mount point is a substring of another mountpoint. Is this a bug with the disklist pattern matching? Background: From amanda(8), describing the disklist: diskdevice The name of the disk device to be backed up. It may be a full device name, a device name without the /dev/ prefix, e.g. sd0a, or a mount point such as /usr. ^^ Hence, I should be able to use / /var /export/home /export/home1 /export/home2 : /export/homeN My "ssm1" disklist: hostx / comp-user hostx /varcomp-user hostx /export/home2 comp-user hostx /export/home3 comp-high hostx /export/home4 comp-high All are unique filesystems on hostx. The amdump using dump (ufsdump on Soalris) works fine. But odd behavior with amadmin and amrestore occurs when the mount point is a substring of other mount points. e.g.: amadmin ssm1 info hostx / Current info for hostx /export/home4: : Current info for hostx /export/home3: : Current info for hostx /export/home2: : Current info for hostx /var: : Current info for hostx /: Why am I getting information about filesystems other than "/"? The worst behavior is doing a restore. If I want to restore, and the tape holds another file system first, I will restore from the mismatched system first (e.g., I want to amrestore "/", but /export/home4 appears on the tape first). Is this a bug with the pattern matching? It's as if the pattern match is like a "grep" instead of an exact match on the mount point. I looked in the server-src source, but could not find it. Mario Obejas Engineering Automation Computing Raytheon Electronic Systems 310-334-7201 (Voice) 310-366-4867 (Pager)
Re: Bad pattern match on disklist
On Feb 15, 2001, Mario Obejas [EMAIL PROTECTED] wrote:
amadmin ssm1 info hostx /
See `man amdmin'. disk is a regular expression in 2.4.1p1; use `/$'.
In 2.4.2, a new pattern matching scheme was introduced. `/' should no
longer match other disks in 2.4.2.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
