search for: ext3_free_block

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 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freeing blocks not in datazone - block = 1481734211, count = 1 Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freei...

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, count = 1 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1263356887, count = 1 EXT3-fs warning (device sd(8,49...

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 - block = 269488128, count = 1 EXT3-fs error (device sd(8,38)): ext3_fr...

...f, 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 server that is using ext3 filesystems. I started to get the following error: EXT3-fs error (device lvm(58,6)): ext3_free_blocks: bit already cleared for bloc k 290754 EXT3-fs error (device lvm(58,6)): ext3_free_blocks: bit already cleared for bloc k 289980 EXT3-fs error (device lvm(58,6)): ext3_free_blocks: bit already cleared for bloc k 289981 (Many more errors than this) And then I lost that NFS filesystem. The load w...

...cess beyond end of device Mar 22 10:48:35 trigger kernel: 03:03: rw=0, want=365461636, limit=13001688 Mar 22 10:48:35 trigger kernel: EXT3-fs error (device ide0(3,3)): ext3_free_branches: Read failure, inode=1447023, block=1701978144 Mar 22 10:48:35 trigger kernel: EXT3-fs error (device ide0(3,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 1179403647, count = 1 Mar 22 10:48:35 trigger kernel: EXT3-fs error (device ide0(3,3)): ext3_free_blocks: Freeing blocks in system zones - Block = 65793, count = 1 Mar 22 10:48:35 trigger kernel: EXT3-fs error (device ide0(3,3)): ext3_free_blocks: bit alre...

...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: EXT3-fs error (device ide0(3,2)): ext3_new_block Feb 22 08:06:41 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:07:11 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Feb 22 08:07:48 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zone...

...0013020 Call Trace: [<c011763e>] do_fork [kernel] 0x2ce (0xca5fdf6c)) [<c0107515>] sys_fork [kernel] 0x15 (0xca5fdfac)) [<c010893b>] system_call [kernel] 0x33 (0xca5fdfc0)) And now and then I see this messages (sometimes without any effects) EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing block in system zone - block = 2 fsck: contains a file system with errors, check forced. <2>EXT3-fs error (device ide0(3,5)): ext3_free_blocks: Freeing blocks not in datazone - block = 3471323520, count = 1 EXT3-fs error (device ide0(3,5)): ext3_free_blocks: Freeing blocks no...

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 at the 12% appears this message 3w-xxxx: scsi2: AE...

...00 27 13 22 c0 83 c4 0c 89 d8 2b 05 30 3e 2c c0 69 Dec 5 15:53:20 postamt1 authdaemond.mysql: authdaemon: modules="authcustom authcram authuserdb authmysql authpam", daemons=5 # This is where I restarted Courier! Dec 5 15:53:53 postamt1 kernel: <2>EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1094928743, count = 1 Dec 5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freeing blocks not in datazone - block = 1095059815, count = 1 Dec 5 15:53:53 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_free_blocks: Freei...

...d 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 - block = 381746234, count = 1 Can I ignore this error, or is this a warning that something is seriously broken? should i force a e2fsck after the next reboot for that drive? greetz michael Michael Renner - inode Internet Junior System Engineer

...ferent motherboards?) I've included below some of the debug output from the kernel below, there is a lot of it so I've only included the different types of errors reported (with times when the problems started) Thu 12/12/02 15:50:37.315 [KMSG:<2>EXT3-fs error (device ide0(3,10)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1] Fri 13/12/02 23:55:46.383 [KMSG:<4> <6>attempt to access beyond end of device] [KMSG:<6>16:05: rw=0, want=137058900, limit=39230698] [KMSG:<2>EXT3-fs error (device ide1(22,5)): ext3_free_branches: Read failure, in...

...w=0, want=1526984940, limit=12289725 Some of the files reportet an input/output-error while accessing them. after deleting the whole directory (which was very stupid, no chance for debugging at all) i got the following errors: Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)): ext3_free_blocks: Freeing blocks not in datazone - block = 1223964245, count = 1 Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)): ext3_free_blocks: Freeing blocks not in datazone - block = 59368495, count = 1 Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)): ext3_free_block...

...unning 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 datazone - block = 1634890784, count = 1 EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1667330926, count = 1 EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1852795252, count = 1 EXT3-fs err...

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, limit=976791680 attempt to access beyond end of device 09:00: rw=0, want=1930439616, limit=976791680 EXT3-fs error (device md(9,0)): ext3_free_blocks: Freeing blocks...

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 when this device (/dev/md4, a MD RAID-1 array) ran out of space, so it may well...

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

...09:50 deleted the bigfile (this took a LONG time) 10:04 pulled a drive on the raid array (hardware raid5) 10:12 errors started appearing in the logs, and the filesystem remounted itself read-only Here are some sample errors: Feb 16 10:12:05 hera kernel: EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 1027000215, count = 1 Feb 16 10:12:05 hera kernel: Aborting journal on device sdb1. Feb 16 10:12:05 hera kernel: EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in datazone - block = 3696983906, count = 1 Feb 16 10:12:05 hera kernel: EXT3...

...ail 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 seems to be ok. But there was in /etc/log/message Aug 13 10:55:40 web kernel: EXT3-fs error (device sd(8,1)): ext3_free_blocks: Freeing blocks not in datazone - block = 439612, count = 1 Aug 13 10:55:41 web syslogd: /var/log/maillog: No space left on device Aug 13 10:55:40 web kernel: EXT3-fs error (device sd(8,1)): ext3_free_blocks: Freeing blocks not in datazone - block = 439611, count = 1 Aug 13 10:55:41 web kernel: EX...

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 there. > Apr 23 20:35:41 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone...