[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference aosg::lsm

Title:LSM
Moderator:SMURF::SHIDERLY
Created:Mon Jan 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:803
Total number of notes:2852

796.0. "How do you disable block-change logging?" by CSC32::TRENTA () Tue May 20 1997 19:19

    Hi,
    
    I am trying to disable block-change logging on a LSM mirrored
    volume and am not having success.
    
    I followed the documentation to use:
    
    voledit -g ase_mir_dg set logtype=none volume 
    
    and got an error:
    
    voledit: variable logtype not recognized or cannot be changed
    
    
    So I checked the fields by doing a volprint -g ase_mir_dg -mvps
    and saw that the field is log_type instead of logtype.
    However when I issue that command I get the same error.
    
    I even did a volume stop to see if I needed the volume to be 
    disabled but that did nothing.
    
    Any suggestions as to what I am doing wrong?
    
    Thanks in advance,
    
    Debbie Trenta
    Lucent/AT&T Support
T.RTitleUserPersonal
Name
DateLines
796.1wrong commandNNTPD::"[email protected]"[email protected]Wed May 21 1997 11:538
Hi!

You want to use the 'volume' command to disable logging, i.e

	volume -g ase_mir_dg set logtype=none <volume name>


[Posted by WWW Notes gateway]
796.2stop the volume first.BACHUS::DEVOSManu Devos NSIS Brussels 856-7539Thu May 22 1997 09:214
    And also, the volume must be stopped to change the log_type !!!
    
    Manu.
    
796.3do it on-line with volsdNNTPD::&quot;[email protected]&quot;Thu May 22 1997 09:4863
To disable BCL on-line (i.e., while volume's actively being used), dissociate
the logging subdisk so there's <2.  For example:

   # showfdmn usr_domain

                  Id              Date Created  LogPgs  Domain Name
   30bf53df.000ebe60  Fri Dec  1 14:13:35 1995     512  usr_domain

     Vol   512-Blks        Free  % Used  Cmode  Rblks  Wblks  Vol Name
      1L     819200      334944     59%     on    128    128 
/dev/vol/rootdg/vo
lrz0g
   # volprint -ht volrz0h
   DG NAME         GROUP-ID
   DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   PUBPATH
   V  NAME         USETYPE      KSTATE   STATE    LENGTH   READPOL  PREFPLEX
   PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT   ST-WIDTH
MOD
   SD NAME         PLEX         PLOFFS   DISKOFFS LENGTH   DISK-NAME    DEVICE

   v  volrz0h      gen          ENABLED  ACTIVE   838444   SELECT   -
   pl volrz0h-01   volrz0h      ENABLED  ACTIVE   838444   CONCAT   -       
RW
   sd rz1h-04      volrz0h-01   LOG      1778976  1        rz1h         rz1h
   sd advfs_rz0h-01 volrz0h-01   0        0        838444   advfs_rz0h   rz0h
   pl volrz0h-02   volrz0h      ENABLED  ACTIVE   838444   CONCAT   -       
RW
   sd rz1h-05      volrz0h-02   LOG      1778977  1        rz1h         rz1h
   sd rz1h-01      volrz0h-02   0        0        838444   rz1h         rz1h
   # volprint -l volrz0h
   Volume:   volrz0h
   info:     len=838444
   type:     usetype=gen
   state:    state=ACTIVE kernel=ENABLED
   assoc:    plexes=volrz0h-01,volrz0h-02
   policies: read=SELECT (round-robin) exceptions=GEN_DET_SPARSE
   flags:    open writecopy writeback
   logging:  type=BLKNO loglen=1 serial=0/7 (enabled)
   device:   minor=6 bdev=40/6 cdev=40/6 path=/dev/vol/rootdg/volrz0h
   perms:    user=root group=system mode=0600
   # volsd dis rz1h-05
   # volprint -l volrz0h
   Volume:   volrz0h
   info:     len=838444
   type:     usetype=gen
   state:    state=ACTIVE kernel=ENABLED
   assoc:    plexes=volrz0h-01,volrz0h-02
   policies: read=SELECT (round-robin) exceptions=GEN_DET_SPARSE
   flags:    open writeback
   logging:  type=BLKNO loglen=1 serial=0/9 (disabled)
   device:   minor=6 bdev=40/6 cdev=40/6 path=/dev/vol/rootdg/volrz0h
   perms:    user=root group=system mode=0600

To re-enable BCL while the volume's actively being used, just
associate the BCL subdisk to the plex(s) so there's 2 of them.
For example:

   # volsd aslog volrz0h-02 rz1h-05

Hope that helps.


[Posted by WWW Notes gateway]
796.4minor correction in exampleNNTPD::&quot;[email protected]&quot;Thu May 22 1997 09:5513
Oops, volrz0h was being used for var_domain instead of usr_domain
in that example (762.3).


# showfdmn var_domain

               Id              Date Created  LogPgs  Domain Name
30bf5442.0008bdf0  Fri Dec  1 14:15:14 1995     512  var_domain

  Vol   512-Blks        Free  % Used  Cmode  Rblks  Wblks  Vol Name
   1L     838444      160672     81%     on    128    128 
/dev/vol/rootdg/volrz0h
[Posted by WWW Notes gateway]
796.5Whow, even possible online !!!BACHUS::DEVOSManu Devos NSIS Brussels 856-7539Fri May 23 1997 08:5413
    Thanks, 
    
    I didn't know that we could do that online.
    
    May I suggest for the facility of our relationship (between the field
    and Engineering) that you sign your reply with your firstname,
    particularly when the Account name is cryptic like [email protected].
    We are all member of a team facing the same LSM problems, and I think
    that knowing the folks helping us makes the contacts more warmly. It
    helps also identifying who is responding and how accurate can be his
    reply.
    
    Regards, Manu.