similar to: EXT3 crash: ext3_free_blocks: bit already cleared

On a 2.4.15-pre5 system with a 3ware-Escalade-68000 IDE RAID (mode 1) we had the follwing "dmesg" output today: EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device sd(8,38)): ext3_free_blocks: bit already cleared for block 1052672 EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks not in datazone

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! 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 -

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,

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

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

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

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

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

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

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

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 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

Hi - We have had 3 rather major occurances of ext3 filesystem corruption lately, i.e. so bad we couldn't event mount, and fsck didn't help. I am looking for pointers, that could help us investigate the root cause. In general... We are running RedHat WS 3 Update 6, 2.4.21-40.2.ELsmp or 2.4.21-37.ELsmp We have a small SAN system that looks like this

[sorry if this isn't threaded right... I just subscribed] Theodore Ts'o wrote: > > There are two reasons for the reserve. One is to reserve space on the > partition containing /var and /etc for log files, etc. The other is > to avoid the performance degredation when the last 5-10% of the disk > space is used. (BSD actually reserves 10% by default.) Given that > the

Hi ! My system is RH7.2 with Adaptec/DPT/I2O drivers (http://people.redhat.com/tcallawa/dpt/). There is a 2 disk RAID 1 array which had no disk fail. Several partition on it: Filesystem Size Used Avail Use% Mounted on /dev/sda1 1.9G 435M 1.4G 24% / /dev/sda2 13G 3.2G 9.1G 26% /home none 504M 0 503M 0% /dev/shm At this time, all

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

On Apr 29, 2004 14:15 +0200, David Mart?nez Moreno wrote: > Hello all. I'm writing to all the people in charge of ext3 fs > > Apr 29 12:21:21 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone - block = 1071716394, count = 1 You need to run "e2fsck -f /dev/sda7" on the unmounted filesystem. There is some sort of corruption

Hello, I'm running a 2.4.20-8smp RH9 kernel and occassionally get the following error reported to syslog Sep 12 07:45:14 nfs0020 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: Freeing blocks not in datazone - block = 2251915074, count = 1 Sep 12 07:45:14 nfs0020 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: Freeing blocks not in datazone - block = 806949550,