similar to: EXT3-fs error (device md(9,1)) in ext3_new_inode: error 28

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

I'm constructing a raid 5 of 3 160gb sata drives. They're connected to a promise sx4 150 card, using the kernel drives (not promise's binary only drivers). the raid builds fine, as does creation of the ext3 filesystem. however, if i then run e2fsck (with the -f option since the filesystem is brand new) i get thousands of these type of errors: Inode 15461 has imagic flag set.

Hello, i posted a question about a possible ext3fs bug a few month ago. I see this kernel-msg in the messages: Oct 8 18:30:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:35:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:40:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 they repead

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

Hi, I would appreciate if somebody could help me with this small issue... I have a dataframe like this (originaly has more than 100 000 rows): > subz jul time dtime fix ddawn ddusk day 101608 15006 2011-02-01 19:14:49 19.24694 noon 7.916667 19.88333 1 101609 15006 2011-02-01 19:24:49 19.41361 midnight 7.916667 19.56667 1 101610 15006 2011-02-01

Dear All, I have a pair of .cpp and .def file can be compiled using VC++ and works perfectly well in S-PLUS. I wanted to do the same for R; so I followed the guidline given in "Building from a source-code library under Windows" as much as possible and manage to compile them using VC++ and call it from R. But it gives different answer from the one called from S-Plus. I know that I did

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Is there a reason why an ext3 root partition cannot be copied to an alternate partition using the "dd" command? The dd is copying the mounted root partition into an alternate partition that is not mounted. The dd returns success, but the fsck on that partition fails with errors as follows: ----------------- fsck 1.37 (21-Mar-2005) /dev/Active_Update/root2: recovering journal

hello: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

Greetings, useRs. Does anybody have replication of the examples from the RMS book by Harrell coded in R? I find that most the code does not work and it takes too much time to debug. For example from p.276 > age.t <- w[,"age"] > f.full <- lrm(cvd~scored(rx)+rcs(dtime,5)+age.t+wt.t+pf.t+hx+sbp+ekg.t+sz.t+sg.t+ap.t+bm+hg.t,x=T,y=T) Error in model.frame.default(formula = cvd ~

Hello, last fsck says my /tmp and my /home files system has errors, here is the log from fsck using the read-only option: How to recover from this savely? How to avoid this in future? i am using kernel 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail.

Hi All, > act_2 Date Dtime Hour Min Second Rep 51 2006-02-22 14:52:18 14 52 18 useractivity_act 52 2006-02-22 14:52:18 14 52 18 4 55 2006-02-22 14:52:49 14 52 49 4 57 2006-02-22 14:52:51 14 52 51 4 58 2006-02-22 14:52:52 14 52 52 3 60 2006-02-22 14:54:42 14 54

Hi, The attached patch is an update to the latest klibc (I just checked a few bits into CVS) which adds support for initramfs. Since it contains bits that aren't available yet on the main site, I've also put a tarball up which contains only what's in the latest CVS. The initramfs stuff is what I use here to boot one of my machines; it works for me, but probably won't work

About two weeks ago i was whining about an inode that got lost, now i'm going to whine more about strange things happening here. A matroxfb just oopsed on me (thats not strange), the machine got unusuable, so i logged in from another and got the idea to touch /forcefsck. Upon reboot, fsck said that some inodes are in use but have dtime set and that some files are illegal sockets. Now this

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

Hi, (I'm not subscribed to ext3-users, please CC: me) Kernel: 2.4.18. I've just converted a 100(ish) MiB ext2 filesystem to ext3 (umount, tune2fs -j, e2fsck, mount) and it seems to be happy, except... As a test, I then filled the filesystem up, lastly copying /usr/bin (as root, so the filesystem became brim full). I then umounted it, and ran e2fsck -n -f /dev/hda6, and got the