Tools

I Want To

Home » Historical Section » System Call Traces

Historical Section : System Call Traces

The Historical Section includes all traces that are older than 10 years.

System Call I/O Traces typically reflect operating system calls to the file system.

The following traces are free to download under the terms of the SNIA Trace Data Files Download License. Please note that cookies must be enabled within your browser in order to download traces.
For questions about downloading using a shell script, see Using Shell Scripts, and for more information about downloading using a Windows batch script, see Using Batch Scripts.

Displaying all 9 Traces

View Additional Columns

Trace Name	Details	Related Tools	Year Recorded	Timespan	Record Count	File Size
TraceFS Sample Traces	Sample traces collected with the TraceFS system. Long Description Sample traces of three benchmark runs collected with the TraceFS tracing system. Additional information about TraceFS can be found at the following URL: http://www.filesystems.org/project-tracefs.html Short Description	This traces are stored in a binary format. The code for opening them can be found at http://www.filesystems.org/project-tracefs.html.	2007	13 days	1 Million	57.7 MB
HP FSTraces	Five system call traces taken in 2000 Long Description Five system call traces taken in 2000 Short Description		2000	10 days		9.9 GB
LASR Traces	System-call I/O traces of thirteen machines taken in 2000 and 2001. Long Description I/O traces taken at the system-call level in 2000 and 2001 as part of a security research project. The traces cover thirteen computers used for software development by CS researchers. The longest trace (machine02) runs from June 2000 to August 2001. The traces are further described in a README file. Short Description	The traces are in the SEER format; a tool to read the traces can be found here.	1999-2001	over 1 year	566 Million	3.17 GB
LASR Traces (ASCII)	System-call I/O traces of thirteen machines taken in 2000 and 2001. Long Description I/O traces taken at the system-call level in 2000 and 2001 as part of a security research project. The traces cover thirteen computers used for software development by CS researchers. The longest trace (machine02) runs from June 2000 to August 2001. The traces are further described in a README file. Short Description	The traces have been converted to ASCII using the binary tool to read the Seer format.	1999-2001	over 1 year	566 Million	5.49 GB
LASR Traces (Binary)	System-call I/O traces of thirteen machines taken in 2000 and 2001. Long Description I/O traces taken at the system-call level in 2000 and 2001 as part of a security research project. The traces cover thirteen computers used for software development by CS researchers. The longest trace (machine02) runs from June 2000 to August 2001. The traces are further described in a README file. Short Description	The traces can be read using the Seer reading tool.	1999-2001	over 1 year	566 Million	3.17 GB
Seer Traces (ASCII)	ASCII format of Seer Traces. System-call traces (excluding read/write) of nine laptops, taken in 1996 and 1997. Long Description I/O traces taken at the system-call level, excluding reads and writes but including opens, closes and all other I/O calls, and including process-related calls such as fork and exec. The traces cover nine laptop computers used for software development by CS researchers, some with very heavy activity. The longest trace (norgay) extends from April 2, 1996, to January 28, 1997; the shortest (crockett) is October 11 to November 19, 1996. All traces contain gaps representing times when the machines were rebooted or the trace software failed. Activity by the superuser is generally omitted. Additional information about these traces can be found here. Short Description	These traces are already in readable (ASCII) format.	1996-1997	about 1 year	72 Million	792 MB
Seer Traces	System-call traces (excluding read/write) of nine laptops, taken in 1996 and 1997. Long Description I/O traces taken at the system-call level, excluding reads and writes but including opens, closes and all other I/O calls, and including process-related calls such as fork and exec. The traces cover nine laptop computers used for software development by CS researchers, some with very heavy activity. The longest trace (norgay) extends from April 2, 1996, to January 28, 1997; the shortest (crockett) is October 11 to November 19, 1996. All traces contain gaps representing times when the machines were rebooted or the trace software failed. Activity by the superuser is generally omitted. Additional information about these traces can be found here. Short Description	A tool to read these traces is here.	1996-1997	about 1 year	72 Million	553 MB
CMU DFS Traces (ASCII)	System-call traces from the CMU Coda project, 1991-93. Long Description This is a set of system-call traces collected for the Carnegie Mellon Online Coda Project. The traces cover 33 hosts running Mach. Several different workloads are represented, including file server, workstation, and time-sharing systems. Short Description	The traces have been converted to ASCII using the CMU-DFStrace Reading Tools	1991-1993	almost 3 years	1.01 Billion	13.7 GB
CMU DFS Traces	System-call traces from the CMU Coda project, 1991-93. Long Description This is a set of system-call traces collected for the Carnegie Mellon Online Coda Project. The traces cover 33 hosts running Mach. several different workloads are represented, including file server, workstation, and time-sharing systems. Short Description	These traces are in a binary format. Tools for processing the traces can be found here	1991-1993	almost 3 years	1 Billion	22.6 GB

Displaying all 9 Traces

Contact Us

Related Resources

Member Links

SNIA IOTTA TWG

Join IOTTA

Featured Events

FAST '20
(Feb 24–27, 2020)
Santa Clara, CA
NSDI '20
(Feb 25–27, 2020)
Santa Clara, CA
Data Centre World 2020
(Mar 11–12, 2020)
London, United Kingdom
ASPLOS 2020
(Mar 16–20, 2020)
Lausanne, Switzerland
EuroSys '20
(Apr 27–30, 2020)
Crete, Greece
Computex Taipei
(Jun 2–6, 2020)
Taipei, Taiwan

All Upcoming Events