Error Device Ide0
Contents |
ext3_readdir Date: Tue, 20 fortigate error 174 Nov 2001 20:02:39 +0100 Hi, yesterday I upgraded forticlient error my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and fortinet support had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device http://kb.fortinet.com/kb/documentLink.do?externalID=FD31857 ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have any of raid, acl or anything else, just a plain ide https://www.redhat.com/archives/ext3-users/2001-November/msg00379.html drive. So what should I do now ? Go to runlevel 1, umount /usr and run fsck ? Remounting rw doesn't work : root enterprise:/ #mount -o remount,rw /usr mount: block device /dev/hda9 is write-protected, mounting read-only and then in syslog: Nov 20 19:47:04 enterprise kernel: ext3_abort called. Nov 20 19:47:04 enterprise kernel: EXT3-fs abort (device ide0(3,9)): ext3_remount: Abort forced by user As I already said, the first time ever I had any problems since the very first versions. Thanks for your great work ! Cheers, Dirk Follow-Ups: Re: EXT3-fs error (device ide0(3,9)): ext3_readdir From: Andreas Dilger [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 19:34:12 GMT by s_ac5 (squid/3.5.20)
honeywell com> Subject. Help on ext3 file system corruption issue Date. Tue, 5 Jun 2007 22:01:00 +0530 I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. Call Trace: [