AFS Cell Management Tools and Techniques Russ Allbery March 20, - - PowerPoint PPT Presentation

▶
afs cell management
SMART_READER_LITE
LIVE PREVIEW

AFS Cell Management Tools and Techniques Russ Allbery March 20, - - PowerPoint PPT Presentation

Oct 11, 2023 138 likes •233 views

Stanford University March 20, 2004 1 AFS Cell Management Tools and Techniques Russ Allbery March 20, 2004 Russ Allbery (rra@stanford.edu) Stanford University March 20, 2004 2 Introduction Stanford has 2.6TB of data in AFS, in 54,686

slide-1
SLIDE 1

Stanford University March 20, 2004 1

AFS Cell Management

Tools and Techniques

Russ Allbery March 20, 2004

Russ Allbery (rra@stanford.edu)

slide-2
SLIDE 2

Stanford University March 20, 2004 2

Introduction

  • Stanford has 2.6TB of data in AFS, in 54,686 volumes (as of March 1st). (1TB

user home directories, 600MB data, 100MB groups and departments, 280MB classes).

  • Administration takes around an hour a week, mostly creating unusual

volumes, moving volumes around, and upgrading servers.

  • Tools presented here developed by Neil Crellin.
  • http://www.eyrie.org/˜eagle/software/

Russ Allbery (rra@stanford.edu)

slide-3
SLIDE 3

Stanford University March 20, 2004 3

Contents

  • Volume creation and management
  • Managing ACLs
  • Analysis and reporting
  • Replicated volumes
  • Monitoring with Nagios

Russ Allbery (rra@stanford.edu)

slide-4
SLIDE 4

Stanford University March 20, 2004 4

Creating Volumes

  • volcreate wrapper to balance where volumes are placed
  • Mapping volume types to servers
  • Size policy (2-4GB max for ease of moving volumes)
  • Automated log volume creation with volcreate-logs
  • Wrapper scripts for volume types (create-user, etc.)

Russ Allbery (rra@stanford.edu)

slide-5
SLIDE 5

Stanford University March 20, 2004 5

Managing Volumes

  • partinfo wrapper for usage information
  • mvto utility for all volume moving
  • Generating volume lists with vos listvol
  • Checking for unreleased volumes with unreleased
  • Balacing: why or why not, and possible overkill solutions
  • volnuke wrapper to delete volumes

Russ Allbery (rra@stanford.edu)

slide-6
SLIDE 6

Stanford University March 20, 2004 6

Managing ACLs

  • One PTS group per course, deptartment, or group volume
  • fsr wrapper for users
  • Be careful of IP-based ACLs: subnets work best, better to use runauth

and machine srvtabs over IP ACLs

  • Log volume ACLS (lik) and the potential problems
  • Think about fs cleanacl
  • Unix directory owners and their special ACLs

Russ Allbery (rra@stanford.edu)

slide-7
SLIDE 7

Stanford University March 20, 2004 7

Tracking Volumes

  • Hierarchical naming scheme for volumes
  • Mount point database (mtpt, loadmtpt, cleanmtpts)
  • Nightly load into an Oracle database
  • Nightly reports from the Oracle database (released volumes, high accesses,

volumes moved, unreleased changes, missing mount points)

  • Monthly usage reports

Russ Allbery (rra@stanford.edu)

slide-8
SLIDE 8

Stanford University March 20, 2004 8

Replicated Volumes

  • Replication helps when server is down, not when it’s slow
  • How many replicas do you want? (2-4)
  • volcreate and server geographic locations
  • How RW and RO paths work: replicate the whole path
  • Delegated volume release ability (remctl and afs-backend)
  • frak to find changes
  • Restoring a RW from a RO with vos dump and vos restore

Russ Allbery (rra@stanford.edu)

slide-9
SLIDE 9

Stanford University March 20, 2004 9

Monitoring with Nagios

  • Basic tool: bos status
  • Monitor VLDB servers with udebug:

fs 7001, pt 7002, vl 7003 (alphabetical order)

  • Available disk with vos partinfo
  • Blocked connections and rxdebug
  • AFS logs and kill -TSTP
  • Nightly problem reports from Oracle database

Russ Allbery (rra@stanford.edu)