SUMMARY: ODS 4.1 replica DB

2007-12-24 20:27:00

It would appear that this is normal. The flags will be reset once the
system is rebooted.

Thanks to the following:

Chris Miles <cmiles at connect.com.au>
Przemyslaw Bak <przemolicc at poczta.fm>
hmnguyen at verizongni.com
Alvaro F. Figueroa Cabezas <fede2 at fuerzag.ulatina.ac.cr>

-Paul

On Wed, 25 Jul 2001, Paul Kanz wrote:

>
> I'm in the process of documenting replacing a failed drive that is under
> ODS 4.1 control and I have a question about replica DBs.
>
> After I recreate the Meta DBs via metadb -a /dev/dsk/c0t1d0s7 and I do a
> metadb, I get the following results:
>
> # metadb
> flags first blk block count
> a m p luo 16 1034 /dev/dsk/c0t0d0s7
> a p luo 1050 1034 /dev/dsk/c0t0d0s7
> a u 16 1034 /dev/dsk/c0t1d0s7
> a u 1050 1034 /dev/dsk/c0t1d0s7
>
> Is it normal for the flags for the new replicas to be set this way? What
> will it take to get the p,l, and o flags to be reset?
>
> The system is a E220, running Solairs 2.6. I'm mirroring the file
> systems.
>
> -Paul
>
>
>

Actived: 0 answers; - size: 1716 bytes; - view related info - Similar thread

Comments

Got something to say?

You must be logged in to post a comment.

thatsjava.com

SUMMARY: ODS 4.1 replica DB

Comments