ADSM-L

Re: Raw striped logical volume giving write errors

1998-12-24 13:57:24
Subject: Re: Raw striped logical volume giving write errors
From: Bruce Elrick <belrick AT HOME DOT COM>
Date: Thu, 24 Dec 1998 12:57:24 -0600
I did a recent install with AIX 4.3.2 and ADSM 3.1.2.0/1 and used raw
logical volumes on SSA disk (my standard fare) and ran into the same
problem.  Our level 2 support here in Canada (Rejean Larivee) happened to
have another customer with the same problem.  That customer was given a
debugging kernel by AIX support and it showed no AIX errors.  Currently
they are getting special ADSM server code to get more information about the
error.

I have another customer who upgraded from v2 to v3 and ran into the same
problem; they backed out of the upgrade.  However, a better temporary
workaround is to use files in a JFS.  Take your disk, make filesystems, and
use dsmfmt to format large files, and use those for ADSM.  You done get the
errors then.  When they figure out what is causing the problem and fix it,
then you can switch back.

It would appear that the problem is restricted to ADSM v3 with SSA disks
and raw logical volumes for storage pool volumes.  Also, it may only affect
volumes > 2 GB because I have another customer that recently went v2 to v3
but had been on AIX 4.1 so had raw lv's that were all < 2 GB; they did not
experience the problem.

When an answer is found, I'm sure Rejean or I will post the result.

Cheers...
Bruce

Tom Smith wrote:

> Hello,
>
> we are using a 45 Gb (5 ssa disks) raw logical volume in our disk-
> storagepool. Last week we put caching off, because we run into
> the exceeded filesize error on our Informix backup.
>
> We had a write error in the actlog on this disk, which set the
> volume read-only. The result was a lot of backups not succeeding in
> time.
>
> We looked at the aix-errorreport and did not see any error at all.
> Just to be safe we replaced all 5 ssa disks.
>
> Last night we had the same.
>
> Does this sound familiar to anybody ?
> Maybe put caching back on (IBM strongly advises us not to do so !??)
>
> AIX 4.3.2, ADSM server 3.1.1.5
>
> Here4s the part of the actlog referring to it:
>
> Date/Time            Message
> --------------------
> ----------------------------------------------------------
> 12/22/1998 23:00:05  ANR0406I Session 15028 started for node NLAVCBRE
> (AIX)
>                       (Tcp/Ip 145.219.1.165(1639)).
> 12/22/1998 23:00:05  ANR0403I Session 15028 ended for node NLAVCBRE
> (AIX).
> 12/22/1998 23:03:39  ANR9999D blkdisk.c(1245): Error writing to disk
>                       /dev/rvol1.
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1899): Error writing to volume
>                       /dev/rvol1: execRc=-1, summaryRc=-1.
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986917
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986918
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986919
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986920
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986921
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986922
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
> more...   (<ENTER> to continue, 'C' to cancel)
> more...   (<ENTER> to continue, 'C' to cancel)
>                       2986923
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986924
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986925
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986926
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986927
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986928
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986929
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986930
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986931
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986932
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1899): Error writing to volume
>                       /dev/rvol1: execRc=-1, summaryRc=-1.
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986914
> more...   (<ENTER> to continue, 'C' to cancel)
> more...   (<ENTER> to continue, 'C' to cancel)
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986915
> 12/22/1998 23:03:39  ANR9999D dsalloc.c(1903): Volume /dev/rvol1,
> Logical Block
>                       2986916
> 12/22/1998 23:03:39  ANR1411W Access mode for volume /dev/rvol1 now set
> to
>                       "read-only" due to write error.
> 12/22/1998 23:03:39  ANR1411W Access mode for volume /dev/rvol1 now set
> to
>                       "read-only" due to write error.
> 12/22/1998 23:03:39  ANR1181E dstxn.c241: Data storage transaction
> 0:106613154
>                       was aborted.
> 12/22/1998 23:03:39  ANR0523W Transaction failed for session 14993 for
> node
>                       NLAVCBRE.AVERO.NL (XOpen/ADSM) - error on output
> storage
>                       device.
> 12/22/1998 23:03:39  ANR0524W Transaction failed for session 15027 for
> node
>                       LWLMSPN3 (WinNT) -  data transfer interrupted.
> 12/22/1998 23:03:39  ANR0532W smnode.c1125: Transaction 0:106613154 was
> aborted
>                       for session 14992 for node LWLMSP02 (NetWare) .
> 12/22/1998 23:03:39  ANE4952I (Sessio: 14992, Nod: LWLMSP02)  Total
> number of
>                       objects inspected:  703,421
> 12/22/1998 23:03:39  ANE4954I (Sessio: 14992, Nod: LWLMSP02)  Total
> number of
>                       objects backed up:   25,710
> 12/22/1998 23:03:39  ANE4958I (Sessio: 14992, Nod: LWLMSP02)  Total
> number of
>                       objects updated:          0
> more...   (<ENTER> to continue, 'C' to cancel)
>
> Thanks, Tom Smith
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
<Prev in Thread] Current Thread [Next in Thread>