09-17-2001
update
i've been on HP's site for weeks awaiting any new drivers, unfortunately this server is still being tested by red hat from what i understand, I did install the newer netraid drivers and was hoping this would fix it but it didn't. I'm basically always getting the root to lock up no matter what i log in with (gnome, kde) then once i kill it, i get those errors requiring me to use the fsck command. once i login as root the very first time, its fine, its after that 2nd reboot is where it locks. thanks for the info.
Lyghtnin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a SCO Openserver 5.0.5 server running RAID5 on the hp NETRAID-1M controller and it works just fine.
However, I cannot add a tape drive in. The standard SCSI card is a Symbios and I am using the 'slha' driver, but the system doesnt see the adaptor at SCO startup. The adaptor and... (1 Reply)
Discussion started by: christate
1 Replies
2. Shell Programming and Scripting
Hi ,
Could u please tell me What is lpr -P ?
Regards
Ashish Malviya:) (2 Replies)
Discussion started by: Ashishm
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
Can anybody tell me how to configure my printer to handle lpr -o landscape? Or what I need to do to print a text file in landscape format using the lpr command.
Thanks
Monique (1 Reply)
Discussion started by: squeakywheel
1 Replies
4. UNIX for Dummies Questions & Answers
good day!
i would just like to ask for advice regarding an lp problem i have..
we currently migrated a GIS appl from sol 2.6 to sol 8 but maintained the same version of jetadmin (for the appl plotters and printers). we are able to print files on a printer but not on a plotter. the... (1 Reply)
Discussion started by: maria_iris
1 Replies
5. UNIX for Advanced & Expert Users
--------------------------------------------------------------------------------
I tried to install SCO Open Server on HP2000 U3
drivers is amrid,
at install of SCO unnix only recognize non hot plugged devices
I have 2 HD of 40 GO under ID 0 and 1 but unix does not see them at boot ?? (0 Replies)
Discussion started by: Bernardschmitt
0 Replies
6. UNIX for Dummies Questions & Answers
I tried to install SCO Open Server on HP2000 U3
drivers is amrid,
at install of SCO unnix only recognize non hot plugged devices
I have 2 HD of 40 GO under ID 0 and 1 but unix does not see them at boot ?? (1 Reply)
Discussion started by: Bernardschmitt
1 Replies
7. UNIX for Dummies Questions & Answers
This server had an HP C1555 tape drive that appears to have gone belly up. We found a replacement, an HP C1537, that we want to install. We did the hardware thing, with power off, of course, but when the box was rebooted it did not seem to recognize the drive. At least the backup software did... (4 Replies)
Discussion started by: akirson
4 Replies
8. Red Hat
Dear experts,
Can any one suggest, whether RHEL is supported in HP NetServer LH6000 U3
Thanks (2 Replies)
Discussion started by: ./hari.sh
2 Replies
9. Shell Programming and Scripting
Hi Guys,
I am using the following command in unix for printing.
pr -t -l34 "$1" | lpr -r
But i was not able to see the file getting deleted. Is anything wrong with the command.
---------- Post updated at 10:56 AM ---------- Previous update was at 10:38 AM ----------
Hi... (0 Replies)
Discussion started by: Kar1234
0 Replies
10. UNIX for Beginners Questions & Answers
Hi ,
We are trying to automate Printing the word document directly from the Server level to a Printer.
We have printer registered and command I use is
lp -d printername 1234.doc
Even though the program completes fine, a print does not reach to the printer for word document. In... (4 Replies)
Discussion started by: PrashantTalele
4 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)