HPE GreenLake Administration
Operating System - HP-UX
1832609
Members
2262
Online
110043
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
Go to solution
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
05-06-2003 11:24 AM
05-06-2003 11:24 AM
After using the
"tar xvf" command to extract a file to magneto optical (MO) disk, I recived the following error: TAR error! blocksize changed. Does anyone know what this means?
The MO disk seems to have all the information, but I don't like unexplained errors.
"tar xvf" command to extract a file to magneto optical (MO) disk, I recived the following error: TAR error! blocksize changed. Does anyone know what this means?
The MO disk seems to have all the information, but I don't like unexplained errors.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2003 11:44 AM
05-06-2003 11:44 AM
Solution
This is probably due to the different blocking factors between your source and destination disks. Your MO drive has one factor (usually some increment of 512 bytes) and your disk has another. This is just a warning error, so if I were you, I'd forget it.
You can avoid this in the future by finding out the blocksize of your MO disk, and then making your tar file with the -b flag (tar cvfb /dev/rmt/0 1024 /PATH/FILE).
Chris
You can avoid this in the future by finding out the blocksize of your MO disk, and then making your tar file with the -b flag (tar cvfb /dev/rmt/0 1024 /PATH/FILE).
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2003 11:48 AM
05-06-2003 11:48 AM
Re: TAR
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2003 03:53 PM
05-06-2003 03:53 PM
Re: TAR
Hi Richard,
You should take one further step to ease your mind - read the tarball.
Do a:
tar tvf filename
And make sure it completes w/o errors. All this does is read it - it writes nothing.
IF you get an error, suspect that the extract may be incomplete.
This can come from something simple, harmless - and dumb - like creating the tarball in the same dir the input files come from. Or it could indicate the tarball itself is corrupt...
Either way I'm like you - I *want* to know. Can you compare size/chksum of the dest files to the source?
Rgds,
Jeff
You should take one further step to ease your mind - read the tarball.
Do a:
tar tvf filename
And make sure it completes w/o errors. All this does is read it - it writes nothing.
IF you get an error, suspect that the extract may be incomplete.
This can come from something simple, harmless - and dumb - like creating the tarball in the same dir the input files come from. Or it could indicate the tarball itself is corrupt...
Either way I'm like you - I *want* to know. Can you compare size/chksum of the dest files to the source?
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
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