GNU bug report logs -
#29790
How to extract overridden tarred file
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29790 in the body.
You can then email your comments to 29790 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gzip <at> gnu.org:
bug#29790; Package
gzip.
(Wed, 20 Dec 2017 20:10:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
narasimha kumar <narasimhakumar1111 <at> gmail.com>:
New bug report received and forwarded. Copy sent to
bug-gzip <at> gnu.org.
(Wed, 20 Dec 2017 20:10:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi when I perform the tar it has tarred but after removing the original
file.i mistakanley pressed the previous command to tar then it has
overriden and size showed 45.so pls help me to extract the original or
tarred file.
#tar -cvzf server.log.tar.gz server.log
#ls -ltr-> it showed size 270mb server.log.tar.gz
And then mistakenly I pressed previous command
#tar -cvzf server.log.tar.gz server.log
It showed file is missed
#ls -ltr-> it shows size 45 server.log.tar.gz
Please provide me the solution for this
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gzip <at> gnu.org:
bug#29790; Package
gzip.
(Wed, 20 Dec 2017 20:23:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 29790 <at> debbugs.gnu.org (full text, mbox):
tag 29790 notabug
thanks
On 12/20/2017 01:21 PM, narasimha kumar wrote:
> Hi when I perform the tar it has tarred but after removing the original
> file.i mistakanley pressed the previous command to tar then it has
> overriden and size showed 45.so pls help me to extract the original or
> tarred file.
> #tar -cvzf server.log.tar.gz server.log
> #ls -ltr-> it showed size 270mb server.log.tar.gz
> And then mistakenly I pressed previous command
> #tar -cvzf server.log.tar.gz server.log
> It showed file is missed
> #ls -ltr-> it shows size 45 server.log.tar.gz
> Please provide me the solution for this
You sent your question to the gzip mailing list, but gzip wasn't
responsible for your data loss. While I feel sorry for your loss,
there's not much I can do beyond pointing you to this coreutils FAQ:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#I-used-rm-to-remove-a-file_002e-How-can-I-get-it-back-now_003f
Meanwhile, I'm tagging this thread so that the bug-tracker doesn't keep
it open as a gzip bug.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
Added tag(s) notabug.
Request was from
Paul Eggert <eggert <at> cs.ucla.edu>
to
control <at> debbugs.gnu.org.
(Fri, 01 Apr 2022 00:06:01 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
29790 <at> debbugs.gnu.org and narasimha kumar <narasimhakumar1111 <at> gmail.com>
Request was from
Paul Eggert <eggert <at> cs.ucla.edu>
to
control <at> debbugs.gnu.org.
(Fri, 01 Apr 2022 00:06:01 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Fri, 29 Apr 2022 11:24:09 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 210 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.