ext2fs problems with innd

ext2fs problems with innd

Post by Robert Ade » Sun, 12 Apr 1998 04:00:00



Hi!
I have a problem with my innd (version 1.7) server. I keep getting
errors on my
spool partition which is a 6.4gb IDE harddrive.
I have tried to change harddrive but this didn't help.
I'm running kernel 2.0.33 and Redhat 5.0.
The problem I'm getting is as follows from /var/log/messages:

Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
ext2_find_entry: directory #387105 contains a hole at offset 1024
Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
ext2_find_entry: directory #387105 contains a hole at offset 2048
Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
ext2_find_entry: directory #387105 contains a hole at offset 3072
Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
ext2_find_entry: directory #387105 contains a hole at offset 4096
Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
ext2_find_entry: directory #387105 contains a hole at offset 5120
Apr 11 01:02:47 server2 kernel: EXT2-fs error (device 16:41):
ext2_free_blocks: Freeing blocks not in datazone - block = 67108864,
count = 1

---

Is this some kind of problem with the ext2fs filesystem when it contains
a lot of files?
If so, is there anything you can do to prevent it?
Any help appreciated!

 
 
 

ext2fs problems with innd

Post by Mike O'Conno » Mon, 13 Apr 1998 04:00:00




:Hi!
:I have a problem with my innd (version 1.7) server. I keep getting
:errors on my
:spool partition which is a 6.4gb IDE harddrive.
:I have tried to change harddrive but this didn't help.
:I'm running kernel 2.0.33 and Redhat 5.0.
:The problem I'm getting is as follows from /var/log/messages:
:
:Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
:ext2_find_entry: directory #387105 contains a hole at offset 1024
:Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
:ext2_find_entry: directory #387105 contains a hole at offset 2048
:Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
:ext2_find_entry: directory #387105 contains a hole at offset 3072
:Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
:ext2_find_entry: directory #387105 contains a hole at offset 4096
:Apr 10 02:02:56 server2 kernel: EXT2-fs error (device 16:41):
:ext2_find_entry: directory #387105 contains a hole at offset 5120
:Apr 11 01:02:47 server2 kernel: EXT2-fs error (device 16:41):
:ext2_free_blocks: Freeing blocks not in datazone - block = 67108864,
:count = 1
:
:---
:
:Is this some kind of problem with the ext2fs filesystem when it contains
:a lot of files?
:If so, is there anything you can do to prevent it?

It could be a disk controller, controller driver, or possibly an
e2fsck version issue.  This is probably a disk read issue.  In my
experience with running Linux news servers, I haven't seen those
messages when fsck-ing a Linux disk simply because it had a lot of
files in it, but Usenet news can stress I/O subsystems and tickle
bugs that normally don't show up with lesser loads.

--

 InterNIC WHOIS: MJO | (has my PGP & Geek Code info) | Phone: +1 248-848-4481

 
 
 

1. Reserved blocks on ext2fs (was ext2fs broken)


Could some please explain this further?

I probably have the false belif that only the root (/) filesystem needs
some reserved blocks for root.  Recently, when I resize both /home and
/var filesystems, I re-created them with 0% reserved for root.  Ooops!

Lin
--

School of Computer Science and Software Engineering
Monash Univeristy, Clayton, Vic. 3168, Australia

2. Two Questions on Motif for Solaris 2.3

3. ext2fs: ext2fs filesystem not available

4. Free Raima Clone

5. innd problem!

6. Books wanted - Toronto area

7. Newbie - innd problem

8. PPP Freeze Problem - Months

9. Rn/INND problem

10. Problem building innd under Solaris 2.5.1: ../libinn.a: unknown type

11. Newbie - innd problem...

12. HELP: problems with INND

13. 2.3's INND and 2.4 problem?