Hi all,
  I am a guitar player. I have a hardware engineering background but
I am not a sys admin. I use computers as tools. Gentoo has been the
most stable and day to day productive tool I've ever used.

  That said, I seem to have file system problems on my external 1394
hard drives. I do not know if this is due to a recent move to
2.6.17-rt1, or bad maintenance on my part, or just bad luck. I've
noticed over the last couple of days that when using Aqualung (a
non-portage music player) I was getting some strange results. Songs
that used to work not working, strange timing, etc. Just weird stuff.

  This evening, for no good reason since I don't know what I am
doing, I decided to run fsck and let it look around and fix things if
it wanted to. I wouldn't know how to do any better. At the end of this
I wondered if there is really any value to a journaled file system?
Did it protect me? I cannot tell.

  Here is how these drives are mounted:

LABEL=music             /home/mark/music        ext3    rw,noauto,user  0 0
LABEL=audio1_94b        /home/mark/Audio/audio1 ext3    rw,noauto,user  0 0

Both partitions are on external 1394 drives, but not the same drives.

  Following down below are the sorts of problems I found using fsck.
The problem is it it didn't fix most of the problems I found with the
failing songs. Two seem to play now but the rest do not. Did the
journal dot work? Did I do something wrong?

  NOTE: The two Porcupine Tree tracks do not play so they seem to be damaged.

Thanks,
Mark


lightning ~ # fsck /dev/sdb1
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
audio1_94b has been mounted 57 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? no

Pass 4: Checking reference counts
Pass 5: Checking group summary information

audio1_94b: ********** WARNING: Filesystem still has errors **********

audio1_94b: 1492/3662848 files (19.1% non-contiguous), 4014481/7325632 blocks
lightning ~ #





lightning ~ # fsck /dev/sdc1
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
music: recovering journal
music contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 6115654 has illegal block(s).  Clear<y>? yes

Illegal block #1036 (1376776629) in inode 6115654.  CLEARED.
Illegal block #1037 (1927720517) in inode 6115654.  CLEARED.
Illegal block #1038 (2407185755) in inode 6115654.  CLEARED.
Illegal block #1039 (3472556839) in inode 6115654.  CLEARED.
Illegal block #1040 (2208668609) in inode 6115654.  CLEARED.
Illegal block #1041 (3293443330) in inode 6115654.  CLEARED.
Illegal block #1042 (375135243) in inode 6115654.  CLEARED.
Illegal block #1043 (1249063009) in inode 6115654.  CLEARED.
Illegal block #1044 (1201632328) in inode 6115654.  CLEARED.
Illegal block #1045 (2618458457) in inode 6115654.  CLEARED.
Illegal block #1046 (3116863600) in inode 6115654.  CLEARED.
Too many illegal blocks in inode 6115654.
Clear inode<y>? yes

Error reading block 12279239 (Attempt to read block from filesystem
resulted in short read) while reading indirect blocks of inode
6115655.  Ignore error<y>? yes

Force rewrite<y>? yes

Inode 6115655 has illegal block(s).  Clear<y>? yes

Illegal block #1036 (937597786) in inode 6115655.  CLEARED.
Illegal block #1037 (2426970144) in inode 6115655.  CLEARED.
Illegal block #1038 (2863076451) in inode 6115655.  CLEARED.
Illegal block #1039 (2251569750) in inode 6115655.  CLEARED.
Illegal block #1040 (1393869746) in inode 6115655.  CLEARED.
Illegal block #1041 (382868669) in inode 6115655.  CLEARED.
Illegal block #1042 (1149983442) in inode 6115655.  CLEARED.
Illegal block #1043 (4028337212) in inode 6115655.  CLEARED.
Illegal block #1044 (1162660121) in inode 6115655.  CLEARED.
Illegal block #1045 (1576522261) in inode 6115655.  CLEARED.
Illegal block #1046 (2289199545) in inode 6115655.  CLEARED.
Too many illegal blocks in inode 6115655.
Clear inode<y>? yes

Restarting e2fsck from the beginning...
music contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 1531447 (Attempt to read block from filesystem
resulted in short read) while reading indirect blocks of inode 719553.
Ignore error<y>? yes

Force rewrite<y>? yes

Inode 719553, i_blocks is 16144, should be 8304.  Fix<y>? yes


Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 719554: 1532443
Pass 1C: Scanning directories for inodes with multiply-claimed blocks.
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)

File /Christmas CDs/Star Bright (Vanessa Williams)/11 - Go Tell It On
The Mountain.ogg (inode #719554, mod time Fri Jan 28 14:51:35 2005)
 has 1 multiply-claimed block(s), shared with 0 file(s):
Multiply-claimed blocks already reassigned or cloned.

Pass 2: Checking directory structure
Entry '09 - Every Home Is Wired.ogg' in /Porcupine Tree/Signify
(6115649) has deleted/unused inode 6115654.  Clear<y>? yes

Entry '02 - Signify.ogg' in /Porcupine Tree/Signify (6115649) has
deleted/unused inode 6115655.  Clear<y>? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(1531448--1532427) -1532441 -(12277546--12280396)
Fix<y>? yes

Free blocks count wrong for group #46 (0, counted=981).
Fix<y>? yes

Free blocks count wrong for group #374 (2884, counted=5735).
Fix<y>? yes

Free blocks count wrong (2464583, counted=2468415).
Fix<y>? yes

Inode bitmap differences:  -(6115654--6115655)
Fix<y>? yes

Free inodes count wrong for group #374 (16328, counted=16330).
Fix<y>? yes

Free inodes count wrong (7317173, counted=7317175).
Fix<y>? yes


music: ***** FILE SYSTEM WAS MODIFIED *****
music: 8521/7325696 files (15.2% non-contiguous), 12182857/14651272 blocks
lightning ~ #
--
[email protected] mailing list

Reply via email to