similar to: ext3_free_blocks

Since I ain't got a better place to report this, I do it here: Kernel 2.4.20-ac1 # uptime 16:31:00 up 2 days, 22:10, 7 users, load average: 1.89, 2.20, 2.99 This is our main mailbox server. We're running ext3: # cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 /dev/sdb5 /boot ext3 rw 0 0 /dev/sda6 /home ext3 rw,noatime,nosuid 0 0 /dev/sdb8 /tmp

Which disk is it? /dev/sda6 or /dev/sdb8 or /dev/sdc6? >From my log: Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548 Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616 $ mount /dev/sdb6 on / type auto (rw)

I had a failure over the weekend of my ext3 filesystems. Hardware: Dell 2550 (dual PIII 1 Ghz, 1GB ram, Acenic GigE card) Software: linux-2.4.14 ext3-2.4-0.9.15-2414 Trond's NFS patches (pathconf, tune,read,rpc_blk) The filesystem is RAID0 using LVM (1.0.1-rc4). The disks are connected using fiber channel (qlogic 2200, qlax00-4.27beta). I was generating high load on my nfs

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

Hi all, after an uprade to new kernel 2.4.21-15.0.4.EL on my server appears a lot of these messages: EXT3-fs error (device sd(8,17)): ext3_free_blocks: bit already cleared for block 19268224 EXT3-fs error (device sd(8,17)): ext3_free_blocks: bit already cleared for block 19268225 EXT3-fs error (device sd(8,17)): ext3_free_blocks: bit already cleared for block 19268226 I try to rebuild array but

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752

I'm using the doveadm import command to extract mails from my backup: % doveadm import -u restore at backup.invalid mdbox:/home/copymail/mdbox "" \ mailbox INBOX header Delivered-To backup+$SEARCHPATTERN at backup.invalid This works like a charm, I'm getting all the mails, and I can access the newly generated mailbox. But when executing the command I'm getting an

hi! I'm using ext3 for a few weeks by now, and i'm quite satisfied, especially in combination with the new quota code in the ac kernels... i never had any fs-errors till now... i upgraded to 2.4.9-ac12 (w/o any additional patches, runs ext3fs 2.4-0.9.6) yesterday, and today i got this errormessage... EXT3-fs error (device ide1(22,66)): ext3_free_blocks: Freeing blocks not in datazone -

Hi, I had enabled an option in dovecot. mail_attachment_dir = /var/mail/virtual/copymail/attachments After a while I checked /var/mail/virtual and did some cleanup. I did not remember that copymail was specified in dovecot and erased it. Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error:

My users say that "greetings of the day" occurs in academic spam a lot. Since I don't trust my users, I opted to verify this bold claim. But how do I search for a sequence of multiple words? doveadm import -u restore at backup.invalid mdbox:/home/copymail/mdbox "" mailbox INBOX BODY "Greetings of the day" doveadm import -u restore at backup.invalid

These came up on dmesg this morning: attempt to access beyond end of device 09:00: rw=0, want=1635237736, limit=976791680 attempt to access beyond end of device 09:00: rw=0, want=1635237736, limit=976791680 EXT3-fs error (device md(9,0)): ext3_free_blocks: Freeing blocks not in datazone - block = 4293394431, count = 1 attempt to access beyond end of device 09:00: rw=0, want=1930439616,

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

A brand new system setup with RH 7.3 is still Oopsing after every X hours. The problem started after about 1 week without errors. Sometimes everything is locked, sometimes still messages are written to /var/log/messages. Sometimes other processes keep running (can still ping the machine) I upgraded the kernel to 2.4.18-19.7.x, changed the memory, but still got problems. When I read all sort of

A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in

hiya! i'm currently running 2.4.12-ac1 w/o any further ext3 patches. i've got a dir with some fairly big files (like 15mb/file) in it and while sfv-checking these i got the following errors: Oct 14 21:47:59 srck@trottelkunde attempt to access beyond end of device Oct 14 21:47:59 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725 Oct 14 21:47:59 srck@trottelkunde attempt to

For archiving purposes I'm delivering all addresses to the same mdbox: like this: passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } userdb { driver = static args = uid=1000 gid=1000 home=/home/copymail allow_all_users=yes } Yet I'm getting this: Jan 3 19:03:27 mail postfix/lmtp[29378]: 3THjg02wfWzFvmL: to=<firstname.lastname at

Hi, I just noticed that my file server running 2.4.18-pre3 + IDE patches & NTFS patches has this error message in the logs: EXT3-fs error (device md(9,4)): ext3_free_blocks: Freeing blocks not in datazone - block = 33554432, count = 1 This is the only ext3 error I have seen and the uptime is currently over 74 days. The error actually appeared two weeks ago. The timing coincides well with

every one,I meet a problem: I used reahat9.0(kernel 2.4.20-8smp,I installed a SCSI RAID Card),and there are always some problems and them the system is dead. is anyone can help me about it? Thanks Crist Below is the error log: Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freeing blocks not in datazone - block = 1382828372, count = 1 Jun 11 22:19:03 mail1

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose