Mike,

include must be a glob expression, not a regex, so "./[a-c]*" is the correct syntax,

Do /home and /home/aaronson are on the same filesystem?
  df /home
  df /home/aaronson

Are you using the application 'amgtar' or the program 'GNUTAR'?

Jean-Louis

On 07/31/2013 12:56 PM, Mike Neimoyer wrote:
Replying to multiple folks with this message Thanks for your kind responses! :)

Starting with this disklist entry which returned an error:

localhost /home/a-c /home {
vhost2-user-tar
include "./[a-c]*"
} 1 local

Jon was good enough to respond:

> Might /home be a symbolic link to another
> location, eg. /export/home?  I don't know
> if it matters, but I've always used the
> actual storage dir.
>
> BTW the second parameter (/home/a-c) is
> just a DLE name, not a pathname.  Omitting
> the slashes might avoid future confusion.
> Ex. HOME:a-c

I double-checked that /home was not symbolically linked to anywhere else. Then I edited the diskname parameter in the DLE:

localhost HOME:a-c /home {
vhost2-user-tar
include "./[a-c]*"
} 1 local

and an amcheck Daily returned, after the usualy info dir and index dir not existing and being created on the next run:

ERROR: localhost: [Nothing found to include for disk "HOME:a-c"]
Client check: 1 host checked in 1.303 seconds.  1 problem found.

No love with that, I reverted the DLE to it's original (above) because Chris' suggestion had rolled in:

> Try:
>
> localhost /home/./a-c /home {
> vhost2-user-tar
> include "./[a-c]*"
> } 1 local
>
> That is, put in an intervening "./" in the
> name on the first line.
>
> I have a couple of examples like that in my
> disklist, and it all seems to work just fine.

Sounds interesting!  So I tried that.

localhost /home/./a-c /home {
vhost2-user-tar
include "./[a-c]*"
} 1 local

Unfortunately, an amcheck Daily returned a by-now-familiar message:
ERROR: localhost: [Nothing found to include for disk /home/./a-c]
Client check: 1 host checked in 1.223 seconds.  1 problem found.

Reverting the DLE to original, I then took a crack at it again, based on Christ's suggestion that the regex was invalid:

> Your regex is invalid. It says "the letters
> a, b, or c repeated any number of times" and
> would match a, aa, cab, but not bad or aaron.
> Try "./[a-c].*"

Ahh, okay, this makes sense (sorta, since I thought the regex would catch ANY directories starting with a*, b* c*....) I'll give this new method a go, however! I fix up the original DLE with the new regex:

localhost /home/a-c /home {
vhost2-user-tar
include "./[a-c].*"
} 1 local

AND THE SURVEY SAAAYS:
ERROR: localhost: [Nothing found to include for disk /home/a-c]
Client check: 1 host checked in 1.241 seconds.  1 problem found.

I then tried mixing John's diskname label with Christ's regex: same results. I tried Chris' suggestion for the diskname with Christ's regex: no love.

By all that I've read and all that I've searched, this SHOULD be working. I'm at wit's end, and I'd really like to get this working before I'm laid-off on Friday. :)

Anyone have ANY other ideas? Can it be a problem with Amanda 3.3.1 (under Centos 6, with tar 1.26) passing include directives to tar? Could it be a permission issue with tar? Beuller? Beuller? Anyone?

:)

~~Mike



Reply via email to