09-18-2008
recover your files from a recent backup. If you don't have a backup consider the files gone. It might be possible to recover them but it is not trivial.
If you have a .snapshot directory on the file system then it sounds like you have a netapp filer or something like that. If you do, then the recovery of the file should be as simple as copying that file back to the original place.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi Friends,
How can I Restore the Files present under "lost+found" Directory of a FileSystem (in Solaris & Tru64 OS) to their original Locations.
Now-a-days I am loosing lots of files in 2 of my Machines,
One running Solaris8 and other Tru64(Digital) Unix.
Thanx in... (1 Reply)
Discussion started by: dhasarath
1 Replies
2. UNIX for Dummies Questions & Answers
hiyas
I am trying to get back to the root directory: I went into MAIL directory and now I can't get back to the root directory. What are the commands...
I have '?' coming up and I cannot proceed with this, HELP
Cheers (1 Reply)
Discussion started by: etravels
1 Replies
3. Shell Programming and Scripting
Hi,
I am trying to figure out if there is a way to make linux take me back to the previous directory I was working in. For instance, I am in
/home/username/directory1
Then if I cd into /home/username/directory1/temp1/temp2/temp3
I would like to immediately go back to the previous... (2 Replies)
Discussion started by: Legend986
2 Replies
4. IP Networking
Hi every body,
Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber.
Note it is direct connection & there is no switches between the servers.
I'm concern about using HBA adapters, it is possible or not.
Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies
5. UNIX for Dummies Questions & Answers
Hi there,
I am putting a script together to apply a label to a directory structure but it can't be done down the directory structure, i must start at the end and work back and this is what i am struggling with.
for example, i will supply a path as an argument to a script, e.g
... (11 Replies)
Discussion started by: surfbus78
11 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys
I accidently deleted a directory( and the files in it) in unix using 'rm -rf' :)
Is there any procedure/script/command to recover the same?
Your help is highly apperciated
-thanks
Subramanya (1 Reply)
Discussion started by: sgbhat
1 Replies
7. UNIX for Dummies Questions & Answers
Some time ago I was using a linux system and someone had set up and
alias called "back" that got me back to the directory I was last in, which
was very useful. I've now switched to using a mac, and don't have those aliases available. Can anyone tell me how I could make a an alias that
would... (2 Replies)
Discussion started by: ac2011
2 Replies
8. Shell Programming and Scripting
this is what i have to find the files modified within the past 24 hours
find . -mtime -1 -type f -print0 | xargs -0 tar rvf "$archive.tar"
however i need to save/name this archive as the current date (MM-DD,YYYY.tar.gz)
how do i doo this (1 Reply)
Discussion started by: bugenhagen_
1 Replies
9. UNIX for Dummies Questions & Answers
~/assign1b/assign1/york/>
your current directory is york
how do you go back to your home directory with using relative pathname?
not using cd alone?
:( (3 Replies)
Discussion started by: blackendstars
3 Replies
LEARN ABOUT DEBIAN
bup-fsck
bup-fsck(1) General Commands Manual bup-fsck(1)
NAME
bup-fsck - verify or repair a bup repository
SYNOPSIS
bup fsck [-r] [-g] [-v] [--quick] [-j jobs] [--par2-ok] [--disable-par2] [filenames...]
DESCRIPTION
bup fsck is a tool for validating bup repositories in the same way that git fsck validates git repositories.
It can also generate and/or use "recovery blocks" using the par2(1) tool (if you have it installed). This allows you to recover from dam-
aged blocks covering up to 5% of your .pack files.
In a normal backup system, damaged blocks are less important, because there tends to be enough data duplicated between backup sets that a
single damaged backup set is non-critical. In a deduplicating backup system like bup, however, no block is ever stored more than once,
even if it is used in every single backup. If that block were to be unrecoverable, all your backup sets would be damaged at once. Thus,
it's important to be able to verify the integrity of your backups and recover from disk errors if they occur.
WARNING: bup fsck's recovery features are not available unless you have the free par2(1) package installed on your bup server.
WARNING: bup fsck obviously cannot recover from a complete disk failure. If your backups are important, you need to carefully consider
redundancy (such as using RAID for multi-disk redundancy, or making off-site backups for site redundancy).
OPTIONS
-r, --repair
attempt to repair any damaged packs using existing recovery blocks. (Requires par2(1).)
-g, --generate
generate recovery blocks for any packs that don't already have them. (Requires par2(1).)
-v, --verbose
increase verbosity (can be used more than once).
--quick
don't run a full git verify-pack on each pack file; instead just check the final checksum. This can cause a significant speedup
with no obvious decrease in reliability. However, you may want to avoid this option if you're paranoid. Has no effect on packs
that already have recovery information.
-j, --jobs=numjobs
maximum number of pack verifications to run at a time. The optimal value for this option depends how fast your CPU can verify packs
vs. your disk throughput. If you run too many jobs at once, your disk will get saturated by seeking back and forth between files
and performance will actually decrease, even if numjobs is less than the number of CPU cores on your system. You can experiment
with this option to find the optimal value.
--par2-ok
immediately return 0 if par2(1) is installed and working, or 1 otherwise. Do not actually check anything.
--disable-par2
pretend that par2(1) is not installed, and ignore all recovery blocks.
EXAMPLE
# generate recovery blocks for all packs that don't
# have them
bup fsck -g
# generate recovery blocks for a particular pack
bup fsck -g ~/.bup/objects/pack/153a1420cb1c8*.pack
# check all packs for correctness (can be very slow!)
bup fsck
# check all packs for correctness and recover any
# damaged ones
bup fsck -r
# check a particular pack for correctness and recover
# it if damaged
bup fsck -r ~/.bup/objects/pack/153a1420cb1c8*.pack
# check if recovery blocks are available on this system
if bup fsck --par2-ok; then
echo "par2 is ok"
fi
SEE ALSO
bup-damage(1), fsck(1), git-fsck(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-fsck(1)