Ext3-fs Error Ext3_readdir Directory Contains A Hole At Offset
Contents |
error messages mean? Date: Thu Sep ext3 fs error fortigate 19 13:17:35 2002 I recvieve these errors in messages. ext3-fs error (device sd(8,17)) About the same time, I notice corrupted files (PHP WEB FILES). No other file unable to read inode block fortigate types seem to get corrupted (havent checked all the files obviously) Any Help would be great Thanks Joe Here are the error
Fortinet Support
messages... Aug 23 08:10:12 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:10:12 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:11:01 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:11:40 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:11:42 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:12:39 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Aug 23 08:12:40 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: directory #2 contains a hole at offset 0 Sep 19 04:03:10 wolfserver kernel: EXT3-fs error (device ida0(72,1)): ext3_readdir: bad entry in directory #3129573: directory entry across blocks - offset=124, inode=884983, rec_len=12860, name_len=55 Follow-Ups: Re: What Do These error messages mean? From: Brian Ashe [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
Up Home Storage Reviews Enterprise Reviews Consumer Reviews Enterprise VMmark Benchmark MarkMail Benchmark MarkLogic Benchmark MySQL OLTP Benchmark FIO Synthetic Benchmark Enterprise Test Lab Storage Webinars Leaderboard Reference Guides Forums View New Content Forums Members Calendar Reliability Survey About SR Review Process Sponsors Consumer Test Platforms View New Content Storage Review Forums Members Calendar More All Activity Home Storage Hardware Hard Disk Drives (HDD) Ext3 Fs Error Sign in to follow this Followers 0 Ext3 Fs Error Started by blakerwry, March 25, https://www.redhat.com/archives/redhat-list/2002-September/msg01950.html 2004 5 posts in this topic blakerwry 0 StorageReview Patron Patron 0 4840 posts Location:Kansas City USA Posted March 25, 2004 · Report post I was burning in my newly upgraded server last night and when I awoke my screen was filled with ext3 errors. EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297817600 EXT3-fs error (device http://forums.storagereview.com/index.php?/topic/14657-ext3-fs-error/ ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297821696 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297825792 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297829888 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297833984 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297838080 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297842176 *(each offset is increased by 4096 over the last) The anatomy of my server looks like the following: Onboard VIA 8233 IDE .hda = Fujitsu desktop10 (hda1=/, hda2=swap, hda3=/var) .hdb = empty .hdc = empty .hdd = empty Promise Ultra100 (PDC20267) .hde = empty .hdf = empty .hdg = empty .hdh = empty Promise Ultra133 (PDC20269) .hde = 160GB DM+9 .hdf = 160GB DM+9 .hdg = 160GB DM+9 .hdh = 160GB DM+9 each dm+9 has a single primary partition defined as type FD (linux RAID auto detect) and are RAIDed as device /dev/md0 as a four drive RAID 5 array. The array is mounted as /share. *If you're wondering why
Cisco Bug: CSCtr41546 - N5k flash is programmed for read only. Last Modified Oct https://quickview.cloudapps.cisco.com/quickview/bug/CSCtr41546 13, 2016 Product Cisco Nexus 5000 Series Switches Known Affected Releases 5.0(3)N1(1a) Description (partial) Symptom: Any n5k based platform can experience a issue where the inernal http://www.jimhermann.com/ensim/index9536.htm flash is programmed for read only. -Copy run start fails # copy running-config startup-config [########################################] 100% Jun 30 14:33:54 %KERN-2-SYSTEM_MSG: EXT3-fs error (device sda5): ext3_readdir: fs error directory #2 contains a hole at offset 0 - kernel Configuration update aborted: request was aborted Following messages will also be seen in the log May 6 16:47:36 %KERN-2-SYSTEM_MSG: Remounting filesystem read-only - kernel May 6 16:42:48 %KERN-3-SYSTEM_MSG: FAT: bogus number of reserved sectors - kernel May 6 16:42:50 %KERN-3-SYSTEM_MSG: FAT: ext3-fs error ext3_readdir bogus number of reserved sectors - kernel May 6 16:43:48 %KERN-3-SYSTEM_MSG: scsi0 (0:0): rejecting I/O to dead device - kernel May 6 16:43:48 %KERN-2-SYSTEM_MSG: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block-inode=1969, block=8197 - kernel Conditions: Internal compact flash hangs/is programmed for read only. View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials
disk in removable storage to use only for backup In this day the /backup not show the data in the disk and dmesg show me this: hdc: drive not ready for command ide1: reset timed-out, status=0x80 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 0 end_request: I/O error, dev 16:02 (hdc), sector 12472 journal_bmap_Rc6bd7979: journal block not found at offset 1360 on ide1(22,2) Aborting journal on device ide1(22,2). end_request: I/O error, dev 16:02 (hdc), sector 4176 end_request: I/O error, dev 16:02 (hdc), sector 48 end_request: I/O error, dev 16:02 (hdc), sector 4136 end_request: I/O error, dev 16:02 (hdc), sector 4136 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 0 ext3_abort called. EXT3-fs abort (device ide1(22,2)): ext3_journal_start: Detected aborted journal Remounting filesystem read-only end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4136 EXT3-fs error (device ide1(22,2)): ext3_readdir: directory #2 contains a hole at offset 0 end_request: I/O error, dev 16:02 (hdc), sector 4