similar to: ext3 filesystem corruption

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

An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060828/ce9c7bc0/attachment.htm>

Hi folks -- My machine is a RHEL 3 with 2.4 kernel installed - with some large ext3 filesystems on drives connected internally ( >200G) Now, When this system crashed (for eg:- a CPU panic /hardware error ) - e2fsck on this filesystem seems to be taking a long time to return thereby adding to the overall downtime of this system. could there be any workarounds for my issue? say for

Hello, I was told that work had been done to use R with the CERN developed framework "ROOT" but can't find anything on your site. Please point me to whatever has been done. Sebastian White Sebastian White, Physics Deprtment Brookhaven National Laboratory Offiice: 631-344-5488 cell: 516-443-0039 email: swhite at bnl.gov Sebastian.White at cern.ch

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

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

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

One question that keeps coming up in my discussions about ZFS is the lack of user quotas. Typically this comes from people who have many tens of thousands (30,000 - 100,000) of users where they feel that having a file system per user will not be manageable. I would agree that today that is the case however I personally don''t see this as an insurmountable problem. However the questions

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

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

Hi, i export data from an csv file like this :  Data <- read.csv2("c:/Art.csv",sep=",") # import data into R > Data <- Data [1:5,1:5]# extracting the first 5 rows and columns > Data   Policy.Number AXA.Entity Country LoB ccy.data 1         6e+13        BNL     BNL   P      EUR 2         6e+13        USA     BNL   P      EUR 3         6e+13         UK     BNL  

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

Hi, Actually, i use the function merge like this: (Data1 <- Data1[1:7,1:3])   Policy.Number AXA.Entity Country 1    1060000077        BNL     BNL 2       4001023         CH     BNL 3    1060000006         UK     BNL 4       4001025         CH     BNL 5      6.00E+13        USA     BNL 6       6100001         UK     BNL 7       4001028        USA     BNL > Data2 <-

  Hi, i export data from an csv file like this :  Data <- read.csv2("c:/Art.csv",sep=",") # import data into R > Data <- Data [1:5,1:5]# extracting the first 5 rows and columns > Data   Policy.Number AXA.Entity Country LoB ccy.data 1         6e+13        BNL     BNL   P      EUR 2         6e+13        USA     BNL   P      EUR 3         6e+13         UK     BNL  

Hi, When trying to run a particular program, I reproducibly get a few dozen kernel messages of the form: attempt to access beyond end of device 03:06: rw=0, want=536995844, limit=11680168 attempt to access beyond end of device 03:06: rw=0, want=1342296068, limit=11680168

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

Dear list, pardon my ignorance on ext2/3fs. Is the ext2fs' 4Tb file system and 2GB maximum file size limit still true in ext3fs? Thanks for your reply, Gotze __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com

Hi all, Looks like I'm going to make the trip over to Astricon next month, but finances being what they are and since I'll be paying for my own flight from the UK, I'm trying to cut down on costs. The problem I've got is that the hotel is about 4 miles from the nearest public transportation (Brookhaven station) and the shuttle bus is only for hotel residents. Hiring a car seems

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