huge volume for builds, releases, etc. in scl3



7 years ago
4 years ago


(Reporter: dustin, Assigned: dparsons)



We'll need a heck of a lot of space to replace all of

and any other volumes that are added between now and shutting down the netapps in scj1.

Once this is up, we'll need to keep the volume reasonably in sync with the above mounts, so that we can make it official with a relatively short downtime (make the sjc1 volumes read-only, one final rsync, and start writing to the scl3 volume)

Are there any additional parameters we need to determine before then?
Blocks: 728451
(In reply to Dustin J. Mitchell [:dustin] from comment #0)

Total Used  Mounted from:

6.5T  6.4T
4.2T  3.8T
500G  254G

 14T  4.0T
====  ====
 26T   15T  Totals

The last three appear to be different mount points on the same filesystem on the server end, so they collectively share the same disk space.

Comment 2

7 years ago
I've started an initial ndmpcopy for mpt-netapp-a:/vol/ftp_stage to scl3-na1b:/vol/ftp_stage. It will take a long time.

Comment 3

7 years ago
Making use of our SnapMirror demo licenses to copy this, instead of ndmpcopy.


7 years ago
Assignee: server-ops → dparsons

Comment 4

7 years ago
The space is available for all the mounts listed above. All data is snapmirrored except for the stuff on, which is equallogic. That data will need to be migrated when the systems are ready to move. When that time comes, please open a bug for that.
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.