Netapp Infrastructure SOP

Provides primary mirrors and additional storage in IAD2

Contact Information


Fedora Infrastructure Team


#fedora-admin, sysadmin-main, releng


batcave01, virt servers, application servers, builders, releng boxes


Provides primary mirrors and additional storage in IAD2


At present we have three netapps in our infrastructure. One in TPA, RDU and IAD2. For purposes of visualization its easiest to think of us as having 4 netapps, 1 TPA, 1 RDU and 1 IAD2 for public mirrors. And an additional 1 in IAD2 used for additional storage not related to the public mirrors.

Public Mirrors

The netapps are our primary public mirrors. The canonical location for the mirrors is currently in IAD2. From there it gets synced to RDU and TPA.


Snapshots on the IAD2 netapp are taken hourly. Unfortunately the way it is setup only Red Hat employees can access this mirror (this is scheduled to change when PHX becomes the canonical location but that will take time to setup and deploy). The snapshots are available, for example, on wallace in:


IAD2 NFS Storage

There is a great deal of storage in IAD2 over NFS from the netapp there. This storage includes the public mirror. The majority of this storage is koji however there are a few gig worth of storage that goes to wiki attachments and other storage needs we have in IAD2.

You can access all of the nfs share shares at:




The netapp is provided by RHIS and as a result they also control access. Access is controlled by IP mostly and some machines have root squashed. Worst case scenario if batcave01 is not accessible, just bring another box up under its IP address and use that for an emergency.


There are hourly and nightly snapshots on the netapp. They are available in:



We have iscsi deployed in a number of locations in our infrastructure for xen machines. To get a list of what xen machines are deployed with iscsi, just run lvs:

lvs /dev/xenGuests

Live migration is possible though not fully supported at this time. Please shut a xen machine down and bring it up on another host. Memory is the main issue here.

Updating LVM

iscsi is mounted all over the place and if one xen machine creates a logical volume the other xen machines will have to pick up those changes. To do this run:

vgchange -a y

Mounting ISCSI

On reboots sometimes the iscsi share is not remounted. This should be automated in the future but for now run:

iscsiadm -m discovery -tst -p
sleep 1
iscsiadm -m node -T -p -l
sleep 1
vgchange -a y