Filesystem consistency checkers have historically had three overlappingpurposes:

1. to patch up the damage done when a machine was shut down partway through modifications to the filesystem.

2. to find and fix up problems caused by corrupted disk blocks(whether they're caused by a dying disk, a controller error thatscribbled random data on a track, or whatever).

3. to check for and repair structural errors created by operatingsystem bugs .

Fixing inconsistent filesystems is mostly or entirely obsolete thesedays, due to people moving to journaled filesystems that never

An increasing number of Red Hat/Fedora machines are dual architecture:they run both 64-bit and 32-bit x86 programs, and thus need to haveshared libraries and RPMs and so on for both of them. This canexpose some interesting issues when installing and upgrading RPMs;one of them is the dual architecture file ownership problem.

There are a lot of RPMs that install both architecture-dependent fileslike binaries and shared libraries and architecture-independent fileslike header files and manpages. The

Not all SAN RAID controllers support the idea of logical disks, whereyou can make a bunch of drives into a storage pool and then carve thestorage pool up into software-managed bits; some prefer the simplerand more straightforward approach of just exporting the pool itselfand staying out of the space management business.

Unfortunately, we need logical drives. The problem (and the reason) isthat logical drives are the only way to sensibly dynamically split thespace on a RAID controller between multiple fileservers. This is becauselogical