is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" wrote on 2010-04-19
17:40:57:
> [image removed]
>
> Re: Linux Client failing with ANS1999E error
>
> James Choate
>
> to:
>
>> On Tue, 20 Apr 2010 08:39:11 -0400, Lindsay Morris
>> said:
> The TSM admin is like the canary in the coal mine.
> (Wait, that's a terrible analogy .. they end up dead...)
Terrible because it's inaccurate, or terrible because we don't like
the implications?
Your viewers want to know. :)
-
Ben said
TSM backups are great for sniffing out filesystem problems. ;-)
I would add "and network problems, and application problems , and database
performance problems ..."
The TSM admin is like the canary in the coal mine.
(Wait, that's a terrible analogy .. they end up dead...)
--
our friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" wrote on 2010-04-19
17:40:57:
> [image removed]
>
> Re: Linux Client failing with ANS1999E error
>
> James Choate
>
> to:
>
> ADSM-L
>
> 2010-04-19 21:09
>
> Sent
On Apr 19, 2010, at 5:41 PM, James Choate wrote:
> I am looking for the longest fully qualified file name on the system.
>
> An error=6 might be indicating ENAMETOOLONG (The only errno that equals 6 in
> Linux).
Errno 6 is ENXIO. FWIW, I've accumulated some notes on it over time...
ENXIO
I just ran an fsck on /public/proval-old, No errors were found on that mount.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ben
Bullock
Sent: Monday, April 19, 2010 10:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Linux Client failing with
...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: Monday, April 19, 2010 10:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Linux Client failing with ANS1999E error
On Apr 19, 2010, at 11:45 AM, James Choate wrote:
> 04/19/2010 08:56:26 --- SCHEDULEREC OBJECT BEGIN TEST_SCHEDULE
> 04/19/2010 08
It seems to me that /public/proval-old is a filesystem of some sort since
there was no other virtualmountpoint messages. Maybe it's a loopback
mount or something?
Try putting this in there to exclude it:
exclude.fs /public/proval-old
If that doesn't work, provide the output of a "df"
If it doe
On Apr 19, 2010, at 11:45 AM, James Choate wrote:
04/19/2010 08:56:26 --- SCHEDULEREC OBJECT BEGIN TEST_SCHEDULE
04/19/2010 08:40:00 04/19/2010 08:56:27 Incremental backup of volume
'/'
04/19/2010 08:56:27 Incremental backup of volume '/boot'
04/19/2010 08:56:27 Incremental backup of volume '/pu
I have seen something like this before. I would guess that according to the
log, that something is corrupt in '/public/proval-old' . Perhaps a bad inode,
invalid file name or just plain corrupt file. I would do some 'ls -l' in and
around that directory looking for a bad file.
TSM backups are gr
04/19/2010 08:38:26
04/19/2010 08:38:26 Schedule Name: TEST_SCHEDULE
04/19/2010 08:38:26 Action:Incremental
04/19/2010 08:38:26 Objects:
04/19/2010 08:38:26 Options:
04/19/2010 08:38:26 Server Window Start: 08:40
On Apr 19, 2010, at 6:22 AM, Richard Sims wrote:
Jim -
That evidence says that the warranted changes have not been made to
the client to correct the initially reported problems, which
continue. A thorough review of that client should be conducted,
starting with 'dsmc query option' and 'dsmc qu
Jim -
That evidence says that the warranted changes have not been made to
the client to correct the initially reported problems, which
continue. A thorough review of that client should be conducted,
starting with 'dsmc query option' and 'dsmc query inclexcl', as the
administration of that client
I have attached the dsmsched.log & dsmerror.log
Dsmsched.log file
04/17/2010 18:08:35 TSM Backup-Archive Client Version 5, Release 5, Level 2.0
04/17/2010 18:08:35 Querying server for next scheduled event.
04/17/2010 18:08:35 Node Name: CLLINUX1
04/17/2010 18:08:35 Session established with server
iday, April 16, 2010 1:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Linux Client failing with ANS1999E error
Jim -
The backup log doesn't match timewise with the other logs, but I'll assume they
are from multiple attempts of the same thing.
It looks like the /public/proval-old object is ba
I have not seen this error message before.
I think that if you remove the following line from the opt file your errors
will go away.
VIRTUALMOUNTPOINT /
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of James
Choate
Sent: Friday, April 16,
Jim -
The backup log doesn't match timewise with the other logs, but I'll assume they
are from multiple attempts of the same thing.
It looks like the /public/proval-old object is bad in some way, and needs
examination. If that system hasn't had fsck's in a while, it may be time.
I'd code an Exc
17 matches
Mail list logo
