Hello list I've been having the following error messages pop up in my kernel log: Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0, inode=827218527, rec_len=20275, name_len=73 Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670596: rec_len %% 4 != 0 - offset=0, inode=861103477, rec_len=95, name_len=95 Apr 12 04:08:17 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670597: rec_len %% 4 != 0 - offset=0, inode=1601531495, rec_len=30819, name_len=120 Apr 12 04:08:20 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670598: rec_len %% 4 != 0 - offset=0, inode=1634890872, rec_len=29795, name_len=111 Apr 12 04:08:32 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670599: rec_len %% 4 != 0 - offset=0, inode=1951614277, rec_len=12337, name_len=95 I've done some searching and talked to some people on another mailing list... I can't seem to figure out which device these errors occur on... I'd been told that the "device md(9,2)" ID indicates major 9 and minor 2, and I've also been told that the 9 is the SCSI channel once 8 is subtracted from is (so, 1 in this case), and that 2 is the SCSI Id of the offending device in that channel. So, I'm a little lost here. I figured the experts here could let me know how to map the reported ID numbers to a physical disk or RAID device. Thanks in advance! Mark Mark Cuss, B. Sc. Real Time Systems Analyst System Administrator CDL Systems Ltd Suite 230 3553 - 31 Street NW Calgary, AB, Canada Phone: 403 289 1733 ext 226 Fax: 403 282 1238 www.cdlsystems.com
Mark C., Try ls -l /dev/ | grep "9, 2" -Mark B. On Wed, 2004-04-14 at 14:43, Mark Cuss wrote:> Hello list > > I've been having the following error messages pop up in my kernel log: > > Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: > bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0, > inode=827218527, rec_len=20275, name_len=73 > Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: > bad entry in directory #2670596: rec_len %% 4 != 0 - offset=0, > inode=861103477, rec_len=95, name_len=95 > Apr 12 04:08:17 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: > bad entry in directory #2670597: rec_len %% 4 != 0 - offset=0, > inode=1601531495, rec_len=30819, name_len=120 > Apr 12 04:08:20 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: > bad entry in directory #2670598: rec_len %% 4 != 0 - offset=0, > inode=1634890872, rec_len=29795, name_len=111 > Apr 12 04:08:32 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: > bad entry in directory #2670599: rec_len %% 4 != 0 - offset=0, > inode=1951614277, rec_len=12337, name_len=95 > > I've done some searching and talked to some people on another mailing > list... I can't seem to figure out which device these errors occur on... > I'd been told that the "device md(9,2)" ID indicates major 9 and minor 2, > and I've also been told that the 9 is the SCSI channel once 8 is subtracted > from is (so, 1 in this case), and that 2 is the SCSI Id of the offending > device in that channel. > > So, I'm a little lost here. I figured the experts here could let me know > how to map the reported ID numbers to a physical disk or RAID device. > > Thanks in advance! > > Mark > > Mark Cuss, B. Sc. > Real Time Systems Analyst > System Administrator > CDL Systems Ltd > Suite 230 > 3553 - 31 Street NW > Calgary, AB, Canada > > Phone: 403 289 1733 ext 226 > Fax: 403 282 1238 > www.cdlsystems.com > > > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users >
Cecchi, Gianluca
2004-Apr-15 06:51 UTC
Question about EXT3 error messages in /var/log/messages
>Also, I'm not sure exactly how to directly get the directory name for an >inode, but you can list the contents of that directory, and go from >there.If the inode table is not corrupted, even if it may be time consuming, you can use the -inum switch of find comand, for each file system involved. gcecchi at pc-gcecchi:~$ ll -lid /home/gcecchi 776220 drwx------ 73 gcecchi users 4096 Apr 15 08:37 /home/gcecchi/ gcecchi at pc-gcecchi:/tmp# find /home -inum 776220 /home/gcecchi Gianluca