Nix Server Question : Uploaded gigs of files and downloaded ...

no.


8chars

thx

It can happen - but it happens very slowly - I have a box that is 3% fragmented after years of use.

Defrag : NO

However depending on the amount of data you removed and are replacing it is possible it could need fsck. This all depends on the type of server you have, speed, and amount of data you replaced.

Also nobody can tell you yes or no to this anser unless they have had access in the server.

fsck is the *nix equivelant of defrag (fsck = File System Check)

you can run fsck once in a while wont hurt anything. I've had to do it once in a while to help the drives relize they have free space when they are claiming they don't.

side note if its a freebsd box and you have it rebooted due to high loads or whatever it *MIGHT* not come back and will be stuck and the drive was unclean/marked dirty. usally you have to run a fsck -y /

simple way around this
edit /etc/rc.conf and add this line
fsck_y_enable="YES"

or just type this in a shell as root
echo fsck_y_enable="YES" >> /etc/rc.conf

The first form of fsck preens a standard set of filesystems or the speci-
fied filesystems. It is normally used in the script /etc/rc during auto-
matic reboot. Here fsck reads the table /etc/fstab to determine which
filesystems to check. Only partitions in fstab that are mounted ``rw,''
``rq'' or ``ro'' and that have non-zero pass number are checked.
Filesystems with pass number 1 (normally just the root filesystem) are
checked one at a time. When pass 1 completes, all remaining filesystems
are checked, running one process per disk drive. The disk drive contain-
ing each filesystem is inferred from the longest prefix of the device
name that ends in a digit; the remaining characters are assumed to be the
partition designator. In preening mode, filesystems that are marked
clean are skipped. Filesystems are marked clean when they are unmounted,
when they have been mounted read-only, or when fsck runs on them success-
fully.

The kernel takes care that only a restricted class of innocuous filesys-
tem inconsistencies can happen unless hardware or software failures
intervene. These are limited to the following:
Unreferenced inodes
Link counts in inodes too large
Missing blocks in the free map
Blocks in the free map also in files
Counts in the super-block wrong

These are the only inconsistencies that fsck with the -p option will cor-
rect; if it encounters other inconsistencies, it exits with an abnormal
return status and an automatic reboot will then fail. For each corrected
inconsistency one or more lines will be printed identifying the filesys-
tem on which the correction will take place, and the nature of the cor-
rection. After successfully correcting a filesystem, fsck will print the
number of files on that filesystem, the number of used and free blocks,
and the percentage of fragmentation.

If sent a QUIT signal, fsck will finish the filesystem checks, then exit
with an abnormal return status that causes an automatic reboot to fail.
This is useful when you want to finish the filesystem checks during an
automatic reboot, but do not want the machine to come up multiuser after
the checks complete.

Without the -p option, fsck audits and interactively repairs inconsistent
conditions for filesystems. If the filesystem is inconsistent the opera-
tor is prompted for concurrence before each correction is attempted. It
should be noted that some of the corrective actions which are not cor-
rectable under the -p option will result in some loss of data. The
amount and severity of data lost may be determined from the diagnostic
output. The default action for each consistency correction is to wait
for the operator to respond yes or no. If the operator does not have
write permission on the filesystem fsck will default to a -n action.

Fsck has more consistency checks than its predecessors check, dcheck,
fcheck, and icheck combined.

The following flags are interpreted by fsck.

-b Use the block specified immediately after the flag as the
super block for the filesystem. Block 32 is usually an
alternate super block.

-f Force fsck to check `clean' filesystems when preening.

-l Limit the number of parallel checks to the number specified
in the following argument. By default, the limit is the num-
ber of disks, running one process per disk. If a smaller
limit is given, the disks are checked round-robin, one
filesystem at a time.

-m Use the mode specified in octal immediately after the flag as
the permission bits to use when creating the lost+found
directory rather than the default 1777. In particular, sys-
tems that do not wish to have lost files accessible by all
users on the system should use a more restrictive set of per-
missions such as 700.

-q Do a quick check to determine if the filesystem was unmounted
cleanly.

-y Assume a yes response to all questions asked by fsck; this
should be used with great caution as this is a free license
to continue after essentially unlimited trouble has been
encountered.

-n Assume a no response to all questions asked by fsck except
for `CONTINUE?', which is assumed to be affirmative; do not
open the filesystem for writing.

-c Convert the filesystem to the specified level. Note that the
level of a filesystem can only be raised. There are cur-
rently four levels defined:

0 The filesystem is in the old (static table)
format.

1 The filesystem is in the new (dynamic table)
format.

2 The filesystem supports 32-bit uid's and gid's,
short symbolic links are stored in the inode,
and directories have an added field showing the
file type.

3 If maxcontig is greater than one, build the
free segment maps to aid in finding contiguous
sets of blocks. If maxcontig is equal to one,
delete any existing segment maps.

In interactive mode, fsck will list the conversion to be made
and ask whether the conversion should be done. If a negative
answer is given, no further operations are done on the
filesystem. In preen mode, the conversion is listed and done
if possible without user interaction. Conversion in preen
mode is best used when all the filesystems are being con-
verted at once. The format of a filesystem can be determined
from the first line of output from dumpfs(8).

If no filesystems are given to fsck then a default list of filesystems is
read from the file /etc/fstab.

Inconsistencies checked are as follows:
1. Blocks claimed by more than one inode or the free map.
2. Blocks claimed by an inode outside the range of the filesys-
tem.
3. Incorrect link counts.
4. Size checks:
Directory size not a multiple of DIRBLKSIZ.
Partially truncated file.
5. Bad inode format.
6. Blocks not accounted for anywhere.
7. Directory checks:
File pointing to unallocated inode.
Inode number out of range.
Dot or dot-dot not the first two entries of a directory
or having the wrong inode number.
8. Super Block checks:
More blocks for inodes than there are in the filesystem.
Bad free block map format.
Total free block and/or free inode count incorrect.

Orphaned files and directories (allocated but unreferenced) are, with the
operator's concurrence, reconnected by placing them in the lost+found
directory. The name assigned is the inode number. If the lost+found
directory does not exist, it is created. If there is insufficient space
its size is increased.

Because of inconsistencies between the block device and the buffer cache,
the raw device should always be used.

[/sarcasm]

And how many people actually understood this?

Also does this means you have changed your original answer from no to yes after a few QUALIFIED techs gave a correct answer ?

LMFAO just messing with you man ... How ya been anyways?

"[/sarcasm]"

I really hope you're not referring to yourself when saying "qualified tech"

And my answer still stands, the question was simple and the answer
was simple.
No need to bullshit everyone with assumptions

someone who gets it!

Yeah everyone knows I don't have a clue as to what I'm doing.

not a damn clue glad to see your still with us mark!

thx guys

** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1546 files, 22785 used, 41710 free (750 frags, 5120 blocks, 1.2% fragmentation)