[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-tar] Ongoing TAR Verify Option Problems
From: |
John L . Males |
Subject: |
[Bug-tar] Ongoing TAR Verify Option Problems |
Date: |
Tue, 24 Aug 2004 17:42:08 -0400 |
Hi,
***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****
Ok, this is real simple, tar an entire Linux system with the --verify
and --totals tar option.
The problems that occur are:
1) Files that have not changed are listed as changed in verify phase,
example messages below.
2) The get a variety of messages that franky do not make much sense
as being valid issues, examples listed below.
3) "Total bytes written: 160358400 (153MiB, 423KiB/s)" incorrectly
calculated when tar file is verified. Current calculation of /s is
half of actual written speed. i.e. the time used to calculate
included the verify time and supposed to be the "written" time taken.
The /s is correct when one does not use the verify option.
4) During the verify, the tar program will go into an infinite loop
and never complete the verify.
All of the above can be duplicated 100% of time. I therefore expect
you should have no problems duplicating the above. The 1.14 release
seem to add in the "File fragment" messages which never happened with
the SuSE tar-1.13.25-298 version. The infinite loop and compare file
on verify problems have continued to be onging problems.
Example messages of verify part of tar:
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/221737E1d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/7465FA39d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/CB16B1D9d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/E1CDF7E4d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/40C11E5Bd01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/BE718502d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/FB62FB26d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/6ADE135Ad01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/FBBA3863d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/Cache/38045CA1d01: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/cookies.txt: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/XUL.mfasl: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/localstore.rdf: File fragment at 512 is not a
hol
e
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/install.log: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/cert8.db: Contents differ
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/panels.rdf: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/abook.mab: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/search.rdf: File fragment at 512 is not a hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/downloads.rdf: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/secmod.db: Contents differ
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/mimeTypes.rdf: File fragment at 512 is not a
hole
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/24642119.s: Contents differ
mnt/data-ide-80gb/004/LinuxBackup/20040202/Pre-e2fsck/sdc1/johnl/.moz
il
la/johnl/mv7987t3.slt/24642214.w: Contents differ
Helpful changes:
1) Informational message that verify has started.
2) The "Total bytes written: " message written out at end of tar file
written and closed, so it is indicated before verify starts.
3) A "Total bytes compared: " message for end of verify.
4) A message that indicates if "Total bytes written: " and "Total
bytes compared: " are different.
Regards,
John L. Males
Willowdale, Ontario
Canada
24 August 2004 (15:00 -) 17:42
==================================================================
"Boooomer ... Boom Boom, how are you Boom Boom"
Boomer 1985 (Born)
04 September 1991 - 08 February 2000 18:50
"How are you Mr. Sylvester?"
"... Grunt Grunt" ... quick licks of nose
Sylvester 1989 (estimated Born)
09 February 1992 - 19 January 2003 23:25
***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****
Please BCC me by replacing after the "@" as follows:
TLD = The last three letters of the word "internet"
Domain name = The first four letters of the word "software",
followed by the first four letters of the word
"homeless".
My appologies in advance for the jumbled eMail address
and request to BCC me, but SPAM has become a very serious
problem. The eMail address in my header information is
not a valid eMail address for me. I needed to use a valid
domain due to ISP SMTP screen rules.
Please note: You may experience delays in my replies. I will
reply.
This is due to major restoration activity to my riser
section of the building.
My internet access will be limited to a couple weekday
evenings. Weekend access will be a bit better but
limited as an indirect consequence of the restoration
work.
If for any reason you need a more immediate reply or
fail to receive a reply, please phone and leave a
message. If you do leave a phone message, please note
that I may not be able to hear the message and/or
reply until the evening. This will be due to the
extensive noise levels of the restoration work
activity drowning out most other volume levels of
sound.
The work starts 22 July 2002. Based on similar
experience to other sections of the building I would
estimate the major noise element of the work to be
about 4+ weeks for my riser. There will be secondary
instances once other ajacent riser sections are done
that will have a similar impact, but for lessor
periods of time.
My appologies in advance, but this is mandated work
that must be done.
pgpp6Db0TP9Nh.pgp
Description: PGP signature
- [Bug-tar] Ongoing TAR Verify Option Problems,
John L . Males <=