The way to fsck a filesystem without anything dangerous happening is to use the -n switch:
with the -n meaning, whatever the question is the answer is no. Therefore, no modifications/corrections to the filesystem but the extent of any damage will be shown.
The opposite is:
which means all questions are automatically answered yes meaning correct everything, and yes, in the case of severe damage, can destroy the filesystem completely.
If damage is limited then you can run fsck again with neither -n or -y and answer each question yourself individually to carry out corrections.
I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work
i need to change the mouse configuration, ... (2 Replies)
hello!
when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ?
kindly help me
thanks (1 Reply)
I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
hello guys.
I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message.
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Hi there guys.
I just got this new SCO version and i'm having some problem printing from shell,
This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error.
/dev/fd/7: /usr/lib/lp/sysv/7: not found.
... (1 Reply)
Hi guys,
I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Dear members
when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config.
i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 Replies
LEARN ABOUT DEBIAN
bup-damage
bup-damage(1) General Commands Manual bup-damage(1)NAME
bup-damage - randomly destroy blocks of a file
SYNOPSIS
bup damage [-n count] [-s maxsize] [--percent pct] [-S seed] [--equal]
DESCRIPTION
Use bup damage to deliberately destroy blocks in a .pack or .idx file (from .bup/objects/pack) to test the recovery features of bup-fsck(1)
or other programs.
THIS PROGRAM IS EXTREMELY DANGEROUS AND WILL DESTROY YOUR DATA
bup damage is primarily useful for automated or manual tests of data recovery tools, to reassure yourself that the tools actually work.
OPTIONS -n, --num=numblocks
the number of separate blocks to damage in each file (default 10). Note that it's possible for more than one damaged segment to
fall in the same bup-fsck(1) recovery block, so you might not damage as many recovery blocks as you expect. If this is a problem,
use --equal.
-s, --size=maxblocksize
the maximum size, in bytes, of each damaged block (default 1 unless --percent is specified). Note that because of the way bup-
fsck(1) works, a multi-byte block could fall on the boundary between two recovery blocks, and thus damaging two separate recovery
blocks. In small files, it's also possible for a damaged block to be larger than a recovery block. If these issues might be a
problem, you should use the default damage size of one byte.
--percent=maxblockpercent
the maximum size, in percent of the original file, of each damaged block. If both --size and --percent are given, the maximum block
size is the minimum of the two restrictions. You can use this to ensure that a given block will never damage more than one or two
git-fsck(1) recovery blocks.
-S, --seed=randomseed
seed the random number generator with the given value. If you use this option, your tests will be repeatable, since the damaged
block offsets, sizes, and contents will be the same every time. By default, the random numbers are different every time (so you can
run tests in a loop and repeatedly test with different damage each time).
--equal
instead of choosing random offsets for each damaged block, space the blocks equally throughout the file, starting at offset 0. If
you also choose a correct maximum block size, this can guarantee that any given damage block never damages more than one git-fsck(1)
recovery block. (This is also guaranteed if you use -s 1.)
EXAMPLE
# make a backup in case things go horribly wrong
cp -a ~/.bup/objects/pack ~/bup-packs.bak
# generate recovery blocks for all packs
bup fsck -g
# deliberately damage the packs
bup damage -n 10 -s 1 -S 0 ~/.bup/objects/pack/*.{pack,idx}
# recover from the damage
bup fsck -r
SEE ALSO bup-fsck(1), par2(1)BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown-bup-damage(1)