Last Modified: Monday, 01-Nov-2004 09:18:07 EST
2004.10.22 -- Proposal for temporary and frames storage
2004.11.01 -- Revised Proposal for temporary and frames storage
The status quo
Temporary space was previously distributed as follows:
| GB | name | server | policy | comments
|
| 12 | /srv/temp | bunter | 7 days
|
|
| 273 | /srv/frames | bunter | 21 days
|
|
| 216 | /srv/frames2 | rz01 | 21 days
| old version of linux
|
Problems with status quo ante
- Not enough frames space
- Regular abuse of touch to exceed time limits
- Frames is used instead of temp for non-frames storage, in part
because:
- Temp is too small
- rz01 has 100Mb only, an old version of linux, and /frames2 is ext2.
- Best frames performance is linux to linux
Available resources
Beyond existing filesystems, we had available:
- >1TB of R5 on each of raid1 and raid2.
- >1TB (not mirrored) on Bunter
Proposal
The following steps to be applied in roughly the order shown
-
Expand /srv/temp on bunter to about 100GB
- (completed 2004.10.29)
Create filesystem on spare 1TB partition on raid2. Combine existing
/srv/frames and /srv/frames2 on this parition. Clients will mount it as
/srv/frames from server vs1. Old frames space on bunter and rz01 now
becomes available. Files are deleted after 21 days.
-
Establish a 1TB partition on raid1. This will be exported RO, and will be
mounted by clients as /srv/oldframes from server fr2: (initially aliased
to ds1). A nightly rsync job copies new files from /srv/frames to
/srv/oldframes and updates their timestamps, but does not delete anything
from oldframes, even if it has been deleted from frames. Files are
deleted after 21 days.
-
/bck is moved off rz01 to available space on bunter. Rz01 upgraded with Gb
ethernet and new OS.
-
(?) /bck moved back to entire (500MB) rz01 in R5 config.
Last Modified: Monday, 01-Nov-2004 09:18:07 EST