Administrace komentářů

Ahoj. Jedu na Gentoo 2.6.24-gentoo-r4 64bit 2SMP. MB od Intelu s P35, 2GB DDR2, C2D 2.33GHz, 2x400GB Seagate ES v SW md RAIDu 1. Na stroji jede mailový systém Exim, FTP ProFTPD, webserver Apache a Lighttpd. Vše pro cca 30 uživatelů. Na discích je vytvořen klasický md raid 1. Výpis oddílů:

df -lh
Filesystem            Size  Used Avail Use% Mounted on
/dev/md/3              94G  8.1G   86G   9% /
udev                   10M  196K  9.9M   2% /dev
/dev/md/4             273G  6.1G  254G   3% /home
shm                   1.9G     0  1.9G   0% /dev/shm

A teď k problému. Vše začalo tak, že mi uživatel hlásil, že se nemůže připojit na IMAP účet. Začal jsem tedy pátrat a zjistil jsem, že na FS md3,4 jsou chyby. Dal jsem je tedy na odpojených svazcích opravit a vše zase jelo OK. Problém je v tom, že ty chyby se tvoří stále. Čím déle to běží bez FSCK tím je to horší :(. Přitom HW je fyzicky v pořádku - testováno na jiné desce, cpu, ram, hdd. Pořád vykazuje chyby :(. Výpis s fsck...

fsck -n /dev/md3
fsck 1.40.6 (09-Feb-2008)
fsck.jfs version 1.1.8, 03-May-2005
processing started: 4/22/2008 10.38.51
Filesystem is currently mounted.
WARNING: Checking a mounted filesystem does not produce dependable results.
The current device is:  /dev/md3
Block size in bytes:  4096
Filesystem size in blocks:  24416768
**Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
**Phase 2 - Count links
Incorrect link counts detected in the aggregate.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
Directory entries for unallocated files have been detected.
**Phase 4 - Report Problems
File system object FF86059 is linked as: /var/spool/exim/scan/1JoE1j-0001gD-OV
The path(s) refer to an unallocated file.
File system object FF106534 is linked as: /var/spool/exim/scan/1JoE1k-0001gF-RA
The path(s) refer to an unallocated file.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
**Phase 7 - Verify File/Directory Allocation Maps
Errors detected in the Fileset File/Directory Allocation Map control information. (F)
Errors detected in the Fileset File/Directory Allocation Map. (F)
**Phase 8 - Verify Disk Allocation Maps
Incorrect data detected in disk allocation structures.
Incorrect data detected in disk allocation control structures.
 97667072 kilobytes total disk space.
   198024 kilobytes in 42216 directories.
  8203764 kilobytes in 435944 user files.
        0 kilobytes in extended attributes
   480572 kilobytes reserved for system use.
 89180760 kilobytes are available for use.
File system checked READ ONLY.
ERRORS HAVE BEEN DETECTED.  Run fsck with the -f parameter to repair.
Filesystem is dirty.
Filesystem is dirty but is marked clean.  In its present state,
the results of accessing /dev/md3 (except by this utility) are undefined.

fsck -n /dev/md4
fsck 1.40.6 (09-Feb-2008)
e2fsck 1.40.6 (09-Feb-2008)
Warning!  /dev/md4 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/md4 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (69960966, counted=69960944).
Fix? no
Free inodes count wrong (18087044, counted=18087043).
Fix? no
/dev/md4: ********** WARNING: Filesystem still has errors **********
/dev/md4: 91004/18178048 files (0.3% non-contiguous), 2733130/72694096 blocks

Po opravě jsou FS jako clean, ale stačí počkat hodinku a jsou tam zase chyby :(. Nevíte někdo kde by mohl být problém? Je to docela kritická věc, protože se jedná o produkční server :(... Díky za jakékoli podněty...