All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <j.dittmer@portrix.net>
To: linux-kernel@vger.kernel.org
Subject: ext3 on raid5 failure
Date: Sun, 18 Jan 2004 11:27:54 +0100	[thread overview]
Message-ID: <400A5FAA.5030504@portrix.net> (raw)

Hello,

I've recently upgraded my fileserver to 2.6.1 and since then I had to 
reboot two times because of the following errors. Afterwards the 
blockdevice was set readonly, so I couldn't even remount the partition 
rw. Interestingly after reboot the raid is not marked dirty. So is this 
an ext3 only error?
This never happenend with 2.4.23pre6-aa3 or any other 2.4 version which 
run for about a year on this system without any (linux caused) downtime.
What I can try to debug this? The first time it happened after about 3 
or 4 days uptime, the second time after about 1 day. So it's pretty 
reproducible.

Thanks,

Jan

EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory 
#9783034: rec_len % 4 != 0 - offset=0, inode=1846971784, rec_len=33046, 
name_len=154
Aborting journal on device dm-1.
ext3_abort called.
EXT3-fs abort (device dm-1): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only

and

EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory 
#8422045: rec_len % 4 != 0 - offset=0, inode=655393188, rec_len=1998, 
name_len=0
Aborting journal on device dm-1.
ext3_abort called.
EXT3-fs abort (device dm-1): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device dm-1) in start_transaction: Journal has aborted


$ cat /proc/mdstat
Personalities : [raid5]
read_ahead 1024 sectors
md0 : active raid5 ide/host2/bus1/target1/lun0/part1[3]
ide/host2/bus1/target0/lun0/part1[1]
ide/host2/bus0/target1/lun0/part1[2]
ide/host2/bus0/target0/lun0/part1[0]
ide/host0/bus1/target0/lun0/part1[4]
       468872704 blocks level 5, 4k chunk, algorithm 2 [5/5] [UUUUU]

$ vgdisplay:
   --- Volume group ---
   VG Name               myraid
   System ID
   Format                lvm2
   Metadata Areas        1
   Metadata Sequence No  7
   VG Access             read/write
   VG Status             resizable
   MAX LV                256
   Cur LV                2
   Open LV               2
   Max PV                256
   Cur PV                1
   Act PV                1
   VG Size               447.15 GB
   PE Size               4.00 MB
   Total PE              114470
   Alloc PE / Size       114470 / 447.15 GB
   Free  PE / Size       0 / 0
   VG UUID               0xPsvH-t204-YlD4-jVAW-mYgK-ndF5-nEVOTk

$ lvdisplay:
   --- Logical volume ---
   LV Name                /dev/myraid/lvol0
   VG Name                myraid
   LV UUID                X47Raw-ZGgE-PZ4I-F1o3-lYX9-TVQ1-KIWqrs
   LV Write Access        read/write
   LV Status              available
   # open                 1
   LV Size                100.00 GB
   Current LE             25600
   Segments               1
   Allocation             next free (default)
   Read ahead sectors     0
   Block device           254:1

   --- Logical volume ---
   LV Name                /dev/myraid/lvol1
   VG Name                myraid
   LV UUID                LgnX1d-r3BP-3u7t-yLQb-iRke-544J-v7uBBd
   LV Write Access        read/write
   LV Status              available
   # open                 1
   LV Size                347.15 GB
   Current LE             88870
   Segments               1
   Allocation             next free (default)
   Read ahead sectors     0
   Block device           254:2

$ mount -l
/dev/mapper/myraid-lvol1 on /mnt/data/1 type ext3 (rw)
/dev/mapper/myraid-lvol0 on /mnt/backup type ext3 (rw)


             reply	other threads:[~2004-01-18 10:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-18 10:27 Jan Dittmer [this message]
2004-01-18 18:02 ` ext3 on raid5 failure Mike Fedyk
2004-01-19 15:30   ` Theodore Ts'o
2004-01-23  8:22     ` Jan Dittmer
2004-01-27 19:08       ` Theodore Ts'o
2004-01-28 10:54         ` Jan Dittmer
2004-01-29 11:44           ` Theodore Ts'o
2004-02-04  9:24             ` Bas Mevissen
2004-02-04  9:43               ` Nigel Cunningham
2004-02-04 11:38                 ` Bas Mevissen
2004-02-04 20:49                   ` Nigel Cunningham
2004-02-17 23:14                     ` Pavel Machek
2004-02-17 23:58                       ` Kiko Piris
2004-02-06 19:18               ` Theodore Ts'o
2004-02-09  8:55                 ` Bas Mevissen
2004-02-18  3:07                   ` Bill Davidsen
2004-02-19  9:27                     ` Bas Mevissen
2004-02-19 19:47                       ` Bill Davidsen
2004-01-28 11:06         ` Jan Dittmer
2004-02-19  2:32     ` Leandro Guimarães Faria Corsetti Dutra
2004-02-19  8:07       ` Jan Dittmer
2004-02-19 13:50         ` Leandro Guimarães Faria Corcete Dutra
2004-02-19 14:58           ` Leandro Guimarães Faria Corsetti Dutra
  -- strict thread matches above, loose matches on Subject: below --
2004-02-25 17:45 Muhammad L.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=400A5FAA.5030504@portrix.net \
    --to=j.dittmer@portrix.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.