08-01-2017
Hey
Hopefully it's better now.
Seems there was some corruption in the Database, and I ran some utilities to optimize and repair the db and it works much better now.
I think we may be "good to go!" now.
5 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
PUZZLED:
How can I search for posts on 'VI' if by the new rules (or maybe they are old) I get the messge:
"The search term you specified (vi) is under the minimum word length (3) and therefore will not be found. Please make this term longer.
If this term contains a wildcard, please make... (13 Replies)
Discussion started by: sierra_aar
13 Replies
2. Post Here to Contact Site Administrators and Moderators
Of late, when i start www.unix.com my system is
going to 100% CPU and takes lot of time to get
the information. I think this is happening after
adding the graphics on the page. Has anyone seen
this problem..Sorry to post this here.. (6 Replies)
Discussion started by: sssow
6 Replies
3. Answers to Frequently Asked Questions
Every now and then our users post complete programs to this site. It is especially important that these contributions don't get lost, so I will collect them here. Some of these programs are intended to demonstrate a programming technique and some are ready to run. As a guideline, the code... (0 Replies)
Discussion started by: Perderabo
0 Replies
4. Forum Support Area for Unregistered Users & Account Problems
Folks,
Hope this is not a newbie question, but it might end up being that.
I wanted to retrieve the source code for unix_linux_bench as directed on https://www.unix.com/linux-benchmarks/11175-instructions-linux-benchmarks.html
When one clicks on the links specified for download, the browser... (1 Reply)
Discussion started by: wagdalule
1 Replies
5. Post Here to Contact Site Administrators and Moderators
I've been having a problem connecting to the forum. I know it is just something with my computer but I have no idea what it is. It started last week.
Every time I connect I get this:
<?xml version="1.0" encoding="ISO-8859-1" ?>
- <rss version="2.0"... (2 Replies)
Discussion started by: Vi-Curious
2 Replies
LEARN ABOUT DEBIAN
fsck.reiser4
fsck.reiser4(8) reiser4progs manual fsck.reiser4(8)
NAME
fsck.reiser4 - the program for checking and repairing reiser4 filesystem.
SYNOPSIS
fsck.reiser4 [ options ] FILE
DESCRIPTION
fsck.reiser4 is reiser4 filesystem check and repair program.
CHECK OPTIONS
--check
the default action checks the consistency and reports, but does not repair any corruption that it finds. This option may be used on
a read-only file system mount.
--fix fixes minor corruptions that do not require rebuilding; sets up correct values of bytes unsupported by kernel in the case of trans-
parent compression.
--build-sb
fixes all severe corruptions in super blocks, rebuilds super blocks from scratch if needed.
--build-fs
fixes all severe fs corruptions, except super block ones; rebuilds reiser4 filesystem from the scratch if needed.
-L, --logfile
forces fsck to report any corruption it finds to the specified logfile rather then on stderr.
-n, --no-log
prevents fsck from reporting any kind of corruption.
-a, --auto
automatically checks the file system without any questions.
-q, --quiet
supresses gauges.
-r ignored.
PLUGIN OPTIONS
--print-profile
prints the plugin profile. This is the set of default plugins used for all parts of a filesystem -- format, nodes, files, directo-
ries, hashes, etc. If --override is specified, then prints modified plugins.
-l, --print-plugins
prints all plugins libreiser4 know about.
-o, --override TYPE=PLUGIN, ...
overrides the default plugin of the type "TYPE" by the plugin "PLUGIN" in the plugin profile.
COMMON OPTIONS
-V, --version
prints program version
-?, -h, --help
prints program help
-q, --quiet
suppress messages.
-y, --yes
assumes an answer 'yes' to all questions.
-f, --force
forces fsck to use whole disk, not block device or mounted partition.
-p, --preen
automatically repair minor corruptions on the filesystem.
-c, --cache N
tunes number of nodes in the libreiser4 tree buffer cache
REPORTING BUGS
Report bugs to <reiserfs-devel@vger.kernel.org>
SEE ALSO
debugfs.reiser4(8), mkfs.reiser4(8), measurefs.reiser4(8)
AUTHOR
This manual page was written by Vitaly Fertman <vitaly@namesys.com>
reiser4progs 05 February, 2004 fsck.reiser4(8)