對這文章發表回應

發表限制: 非會員 可以發表

發表者：冷日發表時間： 2007/7/9 4:43:23

All XRF users will be able to read from and write to the tape drive. Since it is the only SCSI tape drive it has the device allocation of /dev/st0 and its status can be checked using the mt command and data archived using tar command. Typical commands that are used during archiving are listed below with a brief explanation:

mt –f /dev/st0 status |Check status of the first SCSI tape drive /dev/st0

tar cvf /dev/st0 my_dir |Write contents of my_dir to tape

tar tvf /dev/st0 |Look at or list contents of previously archived tape

tar -xvf /dev/st0 parent_dir/my_dir |Extract contents of my_dir

mt= magnetic tape; tar= tape archive; -c= create; -v= verbose;-x= extract; st= scsi tape; -t= list; -f= file(system).

Reading DDS-3/4 media

[root@raccoon /]# mt -f /dev/st0 status |Check status of tape drive
SCSI 2 tape drive: File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x25 (DDS-3).
General status bits on (45010000):
BOT WR_PROT ONLINE IM_REP_EN |Beginning of tape; write-protected tape

[root@raccoon DDS]# tar tvf /dev/st0  |List contents of tape
drwxr-xr-x soma/users     0 2001-09-19 15:04:14 TapeDDS3-024/
drwxr-xr-x soma/users     0 2001-09-18 13:44:17 TapeDDS3-024/4mmtp116/
drwxr-xr-x soma/users     0 2001-09-18 12:39:05 TapeDDS3-024/4mmtp116/AdamekF1

[root@raccoon DDS]# tar-xvf /dev/st0  |Extract contents of the tape media
fire2/soma/
fire2/soma/all.list
fire2/soma/Blaber_Fgf/
fire2/soma/Blaber_Fgf/fgf_2/
fire2/soma/Blaber_Fgf/fgf_2/snap.runlist
fire2/soma/Blaber_Fgf/fgf_2/snap_0_001.img

[root@raccoon DDS]# tar -xvf /dev/st0 fire2/soma/Blaber_Fgf      |Extract contents of only Blaber_Fgf directory and NOT all
fire2/soma/Blaber_Fgf/
fire2/soma/Blaber_Fgf/fgf_2/
fire2/soma/Blaber_Fgf/fgf_2/snap.runlist
fire2/soma/Blaber_Fgf/fgf_2/snap_0_001.img

[root@raccoon DDS]# mt -f /dev/st0 offline |Eject the tape

Writing DDS-3/4 media

[root@raccoon /]# mt -f /dev/st0 status |Check status of tape drive
SCSI 2 tape drive: File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x25 (DDS-3).
General status bits on (45010000):
BOT ONLINE IM_REP_EN |Beginning of tape; ready to write

[soma@spruce ~]$ tar -cvvf /dev/st0 tmp/     |Write contents of tmp directory
drwxrwxr-x soma/marccd       0 2003-04-30 16:41:21 tmp/
-rwxr-xr-x soma/marccd  103756 2000-12-22 23:53:35 tmp/font.exe
-rw------- soma/marccd 7223800 2001-05-16 11:36:03 tmp/abc10003.osc
-rw-rw-r-- soma/marccd    1737 2001-08-07 15:10:20 tmp/uniqueify.log

[soma@spruce ~]$ tar -cvvf /dev/st0 erase    |Erase contents of tape. Careful!!!
[soma@spruce ~]$ tar -cvf /dev/st0 my_dir | & tee dds4-listing & |Simultaneously (tee) archive data from my_dir to a tape and write the filenames into another file (dds4-listing).

spruce.sb.fsu.edu (128.186.103.109; RedHat Linux 8.0)
Spruce.sb.fsu.edu the 650 MHz Linux machine located in KLB 410A that controls marCCD165 data collection has an internal DDS-4 tape drive. This SCSI DDS-4 tape drive can read and write to DDS2, DDS3 and DDS4 media. However, it is best to use DDS4 media, since it has a native/compressed capacity of 20/40 GB. IP/CCD data will compress anywhere between 10 to 60% depending upon the level of detail in the original image. The same tar and mt commands shown above can be used to archive data using this tape drive. Please read the mt and tar man pages or check with Soma, or Mike for further help.
General Information & Trouble Shooting of Tape Drive/Media
原文出處

標題
發表者名
內容圖示
內容	樣本 [詳情...]
認證碼		注意事項：預覽不需輸入認證碼，僅真正發送文章時才會檢查驗證碼。認證碼有效期10分鐘，若輸入資料超過10分鐘，請您備份內容後，重新整理本頁並貼回您的內容，再輸入驗證碼送出。
選項	不使用表情圖示