HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- blocking factor on tape drives
Operating System - HP-UX
1838225
Members
3761
Online
110125
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2007 03:44 PM
10-31-2007 03:44 PM
blocking factor on tape drives
i have 2 hpk460/9000 running hp-ux 11i and i'm getting application errors about blocking factors being different from the 2 machines. What does blocking factor mean and what and where do I check for the differences and how do make them the same to stop those errors?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2007 03:55 PM
10-31-2007 03:55 PM
Re: blocking factor on tape drives
Essentially it means the number of fixed size records per tape block.
For example a common tape block size is 512 bytes but this would be a rather slow integral i/o size so you might write with a blocking factor of 128 which would write 64KiB at a time.
The blocking factor is really specific to an application although dd can be used to reblock i/o by specifying different ibs= and obs= values to indicate the input block size and the output block size respectively.
For example, a cpio archive specified with the default 512-byte block could be speeded up tremendously by piping throgh dd.
dd if=/dev/rmt/0m ibs=64k obs=512 | cpio -icvdum
which would read in 128 512-byte blocks at a time and then reblock them to 512 byte chunks that cpio expects.
For example a common tape block size is 512 bytes but this would be a rather slow integral i/o size so you might write with a blocking factor of 128 which would write 64KiB at a time.
The blocking factor is really specific to an application although dd can be used to reblock i/o by specifying different ibs= and obs= values to indicate the input block size and the output block size respectively.
For example, a cpio archive specified with the default 512-byte block could be speeded up tremendously by piping throgh dd.
dd if=/dev/rmt/0m ibs=64k obs=512 | cpio -icvdum
which would read in 128 512-byte blocks at a time and then reblock them to 512 byte chunks that cpio expects.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2007 05:32 PM
10-31-2007 05:32 PM
Re: blocking factor on tape drives
For example, a cpio archive specified with the default 512-byte block could be sped up tremendously by piping through dd.
dd if=/dev/rmt/0m ibs=64k obs=512 | cpio -icvdum
>which would read in 128 512-byte blocks at a time and then reblock them to 512 byte chunks that cpio expects.
While a good example this is meaningless if you use a pipe. Anything sent to a pipe is unblocked and assumed to be a byte stream.
Of course you may be right in that you can't write more than 8 Kb to a pipe. You may want to reblock to 5120 so you can use the cpio -B option.
See comments in this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1163073
dd if=/dev/rmt/0m ibs=64k obs=512 | cpio -icvdum
>which would read in 128 512-byte blocks at a time and then reblock them to 512 byte chunks that cpio expects.
While a good example this is meaningless if you use a pipe. Anything sent to a pipe is unblocked and assumed to be a byte stream.
Of course you may be right in that you can't write more than 8 Kb to a pipe. You may want to reblock to 5120 so you can use the cpio -B option.
See comments in this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1163073
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP